Skip to main content

Health Gorilla Lab Orders

Health Gorilla is an interoperability services used to order labs and diagnostics, and do records requests via API. Medplum offers a first party integration with Health Gorilla.


This is advanced integration. Email us for more information.

The Medplum toolkit provides tooling to optimize the physician ordering experience (CPOE), to minimize errors and enhance patient experience. A well defined workflow with diagnostic menu will help set you up for success. The workflows shown here are intended to reduce the amount of repeated data entry required by clinicians and staff.

This guide is not comprehensive, but is meant to be used as a tool in planning and scoping your lab orders workflow.

Workflow considerations

The following flowchart shows the most common workflows associated with Lab orders for illustration.

As indicated by the flowchart, designing your workflow will require making decisions about which of the nodes in the above flowchart apply to your workflow. Refer to the following table for major considerations and implementation implications.

ChoiceImplicationSamples (Medplum Team)
Lab MenuDetermines AOE questionsComing soon
Specimens onsiteEnter specimen date timeSample Req w/ collected date
Specimens offsiteShare requisition with patientSample PSC Hold
Medicare insuranceDiagnosis codesDiagnosis samples
Medicare insuranceShow patient ABN, and collect copaySample ABN
Multiple insurancesSend insurances in priority orderSample requisition
Release resultsShow patient PDF follow in state regulationsComing soon


Requisitions from Health Gorilla are PDFs, and have multiple use cases based off of the desired workflow. The below describes the sample use cases for requisitions.

Specimens collected on siteAttach requisition to sample when dropped off at labSample requisition
Specimens collected at third party labSend patient with requisition to labSample requisition
Bill provider accountSend patient with requisition but they will not need to provide paymentComing soon
Bill multiple insurancesSend specimen to lab and lab will bill both insurances in orderSample requisition


If collecting specimens on site, you'll need to provide the collection details and attach a printed specimen with barcode to the specimen to ensure correct chain of custody and turnaround times. This sample requisition shows an example of a PDF that should be printed and attached.


Medicare has two important integration features that need to be implemented in order to implement the workflow. These are (1) Advanced Beneficiary Notice (ABN) and (2) Diagnosis codes.

In an integration, and Advanced Beneficiary Notice (ABN) is a PDF that is generated by the Health Gorilla system for orders that are placed for patients with Medicare coverage. They give the patient an indication of their out of pocket cost for the lab test. The patient should be informed of their expected cost before testing. This is a Sample ABN.

In the majority of Medicare orders, patients need diagnosis codes added to their order to receive overage for the tests, so it's important to include those. These are ICD-10 codes, and a sample ValueSet with common ICD-10 codes can be downloaded

Diagnosis Codes

For all lab orders, entering diagnosis codes is a best practice, as interpretations of lab results can be a function of diagnosis.


In a lab implementation, you'll see the following abbreviations.

PSCPatient Service CenterIn a Quest workflow - if you place an order without a specimen and not to a specific center, it is a PSC workflow and the patient can walk into many Quest locations to have the order filled
AOEAsk on EntryFor a given lab test, there may be special questions only needed for that test - these are called Ask on Entry or AOE questions
ABNAdvanced Beneficiary NoticeThis is a document produced for Medicare patients indicating how much they are likely to pay out of pocket
ICD-10Diagnosis CodeThese are codes submitted with orders that indicate what medical conditions patients have
QNSQuantity Not SufficientWhen a report comes back with QNS, there was not enough specimen to do the test
TNPTest Not PerformedThis is seen on diagnostic reports where tests were not performed
NTINo test indicatedThis is another error case in the workflow usually related to missing or unclear labeling of specimens
NSPRNo specimen receivedAnother error workflow where specimens are not available
Patient BillPatient responsible for payingThis encompasses two cases: one where the patient pays out of pocket and the other where a patient shows their coverage card to the lab
Third Party BillInsurance responsibleIn this case, a patient's insurance is billed
Account BillOwner of lab account responsibleThis is common in clinical research and concierge care
  • Sample Implementation via Medplum Bot - this is reference material that can be used to plan your integration
  • React Component - this is a sample questionnaire that shows an ordering workflow