Consent shouldn't be a sub-type of Contract

XMLWordPrintableJSON

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

      Persuasive – continue work on Consent Resource

      Show
      Persuasive – continue work on Consent Resource
    • Kathleen Connor/John Moehrke: 4-0-0
    • Enhancement
    • Non-substantive
    • Yes
    • DSTU1 [deprecated]

      Resources need to reflect how data is used in real systems. I'm not aware of any systems that would reasonably mix patient directives information with insurance policies or other contracts. The commonality of data elements or logical modeling is not a primary consideration in whether distinct resources should be used. No implementer would reasonably be expected to look under Contract for patient directives and many of the data elements are totally inappropriate.

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

              Created:
              Updated:
              Resolved: