Help
Login
Search
Consolidated CDA - Templates

 
Template locked
OK Not OK
Templates (External repositories)
Warning Ok
Warning
Filter
true50
Unstructured Document –
false
Issues (2)
false
Change Request Status = Closed ( ccda-issue-25 ): Erratum 648 Relax constraint on id to allow more than one [CONF:7643]
Type Change Request Status Change Request Status = Closed Priority Normal
Events
Tracking / Status = Closed 2017-08-28 21:44:54 : Tracking by Lisa Nelson
Description
Reviewed and approved on 8/28/2017 TCON
Assignment 2017-08-28 21:44:16 : Assigned To Lisa Nelson by Lisa Nelson
Assignment 2017-08-28 21:40:17 : Assigned To Didi Davis by Lisa Nelson
Description
Can we confirm the M box and when to check it or not.
Tracking / Status = Closed 2017-08-28 21:06:02 : Tracking by Lisa Nelson
Description
We should look and just make sure I understand the M "mandatory" check box.
Assignment 2017-08-28 21:02:36 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-08-28 21:02:35 : Tracking by Lisa Nelson
Description
Finding:

-Theme - requiring only one id, when more than 1 is appropriate.

Suggestion:

-Conformance Constraint Prior to Change:
SHALL contain exactly one [1..1] recordTarget/patientRole/id (CONF:7643).
-Conformance Constraint Prior to Change:
SHALL contain or one  or more [1..*] recordTarget/patientRole/id (CONF:7643).

Findings:
CONF: 7643
Change Request Status = Closed ( ccda-issue-190 ): CS - Validation too tight on recordTarget/patientRole/addr/@use
Type Change Request Status Change Request Status = Closed Priority Normal
Current Labels
 
 (CS) Customer Support 
Events
Tracking / Status = Closed 2018-07-02 23:10:29 : Tracking by Lisa Nelson
 
 CS 
Description
This issue was re-logged under the ADDR template and was closed as #189.
Assignment 2018-04-30 22:48:49 : Assigned To Abderrazek Boufahja by Lisa Nelson
 
 CS 
Description
JIRA Ticket SEQUOIA-68
Assignment 2018-04-30 22:46:08 : Assigned To Lisa Nelson by Lisa Nelson
 
 CS 
Description
Additional issue/question discovered while reviewing this one.  Why is the cardinality of streetAddressLine [1..1] when the constraint logic says, SHALL contain at least one and not more than 4 streetAddressLine (CONF:81-7291)
Tracking / Status = Open 2018-04-29 22:24:02 : Tracking by Lisa Nelson
 
 CS 
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:05:31 : Assigned To Lisa Nelson by Lisa Nelson
 
 CS 
Tracking / Status = Open 2018-04-29 22:05:30 : Tracking by Lisa Nelson
 
 CS 
Description
Finding:

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

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.

File Name  patient1666580073_34133-9_2.16.840.1.113883.3.198^1666580073_34133-9_BFD....xml

OID : 1.3.6.1.4.1.12559.11.28.11289

Schematron : N/A (Version N/A)

Schematron Validation Result : N/A

Validation Date : 4/25/18 4:14:49 PM (CEST GMT+0200)

Model Based Validator : HL7 - C-CDA R2.1 - Meaningful Use Stage 3 (Version N/A)

Model Based Validation Result : FAILED SC

Permanent link : https://gazellecontent.sequoiaproject.org/EVSClient/detailedResult.seam?type=CDA&oid=1.3.6.1.4.1.12559.11.28.11289

Data Visibility : Public

Also, 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:

-
 
 
Structure Definitions (External repositories)