Skip to Main Content

General Questions

Announcement

For information related to the Oracle Partner Network (OPN) Industry Healthcare Track please visit our OPN Industry Healthcare Program page.

For specific questions related to Oracle Partner Network (OPN), please contact Partner Assistance.

Millennium FHIR and non-FHIR API Specifications and Supporting Documents can be found HERE on docs.oracle.com
Soarian FHIR API Specifications and Supporting Documents can be found HERE on docs.oracle.com.

How to integrate Cerner EHR with a local PC application

HYEONGGEUN JEONMar 13 2025 — edited Mar 13 2025

I am working on integrating Cerner with a LB120(PC-based application, C# Winform) at the request of a hospital.

LB120 will be installed and used on hospital PCs.

We aim to:

  1. Receive patient information from Cerner (id, sex, height, day of brith (age))
    1. Cerner → LB120
  2. Perform body composition analysis using a medical device
    1. LB120 ←→ Medical device
  3. Send the measured data back to Cerner
    1. LB120 → Cerner

What is the best way to achieve this?

The hospital is located in another country.

I can implement HL7 FHIR, HL7 V2.

I have registered a local PC-based application (LB120) in Oracle Health Code and am testing its integration.

The program will be used on hospital PCs.

What is the best way to handle authentication in this environment?

I am now trying to test OAuth 2.0 authentication.

How should I configure the URLs (such as redirect URI, authorization URL, and token endpoint) for proper authentication and testing?

Background Information:

Failure to provide answers will impact our ability to respond in a timely and effective manner
Developer questions:

Are you an OPN Member? Yes
Have you signed up to be in the Healthcare Developer Track? Yes
Are you a registered Code Program member? Yes
Does your App have a presence on the Oracle Healthcare App Marketplace? No

Are you developing on behalf of an Oracle Health client? Yes
If so, which client:

Application Name : LB120

Application ID : 6a21fcef-6ffd-468a-946e-c9469231f4db

Client ID : 9f3ca5b1-7d52-4aa3-9c6f-5933dd7a0b49

Comments
Post Details