Integrations

Outside systems that send data into RaneemHCP or read from it, and how each one is doing.

This screen answersUS-47 OP-4 DS-2

Acceptance criteria

US-47 Inbound Diagnosis Integration (vendor-agnostic) MEDIUM NEW SCREEN

As a clinical/reception user, I want diagnosis data pulled from our clinical system into RaneemHCP, so that I don't re-enter diagnoses manually on the NPHIES-integrated system.

RaneemHCP accepts diagnosis data pushed from an external clinical system (WeCare or other) into the diagnosis page, reducing manual re-entry.
Input contract defined (probably we will consider FHIR Condition-but to investigate further).
integration remains vendor-agnostic.

OP-4 Background NPHIES poll P1 OPERATIONAL REVIEW

As the system, I poll NPHIES on a schedule, so answers and payer-issued authorizations are not missed.

Task poll shows the schedule, the last poll and the next one. Poll now stays as a fallback.
Every page shows the last poll in the top bar. A failed poll says so in the top bar.
New answers land in the Inbox. The administrator sets the interval (confirm the allowed rate on the NPHIES IG).

DS-2 Plugins, connection and credentials P1 ADDED BY SCOPE: DATA SOURCES

As a Super admin, I need to install a connector plugin and test the connection, so I know the hospital system answers before anything depends on it.

A plugin is a way to reach a source: REST or FHIR API, SQL database, HL7 feed, file drop (SFTP or CSV) or a vendor plugin. The catalog shows installed and available plugins.
Credentials are masked after saving and live in a vault, never in the portal database. Test connection shows what was reached, how fast and what failed.

Wireframe state

DefaultEmptyPoll schedule

Connected systems

Add API client

System	Direction	Format	Status	Last data	Today
WeCare clinical systemPushes diagnoses to the Diagnoses step	Diagnosis, inbound	FHIR Condition	Active	2 min ago	1,284 accepted, 2 quarantined
Al Raneem ERP finance feedReads claims and payment notices	Finance, outbound	JSON v1	Active	14 min ago	362 read
Lab results gatewayPlanned, not connected	Diagnosis, inbound	FHIR Observation	Not connected	Never	None

Inbound diagnosis contract

Any clinical system can push diagnoses if it follows this contract.

Resource: FHIR Condition, to be confirmed
Required: Patient, encounter, ICD-10-AM code, recorded date
Endpoint: POST /v1/diagnoses
Where it shows: Diagnoses step of the claim and prior authorization

Read the contractQuarantined responses

No systems connected

Connect a clinical system so diagnoses arrive without typing. Start by adding an API client with the Diagnosis scope.

Add API client

Inbound diagnosis contract

Any clinical system can push diagnoses if it follows this contract.

Resource: FHIR Condition, to be confirmed
Required: Patient, encounter, ICD-10-AM code, recorded date
Endpoint: POST /v1/diagnoses
Where it shows: Diagnoses step of the claim and prior authorization

Read the contractQuarantined responses

NPHIES outbox

See what is queued, retried or failed at NPHIES, and the last success.Open the outbox

Poll interval

Ask NPHIES for answers every

Between 5 and 60 minutes. The default is 15.

Runs

The poll does not stop at night or on weekends.

Note for the audit log (optional)

Saving is written to the audit log with the old and new interval and your name.

CancelSave interval

Last result

Last poll: 09:30, answered
Answers received: 3
Next poll: 09:45
If NPHIES does not answer: The poll is tried again at the next time and nothing is lost

Poll nowOpen the poll screen

Poll now is the fallback when someone is waiting for an answer.

NPHIES outbox

Requests saved while NPHIES did not answer wait here and are sent again by themselves. 3 are queued and 2 failed.

Open the outbox