Help
Login
Busy
Search
Consolidated CDA - Templates

 
Template locked

OK Not OK
Templates (External repositories)

Warning Ok
Warning
Filter
true50
Problem Observation (V3)
false
Issues (6)
false
Change Request Status = Closed ( ccda-issue-106 ): Erratum-1224 Update translation conformance
Type Change Request Status Change Request Status = Closed Priority Normal
Current Labels
 
 (COND) Conditional Conformance 
Events
Tracking / Status = Closed 2017-10-16 16:46:09 : Tracking by Lisa Nelson
 
 COND 
Tracking / Status = Feedback needed 2017-10-12 19:38:26 : Tracking by Lisa Nelson
 
 COND 
Assignment 2017-09-30 19:55:15 : Assigned To dr Kai U. Heitmann by Lisa Nelson
Description
Conditional Conformance
Assignment 2017-09-22 02:48:52 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-09-22 02:48:51 : Tracking by Lisa Nelson
Description
Finding:

-Update translation conformance 

Suggestion:

-Prior Conformance:
a. This code SHALL contain at least one [1..*] translation, which SHOULD be selected from ValueSet Problem Type urn:oid:2.16.840.1.113883.3.88.12.3221.7.2 2014-09-02 (CONF:1198-32848).
-Conformance After Update:
a. If code is selected from ValueSet Problem Type urn:oid:2.16.840.1.113883.3.88.12.3221.7.2 STATIC 2012-06-01, then it SHALL have at least one [1..*] translation, which SHOULD be selected from ValueSet Problem Type urn:oid:2.16.840.1.113883.3.88.12.3221.7.2 STATIC 2014-09-02 (CONF:1198-32950).

Further explanation:
1198-32848 or 1198-32950 ??

-

Change Request Status = Closed ( ccda-issue-178 ): CS-20180126-01 Value element should allow nullFlavor
Type Change Request Status Change Request Status = Closed Priority Normal
Current Labels
 
 (CS) Customer Support 
Events
Tracking / Status = Closed 2018-06-04 20:56:06 : Tracking by Didi Davis
 
 CS 
Description
This issue was never closed.  Verified this issue was fixed by rerunning the original document showing improper fail.  
https://gazellecontent.sequoiaproject.org/EVSClient/detailedResult.seam?type=CDA&oid=1.3.6.1.4.1.12559.11.28.1638

The rerun permanent link is  https://gazellecontent.sequoiaproject.org/EVSClient/detailedResult.seam?type=CDA&oid=1.3.6.1.4.1.12559.11.28.13272

ccda212440 allows nulls appropriately now. 
Assignment 2018-01-31 02:18:01 : Assigned To Abderrazek Boufahja by Lisa Nelson
Tracking / Status = In Progress 2018-01-31 02:17:43 : Tracking by Lisa Nelson
Description

This issue has been resolved. Message was sent to customer.

Assignment 2018-01-31 01:53:09 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2018-01-31 01:53:08 : Tracking by Lisa Nelson
Description
Finding:

-I am seeing an unexpected error when attempting to validate a CCD using the Sequoia C-CDA R2.1 validator.  It is not allowing a nullFlavor for the “value” element in the “Problem Observation (V3)” template.  However, the C-CDA R2.1 spec doesn’t state that nullFlavor isn’t allowed, nor does it require the @code attribute.  See info and screenshots below.

 

File Name         patient_CCDA_CCD_R2_1_altered.xml

OID :    1.3.6.1.4.1.12559.11.28.1638

Schematron :   N/A (Version N/A)

Schematron Validation Result :            N/A

Validation Date :           1/26/18 12:20:02 AM (CET GMT+0100)

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.1638

Data Visibility : Private - Owned By kstevenson / DOD

 

               

 

I believe the nullFlavor should be allowed for the “value” element since it isn’t specifically not allowed and the code attribute is not specifically required.

Suggestion:

-

Further explanation:

-

Change Request Status = Open ( ccda-issue-187 ): CS-Value Set Binding -Validation too tight
Type Change Request Status Change Request Status = Open Priority Normal
Current Labels
 
 (CS) Customer Support 
Events
Assignment 2018-04-30 22:26:14 : Assigned To Abderrazek Boufahja by Lisa Nelson
 
 CS 
Tracking / Status = Open 2018-03-26 23:14:01 : Tracking by Lisa Nelson
 
 CS 
Description
Added a CS label.
Tracking / Status = Open 2018-03-23 19:15:25 : Tracking by Lisa Nelson
Description
Researched the issue and sent a message to Abderrazek.
Assignment 2018-03-23 19:09:20 : Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2018-03-23 19:09:19 : Tracking by Lisa Nelson
Description
Finding:

-Validator is giving a Error when the value element of a Problem Observation is not coded using the value set which is only specified as a SHOULD.  
Permanent link :https://gazellecontent.sequoiaproject.org/EVSClient/detailedResult.seam?type=CDA&oid=1.3.6.1.4.1.12559.11.28.11084
The binding strength is given in Art Decor as --Not Set--, but there are  no other options available in the drop down list.

Suggestion: This situation should produce a WARNING, not a ERROR

-

Further explanation:

- Do I need to make a modification using Temple Editor?  What should the Coding Strength be?  What are the available options?  Where is this documented?

Request for Information/Education Status = Open ( phcrg-issue-30 ): Should we include all the optional template in IG
Type Request for Information/Education Status Request for Information/Education Status = Open Priority Normal
Events
Tracking / Status = Open 2015-11-03 16:37:32 : Tracking by Eric M Haas
Description
Finding:

-Should we include all the optional template in IG that PHRC does not care about.  (e.g. contains: 2.16.840.1.113883.10.20.22.4.113 Prognosis Observation (2015-08-13T00:00:00)
Suggestion:)

-Use other guides as guidance.  my philiosophy is to be silent on these 

Further explanation:

-

Change Request Status = Open ( phcrg-issue-32 ): missing contains for prognosis obs
Type Change Request Status Change Request Status = Open Priority Normal
Events
Tracking / Status = Open 2015-11-03 17:11:24 : Tracking by Eric M Haas
Description
Finding:

-missing contains for prognosis obs
Suggestion: 

-sent email to art decor add in here.

Further explanation:

-

Change Request Status = Open ( phcrg-issue-43 ): how to document constraints for symptoms and Diagnosis
Type Change Request Status Change Request Status = Open Priority Normal
Current Labels
 
 (CLAR)  
 
 (REUSE3)  
Events
Tracking / Status = Open 2015-11-03 20:12:13 : Tracking by Eric M Haas
 
 CLAR 
 
 REUSE3 
Description
Finding:

-how to document constraints for symptoms and Diagnosis

Suggestion:

-Discuss with AMS , check other IG's  want only diagnosis and symptoms without constraining template or valueset

Further explanation:

-

 
 
Busy
Structure Definitions (External repositories)