This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Improvements to C-CDA Errata, V3 Template Design, Example Taskforce"
Jump to navigation
Jump to search
(Created page with "Below are the deliverables created to improve to C-CDA Errata, the V3 Template Design, updates to the Example Taskforce *Design and deployment of a new C-CDA errata Process ...") |
|||
| Line 5: | Line 5: | ||
**The attached document includes a suggested migration plan to JIRA | **The attached document includes a suggested migration plan to JIRA | ||
**The team hosted two requirements sessions to develop and document processes | **The team hosted two requirements sessions to develop and document processes | ||
| − | + | [https://gforge.hl7.org/gf/project/enhanceccdaimpl/docman/Improvements%20to%20C-CDA%20Errata,%20V3%20Template%20Design,%20Example%20Taskforce/C-CDA%20STU%20Comment%20and%20Errata%20Process%20-%20Future%20State.pdf C-CDA STU Comment and Errata Process - Future State] | |
*Future C-CDA templates design guide | *Future C-CDA templates design guide | ||
**The document linked below is a MS Word template for the development of new C-CDA templates | **The document linked below is a MS Word template for the development of new C-CDA templates | ||
**The team completed an analysis of UDI vs Advance Directive vs prior companion guides | **The team completed an analysis of UDI vs Advance Directive vs prior companion guides | ||
| − | + | [https://gforge.hl7.org/gf/project/enhanceccdaimpl/docman/Improvements%20to%20C-CDA%20Errata,%20V3%20Template%20Design,%20Example%20Taskforce/Additional%20CDA%20Templates%20Companion%20Guide%20Template.pdf Additional CDA Templates Companion Guide Template] | |
*Example Task Force Updates | *Example Task Force Updates | ||
**The document linked below is a best practices guide for narrative-entry linking. | **The document linked below is a best practices guide for narrative-entry linking. | ||
| − | The team reviewed this guide with the Example Task Force. | + | **The team reviewed this guide with the Example Task Force. |
**The Example Task Force Trello board has been reviewed and cleaned up. | **The Example Task Force Trello board has been reviewed and cleaned up. | ||
| + | [https://gforge.hl7.org/gf/project/enhanceccdaimpl/docman/Improvements%20to%20C-CDA%20Errata,%20V3%20Template%20Design,%20Example%20Taskforce/Example%20Task%20Force%20-%20best%20practices%20guide%20for%20narrative-entry%20linking.pdf Example Task Force - best practices guide for narrative-entry linking] | ||
Revision as of 20:42, 27 September 2017
Below are the deliverables created to improve to C-CDA Errata, the V3 Template Design, updates to the Example Taskforce
- Design and deployment of a new C-CDA errata Process
- The document linked below summarizing the current and proposed future C-CDA errata/DSTU comment process.
- The attached document includes a suggested migration plan to JIRA
- The team hosted two requirements sessions to develop and document processes
C-CDA STU Comment and Errata Process - Future State
- Future C-CDA templates design guide
- The document linked below is a MS Word template for the development of new C-CDA templates
- The team completed an analysis of UDI vs Advance Directive vs prior companion guides
Additional CDA Templates Companion Guide Template
- Example Task Force Updates
- The document linked below is a best practices guide for narrative-entry linking.
- The team reviewed this guide with the Example Task Force.
- The Example Task Force Trello board has been reviewed and cleaned up.
Example Task Force - best practices guide for narrative-entry linking
