Consent does not have a clean Workflow report

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Community-Based Care and Privacy
    • Consent
    • Hide

      change scope to Event.class

      Change category to Event.code

      There is no Event element to have "when recorded" for Datetime to be aligned with.

      Event.context is not relevant and should be added to the override

      Event.note is not relevant and should be added to the override due to the Consent.verification has the basis for what would be annotated. Ask Lloyd

      Event.partof is not relevant and should be added to the override

      Remove Event.Performer from consent.organization

      Consent.ConsentingParty becomes consent.Performer with a function including grantor, grantee, etc.

      Move Consent.Status to Event status valuset

      Consent.statusReason is not needed and should be added to the override

      Move consent.patient to consent.subject

      Consent.subject(formerly patient) should be 1..1 unless a specific usecase is presented. Should be added to override.

      Show
      change scope to Event.class Change category to Event.code There is no Event element to have "when recorded" for Datetime to be aligned with. Event.context is not relevant and should be added to the override Event.note is not relevant and should be added to the override due to the Consent.verification has the basis for what would be annotated. Ask Lloyd Event.partof is not relevant and should be added to the override Remove Event.Performer from consent.organization Consent.ConsentingParty becomes consent.Performer with a function including grantor, grantee, etc. Move Consent.Status to Event status valuset Consent.statusReason is not needed and should be added to the override Move consent.patient to consent.subject Consent.subject(formerly patient) should be 1..1 unless a specific usecase is presented. Should be added to override.
    • John Moehrke/Kathleen Connor: 17-0-2
    • Enhancement
    • Non-compatible
    • STU3

      The workflow project has put together a report identifying places where resources don't align with patterns, as well as a mechanism for work groups to mark as "ignored" if they don't feel alignment is appropriate/necessary. Consent is still showing up on the report - meaning that an alignment review has not been completed (or there are issues with the suppression process - in which case please let me know). Alignment is most critical for normative resources, but should be completed for all resources that are FMM3 or higher (and should be considered for resources with lower FMM levels)

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: