This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Device FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
 
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
−
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents an [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
−
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  
Line 13: Line 12:
  
  
−
=putProposedResourceNameHere=
+
=Device=
−
 
 
−
<!-- Resource names should meet the following characteristics:
 
−
* Lower camel case
 
−
* U.S. English
 
−
* Domain-friendly
 
−
* Short
 
−
* Clear
 
−
* Unique
 
−
* Avoid non-universal abbreviations (e.g. URL would be ok)
 
−
* Be expressed as a noun
 
−
* Be consistent with other similar resources
 
−
-->
 
  
 
==Owning committee name==
 
==Owning committee name==
  
−
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
+
[[Orders & Observations WG]]
−
[[YourCommitteeName]]
 
  
 
==Interested Work Groups==
 
==Interested Work Groups==
  
−
<!-- Additional work groups that may have an interest in assisting with the content of the resource (optional) -->
+
* Laboratory (and Lab Automation)
−
* Work Group Name
+
* Anatomic Pathology
−
* or link
+
* Clinical Genomics
−
* or "None"
+
* Imaging Integration
 +
* Pharmacy
 +
* Public Health and Emergency Response
 +
* Devices
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
  
−
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
+
952
  
 
==Scope of coverage==
 
==Scope of coverage==
Line 55: Line 44:
 
As a rule, resources should encompass all of these aspects.
 
As a rule, resources should encompass all of these aspects.
 
  -->
 
  -->
 +
 +
DEFINITION (DEVICES):
 +
This resource identifies an instance of a manufactured thing that is used in the provision of healthcare without being substantially changed through that activity. The device may be a machine, an insert, a computer, an application, etc.  This includes durable (reusable) medical equipment as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health.
 +
 +
Primarily used for recording which device performed an action and can also be used to track device location.  Can also be used for prescribing and dispensing devices for patient use.
 +
 +
A device with multiple components which, in a particular use case, may need to be to be separately identified or manipulated, may be represented as a composition of component Device resources with links from the component to a parent device.
  
 
==RIM scope==
 
==RIM scope==
  
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
 +
 +
*Entity: ManufacturedMaterial (Enity.classCode="MMAT")
 +
*Entity: Devices (Entity.code=DeviceGenericType)
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 74: Line 73:
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
  -->
 
  -->
 +
Devices are used throughout healthcare for the precise (and imprecise) measurements related to diagnostics and treatments, to deliver therapeutic drugs and other forms of treatment, for use in surgical procedures, and used throughout research scenarios.  As such, a device resource is required for the information components.
  
 
==Expected implementations==
 
==Expected implementations==
  
 
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource.  (Should ideally have multiple independent implementations) -->
 
<!-- For resources not deemed "key", what interest is there by implementers in using this particular resource.  (Should ideally have multiple independent implementations) -->
 +
Needed as part of CCDA
  
 
==Content sources==
 
==Content sources==
Line 84: Line 85:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
 +
*HL7 v3 Laboratory Standard - Normative
 +
*HL7 v3 Implantable Devices Standard - Normative
 +
*HL7 v2.x (including SFT segment)
 +
 +
==Example Scenarios==
 +
 +
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
  
 
==Resource Relationships==
 
==Resource Relationships==
Line 95: Line 104:
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
  -->
 
  -->
 +
*Order
 +
*DiagnosticOrder
 +
*DiagnosticReport
 +
*Procedure
 +
*ImagingStudy (future)
 +
*Specimen
 +
*Location
 +
*Medication
 +
*Product
  
 
==Timelines==
 
==Timelines==
  
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 +
 +
*Proposal Approved by WG: Aug 2013, then updated and re-approved May 2013 at WGM
 +
*Planned Ballot: September 2013
  
 
==gForge Users==
 
==gForge Users==
  
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
 +
*Lorraine Constable
 +
*Patrick Loyd
 +
 +
==Issues==
 +
* What's the determinerCode?  instance, kind or don't care?  If not fixed, is there a way to infer it?
 +
* Need example scenarios
 +
* Look at NCPDP and OpenEHR as possible sources for device as well (not sure if they have coverage or not)
 +
* Need to explain the types of relationships to the listed resources

Latest revision as of 14:39, 24 June 2019

OpenHotTopic.GIF

This page documents an Approved FHIR Resource Proposal



Device

Owning committee name

Orders & Observations WG

Interested Work Groups

  • Laboratory (and Lab Automation)
  • Anatomic Pathology
  • Clinical Genomics
  • Imaging Integration
  • Pharmacy
  • Public Health and Emergency Response
  • Devices

FHIR Resource Development Project Insight ID

952

Scope of coverage

DEFINITION (DEVICES): This resource identifies an instance of a manufactured thing that is used in the provision of healthcare without being substantially changed through that activity. The device may be a machine, an insert, a computer, an application, etc. This includes durable (reusable) medical equipment as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health.

Primarily used for recording which device performed an action and can also be used to track device location. Can also be used for prescribing and dispensing devices for patient use.

A device with multiple components which, in a particular use case, may need to be to be separately identified or manipulated, may be represented as a composition of component Device resources with links from the component to a parent device.

RIM scope

  • Entity: ManufacturedMaterial (Enity.classCode="MMAT")
  • Entity: Devices (Entity.code=DeviceGenericType)

Resource appropriateness

Devices are used throughout healthcare for the precise (and imprecise) measurements related to diagnostics and treatments, to deliver therapeutic drugs and other forms of treatment, for use in surgical procedures, and used throughout research scenarios. As such, a device resource is required for the information components.

Expected implementations

Needed as part of CCDA

Content sources

  • HL7 v3 Laboratory Standard - Normative
  • HL7 v3 Implantable Devices Standard - Normative
  • HL7 v2.x (including SFT segment)

Example Scenarios

Resource Relationships

  • Order
  • DiagnosticOrder
  • DiagnosticReport
  • Procedure
  • ImagingStudy (future)
  • Specimen
  • Location
  • Medication
  • Product

Timelines

  • Proposal Approved by WG: Aug 2013, then updated and re-approved May 2013 at WGM
  • Planned Ballot: September 2013

gForge Users

  • Lorraine Constable
  • Patrick Loyd

Issues

  • What's the determinerCode? instance, kind or don't care? If not fixed, is there a way to infer it?
  • Need example scenarios
  • Look at NCPDP and OpenEHR as possible sources for device as well (not sure if they have coverage or not)
  • Need to explain the types of relationships to the listed resources
Retrieved from "https://wiki.hl7.org/w/index.php?title=Device_FHIR_Resource_Proposal&oldid=166145"