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

Device subject Jiras stomped on each other

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Orders & Observations
    • STU
    • Device
    • Hide

      Link to FHIR-38904 disposition

      Show
      Link to FHIR-38904 disposition
    • Marti Velezis / Elliot Silver : 8-0-2
    • Enhancement
    • Non-compatible
    • R5

    Description

      There are a few Jiras that got mixed up:

      https://jira.hl7.org/browse/FHIR-30243 - This requested new reference types for Device.subject (with a use case)

      https://jira.hl7.org/browse/FHIR-34135 - this removed Person.  We proposed adding Person in FHIR-30243, and that was accepted.  However I agree that we should have made that RelatedPerson, not Person.

      https://jira.hl7.org/browse/FHIR-32570 - as part of the move from subject to association, this removed Practitioner as a reference type, claiming that there was no use case for it. 

       

      To resolve these, I'd propose these updates:

      1. Update Device.association.humanSubject to add back in Practitioner.  Also add in RelatedPerson (instead of Person) to allow associating devices (like RLTS tags) to (for example) parents or other caregivers accompanying patients in the hospital.
      2. Either update humanSubject to be just subject, and expand the reference type to include Device.  Or add a sibling property (nonHumanSubject) for devices associated to non-humans.  This allows an RTLS device to be associated with a medical device (for example, and infusion pump.  Device(RTLS Tag)-> Device (Infusion Pump).

       

      My strong preference for #2 is to just make it Device.association.subject so you can associate to any type of subject.

      Attachments

        Activity

          People

            Unassigned Unassigned
            cooper.thompson Cooper Thompson
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: