Uploaded image for project: 'CDA Specification Feedback'
  1. CDA Specification Feedback
  2. CDA-2037

STU-2037 - US Realm Header for PGD free-text conformance should be modelled instead

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Highest Highest
    • C-CDA Templates Clinical Notes (CDA)
    • 2.1.0 [deprecated]
    • Structured Documents
    • Templates [deprecated]
    • Hide

      The following narrative guidance will be removed:

      The functionCode SHALL be selected from value set ParticipationType 2.16.840.1.113883.1.11.10901

      The existing conformance statement will be updated to be the following:

      The performer, if present, MAY contain zero or one [0..1] functionCode which SHALL be selected from ValueSet ParticipationType urn:oid:2.16.840.1.113883.1.11.10901 DYNAMIC (CONF:XXXX-XXXXX).

       

      The following narrative guidance will remain, but adjusted to not be confused as a conformance statement:

      When indicating the performer was the primary care physician, implementers should indicate "PCP" as the functionCode

      Show
      The following narrative guidance will be removed: The functionCode SHALL be selected from value set ParticipationType 2.16.840.1.113883.1.11.10901 The existing conformance statement will be updated to be the following: The performer, if present, MAY contain zero or one [0..1] functionCode which SHALL be selected from ValueSet ParticipationType urn:oid:2.16.840.1.113883.1.11.10901 DYNAMIC (CONF:XXXX-XXXXX).   The following narrative guidance will remain, but adjusted to not be confused as a conformance statement: When indicating the performer was the primary care physician, implementers should indicate "PCP" as the functionCode
    • Brett Marquard / Gay Dolin: 18-0-0
    • Correction
    • Non-substantive

    Description

      Specification - Extended

      HL7 CDA® R2 IG: C-CDA Templates for Clinical Notes DSTU Release 2.1 - US Realm

      Document Description

      extended per extended per TSC tracker 12437, again with 14128 and jira.hl7.org/browse/TSC-38

      Existing Wording

      The US Realm Header for Patient Generated Document (V2) template contains the following free-text constraints: The functionCode SHALL be selected from value set ParticipationType 2.16.840.1.113883.1.11.10901 When indicating the performer was the primary care physician the functionCode shall be =”PCP”

      Proposed Wording

      Why aren't these actual conformance statements? The first one is computable, and even though the second one isn't, can't it still be written as a free-text conformance statement in Trifolia with a CONF: number and everything rather than just hiding in the free-text guidance?

      Attachments

        Activity

          People

            Russell Ott Russell Ott
            mszczepa Matt Szczepankiewicz
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: