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

Add OperationalContext data element to DeviceAssociation

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R6
    • Orders & Observations
    • DeviceAssociation
    • (NA)
    • 8.16

    Description

      In working through the SDC/SDPi (Gemini) device operational contexts, it was recognized that this has never been a topic within the DoF work.  How do we represent device-to-device associations.  

      This topic is of immense importance within the SDPi D2D Plug-and-Trust ecosystem and if that is represented in FHIR we should have a clear way to represent those relationships.  This includes Patient Context, Location Context, Ensemble Context, and Workflow Context.  

      One proposal would be to add an "OperationalContext" data element to the DeviceAssociation resource.  This could be 0..* and would then enable these relationships to be properly modeled.  

      Note:  There is a bi-directional aspect to this subject area:  Information such as Patient and Workflow contexts will most likely come from a FHIR-based sources; whereas, information related to D2D Location and Ensemble associations (e.g., for external control) would come from the SDC ecosystem.  And of course, both can operate independently!  But keeping coherence is important.  

      Attachments

        Activity

          People

            Unassigned Unassigned
            todd.cooper Todd Cooper
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: