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

- CDA-CH-EMED eMedication
- EHR4CR2eHDSI Project
- Export-Normdatensatz
- CDA-CH
- Consolidated CDA
- Continuity of Care Document (CCD)
- Emergency Encounter Report
- epSOS
- Sandbox X-eHealth
- gevko Sandbox
- Development
Project
Datasets
Scenarios
Terminology
Templates
Issues
Login
- English (en-US)

url-scheme

Template locked

Templates (External repositories)

Filter

Templates


	Search true50
Templates

Encounter Activity (V3) – Effective date

false

Issues (6)

false

Change Request Status = Closed ( ccda-issue-64 ): Erratum-797 Incorrect cardinality CONF-32177

Type

Change Request

Status

Change Request Status = Closed

Priority

Normal

Events

Tracking / Status = Closed

2017-10-09 17:33:12 : Tracking by Lisa Nelson

Assignment	2017-10-03 06:47:18 : Assigned To dr Kai U. Heitmann by Lisa Nelson
Description	I changed the description but could not see how to modify the cardinality expectation in the template.

Assignment

2017-09-18 06:11:08 : Assigned To Lisa Nelson by Lisa Nelson

Tracking / Status = Open	2017-09-18 05:57:25 : Tracking by Lisa Nelson
Description	Finding: - Incorrect Cardinality Suggestion: -Prior Conformance This sdtc:dischargeDispositionCode SHOULD contain exactly [1..1] @code, which SHOULD be selected from ValueSet 2.16.840.1.113883.3.88.12.80.33 NUBC UB-04 FL17-Patient Status (code system 2.16.840.1.113883.6.301.5) DYNAMIC or, if access to NUBC is unavailable, from CodeSystem 2.16.840.1.113883.12.112 HL7 Discharge Disposition (CONF:1198-32177). -Conformance After Update a.This sdtc:dischargeDispositionCode SHOULD contain zero or one [0..1] @code, which SHOULD be selected from ValueSet 2.16.840.1.113883.3.88.12.80.33 NUBC UB-04 FL17-Patient Status (code system 2.16.840.1.113883.6.301.5) DYNAMIC or, if access to NUBC is unavailable, from CodeSystem 2.16.840.1.113883.12.112 HL7 Discharge Disposition (CONF:1198-32177). Further explanation: -CONF:32177

Change Request Status = Closed ( ccda-issue-65 ): Erratum-798 Incorrect Cardinality CONF-32377

Type

Change Request

Status

Change Request Status = Closed

Priority

Normal

Events

Tracking / Status = Closed

2017-10-09 17:32:21 : Tracking by Lisa Nelson

Assignment	2017-10-03 06:51:11 : Assigned To dr Kai U. Heitmann by Lisa Nelson
Description	This is not making sense to me. Why do we have a constraint that has cardinality parameter when the element can't have its cardinality set?

Assignment

2017-09-18 06:10:50 : Assigned To Lisa Nelson by Lisa Nelson

Tracking / Status = Open	2017-09-18 06:00:29 : Tracking by Lisa Nelson
Description	Finding: -Incorrect Cardinality Suggestion: -Prior Conformance: b.This sdtc:dischargeDispositionCode SHOULD contain exactly [1..1] @codeSystem, which SHOULD be either CodeSystem: NUBC 2.16.840.1.113883.6.301.5 OR CodeSystem: HL7 Discharge Disposition 2.16.840.1.113883.12.112 (CONF:1198-32377). -Conformance After Update b.This sdtc:dischargeDispositionCode SHOULD contain zero or one [0..1] @codeSystem, which SHOULD be either CodeSystem: NUBC 2.16.840.1.113883.6.301.5 OR CodeSystem: HL7 Discharge Disposition 2.16.840.1.113883.12.112 (CONF:1198-32377). Further explanation: -CONF:32377

Change Request Status = In Progress ( ccda-issue-73 ): Erratum-825 Invalid codes in Encounter Type Code Value Set

Type

Change Request

Status

Change Request Status = In Progress

Priority

Normal

Events

Tracking / Status = In Progress	2017-10-23 23:08:33 : Tracking by Lisa Nelson
Description	Added STU Comment 1477 The EncounterType Value Set 2.16.840.1.113883.3.88.12.80.32 has a newer version 2017-09-15 that has a status of Published in the authoring area of the VSAC. However, this version of the value set is not available from the Value Set Search side of the VSAC. The only versions we see as available for downloading are versions: 2017-06-09 and 2017-06-23. We think there is a problem that the latest published version of the value set is not available from the Value Set Search or from the C-CDA R2.1 filter.

