Loading...
Help
Login
Busy
Search
Consolidated CDA - Template mapping
 
Template locked

OK Not OK
Filter
Datasets
Template Associations
Templates
Concept:
IdVersion
StatusVersion Label
Description
/
-
Care Plan (V2)
Issues (7)
Change Request Status = Closed (ccda-issue-43): Erratum-757 Including R1.1 templateId in compatible C-CDA R2.1 Instancces [CONF-32934]
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-10-03 15:00:52: Tracking by Lisa Nelson
Description
We added CONF 1198-32934 at the top of the document template.  THIS IS A HIGHLY PROBLEMATIC APPROACH to handling this need, but it was the best choice we could make at this time.
Assignment2017-10-03 06:30:05: Assigned To dr Kai U. Heitmann by Lisa Nelson
Description
I can't tell where the right place would be to put this conformance statement.
Assignment2017-09-18 06:17:50: Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-18 04:58:43: 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-32934]
Change Request Status = Closed (ccda-issue-112): Erratum-1048/1260 Fix Vocab binding for clinicalDocument.code
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Current Labels
 
 (TOOLING) Tooling questions or issues 
Events
Tracking / Status = Closed 2017-10-09 16:57:25: Tracking by Lisa Nelson
 
 TOOLING 
Assignment2017-10-03 22:06:34: Assigned To dr Kai U. Heitmann by Lisa Nelson
 
 TOOLING 
Tracking / Status = Open 2017-10-03 22:02:11: Tracking by Lisa Nelson
 
 TOOLING 
Description
We were able to update the constraint description, but the gear tool didn't allow us to make a new attribute in order add the vocabulary binding.

This code SHALL contain exactly one [1..1] @code, which SHALL be selected from ValueSet Care Plan Document Type urn:oid:2.16.840.1.113762.1.4.1099.10 DYNAMIC (CONF:1198-32959).

Is in limbo...inserted it into the conformance statements for the clinicalDocument.code
Assignment2017-09-30 19:39:06: Assigned To Didi Davis by Lisa Nelson
Description
Need to review how to create a new value set in Art Decor before I can execute this change.
Assignment2017-09-22 03:22:22: Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-22 03:22:21: Tracking by Lisa Nelson
Description
Finding:

-The clinicalDocument.code element of the Care Plan Document template is too narrowly defined - need to use a DYNAMIC binding

Suggestion:

-Prior Conformance:

SHALL contain exactly one [1..1] code (CONF:1198-28745).

a. This code SHALL contain exactly one [1..1] @code="52521-2" Overall Plan of Care/Advance Care Directives (CONF:1198-28746).

b. This code SHALL contain exactly one [1..1] @codeSystem="2.16.840.1.113883.6.1" (CodeSystem: LOINC urn:oid:2.16.840.1.113883.6.1) (CONF:1198-28747).

- Conformation After Update:

3. SHALL contain exactly one [1..1] code (CONF:1198-28745).

            a. This code SHALL contain exactly one [1..1] @code, which SHALL be selected from ValueSet Care Plan Document Type urn:oid:2.16.840.1.113762.1.4.1099.10 DYNAMIC (CONF:1198-32959).

Further explanation:

-CONF:1098-28746; CONF:1198-32959

Change Request Status = Closed (ccda-issue-113): Erratum-1267 Update to include parentDocument id reference
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Current Labels
 
 (TOOLING) Tooling questions or issues 
Events
Tracking / Status = Closed 2017-10-16 16:20:44: Tracking by Lisa Nelson
 
 TOOLING 
Tracking / Status = Feedback needed 2017-10-12 21:08:50: Tracking by Lisa Nelson
 
 TOOLING 
Assignment2017-10-12 20:27:20: Assigned To dr Kai U. Heitmann by Lisa Nelson
 
 TOOLING 
Description
I am trying to add an element and it won't go into the correct location.  Also, I am getting a resource error when I try to save the change (I added an element in the wrong place then tried to delete it.) 
Assignment2017-10-12 20:08:00: Assigned To Lisa Nelson by Lisa Nelson
 
 TOOLING 
Description
This one is still for Kai - what am i doing wrong that I don't see how to add a row to include the id element 
Assignment2017-10-12 20:03:24: Assigned To Didi Davis by Lisa Nelson
Assignment2017-09-30 19:37:31: Assigned To dr Kai U. Heitmann by Lisa Nelson
Description
Tool operation - can't figure out how to insert a row....None of the available options seem right for what I need to do.
Tracking / Status = Open 2017-09-30 19:35:14: Tracking by Lisa Nelson
Description
I could not figure out how to add another row above setId to Add an Element.  I'm not understanding how to insert additional conformances.  I tried add constraint and that wasn't right. None of the options seem to give me what I need.
Assignment2017-09-22 03:24:52: Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-22 03:24:51: Tracking by Lisa Nelson
Description
Finding:

- Update to include parentDocument id reference

Suggestion:

-Prior Conformance:

11.MAY contain zero or more [0..*] relatedDocument (CONF:1198-29893) such that it

a.SHALL contain exactly one [1..1] @typeCode, which SHALL be selected from ValueSet Related Document (append/replace) urn:oid:2.16.840.1.113883.11.20.9.62 STATIC (CONF:1198-31889).

b.SHALL contain exactly one [1..1] parentDocument (CONF:1198-29894).

i.This parentDocument SHALL contain exactly one [1..1] setId (CONF:1198-29895).

ii.This parentDocument SHALL contain exactly one [1..1] versionNumber (CONF:1198-29896).

-Conformance After Update

11. MAY contain zero or more [0..*] relatedDocument (CONF:1198-29893) such that it

a. SHALL contain exactly one [1..1] @typeCode, which SHALL be selected from ValueSet x_ActRelationshipDocument urn:oid:2.16.840.1.113883.1.11.11610 STATIC (CONF:1198-31889).

b. SHALL contain exactly one [1..1] parentDocument (CONF:1198-29894).

i. This parentDocument SHALL contain at least one [1..*] id (CONF:1198-32949).

ii. This parentDocument SHALL contain exactly one [1..1] setId (CONF:1198-29895).

iii. This parentDocument SHALL contain exactly one [1..1] versionNumber (CONF:1198-29896).

Further explanation:

-29893

Change Request Status = Closed (ccda-issue-117): Erratum-1288 Update purpose statement
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-09-30 19:15:23: Tracking by Lisa Nelson
Assignment2017-09-22 03:53:10: Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-22 03:53:09: Tracking by Lisa Nelson
Description
Finding:

-Update purpose statement

Suggestion:

-Prior Purpose Statement

Key differentiators between a Care Plan CDA and CCD (another “snapshot in time” document):


•  Requires relationships between various acts:

        o  Health Concerns

        o  Problems

        o  Interventions

        o  Goals

        o  Outcomes

-Purpose Statement After Change:

There are 2 required sections:

        o  Health Concerns

        o  Interventions

There are 2 optional sections:

        o  Goals

        o  Outcomes

A care plan document can include entry references from the information in these sections to the information (entries) in other sections.

Further explanation:

-

Change Request Status = Closed (ccda-issue-123): Erratum-1333 Retire Related Document Table, instead update Table 23: x_ActRelationshipDocument to include XFRM
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Current Labels
 
 (VALUESET) Value Set Issue 
Events
Tracking / Status = Closed 2017-10-09 15:57:26: Tracking by Lisa Nelson
 
 VALUESET 
Assignment2017-10-04 17:30:35: Assigned To Kai Heitmann by Lisa Nelson
 
 VALUESET 
Tracking / Status = Open 2017-10-04 17:15:48: Tracking by Lisa Nelson
 
 VALUESET 
