Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-34830

Clarification of Use Case (Create)

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • US PACIO Advance Directive Interoperability (FHIR)
    • 0.1.0
    • Patient Empowerment
    • STU
    • PADI CapabilityStatement [deprecated]
    • Patient Stories and Personas
    • Hide

      Include an example of data exchange, and also add a statement that this IG makes no comment as to how EHRs should be architected, as this is beyond the scope of a FHIR implementation guide.

      Show
      Include an example of data exchange, and also add a statement that this IG makes no comment as to how EHRs should be architected, as this is beyond the scope of a FHIR implementation guide.
    • Dave Hill / Kim Herman : 6-0-1
    • Clarification
    • Non-substantive

    Description

      Sufficiently capable enterprise EHRs will be in the position of content creator (patient uses "commercially available product" to create a digital set of advanced directives) OR content receiver (patient send content to EHR, HIE, etc).   Example:  patient has advanced directive information on file at Healthcare organization A directly inside the EHR as either scanned documents or in the future, e-signed digital content as allowable by state regulations.  patient is on vacation and ends up in ED of Healthcare organization B and allows sharing of content, in which case EHR of organization B consumes the content.    Or patient has advanced directive on file EMR A and EMR A shares information with a state repository, etc..  

      Attachments

        Activity

          People

            may_terry May Terry
            kherman Kimberly Herman
            David Hill, Kimberly Herman, Michael Brodsky (Inactive)
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: