This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "CDA R2.1 Project"

From HL7Wiki
Jump to navigation Jump to search
Line 38: Line 38:
 
== '''Agenda Items''' ==
 
== '''Agenda Items''' ==
 
'''Review Action Items''':
 
'''Review Action Items''':
−
# CDA R2.1 Narrative Block - C. Beebe
 
−
# Analysis of new codes from current RIM - C. Beebe
 
 
# Status of secure Wiki site for Editors - Ben Flessner
 
# Status of secure Wiki site for Editors - Ben Flessner
 
'''Current Agenda'''
 
'''Current Agenda'''
−
# Review Requests from Kathleen
+
# Question about the modeling of AssignedCustodian class; I.e. Playing / Scoping usage.
−
## Add new Author Scoper Entity Choices - Person/Device
+
# Review the write up for the Harmonization discussion on CDA R2.1 vocabulary changes.
−
## Add Sequence # to all participations – to associate participations
+
# The CDA R2.1 project is attempting to make some improvements to the CDA R2.0 standard, as we pulled the team together, a request was made to support new vocabularies submitted via RIM Harmonization in later versions of the RIM, not found in RIM 2.07, which is the basis of the CDA R2.0 standard.
−
## Add Header Participant playing Entity - to pick up Device Entity info
+
## Issues to consider:
−
## Add Section Participant – to convey Assembly, Composer or other facilitating devices
+
### CDA R2.0 is based on RIM 2.07 (2005), the current RIM is 2.41 (2015)
−
## Add ParticipationFunction to Section and Entry Participant Classes
+
### We need to continue to support HL7 Data Types 1.0, as support of Data Types 2.0 would break our wire format backwards compatibility.
−
## Add all ActRelationship and Participation Type Codes to CDA R2.1 Value Sets – to extend the types of state transitions that may occur among artifacts
+
### The CDA R2.1 team is being asked to support new participation type codes & function codes, and new act relationship codes.
−
## Add more detailed ParticipationFunction Codes
+
### Just renaming the VOC.xml file does not look feasible, as there  are significant structural differences between earlier generation behavior and current generation behavior for the schemas.  (e.g. data types enumerations were included in VOC.XML at RIM 2.07, but not in later versions)
−
## Add Universal and Global Medical Device Nomenclature Systems as HL7 Value Sets for Device RoleType Codes
+
### Current thinking is that we would like to present a future harmonization request RIM to 2.07 on a selected set of vocabularies which would only add codes defined in later versions of the RIM.
−
# Request Doodle Poll for project meeting time
+
### We will also update value sets defined for CDA R2.0, when we create CDA R2.1
 +
### We assuming that we might have to manually update the publication package to support a RIM 2.07a, with updated vocabulary documentation, along with the CDA R2.1 release to create a normative publication.
 +
## Look at some analysis of the vocabulary schemas (review)
 
# Open Topics  
 
# Open Topics  
 
|}
 
|}

Revision as of 21:55, 5 February 2015

Return to

CDA R2.1 Project

Welcome to the CDA R2.1 Project Wiki Site. On these pages we will manage the various moving pieces necessary to support development of CDA Release 2.1



Project Information

Meeting Times Current Agenda

Conference Calls

The CDA R2.1 Project Team conference call is scheduled every Friday at 2:00 PM Eastern Time.
It is scheduled for 1 hour.

Participation Information

Phone Number: +1 770-657-9270
Participant Passcode: 310940

Web Meeting Info

Participant: Join a Meeting

Global Crossing Conf#: 866-365-4406
Access Code: 284-3827
Calvin to Host

Agenda Items

Review Action Items:

  1. Status of secure Wiki site for Editors - Ben Flessner

Current Agenda

  1. Question about the modeling of AssignedCustodian class; I.e. Playing / Scoping usage.
  2. Review the write up for the Harmonization discussion on CDA R2.1 vocabulary changes.
  3. The CDA R2.1 project is attempting to make some improvements to the CDA R2.0 standard, as we pulled the team together, a request was made to support new vocabularies submitted via RIM Harmonization in later versions of the RIM, not found in RIM 2.07, which is the basis of the CDA R2.0 standard.
    1. Issues to consider:
      1. CDA R2.0 is based on RIM 2.07 (2005), the current RIM is 2.41 (2015)
      2. We need to continue to support HL7 Data Types 1.0, as support of Data Types 2.0 would break our wire format backwards compatibility.
      3. The CDA R2.1 team is being asked to support new participation type codes & function codes, and new act relationship codes.
      4. Just renaming the VOC.xml file does not look feasible, as there are significant structural differences between earlier generation behavior and current generation behavior for the schemas. (e.g. data types enumerations were included in VOC.XML at RIM 2.07, but not in later versions)
      5. Current thinking is that we would like to present a future harmonization request RIM to 2.07 on a selected set of vocabularies which would only add codes defined in later versions of the RIM.
      6. We will also update value sets defined for CDA R2.0, when we create CDA R2.1
      7. We assuming that we might have to manually update the publication package to support a RIM 2.07a, with updated vocabulary documentation, along with the CDA R2.1 release to create a normative publication.
    2. Look at some analysis of the vocabulary schemas (review)
  4. Open Topics

Lists and Links

Past Minutes Documents, Action Items, Etc. See also


Retrieved from "https://wiki.hl7.org/w/index.php?title=CDA_R2.1_Project&oldid=96159"