Description
We want Kai to check if the concepts we added to the new value set we made (x_ActRelationshipDocument) are truly present in the Code System   HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002.
Assignment2017-09-29 23:24:14: Assigned To Didi Davis by Lisa Nelson
Description
Value Set issue
Assignment2017-09-22 04:15:33: Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-22 04:15:32: Tracking by Lisa Nelson
Description
Finding:

-Retire Related Document Table, instead update

Table 23: x_ActRelationshipDocument to include XFRM  

Suggestion:

-Prior Conformance:

11. MAY contain zero or more [0..*] relatedDocument (CONF:1198-29893) such that it

a. SHALL contain exactly one [1..1] @typeCode, which SHALL be selected from ValueSet Related Document (append/replace) urn:oid:2.16.840.1.113883.11.20.9.62 STATIC (CONF:1198-31889).


Table 25: Related Document (append/replace)

The Related Document value set is used to constrain a related document to two concepts - append and replace

APND HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Append

RPLC HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Replace


-Conformance After Update:

11. MAY contain zero or more [0..*] relatedDocument (CONF:1198-29893) such that it

a. SHALL contain exactly one [1..1] @typeCode, which SHALL be selected from ValueSet x_ActRelationshipDocument urn:oid:2.16.840.1.113883.1.11.11610 STATIC (CONF:1198-31889).                                                                                                                                                                           


Table 23: x_ActRelationshipDocument

Value Set: x_ActRelationshipDocument urn:oid:2.16.840.1.113883.1.11.11610

Used to enumerate the relationships between two clinical documents for document management.

Code Code System Code System OID Print Name

RPLC HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Replaces

APND HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Is appendage

XFRM HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Transformation

Further explanation:

-

Change Request Status = Closed (ccda-issue-131): Erratum-1333 Modify x_ActRelationshipDocument to include XFRM
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-10-04 17:45:51: Tracking by Lisa Nelson
Assignment2017-09-29 22:04:13: Assigned To Didi Davis by Lisa Nelson
Description
Value Set issue
Assignment2017-09-25 22:39:11: Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-25 22:39:10: Tracking by Lisa Nelson
Description
Finding:

-Modify x_ActRelationshipDocument to include XFRM
We didn't have this value set present in our value sets, so we also need to create it first.

Find this value set in VSAC first.

Suggestion:

-Prior Value Set Members:

The Related Document value set is used to constrain a related document to two concepts - append and replace

APND HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Append

RPLC HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Replace

- Value Set Members after the change:

Value Set: x_ActRelationshipDocument urn:oid:2.16.840.1.113883.1.11.11610

Used to enumerate the relationships between two clinical documents for document management.

Code Code System Code System OID Print Name

RPLC HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Replaces

APND HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Is appendage

XFRM HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 Transformation

Further explanation:

- Use the VSAC as the Source of Truth.

Change Request Status = Closed (ccda-issue-138): Erratum-814 Update 32367 to SHOULD value set binding
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-10-13 23:57:26: Tracking by Lisa Nelson
Assignment2017-09-29 20:48:50: Assigned To Didi Davis by Lisa Nelson
Tracking / Status = Open 2017-09-29 20:44:45: Tracking by Lisa Nelson
Description
I'm doing something wrong and the gear tool on the code element does not bring up options to add a vocabulary constraint on the @code.  Can't see how to get the @code added.
Assignment2017-09-26 01:27:04: Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-26 01:27:03: Tracking by Lisa Nelson
Description
Finding:

-Update 32367 to SHOULD value set binding

Suggestion:

-Prior:
1. The code, if present, SHALL contain exactly one [1..1] @code (ValueSet: Personal And Legal Relationship Role Type urn:oid:2.16.840.1.113883.11.20.12.1) (CONF:1198-32367).
-After Update:
1.    The code, if present, SHALL contain exactly one [1..1] @code, which SHOULD be selected from ValueSet Personal And Legal Relationship Role Type urn:oid:2.16.840.1.113883.11.20.12.1 DYNAMIC (CONF:1198-32367).

Further explanation:

-''32367, 

 
 
Busy