Integration Architecture
Important system responsibilities:
- Ocean is the provider-facing front end system and the eOrder API client.
- LifeLabs operates as the validation system, eOrder repository, SOPLR PDF-generation system, eOrder API client, and lab-side retrieval service.
- Participating labs/LIS retrieve and claim orders from the holding tank; they do not use Ocean as their primary receiver workflow.
| Integration | Design |
|---|---|
| Protocol/style | RESTful API, FHIR payloads/resources, and CDS Hooks validation. |
| Authentication | OAuth 2.0 client credentials - Ocean receives a client ID and client secret to obtain access tokens. |
| Order codes/catalogue | Ocean can retrieve ValueSet order codes and metadata such as display name, alias, additional information required, category, collection instructions, patient instructions, and last updated. |
| Validation | CDS validates an eOrder payload with LL and returns CDS response cards confirming validation. |
| Order creation | Ocean creates a new eOrder ServiceRequest in the LifeLabs system. |
| SOPLR PDF | Not returned synchronously but delivered asynchronously to Ocean as a FHIR Communication Bundle payload containing base64 PDF binary titled “soplr.pdf”. |
| Claim/status update | When LIS claims the SOPLR/order, eOrder sends a FHIR Task Bundle to Ocean with details such as date claimed and LIS accession identifier. |
| Retries | Ocean message retries occur immediately and several times in the first hour. If unsuccessful, Ocean will try once an hour for the next 96 hours. Every 24 hours, Ocean will send an email alert to the 'Clinical Administrator / Ocean Support Contact' listed on the Lifelabs eOrder site. After 96 hours, Ocean will abort attempts to reach the endpoint. Ocean will, however, continue to send daily emails. |