Understanding Validation Ready: Purpose, Usage and Rules

Previously, ICU stays that had not yet been fully reported could be submitted with the discharge status "Not discharged". As a result, certain analyses, such as occupancy monitoring, did not always provide a fully accurate near real-time view.

With this variable, an ICU stay can be reported with a discharge date/time and discharge destination while still being marked as not validation ready. This allows the registry to use available data for purposes such as occupancy calculations without requiring full validation to be completed immediately.

How is the variable used?

ValidationReady = true

• The ICU stay has been fully reported and is ready for complete validation.
• A discharge date/time must be provided.
• All standard validation rules and requirements for mandatory modules are applied.

ValidationReady = false

• A discharge date/time may be provided, but the ICU stay is not yet ready for final reporting.
• Only selected validation rules are applied.
• Requirements for mandatory modules are not fully enforced until the ICU stay is marked as validation ready.

If the variable is omitted

• The ICU stay is processed as before.
• If a discharge date/time is provided, the ICU stay is considered validation ready.

Important considerations

• ValidationReady may only be set to true if a discharge date/time has been provided. Otherwise, a validation error will be generated.
• The validation rules affected by this setting are described in the XML and JSON format documentation.
• The output structure now also includes the FinalValidated column, indicating whether final validation has been completed for the ICU stay.

Time limit for final reporting

To ensure high data quality, ICU stays that are not marked as validation ready are monitored. If an ICU stay is still not marked as validation ready 90 days after the discharge date, a validation error will be generated. This ensures that final reporting is completed within a reasonable timeframe.