USCDIv3 b1 Amb - procedure effective time value error

[Jessica Ordoyne]

We are receiving the below error:

Result Description: The Effective Time element for Procedure Act Procedure Entry corresponding to the code 56251003 (value time element ) is required, but submitted CCDA does not contain the (value time element) for Effective Time element for Procedure Act Procedure Entry corresponding to the code 56251003

We currently send the effectiveTime with a low and high value for procedure, and we were passing this test before this latest validator update. The release notes mention a change to the procedure time validation, but they seem to indicate it is only for USCDIv4. Why is it triggering this error on USCDIv3?

[Arslan Iqbal]

Hi - Thanks for reaching out. This has been logged for review and a member of the team will reach out in the near future.

Internal reference: SITE-4567

[Glenn Jenkins]

Same issue for me today, it worked OK on 3/28/25

[Braeden Rai]

We are also seeing this now, any updates on whether this should be an error?

[Arslan Iqbal]

SITE/ETT team's internal reference SITE-4567

[Braeden Rai]

Quick note that we are seeing this for the b1 Inpatient sample 2 patient, John Wright.

[Lara Shkordoff]

Hi - is there any update here? Can you confirm this is a bug in the validator? We are getting the same error for patient John Wright. Thanks!

[Lara Shkordoff]

Hi - we are getting the same error here. Can you confirm this is a bug and that it will get fixed? Thanks!

[Braeden Rai]

Hi, are there any updates on this?

[Lara Shkordoff]

Hi there - can we receive an update here? Thank you!

[Braeden Rai]

We are also still waiting for an update on this, will this be looked at soon?

[Miles Williams]

Hello, any update on this issue?

[Miles Williams]

Pinging again, any update?

[Arslan Iqbal]

We're continuing to work on this and will share an update as soon as possible. Thanks for your patience.

-SITE/ETT team

[Miles Williams]

Hello, any update here?

[Arslan Iqbal]

We're continuing to work on this and will share an update as soon as possible. Thanks for your patience.

-SITE/ETT team

[Mat Davis]

Hi all - I was reviewing some Github docs and looks like an update was made to help address this issue.

Release Notes

4.1.5 | Released on 6/23/2025

• Content Validator API updated to version 1.1.2

  • Update procedure activity procedure entry effective time comparison to use either value or low/high value. (SITE-4567)
  • Update planned procedure comparison to check both "plan of treatment" and "assessment and plan" sections. (SITE-4555)

After Testing

1 - This Works

<effectiveTime value="20150622"></effectiveTime>

2 - This Works
            <effectiveTime>
                <low value="20111005" />
                <high value="20111005" />
              </effectiveTime>

3 - This Works

            <effectiveTime>
                <low nullFlavor="UNK" />

                <high value="20111005" />

              </effectiveTime>

4 - This Does Not Work with 170.315_b1_ToC_Amb > uscdiv3_sample1_v1.pdf

THIS IS EXPECTED BASED OFF THE SCENARIO FILE

            <effectiveTime>
                <low value="20111005" />
                <high nullFlavor="UNK" />
              </effectiveTime>

EXPECTED Error

Result Description: The Effective Time element for Procedure Act Procedure Entry corresponding to the code 56251003 (value time element) is required, but submitted CCDA only contains the (low time element) for Effective Time element for Procedure Act Procedure Entry corresponding to the code 56251003, value, both low and high, or just high must be supplied

Thanks - Mat

[Sean Muir]

4 - This Does Not Work with 170.315_b1_ToC_Amb > uscdiv3_sample1_v1.pdf

THIS IS EXPECTED BASED OFF THE SCENARIO FILE

            <effectiveTime>
                <low value="20111005" />
                <high nullFlavor="UNK" />
              </effectiveTime>

Per internal conversation - high or value was always required and null flavor was not acceptable - 

I do not see using low define in the sample - can you elaborate on where in the pdf you see the use of low and null flavor ?

[Mat Davis]

Thanks for your reply Sean. My example was only to illustrate the outcome with the latest code changes. 

I’m not recommending or suggesting any changes need to be made. 

Note my all caps NOTE that this failure is expected and the error message is very helpful and sensible based on the scenario file. 

Thanks -Mat

--
You received this message because you are subscribed to the Google Groups "Edge Test Tool (ETT)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to edge-test-too...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/edge-test-tool/4fcf4ef5-d4b2-44f6-bfe0-ff087c469002n%40googlegroups.com.

[James Spillman]

Locking this conversation. If you're still having an issue please start a new conversation.