NPHIES
Public FHIR implementation guidance informs selected structural checks, not live exchange.
SYSTEM CONNECTIONS
Integrations should fit the hospital, not the other way around.
Burhaneo’s architecture is intended to support authorized healthcare workflows. No hospital HIS or live NPHIES connection is claimed in the public demonstration.
HIS / EHR
Requires vendor interfaces, hospital permission, mappings and end-to-end testing.
File imports
Defined retrospective import processes are possible, with the required security approval.
Payer policies
Rules must come from verified sources, with effective dates and clinical review.
NPHIES
Reference is not connectivity.
Saudi NPHIES publishes implementation guidance for electronic health-insurance transactions. Public specifications help engineering teams plan data models and validations. Production transactions require onboarding, certificates, permissions and tested connectivity.
Status of the current demo
- — No live NPHIES request or response
- — No insurer submissions or approvals
- — No production hospital HIS connection
- ✓ Selected educational schema checks available in development code
Implementation sequence
Scope, secure, test, then connect.
01
System discovery
Identify source systems, fields and existing workflows.
02
Authority & controls
Confirm contracts, permissions and information-security requirements.
03
Sandbox testing
Validate schema mappings and error handling in approved environments.
04
Operational acceptance
Review monitoring, responsibilities and rollback with hospital IT.