-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Medium
-
FHIR Core (FHIR)
-
DSTU1 [deprecated]
-
Orders & Observations
-
Device
DeviceComponent [deprecated]
DeviceMetric
DeviceObservationReport [deprecated]
DeviceRequest (was DeviceUseRequest)
DeviceUsage (DeviceUseStatement) -
5.8.3.2
-
-
Clarification
-
Non-substantive
-
DSTU1 [deprecated]
Existing Wording
There are many sources of possible codes for device type. The example suggests to use device codes from RTM. Another source which will be appropriate for many devices is the FDA GUDID (see below) or equivalent. Alternatively, many jurisdictions have their own supply chain arrangements which define many useful codes.
Proposed Wording
There are many sources of possible codes for device type. The example suggests to use device codes from RTM. Another source which will be appropriate for many devices is the FDA GUDID – the device identifier (DI) or GMDN code could be used for Device.type. A full UDI string (without a serial number) can also be stored in the Device.type element. (see below) or equivalent. Alternatively, many jurisdictions have their own supply chain arrangements which define many useful codes.
Comments
My 'proposed wording' is based on the assumption that UDI can be stored in FHIR Identifier or Type based on the UDI content (with or without serial number), but this is all in addition to the UDI being stored in the FHIR UDI field. Correct?
If yes, my 'Proposed wording' stands.
If not, more discussion is needed.
Grahame's Comments
ok
- is voted on by
-
BALLOT-388 Affirmative - Leslie Tompkins : 2015-Jan-FHIR R1
- Closed