Difference between revisions of "Device FHIR Resource Proposal"
Hbuitendijk (talk | contribs) |
|||
| Line 49: | Line 49: | ||
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. | 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== | ||
Latest revision as of 14:39, 24 June 2019
This page documents an Approved FHIR Resource Proposal
Contents
- 1 Device
- 1.1 Owning committee name
- 1.2 Interested Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
- 1.13 Issues
Device
Owning committee name
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
