Testing Guidelines

Prerequisites

Shareback testing requires the following conditions:

• Shareback enabled for your organization in the sandbox environment
• Access to at least one submission method:
  • Patient360 UI
  • Health Gorilla FHIR APIs
• Ability to submit complete patient demographics and clinical data

Both manual and system-to-system submission workflows are supported for testing in the sandbox environment and are evaluated using the same patient matching logic.

Data Sharing

Clinical data submitted during testing represents information your organization would make available to other querying organizations in a production scenario. Submissions should reflect realistic, clinically appropriate content rather than synthetic or incomplete datasets that could interfere with patient matching or shareback readiness.

Relevance

Submitted data should meet the following expectations:

• Information reflects care delivered by your organization
• Test data aligns with realistic clinical scenarios
• Irrelevant or synthetic-only artifacts are avoided unless required for edge-case testing

Completeness

Clinical completeness improves shareback readiness:

• Submitting all relevant data from a care event is recommended
• Partial submissions may limit downstream usability
• C-CDA documents often provide the most complete clinical context in a single submission

Supported Formats

Health Gorilla supports multiple data formats for shareback testing.

Preferred formats:

• C-CDA documents
• Structured FHIR resources, such as:
  • Condition
  • MedicationStatement
  • AllergyIntolerance
  • Observation (labs and vitals)
  • Procedure
  • Encounter

Less preferred formats:

• PDF documents
• Images
• Other unstructured files

Unstructured formats may require manual review and are not reliably parsed into structured clinical data for reuse by querying organizations.