Validating Shareback Readiness

Shareback testing confirms whether submitted data is correctly associated with a patient, stored successfully, and ready to be returned when another organization queries that patient. Validation focuses on readiness and system behavior in the sandbox environment, not on live distribution or downstream consumption.

Validation

Validation begins after patient creation and data submission are complete in the sandbox. Shareback readiness can be confirmed by verifying the following:

• Submitted data is associated with the intended patient
• Data appears correctly in the Patient360 UI or through retrieval workflows
• No unexpected duplicate patient records are created

Successful validation indicates that the system has accepted and associated the data and that it is ready for shareback based on current matching behavior. It does not guarantee when or how often the data will be retrieved.

Common Scenarios

The following outcomes are expected during sandbox testing and reflect how the system processes submitted data.

New Patient Created

Creation of a new patient record typically indicates demographic misalignment. Common causes include:

• Demographic values differ across submissions
• Required demographic fields are missing or inconsistent
• Multiple submissions use similar but not identical patient information

Using stable, consistent demographics across all submissions reduces this outcome.

Data Not Returned During Retrieval

Missing data during retrieval may indicate one or more of the following:

• Partial clinical submissions that lack sufficient context
• Document-only submissions without accompanying structured data
• Data submitted under a different patient match

In sandbox testing, retrieval results reflect system processing and readiness rather than guaranteed delivery. Complete submissions and consistent patient matching improve retrieval results.

Unstructured Data Visibility

Unstructured documents, such as PDFs or images, are returned as documents:

• Parsing into structured data is not guaranteed
• Downstream systems determine how documents are displayed or used

UI and API Validation Differences

UI-based and API-based submissions follow the same processing rules. Differences typically relate to visibility during testing:

• UI submissions allow near-immediate visual confirmation
• API submissions require retrieval or API-based validation to confirm association

This behavior is expected and does not indicate a failure of shareback readiness.

Sandbox Behavior Notes

Sandbox testing validates shareback readiness without initiating live data exchange:

• Data is not distributed to production networks
• Timing and visibility reflect system behavior rather than on-demand delivery
• Results support readiness and integration testing, not operational monitoring or SLA verification