SITE C-CDA Validator – Occupation Code Value Set Version Mismatch (USCDIv3 / 170.315(b)(1))

[Chris Wilson]

Hello,

I work for a software company that develops an EHR, and we are running our C-CDA documents through the SITE Test Tool — specifically the USCDIv3 / Sender / 170.315(b)(1) ToC Ambulatory test case.

Through our investigation, we believe the C-CDA Validator is validating occupation codes against Version 1 of the Occupation ONETSOC Detail (ODH) value set (OID: 2.16.840.1.114222.4.11.7901), rather than the current version.

Background:

• Version 1 of this value set contained ~59,582 compound codes in a three-part format (e.g., 37-2011.00.028742)
• 
• Version 3 (the current published version, updated May 2025) contains 1,884 plain SOC-style codes (e.g., 37-2011) — the compound format no longer exists in the current standard
• 
• We have implemented Version 3 codes in our system, but the SITE validator is returning an error because our codes do not match the Version 1 compound format

CCDA Validator Error:

Questions:

1. Are other vendors encountering this same validation error, and if so, how are they handling it?
2. Given that our implementation aligns with the current published standard, should this error be treated as a validator defect and safely ignored?

Regards,

Chris Wilson

Director of Product [Real Time Payments]

 

 

P: 360-789-4221

E: chris....@officeally.com

www.officeally.com

[Jeff Cardenas]

I asked the same thing here a while back:
https://groups.google.com/g/edge-test-tool/c/nh0gVOQvZWU/m/cMV4bgMkAAAJ

And the consensus was that either version could be used:

https://groups.google.com/g/edge-test-tool/c/y6Norv6KH5g/m/KNxiMXQqAgAJ

You'd just have to work with your test proctor during the validation process to ignore this error and have them verify that the newer version is being used.

It would be nice if they updated the SITE Validator to check this automatically though.

[soumyajeet kanungo]

To ensure we can review this accurately, could you please confirm or provide the following (if not already included):

•        The C-CDA validation scenario you are running (criteria and scenario file name, if applicable)

•        The specific issue you are encountering

•        The relevant C-CDA XML document or snippet (please do not include any PHI/PII)

•        The exact error or warning message(s) observed (screenshots if available)