2015May core #824 - ConsentDirective as a profile

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Low
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Community-Based Care and Privacy
    • (profiles)
    • 5.7.9
    • Hide

      Persuasive - We now have Consent as a Resource

      Show
      Persuasive - We now have Consent as a Resource
    • Kathleen Connor/John Moehrke: 4-0-0
    • Correction
    • Non-substantive
    • Yes
    • DSTU1 [deprecated]

      Comment:

      Consent should be it's own resource, focusing on consent. If there's a contract about the consent, it should be a separate resource that refers to the consent. Making it a profile on contract doesn't seem to offer enough to justify the abstraction it imposes on the model

            Assignee:
            Unassigned
            Reporter:
            Grahame Grieve (Inactive)
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: