STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

Device vs Medication

Messages

A series of messages from the comparison algorithm. Errors indicate that solutions cannot be interoperable across both implementation guides (or that there are structural flaws in the definition of at least one).

PathMessage
Errors Detected
DeviceBase Type is not compatible (Device/Medication)
DeviceDifferent number of children at Device (24/13)
Notes about differences (e.g. definitions)
DeviceElements differ in definition for short:
"Item used in healthcare"
"Definition of a Medication"
DeviceElements differ in definition for definition:
"This resource identifies an instance or a type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. Medical devices includes durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc."
"This resource is primarily used for the identification and definition of a medication. It covers the ingredients and the packaging for a medication."

Intersection

The intersection of the 2 constraint statements. This is what resource authors (either client or server) would need to conform to produce content valid against both implementation guides.

No intersection could be generated

Union

The union of the 2 constraint statements. This is what resource authors (either client or server) would need to be able to handle to accept content valid against either implementation guides.

No union could be generated