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

pave the cowpath, don't only create aspirational IGs

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: High High
    • US PACIO Advance Directive Interoperability (FHIR)
    • 0.1.0
    • Patient Empowerment
    • STU
    • PACIO ADI Document Reference [deprecated]
    • Hide

      We'll update the PACIO ADI IG to ensure that the exchange of scanned documents, as represented by the current state of interoperability complies with the IG, while also enabling/encouraging implementers to begin collecting and transmitting these data elements discretely.

      We also tested the exchange of scanned documents using the IG during the connectathon and will add more specific guidance to the IG.

      Show
      We'll update the PACIO ADI IG to ensure that the exchange of scanned documents, as represented by the current state of interoperability complies with the IG, while also enabling/encouraging implementers to begin collecting and transmitting these data elements discretely. We also tested the exchange of scanned documents using the IG during the connectathon and will add more specific guidance to the IG.
    • Dave Hill / Virginia Lorenzi : 7-0-0
    • Clarification
    • Compatible, substantive

    Description

      The current state of interoperability of advanced directive information is almost entirely the exchanged of scanned paper documents. The PACIO-IG specification says:

       

      > Advance directive documents may take several forms including scanned PDF documents, CDA documents and native FHIR documents. This guide defines interoperability to support any number of types, though focuses on native FHIR documents.

       

      The approach being taken in this specification, as noted, is to focus on creating, net-new, discrete, and complex "native FHIR documents". Defining this aspirational, perfect state is entirely worthwhile; however, it is definitely not the current state, and due to the size and complexity of the currently being defined native FHIR documents is not even near-term nor mid-term. For example, your notary and witness sections seem to even aspire to replace current state-level legislation requiring "wet" signatures. We fear that by only specifying the perfect end-state, you will damage the industry's movement towards interoperable exchange of ADI information as it currently exists in the real world.

       

      You should split off the specific exchange of "scanned PDF documents" and/or "CDA documents" and define as absolutely simple exchange of a DocRef and Binary, and then also continue your aspirational, perfect-world, discrete ADI exchange.

      Attachments

        Activity

          People

            may_terry May Terry
            mbrodsky Michael Brodsky (Inactive)
            Kimberly Herman, Michael Brodsky (Inactive)
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: