Help
Login
Busy
Search
Consolidated CDA - Templates

 
Template locked

OK Not OK
Templates (External repositories)

Warning Ok
Warning
Filter
true50
Progress Note (V3)
false
Issues (2)
false
Change Request Status = Closed ( ccda-issue-51 ): Erratum-757 Including R1.1 templateId in compatible C-CDA R2.1 Instancces [CONF-32942]
Type Change Request Status Change Request Status = Closed Priority Normal
Events
Tracking / Status = Closed 2017-10-24 16:24:27 : Tracking by Lisa Nelson
Assignment 2017-09-18 06:14:57 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-18 05:09:15 : Tracking by Lisa Nelson
Description
Finding:
- Including R1.1 templateId in compatible C-CDA R2.1 instances

Suggestion:
- Prior Conformance

 1. SHALL contain exactly one [1..1] templateId (CONF:1198-xxxx) such that it

 a. SHALL contain exactly one [1..1] @root="Doc Template root" (CONF:1198-xxxx).

 b. SHALL contain exactly one [1..1] @extension="Doc Template version" (CONF:1198-xxxx).

 c. When asserting this templateId, all document, section, and entry templates SHALL include a templateId root without an extension. See C-CDA R2.1 Volume 1 - Design Considerations for additional detail (CONF:1198-xxxx).


- Conformance After Update


2. SHALL contain exactly one [1..1] templateId (CONF:1198-xxxx) such that it

a. SHALL contain exactly one [1..1] @root="Root of Document" (CONF:1198-xxxx

b. SHALL contain exactly one [1..1] @extension="Template version" (CONF:1198-xxxxx).

c. When asserting this templateId, all C-CDA 2.1 section and entry templates that had a previous version in C-CDA R1.1 SHALL include both the C-CDA 2.1 templateId and the C-CDA R1.1 templateId root without an extension. See C-CDA R2.1 Volume 1 - Design Considerations for additional detail (CONF:1198-see below).

Further explanation: 
- [CONF:1198-32942]
Change Request Status = Closed ( ccda-issue-91 ): erratum-1010 Update the purpose of 1.1.19.2 componentOf under Progress Note
Type Change Request Status Change Request Status = Closed Priority Normal
Events
Tracking / Status = Closed 2017-10-03 06:03:19 : Tracking by Lisa Nelson
Description
I made the change and saved it, but the conformance I changed was CONF: 1198-7595 not the conformance that was listed in the errata:  CONF:7596.  This is just another example of how fragile and broken this whole constraint transformance and errata processing process truly is.
Assignment 2017-09-22 01:22:42 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-22 01:22:41 : Tracking by Lisa Nelson
Description
Finding:

-Update the purpose of 1.1.19.2 componentOf under Progress Note

Suggestion:

-Prior Conformance:

1.1.18.2 componentOf

The Progress Note is always associated with an encounter by the componentOf/encompassingEncounter element in the header. The effectiveTime element for an encompassingEncounter represents the time or time interval in which the encounter took

HL7 CDA R2.1 IG: Consolidated CDA Templates for Clinical Note (US Realm), DSTU R2—Vol. 2: Templates Page 194

August 2015 © 2015 Health Level Seven, Inc. All rights reserved.

place. A single encounter may contain multiple Progress Notes; hence the effectiveTime elements for a Progress Note (recorded in serviceEvent) and for an encounter (recorded in encompassingEncounter) represent different time intervals. All visits take place at a specific location. When available, the location ID is included in the encompassingEncounter/location/healthCareFacility/id element.

- Conformance After Update:

1.1.19.2 componentOf

The Progress Note is always associated with an encounter by the componentOf/encompassingEncounter element in the header. The effectiveTime element for an encompassingEncounter represents the time or time interval in which the encounter took place. A single encounter may contain multiple Progress Notes; hence the effectiveTime elements for a Progress Note (recorded in serviceEvent) and for an encounter (recorded in encompassingEncounter) represent different time intervals. For outpatient encounters that are a point in time, set effectiveTime/high, effectiveTime/low, and effectiveTime/@value to the same time. All visits take place at a specific location. When available, the location ID is included in the encompassingEncounter/location/healthCareFacility/id element.

Further explanation:

-CONF:7596

 
 
Busy
Structure Definitions (External repositories)