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

Is it correct to not mandate the transaction interaction in 5.3.1 and 5.4.1?

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DEQM (FHIR)
    • 0.1 [deprecated]
    • Clinical Quality Information
    • (NA)
      (many)
    • 5.3.1 and 5.4.1
    • Hide

      For the Receiver Server CapabilityStatement and Reporter Client CapabilityStatement change the conformance expectations for transactions from MAY to SHALL

      Show
      For the Receiver Server CapabilityStatement and Reporter Client CapabilityStatement change the conformance expectations for transactions from MAY to SHALL
    • Bryn Rhodes/Floyd Eisenberg: 25-0-0
    • Correction
    • Non-compatible

    Description

      The Capability Statements for Receiver and Reporter specify that the system" MAY support the transaction interaction." . However they must support the DEQM Individual Reporting Profile. And Section 2.3.1 of this IG seems to establish that the reporting is done with that transaction ("The Individual MeasureReport(s) and all the referenced resources are bundled together as a set of POST interactions and sent as a single transaction interaction using the Standard FHIR API."). Isn't this a contradiction?

      Attachments

        Activity

          People

            Unassigned Unassigned
            javier_espina Javier Espina
            Javier Espina
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: