Consolidated CDA - Templates

Your browser does not appear to support JavaScript. You may want to try one of the following:

Turn on JavaScript in your browser if it supports it.
Use a browser that supports JavaScript.
Try a JavaScript-free version of this page, if made available by the application author.

An error has occurred

You may want to try one of the following:

Close this dialog and continue to use this page.
Reload this page. Note that you will lose any unsaved changes.
If the above does not work, try reloading the page yourself. Note that you will lose any unsaved changes:
- With Firefox: hold down the shift key and click the Reload button in your browser toolbar.
- With Safari and Chrome: click the Reload button in your browser toolbar.
- With Internet Explorer: hold down the control key and click the Reload button in your browser toolbar.
Return home.

Reloading form

This form has to be reloaded. This most likely happened because your session has expired, which might take to the login page. (If you think that you shouldn't see this message and that the problem persists, please contact support.)

Help

$xforms-template-label$$xforms-template-help$$xforms-template-hint$$xforms-template-label$$xforms-template-help$$xforms-template-hint$ en-US

Consolidated CDA - Templates

- ELGA Ambulanzbefund
- ELGA e-Impfpass
- Consolidated CDA
- ELGA Repository
- epSOS
- HL7 Deutschland e. V.
- HL7 V3 Value Sets
- International Patient Summary (IPS)
- Sandbox X-eHealth
- Sandbox HL7 Russia
- Development
Project
Datasets
Scenarios
Terminology
Templates
Issues
Login
- English (en-US)

url-scheme

Template locked

Templates (External repositories)

Filter

Templates


	Search true50
Templates

Diagnostic Imaging Report – Effective date

false

Issues (5)

false

Change Request Status = Open ( ccda-issue-2 ): assignedPerson

Type

Change Request

Status

Change Request Status = Open

Priority

Normal

Events

Tracking / Status = Open	2017-01-03 14:08:27 : Tracking by dr Kai U. Heitmann
Description	hl7:participant/hl7:assignedPerson in hl7:participant, there are hl7:associatedEntity, not assignedPerson

Change Request Status = Open ( ccda-issue-3 ): serviceEvent

Type

Change Request

Status

Change Request Status = Open

Priority

Normal

Events

Tracking / Status = Open	2017-01-03 14:08:56 : Tracking by dr Kai U. Heitmann
Description	hl7:documentationOf/hl7:serviceEvent the performer is not well included, we need to have an element performer that contains 2.16.840.1.113883.10.20.6.2.1 , the serviceEvent shall not contain 2.16.840.1.113883.10.20.6.2.1

Change Request Status = Open ( ccda-issue-4 ): relatedDocument

Type

Change Request

Status

Change Request Status = Open

Priority

Normal

Events

Tracking / Status = Open	2017-01-03 14:09:12 : Tracking by dr Kai U. Heitmann
Description	hl7:relatedDocument/hl7:id There is no id in relatedDocument

Change Request Status = Open ( ccda-issue-5 ): encouterParticipant

Type

Change Request

Status

Change Request Status = Open

Priority

Normal

Events

Tracking / Status = Open	2017-01-03 14:09:34 : Tracking by dr Kai U. Heitmann
Description	/hl7:componentOf/hl7:encompassingEncounter The encompassingEncounter need to have an element encouterParticipant that contains 2.16.840.1.113883.10.20.6.2.2, 2.16.840.1.113883.10.20.6.2.2 shall not be directly included in encompassingEncounter

Change Request Status = Closed ( ccda-issue-32 ): Erratum 673 Update to align with Schema [CONF:8414]

Type

Change Request

Status

Change Request Status = Closed

Priority

Normal

Events

Tracking / Status = Closed	2017-09-10 03:12:38 : Tracking by Lisa Nelson
Description	We used the temple editor to adjust hierarchy and change the conformance patterns.

Assignment

2017-09-01 17:17:38 : Assigned To dr Kai U. Heitmann by Lisa Nelson

Tracking / Status = Feedback needed	2017-09-01 17:17:29 : Tracking by Lisa Nelson
Description	See Tab 673 in spreadsheet for screen shot. When we attempted to add the associatedEntity (to replace the assingedPerson which was incorrect), we left assignedPerson there to make it easier to compare our new work. We planned to take it out after we finished adding the new associatedEntity.) We were not comfident that the structural representation was correct. AssociatedEntity/AssociatedPerson/name is needed. Adding the name element under associatedEntity seemed like it was missing a level in the hierachical structure.

Assignment

2017-08-30 12:29:58 : Assigned To Didi Davis by Lisa Nelson

Tracking / Status = Feedback needed	2017-08-30 12:29:50 : Tracking by Lisa Nelson
Description	Not sure how to make this change. There is both an element and an additional Schematron test that appears to be associated with the element.

Tracking / Status = In Progress

2017-08-30 12:21:19 : Tracking by Lisa Nelson

Tracking / Status = Open	2017-08-30 12:20:56 : Tracking by Lisa Nelson
Description	Finding: -Update to align with Schema. Suggestion: -Conformance Constraints prior to change: 6. MAY contain zero or one [0..1] participant (CONF:8414) such that it a. SHALL contain exactly one [1..1] assignedPerson (CONF:8415). i. This assignedPerson SHALL contain exactly one [1..1] name (CONF:9406). 1. The content of name SHALL be a conformant US Realm Person Name (PN.US.FIELDED) (2.16.840.1.113883.10.20.22.5.1.1) (CONF:10478). Conformance Constraints After Change: 6. MAY contain zero or one [0..1] participant (CONF:8414) such that it 1. SHALL contain exactly one [1..1] associatedEntity (CONF:26541). 1. This associatedEntity SHALL contain exactly one [1..1] associatedPerson (CONF:26542). 1. This associatedPerson SHALL contain exactly one 1..1] US Realm Person Name (PN.US.FIELDED) (identifier: urn:oid:2.16.840.1.113883.10.20.22.5.1.1) (CONF:26543). Further explanation: -CONF:8414

Structure Definitions (External repositories)

About/Legal