CDA R3 Project Editing

Return to

• CDA R3 Project page
• SDWG page
• SAIF Architecture Program page

CDA R3 Editors Page

Welcome to the CDA R3 Editors page. This is where the project will be tracking which editors are performing editing tasks on various sections of the CDA R3 standard. Below is an outline of the sections within the document and editors working on those sections.

Editing Guidelines

• Editors should indicate what sections they are working on by adding their name to the section below
• As the editors group walks through the document, they are adding notes regarding the types of edits that need to be made for a section
• Editors should grab the relevant section for editing from the CDA R2 spec, make the edits in MS Word. Once the edits are complete for a section, upload the document to the wiki and link the section to in via wiki markup
  • Upload File
  • example file link: [[File:CDA-R3-TaskTracker.zip]]

CDA R3 Editors

• Austin Kreisler
• Amnon Shabo
• Bonnie McAllister
• Diana Behling
• Lisa Nelson
• Stan Rankins
• Calvin Beebe
• Rick Geimer
• Pete Gilbert
• Keith Boone

Editor Conference Calls

• Wednesdays at 1 pm Eastern
• 770-657-9270 passcode: 310940
• Web Coordinates: https://iatric.webex.com/iatric/j.php?ED=201192802&UID=1357648757&RT=MiMxMQ%3D%3D

Upcoming Publishing Deadlines

• June 24 (Sunday) T minus 5 - NIBs
• July 1 (Sunday) T minus 4 - Initial Content Due – XML-based Submissions
• July 8 (Sunday) T minus 3 - Preview and CMET Content Due – XML-based Submissions
• July 15 (Sunday) T minus 2 - Reconciliation, Complete & Supporting Content Deadlines – All Submissions
• July 22 (Sunday) T minus 1 - Final Content Deadline – XML-based Submissions
• July 30 (Monday) T minus 0 - July 30 (Monday) T minus 0

DRAFT CDA R3 in PubDB

I've put some more of the R2 content so that you can see how it will look. You can download the file at File:Uvcd 20120624.zip ... Pete

Useful links for editors

Please add any useful links you can think of here.

• SDWG GForge link: http://gforge.hl7.org/gf/project/strucdoc/
• CDA R3 content GForge/SVN link: http://gforge.hl7.org/gf/project/strucdoc/scmsvn/?action=browse&path=%2Ftrunk%2FCDAR3%2F

1 CDA Overview

• Editor -

1.1 What is the CDA

• Editor -
  • 20120613 - group does not feel any edits to this section are necessary. See document posted by Lisa regarding this section.
  • Does any of the text associated with the 6 document characteristics need to be made? Lisa will follow up with Kalvin, Keith, Bob to see if they have anything from the tutorials.

1.1.1 Key aspects of the CDA

• The thirds bullet that talks about expressiveness and flexibility of R2 needs to be revised slightly to indicate that R3 is introducing additional flexibility where R2 was found limiting in some cases.

1.1.2 Scope of the CDA

• Need add some text outlining the expanded scope of participation in the header as well as the expansion of the right hand side entries to include more or less the entire RIM.

1.1.3 Goals and Design Principles

• These goals and design principles were reviewed on the section and approved making the following changes:
  • Change the final goal
    • From: Enable policy-makers to control their own information requirements without extension to this specification.
    • To: Enable policy-makers and implementers to control their own information requirements without extension to this specification.
  • Following the first goal, add a new goal:
    • Provide additional support for use cases related to secondary use of healthcare data
  • Add a design principle describing how we are supporting the above new goal via the expanded generic header participant as well as the expansion of the "clinical statement" portion of CDA to encompass more or less the entire RIM

1.2 General CDA Concepts

• Editor -

1.2.1 Major Components of a CDA Document

• Editor - Amnon
• Note - This is probably where we need to discuss the implications of splitting semantics from rendering as that change has a major impact on the overall structure of CDA. This file has the text:
• Media:CDA_R3_Split_Semantics_and_Rendering_-_2012.07.18.docx

