2014 10 24 Minutes - CDA R2.1 Project

Attendance

• Calvin Beebe
• Diana Behling
• Kathleen Connor
• Lisa Nelson
• Patricia Powles
• Rob Hausam

Minutes / Notes

1. Review changes made the CDA R2.1 project scope document, based on the feedback from OO.

The following was added in section 3.a Project Scope:

      The intent of the project team is to limit additions to attributes in the RIM not included in CDA R2.0 classes
      and used in IGs or specifically requested.  All attributes added will need to be included optionally to ensure
      backwards wire format compatibility.
 

The following was added in section 3.a Project Scope:

      The addition of new classes to CDA R2.1 will be considered on a case by case basis for example when there is a
      demonstrated need and those classes are added optionally. This is not expected, but not prohibited out right. 
      The Project team intends to seek SDWG endorsement of any decision to add new classes.

The following was added in section 3.a Project Scope:

      These items are out of scope as it is not possible to make these changes and preserve wire format backwards 
      compatibility.

The updated PSS will be reviewed at next weeks SDWG call. The updated PSS will be submitted to TSC for review on Nov. 3rd the week after the SDWG review.

1. Review of the CDA R2.0 Standard (narrative document)

    The team reviewed the CDA R2.0 standard and attempted to identify the scope of changes and effort required. 
    
     1 CDA Overview
     The overview material will likely stay intact. 
     The only subsection needing revision will be the 1.5 which discusses backwards compatibility.
     It will need to speak to CDA R1.0 and CDA R2.0 forwards and backwards compatibility.
   
     2  Introduction to CDA Technical Artifacts
     The team will needs to determine if we can use the current V3 Tooling to generate the technical 
     artifacts for the new release of CDA R2.1
     It was noted that there were a number of hand edits that were made in CDA R2.0 at the time of publication.  
     No one is sure if we would save time to use the tooling or if it would take more time.
     The issue again is that we need to ensure the CDA R2.1 schema is backwards compatible.
     
     3  CDA Document Exchange in HL7 Messages
     No signficant changes were identified for the messaging, except to update references to RFCs.

     4  CDA R-MIM
     The committee discuss changes to the narrative portion of the CDA R2.0 standard.
     Calvin asked if it would be possible to generate the CDA R2.1 narrative from the tooling used for IGs?
     Austin raised some concerns that this approach would make it different from other V3 standards, and 
     that it might not work.  The committee will pickup from this location next week.