ConsentDirective vs Contract

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Low
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Community-Based Care and Privacy
    • Contract
    • 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]

      Although I understand the desire to combine ConsentDirective and Contract into one Resource; I don't think that it meets the desired goal of FHIR of simplicity and implemtable. I recommend that ConsentDirective be promoted to a Resource. It can continue to look much like Contract, looking like other resources is comment in FHIR.

      I have found in discussions that people are expecting ConsentDirective to be a resource, and find it hard to find it within Contract. They do not understand why they should see this as obvious.

      I have found in discussions with people that they have negative impressions of a Consent Directive when it is put into terms of a Contract. Even though they will admit that it really is a form of contract.

            Assignee:
            Unassigned
            Reporter:
            John Moehrke
            John Moehrke
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: