Your browser does not appear to support JavaScript. You may want to try one of the following:
You may want to try one of the following:
If the above does not work, try reloading the page yourself. Note that you will lose any unsaved changes:
shift
control
Show details
Hide details
This form has to be reloaded. This most likely happened because your session has expired, which might take to the login page. (If you think that you shouldn't see this message and that the problem persists, please contact support.)
-Incorrect binding change of patient name (change Person Name to Patient Name).
-Prior Conformance:
iv. This patientRole SHALL contain exactly one [1..1] patient (CONF:1198-5283).
1. This patient SHALL contain at least one [1..*] US Realm Person Name (PN.US.FIELDED) (identifier: urn:oid:2.16.840.1.113883.10.20.22.5.1.1) (CONF:1198-5284).
-Conformance After Update:
1. This patient SHALL contain at least one [1..*] US Realm Patient Name (PTN.US.FIELDED) (identifier: urn:oid:2.16.840.1.113883.10.20.22.5.1) (CONF:1198-5283). (CONF:1198-5284)
-CONF: 1198-5283 (1198-5284)This errata is actually processed against CONF-5284, not CONF1198-5283
-
-Prior Conformance
5. SHOULD contain zero or one [0..1] postalCode, which SHOULD be selected from ValueSet PostalCode urn:oid:2.16.840.1.113883.3.88.12.80.2 DYNAMIC (CONF:81-7294).
a. PostalCode is required if the country is US. If country is not specified, it's assumed to be US. If country is something other than US, the postalCode MAY be present but MAY be bound to different vocabularies (CONF:81-10025).
-Conformance After Update
a. If the country is US, the postalCode element is required but SHOULD have @nullFlavor if the postalCode is unknown. If country is not specified, it's assumed to be US. If country is something other than US, the postalCode MAY be present but MAY be bound to different vocabularies (CONF:81-10025).
-Add clarification on state requirement for US addresses.
-Prior Conformance -
3...
a. State is required if the country is US. If country is not specified, it's assumed to be US. If country is something other than US, the state MAY be present but MAY be bound to different vocabularies (CONF:81-10024).
5....
-Conformance After Update -
a. If the country is US, the state element is required but SHOULD have @nullFlavor if the state is unknown. If country is not specified, it's assumed to be US. If country is something other than US, the state MAY be present but MAY be bound to different vocabularies (CONF:81-10024).
5...
-US Realm Address Restricts address to 1 line, update to allow up to 4
-Prior Conformance6. SHALL contain exactly one [1..1] streetAddressLine (CONF:81-7291).-Conformance After Update6. SHALL contain at least one and not more than 4 streetAddressLine (CONF:81-7291).
-CONF:7291
-Make it clear that only document type codes are legal for ClinicalDocument.code (i.e. not discrete lab test LOINC codes, which should only be used for observation.code)
5. SHALL contain exactly one [1..1] code (CONF:1198-5253).
a. This code SHALL specify the particular kind of document (e.g., History and Physical, Discharge Summary, Progress Note) (CONF:1198-9992).
- Conformance After Update:
b. This code SHALL be drawn from the LOINC document type ontology (LOINC codes where SCALE = DOC) (CONF:1198-32948).
- (LOOK-up NEW CONF-ID from Trifolia)
Thank you for reporting this issue.
-I am seeing an unexpected error when attempting to validate a CCD using the Sequoia C-CDA R2.1 validator. It is requiring that the legalAuthenticator/assignedEntity/id be an NPI. However, the C-CDA R2.1 spec only indicates that the id/@root MAY be “2.16.840.1.113883.4.6”. 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
Submitter: Kent.Stevenson@MariTech.com
https://gazellecontent.sequoiaproject.org/EVSClient/detailedResult.seam?type=CDA&oid=1.3.6.1.4.1.12559.11.28.11902&privacyKey=nFmDmsLs7qqWLiOZ
The error resolved, the example contains authenticator with id with a nullFlavor, and it pass the validation
-2.16.840.1.113883.10.20.22.1.1 USRealmHeaderV3 CONF:1198-16823
legalAuthenticator.assignedEntity.id (you changed that already) but same seems to be the case with authenticator.assignedEntity.id
I fixed the id for the authenticator/assignedEntity by unchecking the mandatory flag.
https://gazellecontent.sequoiaproject.org/EVSClient/detailedResult.seam?type=CDA&oid=1.3.6.1.4.1.12559.11.28.11896&privacyKey=hnor4vXo3ZXdnEaf
The error fixed but few errors where found (and not found in the previous validation) because we missed to add some restrictions in some valuesets.
This has been corrected by Didi per instructions from Abderrazek: The Building Blocks need to be rebuilt to make effective.SEQUOIA-69 response from Abderrazek on May 14, 2018: The definition in ART-DECOR is wrong in C-CDA 2.1 indeed: https://gazellecontent.sequoiaproject.org/art-decor/decor-templates--ccda-?section=templates&id=2.16.840.1.113883.10.20.22.1.1&effectiveDate=2015-08-01T00:00:00&language=en-US
In administrativeGender you need to update mandatory with required , after that we need to regenerate the validation tool. I though that sequoia is managing these kind of modifications in ART-DECOR, and I remark that this modification is still not performed. Modifications in ART-DECOR should not ber performed by Gazelle team in order to keep consistency for sequoia.
-Stevenson, Kent J <Kent.Stevenson@ManTech.com>Thu 4/26/2018 12:57 PM
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 the use of nullFlavor for/ClinicalDocument/recordTarget/patientRole/patient/administrativeGenderCode. The constraint the validator indicates is being violated doesn’t say that nullFlavor cannot be used. Rather, it says that administrativeGenderCode element is required and must use the Administrative Gender (HL7 V3) value set. In section 3.6 of C-CDA R2.1 it states that unless nullFlavor is specifically prohibited or unless the terminology binding is to the @code attribute, a nullFlavor is allowed for required elements. The nullFlavor is not specifically prohibited for administrativeGenderCode and the terminology binding is to the element, not the @code attribute—so the use of nullFlavor should be allowed.
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
Validation Date : 4/25/18 4:14:49 PM (CEST GMT+0200)
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
- The validator is not producing the correct behavior. The assessment provided by the submitter is an accurate assessment of the validation expectations.
-It appears that Section 3.1.2 of the CCDA R2.1 May 2018 Implementation Guide an issue where the model is not properly documented to align with the IG. (http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2_IG_CCDA_CLINNOTES_R1_DSTU2.1_2015AUG_2018MAYwith_errata.zip)Here is the text from that section for your reference:
Volume 2 of this guide includes a requirement that all C-CDA R2.1 conformant instances:
By including both templateIds the sending application is asserting conformance with C-CDA R2.1 and C-CDA R1.1. This requirement is included at each document template. For example, Continuity of Care Document (CCD) (V3):
SHALL contain exactly one [1..1] templateId (CONF:1198-8450) such that it
The US Realm Header does not include an explicit compatability statement to allow reuse in other guides. When using a document template in C-CDA R2.1 it is expected systems will include C-CDA R1.1 and C-CDA R2.1 US Realm Header templateId.
It appears this template address a and be above but not c. I need Kai's help in modeling this in Art DecorSuggestion:
-Need Kai's help in adding this requirement to Art Decor: