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

Provenance.agent.who choices

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • STU3
    • Security
    • Provenance
    • Hide

      no change seems warranted.

      The use-case has only a device type, which can be described in a contained Device, where the Device resource is minimally populated. This is normal use of minimally populated resources, and containment; and therefore does not warrant description on the Provenance page. (It could be described in the v2->FHIR IG).

      Show
      no change seems warranted. The use-case has only a device type, which can be described in a contained Device, where the Device resource is minimally populated. This is normal use of minimally populated resources, and containment; and therefore does not warrant description on the Provenance page. (It could be described in the v2->FHIR IG).
    • Peter van Liesdonk/Kathleen Connor: 5-0-0
    • Enhancement

    Description

      When reviewing the v2-to-FHIR mapping fo ORC-18 Entering Device, the v2 specification would imply that the device referenced is a DeviceDefinition as ORC-18 is a CWE. Clearly, in reality identifier information of an actual device may have been included, but that was not the intent. Provenance.agent.who has Device as a choice, but not DeviceDefinition. We suggest that DeviceDefinition should be added given v2's intent, but then still enable situations where the transformer knows for use it actually references an actual Device, that still could be used instead.

      Attachments

        Activity

          People

            Unassigned Unassigned
            hbuitendijk Hans Buitendijk
            Hans Buitendijk
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: