Guides
  1. Guides
  2. Patient360
  3. Shareback Testing

Submit Clinical Data

Clinical data submission supports testing of Patient360 shareback readiness. Submitted data is assessed for patient matching alignment, completeness, and readiness to be returned to querying organizations during retrieval.

Add Clinical Data Using the Patient360 UI

Manual submission is commonly used to test UI-based workflows, including category mapping, data completeness, and visibility behavior.

  1. Open the patient record created for shareback testing.
  2. On the left, select the appropriate clinical category:
    • Encounters
    • Diagnoses
    • Medications
    • Labs
    • Vitals
    • Procedures
  3. Toward the top, click + Add. The relevant page opens.
  4. Enter the clinical data for care provided by your organization.
  5. Click Save.

After data is saved:

  • Entries created by your organization are editable.
  • Data retrieved from other organizations is read-only.
  • Entries created by your organization are visually distinguished in the UI from externally sourced data.
  • Data is assessed for shareback readiness based on configuration, data type, and patient matching alignment.

Shareback readiness indicates that submitted data is associated with a valid patient identity, stored successfully, and eligible to be returned when another organization queries that patient. Shareback readiness does not guarantee immediate retrieval or distribution timing.

Submit Clinical Data Using Health Gorilla FHIR APIs

System-to-system submission supports automated shareback testing and integration readiness. You can submit clinical data as individual FHIR resources, as a Bundle, or as grouped resources that preserve clinical context.

Commonly submitted structured resources include:

  • Encounter
  • Condition
  • MedicationStatement
  • Observation
  • Procedure
  • DiagnosticReport

Example Request

POST https://sandbox.healthgorilla.com/fhir/R4/Encounter

Example Body

{
    "resourceType": "Encounter",
    "contained": [
        {
            "resourceType": "Condition",
            "id": "1",
            "meta": {},
            "extension": [
                {
                    "url": "https://www.healthgorilla.com/fhir/R4/StructureDefinition/record-provenance",
                    "valueReference": {
                        "reference": "Provenance/1203f465aa71ec36447deb4e"
                    }
                }
            ],
            "category": [
                {
                    "coding": [
                        {
                            "system": "http://snomed.info/sct",
                            "code": "282291009",
                            "display": "Diagnosis"
                        }
                    ],
                    "text": "HealthCare Org"
                }
            ],
            "code": {
                "coding": [
                    {
                        "system": "http://hl7.org/fhir/sid/icd-10",
                        "code": "K57.30",
                        "display": "Diverticulosis of large intestine without perforation or abscess without bleeding"
                    }
                ],
                "text": "Dvrtclos of lg int w/o perforation or abscess w/o bleeding"
            },
            "subject": {
                "reference": "Patient/{{patientId}}"
            }
        },
        {
            "resourceType": "Condition",
            "id": "2",
            "meta": {},
            "extension": [
                {
                    "url": "https://www.healthgorilla.com/fhir/R4/StructureDefinition/record-provenance",
                    "valueReference": {
                        "reference": "Provenance/1203f465aa71ec36447deb4e"
                    }
                }
            ],
            "category": [
                {
                    "coding": [
                        {
                            "system": "http://snomed.info/sct",
                            "code": "282291009",
                            "display": "Diagnosis"
                        }
                    ],
                    "text": "HealthCare Org"
                }
            ],
            "code": {
                "coding": [
                    {
                        "system": "http://hl7.org/fhir/sid/icd-10",
                        "code": "Z00.01",
                        "display": "Encounter for general adult medical examination with abnormal findings"
                    }
                ],
                "text": "Encounter for general adult medical exam w abnormal findings"
            },
            "subject": {
                "reference": "Patient/{{patientId}}"
            }
        },
        {
            "resourceType": "Location",
            "id": "3",
            "name": "HealthCare Org"
        }
    ],
    "extension": [
        {
            "url": "https://www.healthgorilla.com/fhir/StructureDefinition/record-recorder",
            "valueReference": {
                "reference": "Practitioner/f5b97056323db7a7c2cd930c"
            }
        },
        {
            "url": "https://www.healthgorilla.com/fhir/R4/StructureDefinition/record-provenance",
            "valueReference": {
                "reference": "Provenance/1203f465aa71ec36447deb4e"
            }
        }
    ],
    "identifier": [
        {
            "system": "urn:oid:2.16.840.1.113883.4.391.30867",
            "value": "576093"
        }
    ],
    "type": [
        {
            "coding": [
                {
                    "system": "urn:oid:2.16.840.1.113883.4.391.30867",
                    "code": "448",
                    "display": "(Citado New) Pte Nuevo con Cita"
                }
            ],
            "text": "HealthCare Org"
        }
    ],
    "subject": {
        "reference": "Patient/{{patientId}}"
    },
    "participant": [
        {
            "type": [
                {
                    "coding": [
                        {
                            "system": "http://terminology.hl7.org/CodeSystem/v3-ParticipationType",
                            "code": "PPRF",
                            "display": "primary performer"
                        }
                    ],
                    "text": "primary performer"
                }
            ],
            "individual": {
                "reference": "Practitioner/f5b97056323db7a7c2cd930c"
            }
        }
    ],
    "period": {
        "start": "2024-01-03"
    },
    "status": "cancelled",
    "class": {
        "system": "http://terminology.hl7.org/CodeSystem/v3-ActCode",
        "code": "IMP",
        "display": "inpatient encounter"
    },
    "diagnosis": [
        {
            "condition": {
                "reference": "#1"
            }
        },
        {
            "condition": {
                "reference": "#2"
            }
        }
    ],
    "location": [
        {
            "location": {
                "reference": "#3",
                "display": "HealthCare Org"
            }
        }
    ]
}

Example Response Header

HTTP/1.1 201 Created
Location: https://sandbox.healthgorilla.com/fhir/R4/Encounter/{encounterId}

Submit Structured Clinical Data Using the FHIR API

  1. Obtain an OAuth 2.0 access token with permission to create clinical resources.
  2. Prepare the clinical data to submit, either as:
    • A single FHIR resource, or
    • A Bundle containing multiple related resources for the same patient and encounter context.
  3. Submit the resource or Bundle to the appropriate sandbox FHIR R4 endpoint using an HTTP POST request (for example, POST https://sandbox.healthgorilla.com/fhir/R4/Encounter).
  4. Reference the correct Patient ID in each resource to ensure association with the intended patient.
  5. Verify that the request returns a 201 Created response (or 202 Accepted for asynchronous Bundle processing).
  6. Capture the returned resource or request identifier for testing and troubleshooting.

Successful submissions return identifiers that can be used to confirm storage, association, and shareback readiness.

Submit Documents Using Health Gorilla FHIR APIs

Document submission tests how clinical documents—such as CCDs, clinical notes, or other attachments—are associated with a patient and returned during retrieval. All documents are submitted using the DocumentReference resource and must be associated with an existing patient identity.

  1. Prepare the document content and encode it in Base64 format (a standard requirement for binary content in FHIR; most HTTP and API tooling provides built-in Base64 encoding).
  2. Create a DocumentReference resource referencing the correct Patient ID.
  3. Submit the resource to the appropriate sandbox FHIR R4 endpoint using an HTTP POST request (for example, POST https://sandbox.healthgorilla.com/fhir/R4/DocumentReference).
  4. Confirm receipt of a 201 Created response and capture the returned identifier.

Example Request (DocumentReference)

POST https://sandbox.healthgorilla.com/fhir/R4/DocumentReference
Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/fhir+json

Example Request Body

The following example shows a minimal DocumentReference submission for a C-CDA document.

{
  "resourceType": "DocumentReference",
  "status": "current",
  "type": {
    "coding": [
      {
        "system": "http://loinc.org",
        "code": "34133-9",
        "display": "Continuity of Care Document"
      }
    ],
    "text": "Continuity of Care Document"
  },
  "subject": {
    "reference": "Patient/{{patientId}}"
  },
  "content": [
    {
      "attachment": {
        "contentType": "application/xml",
        "title": "sample-import-ccda.xml",
        "data": "PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4gPENsaW5pY2FsRG9jdW1lbnQgLi4uPC9DbGluaWNhbERvY3VtZW50Pg=="
      }
    }
  ]
}

Example Response Header

HTTP/1.1 201 Created
Location: https://sandbox.healthgorilla.com/fhir/R4/DocumentReference/{documentReferenceId}

Documents are returned to querying organizations as document retrieval workflows. Parsing into structured data depends on document type and downstream system capabilities and is not guaranteed.

Submission Behavior During Testing

All submissions follow the same processing sequence during testing:

  • Patient identity is evaluated before data association.
  • Data is stored only when patient matching alignment succeeds.
  • Shareback readiness reflects successful storage and association of submitted data.

Sandbox submissions confirm behavior and readiness without initiating live data exchange.

Updated 18 days ago

What’s Next