-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Medium
-
FHIR Core (FHIR)
-
DSTU2
-
Orders & Observations
-
Device
-
8.9.7.2
-
-
Robert Dieterle/Eric Haas: 9-0-1
-
Clarification
-
Compatible, substantive
-
DSTU2
Existing Wording: Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC identifiers cannot be conveyed in FHIR.
Proposed Wording: Clarify the AIDC liminiate, it is not an issue related to JSON or XML encoding. AIDC could be supported if it could be differentiated from user-entered UdI carrier.
Comment:
AIDC strings could be represented in XML and JSON if the special characterr and delimiters are escaped. FDA and NLM provide a RESTful service that prases a UDI carrier regardless of its entry method: https://accessgudid.nlm.nih.gov/resources/developers/parse_udi_api
Summary:
Clarify any AIDC support guidance Device.udiCarreir (e.g. escaping deliminters and special characters).
- is duplicated by
-
FHIR-11819 Device resource limitations regarding AIDC UDI Carrier are overstated
-
- Duplicate
-
- is voted on by
-
BALLOT-2831 Negative - Greg Staudenmaier : 2018-Sep-FHIR R1
- Balloted