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
- CDA-CH-RESP - Emergency Service Protocol
- ELGA Basisleitfäden
- Überleitungsmanagement
- CH-PCC
- Consolidated CDA
- DGUV BBR
- eVent@home
- International Patient Summary (IPS)
- CDA-CH - Sandbox
- Development
Project
Datasets
Scenarios
Terminology
Templates
Issues
Login
- English (en-US)

url-scheme

Template locked

Templates (External repositories)

Filter

Templates


	Search true50
Templates

Policy Activity – Effective date

false

Issues (2)

false

Change Request Status = Closed ( ccda-issue-18 ): Erratum-277 HL7FinanciallyResponsiblePartyType value set associated with the wrong code system (CONF:16096)

Type

Change Request

Status

Change Request Status = Closed

Priority

Normal

Events

Tracking / Status = Closed

2017-09-13 03:26:00 : Tracking by Lisa Nelson

Assignment

2017-08-28 22:49:31 : Assigned To dr Kai U. Heitmann by Lisa Nelson

Tracking / Status = Feedback needed	2017-08-28 22:49:20 : Tracking by Lisa Nelson
Description	Reviewed in 8/28 TCON. We have more questions about how CONF numbers work between spec coming out of Trifolia and spec as implemented in Art Decor. See CONF: 8962 and CONF:16096. ALSO, this is another issue See CONF: 8961 We are comparing the conformance statement in the IG (R1.1) to what the see as two conformance statements in Art Decor (both labeled CONF:8961. The PRF seems like it should be "required" not "optional". What do you think?

Assignment	2017-08-23 19:45:37 : Assigned To Didi Davis by Lisa Nelson
Description	Missing CONF:16096 CONF:8962 does not match CONF:8962 in the HL7 CDA R1.1 IG 2012-12-21 errata release. CONF:8961 is duplicated. That is not correct.

Tracking / Status = Feedback needed	2017-08-23 19:45:15 : Tracking by Lisa Nelson
Description	Could not determine how to change the value set for the codes system associated with the coded concept "GUAR" in the AssignedEntity/code. Also concerned that the CONF: id does not match. We should be seeing CONF:16096, but I am not seeing this conformance statement.

Tracking / Status = In Progress

2017-08-23 19:26:55 : Tracking by Lisa Nelson

Tracking / Status = Open	2017-08-23 19:26:26 : Tracking by Lisa Nelson
Description	Finding: -The HL7FinanciallyResponsiblePartyType value set 2.16.840.1.113883.1.11.10416 incorrectly associates the RoleCode with code system 2.16.840.1.113883.5.110. Suggestion: -Prior Conformance Statements Fix table: Financially Responsible Party Value Set (excerpt) - update RoleCode to RoleClass which corresponds with the named OID. AND This code SHALL contain exactly one [1..1] @code="GUAR" Guarantor (CodeSystem: RoleCode 2.16.840.1.113883.5.111) (CONF:16096). Conformance Statements After Update: -This code SHALL contain exactly one [1..1] @code="GUAR" Guarantor (CodeSystem: RoleClass 2.16.840.1.113883.5.110) (CONF:16096). Further explanation: -CONF:16096

Change Request Status = Closed ( ccda-issue-34 ): Erratum 701 Update unnecessary cardinality restriction on playing entity name [CONF: 8930]

Type

Change Request

Status

Change Request Status = Closed

Priority

Normal

Events

Tracking / Status = Closed

2017-09-05 22:36:19 : Tracking by Lisa Nelson

Assignment

2017-09-01 20:47:39 : Assigned To dr Kai U. Heitmann by Lisa Nelson

Tracking / Status = Feedback needed	2017-09-01 20:47:29 : Tracking by Lisa Nelson
Description	this has the same issue as Erratum 691. See tab in spreadsheet.

Assignment

2017-08-30 12:49:21 : Assigned To Didi Davis by Lisa Nelson

Tracking / Status = Feedback needed	2017-08-30 12:49:13 : Tracking by Lisa Nelson
Description	Need to learn how to add a conditional conformance statement. "The playingEntity, if present, SHALL contain at least one [1..*] name.

Tracking / Status = In Progress

2017-08-30 12:45:54 : Tracking by Lisa Nelson

Tracking / Status = Open	2017-08-30 12:45:39 : Tracking by Lisa Nelson
Description	Finding: -Update unecessary cardinality restriction on playing entity name Suggestion: -Conformance Constraints Prior to Change: The playingEntity, if present, SHALL contain exactly one [1..1] name (CONF:8930). -Conformance Constraints After Change: The playingEntity, if present, SHALL contain at least one [1..] name (CONF:8930). Further explanation:* -CONF:8930

Structure Definitions (External repositories)

About/Legal