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

Address non-implantable device and how to document usage

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Not Persuasive with Modification
    • US Core (FHIR)
    • 3.1.0
    • Cross-Group Projects
    • Profiles and Extensions
    • 3.29.1
    • Hide

      Re 1) US Core Implantable Device profile  use case is constrained to implantable Devices to allow for a USCDI API.  Other devices (such as software) may use the base resource or an implementation specific profile.  

      Re 1 and 2 Need to see the successful implementation experience before considering adding a general Device Profile to US Core.

      Use base resource and add guidance and request for feedback on the US Core futures page.

      Show
      Re 1) US Core Implantable Device profile  use case is constrained to implantable Devices to allow for a USCDI API.  Other devices (such as software) may use the base resource or an implementation specific profile.   Re 1 and 2 Need to see the successful implementation experience before considering adding a general Device Profile to US Core. Use base resource and add guidance and request for feedback on the US Core futures page.
    • Eric Haas/Brett Marquard:7-0-0
    • Clarification
    • Non-substantive

    Description

      Two points:

      1) US Core only enables an implantable device and needs to also allow reference to a non-implantable device (specifically DME but also to address software as a device). FHIR Device resource allows both.

      2) US Core should provide guidance about how to reference placement, ordering and/or use of a device in a consistent manner: Suggested options to provide greater clarity for expressing device placement or usage include:

      • Procedure for
      • placement/insertion of a device, or
      • use/manipulation of a device for which the result attribute can reference the expected outcome of such use.
      • Observation allows reference to an observation about device usage, stability, and presence.
      • Condition allows reference to the existence of an implantable device on a problem list.
      • DeviceRequest  enables reference to an order for the device with the requester attribute indicating the source of the order information (e.g., requester is practitioner if ordered by the physician; the requester is patient / Care Partner if the patient or caregiver reports the device is in use, i.e., not initiated by a clinician order for durable medical equipment) - I.e., parallel to how an active medication list is managed in US Core.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              feisenberg Floyd Eisenberg
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: