CDA R3 Project Editing

From HL7Wiki
Jump to navigation Jump to search

Return to

Contents

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 (DSTU1 - Sept 2013 ballot)

  • Austin Kreisler
  • Benjamin Flessner
  • Calvin Beebe
  • Pete Gilbert
  • Diana Behling
  • Bonnie McAllister

CDA R3 Editors (Draft for comment 1)

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

Editor Conference Calls

Upcoming Publishing Deadlines (September 2013 Cycle)

  • July 7 (Sunday) T minus 5 - NIBs
  • July 14 (Sunday) T minus 4 - Initial Content Due – XML-based Submissions
  • July 21 (Sunday) T minus 3 - Preview and CMET Content Due – XML-based Submissions
  • July 28 (Sunday) T minus 2 - Reconciliation, Complete & Supporting Content Deadlines – All Submissions
  • August 3 (Sunday) T minus 1 - Final Content Deadline – XML-based Submissions
  • August 12 (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.

Draft For Comment 1 Original Ballot Content

Task Tracker link

DSTU Content

  • Task tracker id# (APPLIES TO ALL SECTIONS OF DOCUMENT): #84, #86, #90, #99, #103, #128, #150

Preface

  • Task tracker id#: #85

1 CDA Overview

  • Editor -

1.1Introduction & Scope

  • Task tracker id#: #101

1.1.1Introduction and Scope

  • Task tracker id#: #101

1.1.1.1 What is the CDA

  • Editor -
  • Task tracker id#: #82, #102

1.1.2 Key aspects of the CDA

1.1.3 Scope of the CDA

1.1.4 Goals and Design Principles

1.1.5 General CDA Concepts

1.1.5.1Major Components of a CDA Document
  • Task tracker id#: #104
1.1.5.1.1 Split Semantics and Rendering
  • Task tracker id#: #55
1.1.5.2The 'A' in 'CDA'
  • Task tracker id#: #105, #106, #107
1.1.5.3 Human Readability and Rendering CDA Documents
  • Task tracker id#: #60, #108
1.1.5.4 XML Markup of CDA Documents
  • Task tracker id#: #109
1.1.5.6 Relationship of CDA to HL7 Messaging Standards
  • Task tracker id#: #110

1.1.6 CDA Conformance

  • Task tracker id#: #4, #111
1.1.6.1Document Originator Role and Responsibilities
  • Task tracker id#: #112
1.1.6.2 Document Recipient Role and Responsibilities
  • Task tracker id#: #113

1.1.7 CDA Extensibility

  • Task tracker id#: #114, #115, #116, #126

1.1.8 Backwards and Forwards Compatability

  • Task tracker id#: #1, #117

1.2 General CDA Concepts

  • Editor -

1.2.1 Major Components of a CDA Document

  • Editor -
  • Previous Editor - Amnon

1.2.2 The "A" in "CDA"

1.2.3 Human Readability and Rendering CDA Documents

1.2.4 XML Markup of CDA Documents

  • editor -
  • previous editor - Keith

1.2.5 Security, Confidentiality, and Data Integrity

1.2.6 Relationship of the CDA to HL7 Messaging Standards

1.2.7 CDA And Digital Signatures

  • NEW SECTION (alternately this could be added to the appendices
  • Task tracker id#: #49

1.3 CDA Conformance

  • editor -
  • previous editor - Keith

1.3.1 Recipient Responsibilities

1.3.2 Originator Responsibilities

1.4 CDA Extensibility

  • Editor -
  • Previous editor - Keith

1.5 Backwards and Forwards Compatibility

  • Editor -

1.6 Document Management

  • NEW SECTION
  • Task tracker id#: #79

1.7 CDA Template Governance

  • NEW SECTION
  • Task tracker id#: #89

2.1.1 Introduction to CDA Technical Artifacts

  • Editor -
  • previous editor - Keith

2.1.2 HL7 Reference Information Model

  • Editor -


2.1.3 HL7 V3 Data Types

  • Editor -

2.1.4 HL7 Vocabulary Domains

  • Editor -

2.1.5 HL7 CDA R-MIM

  • Editor -

2.1.6 HL7 CDA Hierarchical Description

  • Editor -

2.1.7 HL7 CDA XML Implementation

  • Editor -
  • Previous Editor - Rick

? CDA Document Exchange in HL7 Messages

  • THIS SECTION WAS MOVED TO APPENDICES IN DFC1
  • Editor -

2.2 CDA R-MIM

  • Editor -

2.2.1 Clinical Document (POCD_RM000040UV)

  • NOTE - Text fro CDA R2 is missing in thie section
  • Task tracker id#: #118
  • Editor -

2.2.1.1 Clinical Document

  • NOTE - Text fro CDA R2 is missing in thie section
  • Task tracker id#: #25 (APPLIES TO ALL NESTED SECTIONS), #26 (APPLIES TO ALL NESTED SECTIONS)
  • Task tracker id#: #118

2.2.1.1.1 Header

  • Editor -
  • Previous Editor - Rick & Austin

2.2.1.1.1.1 Header Attributes

2.2.1.1.1.1.1 ClinicalDocument.id
  • Task tracker id#: #91
2.2.1.1.1.1.2 ClinicalDocument.code
  • Task tracker id#: #123
2.2.1.1.1.1.5 ClinicalDocument.ConfidentialityCode
  • Task tracker id#: #124
? ClinicalDocument.statusCode
  • NEW SECTION (insert in RIM attribbute order)
  • Task tracker id#: #120
2.2.1.1.1.1.7 ClinicalDocument.setID
  • Task tracker id#: #91
2.1.1.1.1.1.10 ClinicalDocument.copyTime (deprecated)
  • Task tracker id#: #122

2.2.1.1.2 Header Participants

2.2.1.1.2.1 authenticator
  • Task tracker id#: #51, #125
2.2.1.1.2.2 author
  • Task tracker id#: #133
2.2.1.1.2.7 informationRecipient
  • Task tracker id#: #8
2.2.1.1.2.8 legalAuthenticator
  • Task tracker id#: #125
2.2.1.1.2.9 Participant1
  • Task tracker id#: #87, #95, #126, #129
2.2.1.1.2.10 Participant2
  • Task tracker id#: #87, #95, #126, #129
2.2.1.1.2.10.1 Using Participant2 and R-Participant CDA in CDA R3 Document Instances
  • Task tracker id#: #87, #95, #126, #127, #129
2.2.1.1.2.12 recordTarget
  • Task tracker id#: #92, #129

2.2.1.1.3 Header Relationships

2.2.1.1.3.1 ParentDocument
  • Task tracker id#: #134
2.2.1.1.3.2 ServiceEvent
  • Task tracker id#: #30
2.2.1.1.3.5 EncompassingEncounter
  • Task tracker id#: #140
2.2.1.1.3.6 Rule
  • Task tracker id#: #135
? Clinical Document Event
  • NEW SECTION
  • Task tracker id#: #48 (note, this still needs modeling prior to documenting)

2.2.1.1.3.7 Header Rendering

  • Editor -
  • Previous Editor: Keith

2.2.1.1.4 Body

  • Editor -

2.2.1.1.4.1 Body Choice

  • Section not documented in DFC1
  • Task tracker id#: #148
? NonStructuredBody
  • Section not documented in DFC1
  • Task tracker id#: #118

2.2.1.1.4.2 Section Attributes

  • Section not documented in DFC1

Task tracker id#: #148

2.2.1.1.4.3 Section Participants

  • Section not documented in DFC1
  • Task tracker id#: #148
? authenticator
  • NEW SECTION
  • Task tracker id#: #94

? Section Relationships

  • Section not documented in DFC1
  • Task tracker id#: #143, #148

? Entry Acts

  • IN DFC1 THIS SECTION WAS MISSING
  • Task tracker id#: #27 (APPLIES TO ALL NESTED SECTIONS), #32, #51, #149
? Document using templates for the new CDA Act Statement
  • Editor -
  • Previous Editor - Calvin

? Entry Participants

  • Task tracker id#: #149

? Entry Relationships

  • Task tracker id#: #149

2.2.1.1.4.4 Section Narrative Block

  • Editor - Calvin Beebe
  • Previous Editor- Calvin Beebe
  • Task tracker id#: #24 Support nested tables in narrative - Current schema supports tables in td/th
  • Task tracker id#: #27 Use Act ID not XML ID for renderMultimedia
  • Task tracker id#: #73 Use subset of XHTML in the Narrative Block
  • Task tracker id#: #138 Footnote / FootnoteRef as <a rel="">
  • Task tracker id#: #139 Deprecate RegionOfInterest (map/area)

2.2.1.1.5 CDA Context

  • Editor
  • Previous Editor - Amnon

2.2.1.1.5.1 Overview of CDA Context

  • Task tracker id#: #51

2.2.1.1.5.2 Technical Aspects of CDA Context

  • Editor
  • Previous editor: Austin

2.3 Hierarchical Message Descriptions

  • Editor -

? CDA XML Implementation

  • MISING FROM DFC1
  • Editor -

Appendices

  • Editor -
  • Task tracker id#: #144

2.A.1 Annex Clinical Document

A Samples

  • SECTION MISSING IN DFC1
  • Editor -
  • Task tracker id#: #23, #31, #142

A.1 Sample Document

A.2 Sample CDA Instance

A.3 Sample CDA Style Sheet

  • Editor - Alexander/Calvin

Requirements

  • SHOULD where possible stay close to the rendering done by the current cda.xsl Done
  • SHOULD try to have 1 XSL for both CDAr2 and CDAr3 Done
  • SHOULD run in major browsers (Internet Explorer 8 and up, FireFox, Chrome, Safari) Done
    • SHOULD use XSLT 1.0 without EXSLT or other extensions Done
  • SHOULD produce valid XHTML Strict 1.0 (makes sense given that NarrativeBlock is a subset of XHTML Strict) Done
  • SHOULD produce in XHTML default encoding UTF-8 Done
  • SHOULD have core CSS internal, but MAY additionally provide hook to external CSS Done
  • SHOULD work well both on screen and in print (separate CSS to do this) Done
  • SHOULD be localizable, SHOULD provide at least English (en-US) Done
  • MAY use Javascript internally as long as the default is without Done, and MAY additionally provide hook to external Javascript
  • SHOULD NOT implement cookie support Done
  • COULD be optimized for smaller screens such as phones and tablets
  • SHOULD display:
    • All relevant header information, note that 'relevant' is a relative word Done
    • NonStructuredBody if the content type allows it in XSLT 1.0 Done
    • StructuredBody/Section attributes including NarrativeBlock and participations, but except component (Level 3) Done
    • Images and other media as far as content type allows it and if not wrapped in Base64 (unless someone can point out how to Base64 decode in XSL 1.0 without extensions with reasonable performance) Done

The initial result may be viewed here

B Implementation Notes

  • Editor -

B.1 Creating CDA Documents

B.2 LOINC Document Codes

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

B.3 CDA and Semantic Interoperability

B.4 Changes from CDA Release 2

B.4.1 Deprecated Components

B.4.2 CDA R2 to CDA R3 Correspondence

? Education Materials

  • NEW SECTION
  • Task tracker id#: #100

? Header Requirements

  • NEW SECTION
  • Task tracker id#: #121