1.2.2 The "A" in "CDA"

• Need to add a sentence that CDA R3 hasn't really changed the approach to CDA "levels" that was used in CDA R2.
• One note that if we go down the split semantics from rendering path that we can no longer assume that a level 3 CDA has level 2 sections. That will need to be made explicit as opposed to being implicit as it is today.

1.2.3 Human Readability and Rendering CDA Documents

• Needs to be updated to talk about CDA R3 instead of CDA R2)
• Need to take a look at the last bullet to see if R2 really accomplished this and what if any change needs to be made in R3 to allow indicating how narrative was derived from structured content.
  • "When narrative is derived from structured content, there must be a mechanism to identify the process by which narrative was generated from structured data."
• Also need to add a discussion about responsibilities of creators of documents regarding what ends up as machine readable vs. human readable.

1.2.4 XML Markup of CDA Documents

• editor - Keith
• Keith has some tweaks to the meaning of validation of the CDA.

Media:1-2-4 XML Markup of CDA Documents.docx

1.2.5 Security, Confidentiality, and Data Integrity

• Content for this section is tied to the output from the CDA R3 Security Cookbook risk assessment. That won't be completed in time for the draft for comment ballot, but needs to be wrapped up before normative balloting.

1.2.6 Relationship of the CDA to HL7 Messaging Standards

• Leave as is for now

1.3 CDA Conformance

• editor - Keith
• Keith has some tweaks to the meaning of validation of the CDA.

Media:1-3 CDA Conformance.docx

1.4 CDA Extensibility

• Editor - Keith

Media:1-4_CDA_Extensibility.docx

1.5 Backwards and Forwards Compatibility

• Editor -
• Need to add release notes for CDA R3 (based on task tracker)

2 Introduction to CDA Technical Artifacts

• Editor - Keith to review to see what edits need to be made.

Media:2_Introduction_to_CDA_Technical_Artifacts.docx

2.1 HL7 Reference Information Model

• Editor -

2.2 HL7 V3 Data Types

• Editor -

Adopting R2 Datatypes

2.3 HL7 Vocabulary Domains

• Editor -

2.4 HL7 CDA R-MIM

• Editor -

2.5 HL7 CDA Hierarchical Description

• Editor -

2.6 HL7 CDA XML Implementation

• Editor - Rick

Media:2.6_HL7_CDA_XML_Implementation.docx

3 CDA Document Exchange in HL7 Messages

• Editor -

4 CDA R-MIM

• Editor -

4.1 Clinical Document

• Editor -

4.2 Header

• Editor - Rick & Austin
• Same content needs to be pushed into the CDA R3 RMIM as attribute level descriptions.

4.2.1 Header Attributes

• Media:4.2.1_Header_Attributes.docx
• Media:ClinicalDocument-completionCode.doc

4.2.2 Header Participants

• Media:4.2.2_Header_Participants.docx
• Media:ClinicalDocument-participant2.doc

4.2.3 Header Relationships

4.2.3_Header_Relationships.docx

4.2.4 Header Rendering

Editor: Keith Media:4-2-4 Header Rendering.docx Could move to Rendering Section above

4.3 Body

• Editor -

4.3.5 Section Narrative Block

Editor: Calvin Beebe

Uploaded narrative: [Section 4.3.5] additional materials are in this [Zip file] i.e. CDA Narrative Schema (XSD) file and documentation (HTML) file.

4.3.6 Entry Acts

=====4.3.6.1 Document using templates for the new CDA Act Statement

• Editor - Calvin

4.4 CDA Context

• Editor - Amnon

Media:CDA_R3_Context_Conduction_-_2012.07.18.docx

5 CDA Hierarchical Description

• Editor -

6 CDA XML Implementation

• Editor -

Appendices

• Editor -

A Samples

• Editor -

B Implementation Notes

• Editor -

B.2 LOINC Document Codes

Do we still want this in R3, or do we just want to direct folks to LOINC? pete