Source health
Connector status and what happens on each daily screen when a source is down.
You can see the status. Only the Super admin changes Data sources.
Everything is healthy. All three connectors answer normally.
Hospital system (FHIR R4)
Healthy
- Last success
- 08:41
- Latency
- 212 ms
- Error rate
- 0.2 percent
Billing database (SQL Server)
Healthy
- Last success
- 08:40
- Latency
- 95 ms
- Error rate
- 0.0 percent
SFTP price list (CSV)
Healthy
- Last success
- 05 Oct 06:00, file received
- Latency
- Not applicable
- Error rate
- 0.0 percent
Fallback per entity
| Entity | Source | When the source is down | What a receptionist sees |
|---|---|---|---|
| Patients | Hospital system (FHIR R4) | Receptionist sees the last known patient, marked "Last known data from 08:00". | |
| Practitioners | Hospital system (FHIR R4) | Care team picker shows the last known list. | |
| Service and price catalogue | Billing database (SQL Server) | Officer types the service and price by hand, flagged "Not verified at the source". | |
| Coverage and members | Hospital system (FHIR R4) | New eligibility checks wait. A message explains why. |
Block new requests, allow manual entry, or read the last known data. Pick per entity.
Save fallback settings
The hospital system is not answering since 08:12. Next automatic try in 00:42. RaneemHCP tries every minute and alerts the Super admin after 3 failed tries.
Hospital system (FHIR R4)
Down
- Last success
- 08:00
- Latency
- No answer
- Error rate
- 100 percent since 08:12
Billing database (SQL Server)
Healthy
- Last success
- 08:40
- Latency
- 95 ms
- Error rate
- 0.0 percent
SFTP price list (CSV)
Healthy
- Last success
- 06:00, file received
- Latency
- Not applicable
- Error rate
- 0.0 percent
Daily screens affected
- Patient lookup: shows last known data, marked as such
- Practitioner picker: shows the last known list
- Coverage and member checks: new checks are blocked
- Services: still read from the billing database
- Payer step: imported copy, not affected
- Diagnosis search: stored here, not affected
Fallback per entity
| Entity | Source | When the source is down | What a receptionist sees |
|---|---|---|---|
| Patients | Hospital system (FHIR R4) | Receptionist sees the last known patient, marked "Last known data from 08:00". | |
| Practitioners | Hospital system (FHIR R4) | Care team picker shows the last known list. | |
| Service and price catalogue | Billing database (SQL Server) | Officer types the service and price by hand, flagged "Not verified at the source". | |
| Coverage and members | Hospital system (FHIR R4) | New eligibility checks wait. A message explains why. |
Block new requests, allow manual entry, or read the last known data. Pick per entity.
Save fallback settings
The hospital system is slow. Answers take about 4 seconds and 6 percent of reads fail. Screens still work, but lookups feel slow.
Hospital system (FHIR R4)
Degraded
- Last success
- 08:41
- Latency
- 4,100 ms
- Error rate
- 6 percent of reads fail
Billing database (SQL Server)
Healthy
- Last success
- 08:40
- Latency
- 95 ms
- Error rate
- 0.0 percent
SFTP price list (CSV)
Healthy
- Last success
- 06:00, file received
- Latency
- Not applicable
- Error rate
- 0.0 percent
What users notice
Patient lookup shows a spinner for a few seconds. A failed read is tried again once, then falls back as set below.
Fallback per entity
| Entity | Source | When the source is down | What a receptionist sees |
|---|---|---|---|
| Patients | Hospital system (FHIR R4) | Receptionist sees the last known patient, marked "Last known data from 08:00". | |
| Practitioners | Hospital system (FHIR R4) | Care team picker shows the last known list. | |
| Service and price catalogue | Billing database (SQL Server) | Officer types the service and price by hand, flagged "Not verified at the source". | |
| Coverage and members | Hospital system (FHIR R4) | New eligibility checks wait. A message explains why. |
Block new requests, allow manual entry, or read the last known data. Pick per entity.
Save fallback settings