Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-11049

Clarify any AIDC support guidance Device.udiCarreir (e.g. escaping deliminters and special characters). - 2016-09 core #68

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • DSTU2
    • Orders & Observations
    • Device
    • 8.9.7.2
    • Hide

      Original Vote: Feb 2 2107

      Ballot Resolution: Not Persuasive

      Eric Haas/Riki Merrick: 8-3-1

      Deferred

      (Negative ballot items will need to be voted as not persuasive if you want to defer them -make the status "Deferred")

      ---------------------------------------

      Motion to reopen date Feb 5 2017
      Robert Dieterle/Terrie Reed: 9-0-1

      Motion Resolve this tracker as Persuasive with Mod based on attached powerpoint in GForge #11109

      Show
      Original Vote: Feb 2 2107 Ballot Resolution: Not Persuasive Eric Haas/Riki Merrick: 8-3-1 Deferred (Negative ballot items will need to be voted as not persuasive if you want to defer them -make the status "Deferred") --------------------------------------- Motion to reopen date Feb 5 2017 Robert Dieterle/Terrie Reed: 9-0-1 Motion Resolve this tracker as Persuasive with Mod based on attached powerpoint in GForge #11109
    • Robert Dieterle/Eric Haas: 9-0-1
    • Clarification
    • Compatible, substantive
    • DSTU2

    Description

      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).

      Attachments

        Activity

          People

            Unassigned Unassigned
            ioana13 Ioana Singureanu
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: