Access Models

Lab Network supports multiple ways to submit diagnostic orders, including API, the Lab Network UI, and embedded iFrame workflows. Regardless of how orders are submitted, results are retrieved through API-based access.

Access Model Comparison

Lab Network access models differ in capabilities and the level of integration required.

Notes:

• Structured results are returned through the API as FHIR DiagnosticReport and Observation resources.
• Document-based results are retrieved through the API using DocumentReference and Binary.
• The UI provides order-level visibility into result documents but does not support result retrieval.
• UI visibility is order-centric and intended for operational confirmation rather than longitudinal or aggregated result review.
• iFrame sessions are created through an API call that generates an order-entry URL, which is then launched in an embedded frame or browser context.

Lab Network API

API-based integration supports end-to-end electronic ordering and structured results retrieval. Orders are submitted and managed using FHIR R4 resources, and results are returned as normalized FHIR resources suitable for clinical systems, analytics platforms, and longitudinal records.

API access is appropriate when your organization needs full programmatic control over ordering, fulfillment tracking, and results ingestion.

Lab Network UI

The UI supports operational workflows for placing orders and reviewing order status and result documents. It provides order-centric visibility into order status and received result artifacts, such as attached documents, and is intended for operational confirmation rather than structured clinical review.

UI access is appropriate when people with appropriate permissions need to place orders or confirm receipt of results without building or maintaining an API-based workflow.

Lab Network iFrame

iFrame access supports embedded order placement within your application. It allows people with appropriate permissions to place orders through the Health Gorilla interface while remaining in your system’s workflow.

The iFrame is limited to order placement and does not support result display or retrieval.

iFrame access is appropriate when your organization wants to embed ordering without building a custom ordering interface and plans to consume results through APIs or review them in the Lab Network UI.

Choosing an Access Model

Most implementations use more than one access model. For example, UI or iFrame for order placement and API access for results retrieval. Selection depends on how your organization wants to place orders .

• Use API access when your system needs structured results for downstream processing, analytics, or clinical workflows.
• Use the Lab Network UI when people with appropriate permissions need to place orders or review order status and result documents without building integrations.
• Use iFrame access when your application needs embedded order placement and plans to consume results through APIs or the UI.

Limitations

Lab Network access models are designed to support specific roles within the ordering and results lifecycle. The following capabilities are intentionally out of scope:

• Lab Network does not provide real-time querying of external laboratories. Results become available only after laboratories complete processing and deliver them to Health Gorilla.
• The Lab Network UI is not a longitudinal clinical results viewer and does not aggregate results across patients or orders.
• The Lab Network iFrame does not support results display or retrieval.
• Automated downstream results ingestion and analytics workflows require API-based integration.
• UI-based workflows are not intended for high-volume or fully automated ordering scenarios.

These constraints reflect the separation between operational ordering workflows and programmatic results consumption.

Results Consumption

Lab Network delivers diagnostic results through API-based integration. Structured results are exposed as FHIR resources, and unstructured artifacts are available for retrieval through document-based endpoints.

The Lab Network UI and iFrame do not provide comprehensive clinical result access and are intended for order placement and operational confirmation only.