Why aren't we using the standard endpoints for interacting with FHIR Documents? - PCDE #101

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • US Da Vinci PCDE (FHIR)
    • STU3
    • Financial Mgmt
    • (profiles) [deprecated]
    • Hide

      The interaction here is that we want the target system to create a document "now" unless they determine that a document they already have is sufficiently complete/up-to-date. Thus we can't use a "query" mechanism. As well, (for now at least), this isn't a document that can just be automatically assembled from existing data without human intervention. As such the document generation operation isn't appropriate. The CDex mechanism of soliciting the creation of a document seems to be the appropriate course.

      Show
      The interaction here is that we want the target system to create a document "now" unless they determine that a document they already have is sufficiently complete/up-to-date. Thus we can't use a "query" mechanism. As well, (for now at least), this isn't a document that can just be automatically assembled from existing data without human intervention. As such the document generation operation isn't appropriate. The CDex mechanism of soliciting the creation of a document seems to be the appropriate course.
    • Mark Scrimshire / Mary Kay McDaniel: 17-0-2

      Comment:

      This justification for a document-based approach is refreshing and convincing. Why aren't we using the standard endpoints for interacting with FHIR Documents (https://www.hl7.org/fhir/documents.html#bundle). This IG should abandon the use of CommunicationRequest/Communication in favor of more standard and reasonable approaches.

      Summary:

      Why aren't we using the standard endpoints for interacting with FHIR Documents?

            Assignee:
            Unassigned
            Reporter:
            Isaac Vetter
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: