USCDI v4 C-CDA Validator: Error for Facility type 1160-1 for 170.315_b1_ToC_Inp sample1

50 views
Skip to first unread message

surb...@gmail.com

unread,
Sep 24, 2026, 12:46:49 PMSep 24
to Edge Test Tool (ETT)
Hello,

We are testing a C-CDA with the USCDI v4 C-CDA Validator (https://site.healthit.gov/c-cda/uscdi-v4) and are getting a scenario-matching error that doesn't seem to match the published test data. Could you check whether the validator's reference data for this scenario is correct?

Validator settings:
- System: Sender
- Validation criteria: 170.315_b1_ToC_Inp
- Scenario file: 170.315_b1_toc_inp_svap_uscdiv4_sample1_v1.pdf

Error returned:
"The scenario contains Facility data with type 1160-1, however there is no matching data in the submitted CCDA."

What we found:
1. The scenario PDF lists the Encounter's Service Delivery Location with Facility Type 1027-2 (Medical Critical Care), Healthcare Service Location code system (2.16.840.1.113883.6.259).
2. Code 1160-1 (Urgent Care Center) doesn't appear anywhere in the scenario PDF, and neither does any urgent care facility.
3. Our document has a Service Delivery Location (templateId 2.16.840.1.113883.10.20.22.4.32) in the Encounter Activity, coded 1027-2 in 2.16.840.1.113883.6.259, with a facility identifier and name. The 1160-1 error still appears.

Questions:
1. Is 1160-1 intended to be part of this scenario? If so, which section or entry should carry it (for example Encounter, Procedure, or another activity)?
2. If not, could the validator's reference data be updated to match the PDF, or could you confirm that the published PDF is out of date?
3. Until this is resolved, is this error acceptable for certification testing, or is there a workaround you recommend?

Attached is the CCD XML file as well as scenario file for quick reference.

Thank you,
Surbhit Jain
Cert01_new_b7640995-dc44-41a8-9df3-0ee159e13a61.xml
170.315_b1_toc_inp_svap_uscdiv4_sample1_v1 (2).pdf

surbhi...@gmail.com

unread,
Oct 3, 2026, 12:41:11 PMOct 3
to Edge Test Tool (ETT)
Hello,

Is there any update to this?

Reply all
Reply to author
Forward
0 new messages