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

Remove Entries Optional Duplicate Sections

    XMLWordPrintableJSON

Details

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

      Delete all Entries Optional templates where a duplicate Entries Required template exists, and remove "Entries Required" from the template names.

      Document-level templates that exclusively reference the Entries Optional templates will be updated to reference the Entries Required versions.

      Will also add guidance with respect to handling of lack of data: in particular, if no machine-readable data can be sent for a section, the nullFlavor attribute may still be used to include an empty entry in a section where entries are required.

       

      For example, today the Progress Note template says:

      This structuredBody SHALL contain exactly one [1..1] component
      (CONF:1198-30571) such that it
      1. SHALL contain exactly one [1..1] Allergies and Intolerances 
      Section (entries optional) (V3) (identifier: 
      urn:hl7ii:2.16.840.1.113883.10.20.22.2.6:2015-08-01)
      (CONF:1198-30572).

      This will be updated to:

      This structuredBody SHALL contain exactly one [1..1] component
      (CONF:1198-30571) such that it
      1. SHALL contain exactly one [1..1] Allergies and Intolerances 
      Section (V3) (identifier: 
      urn:hl7ii:2.16.840.1.113883.10.20.22.2.6.1:2015-08-01)
      (CONF:1198-30572).

      Show
      Delete all Entries Optional templates where a duplicate Entries Required template exists, and remove "Entries Required" from the template names. Document-level templates that exclusively reference the Entries Optional templates will be updated to reference the Entries Required versions. Will also add guidance with respect to handling of lack of data: in particular, if no machine-readable data can be sent for a section, the nullFlavor attribute may still be used to include an empty entry in a section where entries are required.   For example, today the Progress Note template says: This structuredBody SHALL contain exactly one [1..1] component (CONF:1198-30571) such that it 1. SHALL contain exactly one [1..1] Allergies and Intolerances  Section ( entries optional ) (V3) (identifier:  urn:hl7ii:2.16.840.1.113883.10.20.22.2.6:2015-08-01) (CONF:1198-30572). This will be updated to: This structuredBody SHALL contain exactly one [1..1] component (CONF:1198-30571) such that it 1. SHALL contain exactly one [1..1] Allergies and Intolerances  Section (V3) (identifier:  urn:hl7ii:2.16.840.1.113883.10.20.22.2.6.1:2015-08-01) (CONF:1198-30572).
    • John D'Amore / Brett Marquard : 10 - 0 - 1
    • Enhancement
    • Non-compatible

    Description

      There should be no reason to have "Entries Required" and "Entries Optional" sections - just only make "Entries Required" sections (with the existing comments that nullFlavor=NI means that entries need not be populated)

      Attachments

        Activity

          People

            rosemaryh Rosemary Hofstede
            benjamin Benjamin Flessner
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: