Resource names should meet the following characteristics: (for additional guidance on considerations for resource creation, refer to FHIR Resource Considerations)
- Upper camel case
- Avoid non-universal abbreviations (e.g. URL would be ok)
- Be expressed as a noun
- Be consistent with other similar resources
DeviceDefinition[edit | edit source]
Owning Committee Name[edit | edit source]
Orders & Observations YourWorkGroupName
Committee Approval Date:[edit | edit source]
Please enter the date that the committee approved this Resource proposal
Contributing or Reviewing Work Groups[edit | edit source]
- Work Group Name
- or link
- or "None"
FHIR Resource Development Project Insight ID[edit | edit source]
Scope of coverage[edit | edit source]
The DeviceDefinition is an adminsitrative resource that includes all relevant attributes to define the kind of device that can be referenced by multiple Devices to provide information that does not change for an instance.
The DeviceDefinition can also be used for catalogs or other use cases where the reference to a device is generically to a type of device, not a specific instance of a device. This may include procedures or observations where the specific device is not known or not relevant.
Example device definitions include specifications for an x-ray machine, implantable devices, lab analyzers, etc.
Note that with the acceptance of this proposal, the Device resource scope will be reduced to just the instance related attributes.
RIM scope[edit | edit source]
There does not appear to be a DeviceDefinition concept in the RIM, rather only the Device instance is referenced The Common Product Model touches on elements, but not all.
Resource appropriateness[edit | edit source]
Separating the DeviceDefinition from Device enables more clear distinctions and use considering a number of use cases primarily focus on Device, while others focus on DeviceDefinition. Furthermore, there will be many more Device instances than there will be DeviceDefinition instances. The DeviceDefinition would be used in catalogs and go through independent updates from the Device instance.
Expected implementations[edit | edit source]
Implementations of catalogs, e.g., LIVD as well as implementations needing to reference devices will all directly or indirectly use this device.
Content sources[edit | edit source]
- HL7 FHIR Device, DeviceComponent, and DeviceMetrics
- HL7 V2 EQU and DEV segments
Example Scenarios[edit | edit source]
Resource Relationships[edit | edit source]
Timelines[edit | edit source]
September 2018 inclusion in FHIR R4.
gForge Users[edit | edit source]
Eric Haas, Jose Costa Teixeira
When Resource Proposal Is Complete[edit | edit source]
When you have completed your proposal, please send an email to FMGcontact@HL7.org