Assignment	2017-09-28 02:48:00 : Assigned To Didi Davis by Lisa Nelson
Description	Need training on Value Set updates.

Assignment

2017-09-18 15:40:58 : Assigned To Lisa Nelson by Lisa Nelson

Tracking / Status = Open	2017-09-18 15:40:57 : Tracking by Lisa Nelson
Description	Finding: -Invalid codes in Encounter Type Code Value Set Suggestion: -Prior Conformance- Value Set: EncounterTypeCode urn:oid:2.16.840.1.113883.3.88.12.80.32 This value set includes only the codes of the Current Procedure and Terminology designated for Evaluation and Management (99200 – 99607) (subscription to AMA Required Value Set Source: http://www.amacodingonline.com/ ------------ Snowmed Codes included. -Conformance After Update- Value Set: EncounterTypeCode urn:oid:2.16.840.1.113883.3.88.12.80.32 This value set includes only the codes of the Current Procedure and Terminology designated for Evaluation and Management (99200 – 99607) (subscription to AMA Required) Value Set Source: https://vsac.nlm.nih.gov/ --------- Snowmed Codes were removed. Further explanation: -

Change Request Status = Closed ( ccda-issue-108 ): Erratum-1239 Incorrect binding on the typeCode for participants used to encode a Service Delivery Location.

Type

Change Request

Status

Change Request Status = Closed

Priority

Normal

Events

Tracking / Status = Closed	2017-09-30 19:53:17 : Tracking by Lisa Nelson
Description	Has the font problem I just noticed and will be speaking with Kai about.

Assignment

2017-09-22 03:13:15 : Assigned To Lisa Nelson by Lisa Nelson

Tracking / Status = Open	2017-09-22 03:13:14 : Tracking by Lisa Nelson
Description	Finding: -Incorrect binding on the typeCode for participants used to encode a Service Delivery Location. Change HL7ActRelationshipType to HL7ParticipationType. Suggestion: -Prior Conformance: a. SHALL contain exactly one [1..1] @typeCode="LOC" Location (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 STATIC) (CONF:1198-8740). b. SHALL contain exactly one [1..1] Service Delivery Location (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.32) (CONF:1198-14903). -Conformance After Update: a. SHALL contain exactly one [1..1] @typeCode="LOC" Location (CodeSystem: HL7ParticipationType urn:oid:2.16.840.1.113883.5.90 STATIC) (CONF:1098-7766). b. SHALL contain exactly one [1..1] Service Delivery Location (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.32) (CONF:1098-15912). Further explanation: Encounter Activity (V3) 1198-8740 became 1198-7766

Change Request Status = Open ( phcrg-issue-38 ): assign externally defined valueset

Type

Change Request

Status

Change Request Status = Open

Priority

Normal

Current Labels

(TOOL)

Events

Assignment	2015-12-29 17:52:15 : Assigned To Eric M Haas by Alexander Henket TOOL
Description	Go to the Terminology > Value set menu item Click the button that has a Chain symbol above the Value Set list. It has a hint "New Value set Reference" Search based on id or name. ID worked just fine I've added it for you, so you should be all set. Let us know if that did not solve it for you.

Assignment

2015-11-03 19:44:40 : Assigned To Eric M Haas by Eric M Haas

TOOL

Tracking / Status = Open	2015-11-03 19:44:39 : Tracking by Eric M Haas TOOL
Description	Finding: -assign externally defined valueset Suggestion: -Value Set: EncounterTypeCode urn:oid:2.16.840.1.113883.3.88.12.80.32. This reference not found and need to assign reference. discuss with AD Further explanation: -

Change Request Status = Open ( phcrg-issue-39 ): entry template required but 0..1 in CCDA

Type

Change Request

Status

Change Request Status = Open

Priority

Normal

Current Labels

(Reuse1)

Events

Tracking / Status = Open	2015-11-03 19:48:39 : Tracking by Eric M Haas Reuse1
Description	Finding: -entry template required but 0..1 in CCDA: ServiceDeliveryLocation, Indication, Encounter Diagnosis Suggestion: -Discuss option of constraining templates Further explanation: -

Structure Definitions (External repositories)

About/Legal