Help
Login
Busy
Search
Consolidated CDA - Templates

 
Template locked

OK Not OK
Templates (External repositories)

Warning Ok
Warning
Filter
true50
Unstructured Document (V3)
false
Issues (3)
false
Change Request Status = Closed ( ccda-issue-54 ): Erratum-757 Including R1.1 templateId in compatible C-CDA R2.1 Instancces [CONF-32944]
Type Change Request Status Change Request Status = Closed Priority Normal
Events
Tracking / Status = Closed 2017-10-25 01:59:36 : Tracking by Lisa Nelson
Assignment 2017-09-18 06:13:52 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-18 05:13:29 : 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-32944]
Change Request Status = In Progress ( ccda-issue-188 ): CS-20180326- Validation too tight on Ustructured Document
Type Change Request Status Change Request Status = In Progress Priority Normal
Current Labels
 
 (CS) Customer Support 
Events
Assignment 2018-07-02 23:45:59 : Assigned To Didi Davis by Didi Davis
 
 CS 
Tracking / Status = In Progress 2018-07-02 23:45:31 : Tracking by Didi Davis
 
 CS 
Description
This issue should have been logged to R1.1 2013-01-31 version of template.  This was corrected   in ART-DECOR the cardinality to 1..* ; this needs to remain in progress until validation tool is regenerated by rebuilding the building blocks. 
Tracking / Status = Open 2018-05-30 21:51:37 : Tracking by Didi Davis
 
 CS 
Description

From JIRA - Abderrazek Boufahja

Friday May 25, 2018 4:49 PM

In ART-DECOR we define that the author have the cardinality 1..1. The validation tool created the check accordingly. If we want to have more than one author per document, sequoia need to update in ART-DECOR the cardinality to 1..* ; and then we regenerate the validation tool.

Assignment 2018-05-25 16:56:01 : Assigned To Abderrazek Boufahja by Didi Davis
 
 CS 
Tracking / Status = Open 2018-05-25 16:55:48 : Tracking by Didi Davis
 
 CS 
Description

Abderrazek requested additional information including the testing permanent link.  Didi added the following to the JIRA ticket on 5/25/18. 

The issue reported referenced this permanent link:
https://gazellecontent.sequoiaproject.org/EVSClient/detailedResult.seam?type=CDA&oid=1.3.6.1.4.1.12559.11.28.11125

  • I am seeing an unexpected error when attempting to validate an Unstructured Document using the Sequoia C-CDA R1.1 validator. It is not allowing multiple <author> attributes. The constraint the validator indicates is being violated states that there can be only a single author/assignedAuthor in an <author> element, but doesn’t limit the document to only having a single <author> element.

However, the validator is enforcing only a single <author> element rather than a single <assignedAuthor> element.

Assignment 2018-04-30 22:26:03 : Assigned To Lisa Nelson by Lisa Nelson
 
 CS 
Description
JIRA ticket SEQUOIA-60
Tracking / Status = Open 2018-03-26 23:13:30 : Tracking by Lisa Nelson
 
 CS 
Description
Added a label.
Tracking / Status = Open 2018-03-26 18:02:29 : Tracking by Lisa Nelson
Description
I can't even find Conf-7640 in the Unstructured document of the US Realm header....not sure where this error is coming from.
Assignment 2018-03-26 17:57:08 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2018-03-26 17:57:07 : Tracking by Lisa Nelson
Description
Finding:

-The constraint indicated requires that the <author> element have exactly one <assignedAuthor> child element (the US Realm Clinical Docment Header :

Suggestion:

-However, the validator is enforcing only a single <author> element rather than a single <assignedAuthor> element.

Further explanation:

-

Change Request Status = Open ( ccda-issue-191 ): CS - Validation too tight on ClinicalDocument/recordTarget/patientRole/addr/@use
Type Change Request Status Change Request Status = Open Priority Normal
Current Labels
 
 (CS) Customer Support 
Events
Assignment 2018-04-30 22:47:10 : Assigned To Abderrazek Boufahja by Lisa Nelson
 
 CS 
Description
JIRA Ticket SEQUOIA-68
Tracking / Status = Open 2018-04-29 22:24:23 : Tracking by Lisa Nelson
Description
I think this issue is really on the US Realm Address template.  The @use attribute does not have a cardinality and it should.  

I also noted that addr in this template does have room for a cardinality, but nothing has been entered.  Should that be fixed too?
Assignment 2018-04-29 22:10:58 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2018-04-29 22:10:57 : Tracking by Lisa Nelson
Description
Finding:

Stevenson, Kent J <Kent.Stevenson@ManTech.com>
Thu 4/26/2018 12:44 PM

I am seeing an unexpected error when attempting to validate an Unstructured Document using the Sequoia C-CDA R1.1 validator.  It is requiring the /ClinicalDocument/recordTarget/patientRole/addr/@use attribute to be present.  The constraint the validator indicates is being violated explicitly states that the @use attribute can included “zero or one” times so it should not be required by the validator.

-Test

ccda21184 E - 1 Location/ClinicalDocument DescriptionIn US Realm Header (V3), the code of /hl7:ClinicalDocument[hl7:templateId/@root='2.16.840.1.113883.10.20.22.1.1']/hl7:recordTarget/hl7:patientRole/hl7:addr/@use SHALL be from the valueSet 2.16.840.1.113883.1.11.10637 (flexibility : 2005-05-01T00:00:00) (Item : CONF:81-7290)[  Constraint...  ] [  Assertion... ]TypeVocabulary

The C-CDA R2.1 spec indicates that the @use attribute is optional.  However, the Sequoia validator is requiring it to be present.


Suggestion:

-

Further explanation:

-


 
 
Busy
Structure Definitions (External repositories)