XMLWordPrintableJSON

Details

    • Change Request
    • Status: Deferred (View Workflow)
    • Low
    • Resolution: Considered for Future Use
    • Public Health Case Report - Electronic Initial Case Report (eICR) (CDA)
    • 1.1.1
    • Public Health
    • Narrative Guidance
    • Hide

      Considered for Future Use made 2019-01-15 00:00:00.0 with vote Laura Conn/Sunanda McGarvey: 18-0-0//(Impact: null; Category: null; Version: null)//Explanation: There are two templates to guide the construction of names – PN.US.FIELDED (person) and PTN.US.FIELDED (patient). Patient is where all the constraints around family name, given name etc. are set. If you say that you must use a patient name then you can only put in a properly formatted name. Person loosens this and says it has to be EITHER a patient name (very constrained) OR just a string (and the string can’t have any name parts in it) – so basically – if you don’t have either a properly formatted patient name or a string (i.e. a nullFlavor) then you’ll get a confusing message about it has to be a Patient name (even though you’re not naming a patient). (It would have been much better to call them US Realm Structured Person Name and US Realm Person Name but they didn’t!) Disposition Date: 01/15/2019 Mover/Seconder: Laura Conn/Sunanda McGarvey Vote: 18-0-0

      Show
      Considered for Future Use made 2019-01-15 00:00:00.0 with vote Laura Conn/Sunanda McGarvey: 18-0-0//(Impact: null; Category: null; Version: null)//Explanation: There are two templates to guide the construction of names – PN.US.FIELDED (person) and PTN.US.FIELDED (patient). Patient is where all the constraints around family name, given name etc. are set. If you say that you must use a patient name then you can only put in a properly formatted name. Person loosens this and says it has to be EITHER a patient name (very constrained) OR just a string (and the string can’t have any name parts in it) – so basically – if you don’t have either a properly formatted patient name or a string (i.e. a nullFlavor) then you’ll get a confusing message about it has to be a Patient name (even though you’re not naming a patient). (It would have been much better to call them US Realm Structured Person Name and US Realm Person Name but they didn’t!) Disposition Date: 01/15/2019 Mover/Seconder: Laura Conn/Sunanda McGarvey Vote: 18-0-0
    • Laura Conn/Sunanda McGarvey : 18-0-0

    Description

      Specification - Extended

      HL7 CDA® R2 Implementation Guide: Public Health Case Report, Release 2: the Electronic Initial Case Report (eICR), Release 1, STU Release 1.1 - US Realm

      Document Description

      extended per TSC Tracker 12574, extension TSC GF 15952, JIRA TSC-29, TSC-123

      Existing Wording

      Handling of the name element for responsibleParty/assignedEntity/assignedPerson/name is inconsistent. In the schematron, a name that is nullFlavored generates this error: Description: The content of name *SHALL* be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371). ((cda:name/cda:given and cda:name/cda:family) or (count(cda:name/*)=0 and string-length(normalize-space(string(cda:name)))!=0)) [assert] This appears to be in violation of the specification, conformance 81-9372, which states that the string SHALL NOT contain name parts.

      Proposed Wording

      Remove the restriction against name parts for names in this specification using PN.US.FIELDED.

      Attachments

        Activity

          People

            Unassigned Unassigned
            john_stamm John Stamm
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: