Loading...
Help
Login
Busy
Search
Consolidated CDA (Sequoia) - Templates
 
Template locked

OK Not OK
Templates (External repositories)

Warning Ok
Warning
Filter
Allergy - Intolerance Observation
Issues (2)
Change Request Status = Closed (ccda-issue-20): Erratum-381 Update binding on participantEntity/code [CONF:7419]
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-09-05 22:18:13: Tracking by Lisa Nelson
Description
We added the narrative conformance statement as specified for "After update" in the errata list.
Assignment2017-09-01 21:20:06: Assigned To dr Kai U. Heitmann by Lisa Nelson
Tracking / Status = Feedback needed 2017-09-01 21:19:46: Tracking by Lisa Nelson
Description
NOTE - this does not appear to have the 705 problem, but after discussing 705, we should come back to this one.
Tracking / Status = Closed 2017-08-28 23:21:12: Tracking by Lisa Nelson
Description
Used the gear tool to add the vocabulary. 
Assignment2017-08-25 14:40:08: Assigned To Didi Davis by Lisa Nelson
Tracking / Status = Feedback needed 2017-08-25 14:39:44: Tracking by Lisa Nelson
Description
Trying to assign this to Didi, but I can't see how to do that???
Tracking / Status = Feedback needed 2017-08-25 14:38:41: Tracking by Lisa Nelson
Description
I don't see how to make changes to CONF:7419 to add the Value Set binding.  Where is the screen do to this?  How do you add a new Value Set in Art Decor?
Assignment2017-08-25 14:36:36: Assigned To Lisa Nelson by Lisa Nelson
Tracking / Status = Open 2017-08-25 14:36:35: Tracking by Lisa Nelson
 
 CARD 
Description
Finding:

-1. RxNORM binding to TTY is too tight.

2. SNOMED is not allowed to record ingredients

Update to align with R2.0 VS

Suggestion:

- Conformance Statements Prior to Change

C-CDA R1.1 only included TTY=SCD (selecting the ingredient names) or TTY=GPCK (selecting the generic packs).


2. This playingEntity SHALL contain exactly one [1..1] code (CONF:7419).

...

Conformance Statements After Change:
2. This playingEntity SHALL contain exactly one [1..1] code, which SHALL be selected from ValueSet Substance-Reactant for Intolerance urn:oid:2.16.840.1.113762.1.4.1010.1 DYNAMIC (CONF:7419).

Further explanation:

-CONF:7419

Change Request Status = Closed (ccda-issue-24): Errata-643 Deter use of high-level Severity Element, add support for Criticality Observation [CONF:9961]
TypeChange RequestStatusChange Request Status = Closed PriorityNormal
Events
Tracking / Status = Closed 2017-11-08 17:52:30: Tracking by Lisa Nelson
Assignment2017-09-05 22:51:35: Assigned To Abderrazek Boufahja by Lisa Nelson
Assignment2017-09-05 18:21:42: Assigned To Abderrazek Boufahja by Lisa Nelson
Tracking / Status = Feedback needed 2017-09-05 18:21:32: Tracking by Lisa Nelson
Description
We fixed the conformance constraint, but need to have the schematron assert for CONF:9961.
Assignment2017-08-30 18:20:25: Assigned To dr Kai U. Heitmann by Lisa Nelson
Tracking / Status = Feedback needed 2017-08-30 17:49:47: Tracking by Lisa Nelson
Description
Issues found:

We are looking for: SHALL contain exactly one [1..1] Severity Observation (templateId:2.16.840.1.113883.10.20.22.4.8) (CONF:15956)
We are finding conf-9961 seems to include all the conformance logic of both CONF:9961 and CONF:15956.
We set the requirement to NP for the entryRelationship for the contained. Severity Template  to cause a SHOULD NOT. We can see the NP, but we can't see evidence that this is a SHOULD NOT.  (Question, how do you indicate SHALL NOT vs. SHOULD NOT?)

We added the 0..1 entryRelationship for the contianted Criticality Observation template. All conformance logic seems to be represented, but CONF:32910 seems to hold the logic for both CONF:32910 and CONF:32913.  
Assignment2017-08-25 22:48:04: Assigned To Didi Davis by Lisa Nelson
Tracking / Status = Feedback needed 2017-08-25 22:47:55: Tracking by Lisa Nelson
Tracking / Status = In Progress 2017-08-25 22:47:44: Tracking by Lisa Nelson
Description
Need to add an entry relationship to the newer Criticality Observation in addition to making use of the Severity Observation at the higher level be a SHALL NOT.

This seems straightforward once I learn how to add the additional entryRelationship.
Tracking / Status = Open 2017-08-25 22:45:09: Tracking by Lisa Nelson
Description
Finding:

-Add support for Criticality Observation 

Suggestion:

-Conformance Statements Prior to Updates:

13. SHOULD contain zero or one [0..1] entryRelationship (CONF:9961) such that it

a. SHALL contain exactly one [1..1] @typeCode="SUBJ" Has Subject (CodeSystem: HL7ActRelationshipType 2.16.840.1.113883.5.1002 STATIC) (CONF:9962).

b. SHALL contain exactly one [1..1] @inversionInd="true" True (CONF:9964).

c. SHALL contain exactly one [1..1] Severity Observation (templateId:2.16.840.1.113883.10.20.22.4.8) (CONF:15956)  (This statement is being questioned. Our implementation of the errata does not include this Conformance ID)

- Conformance Statements After Update:

13. SHOULD NOT contain zero or one [0..1] entryRelationship (CONF:9961) such that it

a. SHALL contain exactly one [1..1] @typeCode="SUBJ" Has Subject (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002 STATIC) (CONF:9962).

b. SHALL contain exactly one [1..1] @inversionInd="true" True (CONF:9964).

c. SHALL contain exactly one [1..1] Severity Observation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.8) (CONF:15956).

14. SHOULD contain zero or one [0..1] entryRelationship (CONF:32910) such that it

a. SHALL contain exactly one [1..1] @typeCode="SUBJ" Has Subject (CodeSystem: HL7ActRelationshipType urn:oid:2.16.840.1.113883.5.1002) (CONF:32911).

b. SHALL contain exactly one [1..1] @inversionInd="true" True (CONF:32912).

c. SHALL contain exactly one [1..1] Criticality Observation (identifier: urn:oid:2.16.840.1.113883.10.20.22.4.145) (CONF:32913). (This statement is being questioned. Our implementation of the errata does not include this Conformance ID)

Further explanation:

- CONF:9961, CONF:32910

 
 
Busy
Structure Definitions (External repositories)