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

Device in MessageHeader

XMLWordPrintableJSON

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • US Da Vinci Alerts (FHIR)
    • 0.2.0 [deprecated]
    • Infrastructure & Messaging
    • (many)
    • 2.1.3.1
    • Hide

      Once INM WG decision to add in FHIR R5 will create a cross-version extensions for adding to the MessageHeader Profile.

      Show
      Once INM WG decision to add in FHIR R5 will create a cross-version extensions for adding to the MessageHeader Profile.
    • Tony Julian / Nick Radov: 2-0-0
    • Enhancement
    • Compatible, substantive

      Should we allow a Device to be a sender, responsible, or author? In some automated systems there may be no human provider involved in certain Notifications.

      Existing Wording:

      Each Bundle must support:
      1.US Core Organization, Practitioner, or PractionerRole referenced by MessageHeader.sender
      2.US Core Organization, Practitioner, or PractionerRole referenced by MessageHeader.responsible
      3.US Core Practitioner, or PractionerRole referenced by MessageHeader.author

            Unassigned Unassigned
            nradov Nick Radov
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: