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

[CDA-20767 Fix] Re-add name constraint to Care Plan

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Medium Medium
    • C-CDA Templates Clinical Notes (CDA)
    • 3.0.0-ballot
    • Structured Documents
    • STU
    • Care Plan
    • Hide

      The Key Elements and Snapshot tabs show all of the constraints for a given template.  We will not carry constraints down into the child templates but rather we will make the Key Elements tab the default.

      Show
      The Key Elements and Snapshot tabs show all of the constraints for a given template.  We will not carry constraints down into the child templates but rather we will make the Key Elements tab the default.
    • Jean Duteau / Lisa Nelson : 6-0-0
    • Clarification
    • Non-substantive

    Description

      We fixed CDA-20767 by removing the constraint on a Care Plan's receivedOrganization/name entirely. Technically, this does solve the issue, since now the [1..1] cardinality constraint will carry over from the US Realm Header template... but don't we typically try to explicitly carry over the US Realm Header constraints like that into the document-level templates rather than rely on implementers to know there are other implicit requirements lurking in US Realm Header?

       

      IMO it would be better for the Care Plan to say that the receivedOrganization SHALL have  [1..1] name just like US Realm Header does.

      Attachments

        Activity

          People

            jduteau Jean Duteau
            mszczepa Matt Szczepankiewicz
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: