Submission Types
Health Gorilla supports a defined set of submission methods for contributing new or updated clinical data across products and workflows. Each submission type defines the format, supported FHIR resources, and processing behavior applied during intake and normalization.
The supported types ensure consistent handling of structured and unstructured data, promote reciprocity across the network, and provide a reference for programmatic submission through the FHIR API. Some submission types are available only for specific tenants or controlled implementations. Contact Health Gorilla for details.
FHIR Resource Submissions
The following table lists FHIR resource types that can be created or updated directly through the API using standard RESTful methods. Each submission is validated, normalized, and routed according to tenant configuration.
| Resource Type | Method | Typical Payload | Common Use Case |
|---|---|---|---|
Observation | POST, PUT | application/fhir+json | Submit discrete laboratory or vital sign results |
DiagnosticReport | POST, PUT | application/fhir+json | Share finalized laboratory or imaging reports |
Condition | POST, PUT | application/fhir+json | Submit active problem list entries or diagnoses |
Procedure | POST, PUT | application/fhir+json | Document completed or scheduled procedures |
Immunization | POST, PUT | application/fhir+json | Report vaccination history or new administrations |
AllergyIntolerance | POST, PUT | application/fhir+json | Submit medication or substance allergy data |
MedicationRequest | POST, PUT | application/fhir+json | Submit medication orders or prescriptions |
MedicationStatement | POST, PUT | application/fhir+json | Report adherence or patient-reported medication use |
CarePlan | POST, PUT | application/fhir+json | Contribute care management or treatment plans |
Goal | POST, PUT | application/fhir+json | Record patient care or treatment goals |
Document Submissions
Document submissions allow structured or unstructured clinical documents to be uploaded and shared through the network. Each document is linked to the corresponding patient and encounter, then indexed for retrieval.
| Document Type | Resource | Payload Type | Common Use Case |
|---|---|---|---|
| C-CDA | DocumentReference + Binary | application/xml | Submit comprehensive clinical summaries |
DocumentReference + Binary | application/pdf | Upload scanned reports, discharge summaries, or attachments | |
| Unstructured | DocumentReference | application/octet-stream | Submit narrative-only or system-generated documents |
| HL7 v2 (encapsulated) | Bundle | application/fhir+json | Submit HL7 v2 messages wrapped in a FHIR Bundle |
Diagnostic Result Submissions
Diagnostic submissions contribute laboratory, imaging, or pathology results for inclusion in a patient’s longitudinal record. Each result is linked to the ordering provider, encounter, and diagnostic report.
| Resource Type | Method | Payload Type | Common Use Case |
|---|---|---|---|
Observation | POST, PUT | application/fhir+json | Submit test results or vital measurements |
DiagnosticReport | POST, PUT | application/fhir+json | Transmit completed diagnostic findings |
ServiceRequest | POST, PUT | application/fhir+json | Provide context or linkage to originating orders |
Bulk and Asynchronous Submissions
High-volume or batched uploads should use asynchronous processing to improve reliability and throughput.
| Submission Type | Header | Monitoring | Common Use Case |
|---|---|---|---|
| Bulk Resource Upload | Prefer: respond-async | Poll job status endpoint | Submit large batches of FHIR resources |
| Bulk Document Upload | Prefer: respond-async | Poll job status endpoint | Upload large volumes of documents or attachments |
Implementation Details
- Submissions must include valid
patient,organization, andencounterreferences where applicable. - Unsupported resource types return a
422 Unprocessable Entityerror. - Binary attachments must include a corresponding
DocumentReferenceto associate patient, type, and metadata. - Asynchronous operations return a
202 Acceptedresponse with a job URL for status retrieval. - All submissions are logged for audit and traceability.
- Supported resource types and payloads may expand as new capabilities are released.