Lightbox2
PhotoSwipe
Spotlight JS
Venobox
```plotly
{
"data": [
{
"x": [1, 2, 3, 4],
"y": [10, 15, 13, 17],
"type": "scatter"
},
{
"x": [1, 2, 3, 4],
"y": [16, 5, 11, 9],
"type": "scatter"
}
]
}
```
Which generates:
{
"data": [
{
"x": [1, 2, 3, 4],
"y": [10, 15, 13, 17],
"type": "scatter"
},
{
"x": [1, 2, 3, 4],
"y": [16, 5, 11, 9],
"type": "scatter"
}
]
}
Also another example chart.
```plotly
{
"data": [
{
"x": [1, 2, 3, 4],
"y": [10, 15, 13, 17],
"mode": "markers"
},
{
"x": [2, 3, 4, 5],
"y": [16, 5, 11, 9],
"mode": "lines"
},
{
"x": [1, 2, 3, 4],
"y": [12, 9, 15, 12],
"mode": "lines+markers"
}
],
"layout": {
"title": {
"text": "Line and Scatter Plot"
}
}
}
```
This is how it looks like:
{
"data": [
{
"x": [1, 2, 3, 4],
"y": [10, 15, 13, 17],
"mode": "markers"
},
{
"x": [2, 3, 4, 5],
"y": [16, 5, 11, 9],
"mode": "lines"
},
{
"x": [1, 2, 3, 4],
"y": [12, 9, 15, 12],
"mode": "lines+markers"
}
],
"layout": {
"title": {
"text": "Line and Scatter Plot"
}
}
}
Saudi Arabia’s Vision 2030 represents one of the most ambitious national transformation programs globally, with healthcare digital transformation at its core. As a physician and healthcare AI innovator working in the Kingdom, I’ve witnessed firsthand the remarkable progress and opportunities in this space.
The Kingdom’s healthcare vision is clear and ambitious:
The National Platform for Health Insurance Exchange Services (NPHIES) has been a game-changer for Saudi healthcare. This mandatory platform standardizes claims processing, eligibility verification, and pre-authorization across all healthcare providers and payers.
How AI Enhances NPHIES:
Our BrainSAIT platform has helped multiple healthcare facilities achieve NPHIES compliance while reducing administrative overhead by more than 50%.
Saudi Arabia’s healthcare system serves a diverse population with varying health needs. AI-powered clinical decision support helps physicians deliver consistent, evidence-based care.
Key Applications:
The COVID-19 pandemic accelerated telemedicine adoption in Saudi Arabia. Now, with Vision 2030’s push for accessible healthcare, AI-enhanced telemedicine is bridging geographical gaps.
GIVC Platform Impact:
Healthcare financial sustainability is crucial for Vision 2030 goals. AI transforms revenue cycle management from reactive to proactive.
Measurable Improvements:
Most healthcare AI models are trained on English data, limiting effectiveness in Arabic-speaking environments.
Our Solution:
Saudi Arabia’s Personal Data Protection Law (PDPL) requires strict data handling practices.
Our Approach:
Many Saudi healthcare facilities use a mix of modern and legacy systems.
Integration Strategy:
Challenge: Manual medical coding causing 3-week claim submission delays
Solution: Implemented BrainSAIT’s AI-powered coding engine
Results:
Challenge: NPHIES compliance requirements overwhelming small IT team
Solution: Deployed ClaimLinc and PolicyLinc agents
Results:
As we move toward Vision 2030’s deadline, several AI healthcare trends will accelerate:
Saudi healthcare providers have a unique opportunity to leapfrog traditional digital transformation approaches:
Start with AI-Native Systems: Rather than retrofitting AI onto legacy systems, build new workflows around AI capabilities
Embrace Open Standards: FHIR and NPHIES compliance positions you for future interoperability
Invest in Bilingual Solutions: Arabic-English AI systems serve your population better
Partner with Innovators: Collaborate with local AI healthcare companies who understand the market
Focus on ROI: Measure and demonstrate value to secure continued investment
To accelerate AI adoption in Saudi healthcare:
For Regulatory Bodies:
For Healthcare Organizations:
For Payers:
Saudi Arabia’s Vision 2030 presents an unprecedented opportunity to build a world-class, AI-powered healthcare system. The combination of government vision, regulatory frameworks like NPHIES, and growing local AI expertise creates ideal conditions for transformation.
As someone working at the intersection of clinical medicine and AI innovation in the Kingdom, I’m optimistic about the future. The next five years will see Saudi healthcare evolve from adopting AI to leading global healthcare AI innovation.
The question is not whether AI will transform Saudi healthcare, but how quickly healthcare organizations will embrace this transformation to achieve Vision 2030’s ambitious goals.
About the Author: Dr. Mohamed El Fadil is a physician and healthcare AI innovator, founder of BrainSAIT, and creator of open-source healthcare tools. He works with healthcare organizations across the Middle East to implement AI-powered solutions.
Connect:
Resources:
]]>
Healthcare interoperability remains one of the industry’s most persistent challenges. After implementing FHIR and HL7 solutions across multiple healthcare systems, I’ve learned valuable lessons about what works, what doesn’t, and why these standards matter more than ever.
Every day, critical health information is trapped in silos:
The cost? Lives affected, billions wasted, and physician frustration.
HL7 v2.x has been the backbone of healthcare data exchange for decades. While sometimes criticized as “outdated,” it remains widely deployed and remarkably robust.
MSH|^~\&|SENDING_APP|SENDING_FACILITY|RECEIVING_APP|RECEIVING_FACILITY|20241120140500||ADT^A01|MSG00001|P|2.5
EVN|A01|20241120140500
PID|1||12345^^^MRN||DOE^JOHN||19800115|M|||123 MAIN ST^^RIYADH^^12345^SA||+966501234567
Key Components:
Strengths:
Challenges:
Fast Healthcare Interoperability Resources (FHIR) represents a paradigm shift in healthcare data exchange. Built on modern web standards, it’s designed for today’s API-driven world.
1. Resources: Building Blocks of Health Data
FHIR defines 150+ resource types representing clinical and administrative concepts:
{
"resourceType": "Patient",
"id": "example",
"identifier": [
{
"system": "http://hospital.example.org/mrn",
"value": "12345"
}
],
"name": [
{
"family": "Doe",
"given": ["John"]
}
],
"birthDate": "1980-01-15",
"gender": "male",
"address": [
{
"line": ["123 Main St"],
"city": "Riyadh",
"postalCode": "12345",
"country": "SA"
}
],
"telecom": [
{
"system": "phone",
"value": "+966501234567",
"use": "mobile"
}
]
}
2. RESTful API
FHIR uses standard HTTP operations:
# Create a patient
POST /Patient
Content-Type: application/fhir+json
# Read a patient
GET /Patient/12345
# Update a patient
PUT /Patient/12345
# Search for patients
GET /Patient?family=Doe&birthdate=1980-01-15
# Delete a patient (rarely used in healthcare)
DELETE /Patient/12345
3. Search Parameters
FHIR’s powerful search enables complex queries:
# Find recent observations for a patient
GET /Observation?patient=12345&date=gt2024-01-01&_sort=-date
# Find medications containing "insulin"
GET /Medication?ingredient-code:text=insulin
# Find encounters at a specific location
GET /Encounter?location=Building-A&date=2024-11-20
4. Profiles and Extensions
Customize resources for specific use cases:
{
"resourceType": "StructureDefinition",
"url": "http://example.org/StructureDefinition/SaudiPatient",
"name": "SaudiPatient",
"status": "active",
"kind": "resource",
"type": "Patient",
"baseDefinition": "http://hl7.org/fhir/StructureDefinition/Patient",
"differential": {
"element": [
{
"path": "Patient.extension",
"sliceName": "nationalId",
"type": [
{
"code": "Extension",
"profile": ["http://example.org/StructureDefinition/saudi-national-id"]
}
]
}
]
}
}
Our open-source package demonstrates practical FHIR implementation:
from brainsait_pyheart import FHIRClient, Patient, Observation
# Initialize client
client = FHIRClient(base_url="https://fhir.example.org")
# Create a patient
patient = Patient(
identifier=[{
"system": "http://hospital.example.org/mrn",
"value": "12345"
}],
name=[{
"family": "Doe",
"given": ["John"]
}],
birthDate="1980-01-15",
gender="male"
)
# Save to server
created_patient = await client.create(patient)
# Search for observations
observations = await client.search(
"Observation",
params={
"patient": created_patient.id,
"code": "85354-9", # Blood pressure
"date": "gt2024-01-01"
}
)
# Process results
for obs in observations:
print(f"Date: {obs.effectiveDateTime}")
print(f"Value: {obs.valueQuantity.value} {obs.valueQuantity.unit}")
Traditional hospital interfaces:
[EMR] --HL7 v2.x--> [Interface Engine] --HL7 v2.x--> [Lab System]
Pros:
Cons:
Modern approach using FHIR:
[EMR] --REST/FHIR--> [API Gateway] --REST/FHIR--> [Multiple Systems]
Pros:
Cons:
Best of both worlds:
[Legacy System] --HL7 v2.x--> [Transformation Service] --FHIR--> [Modern Systems]
↓
[Data Repository]
This is our recommended approach for most healthcare organizations.
Saudi Arabia’s National Platform (NPHIES) mandates FHIR for all claims:
# NPHIES Claim Example
claim = {
"resourceType": "Claim",
"identifier": [{
"system": "http://nphies.sa/claim-id",
"value": "CLM-2024-00123"
}],
"status": "active",
"type": {
"coding": [{
"system": "http://terminology.hl7.org/CodeSystem/claim-type",
"code": "institutional"
}]
},
"use": "claim",
"patient": {
"reference": "Patient/12345"
},
"created": "2024-11-20T14:05:00+03:00",
"provider": {
"reference": "Organization/hospital-001"
},
"priority": {
"coding": [{
"code": "normal"
}]
},
"insurance": [{
"sequence": 1,
"focal": true,
"coverage": {
"reference": "Coverage/cov-12345"
}
}],
"item": [{
"sequence": 1,
"productOrService": {
"coding": [{
"system": "http://nphies.sa/terminology/CodeSystem/services",
"code": "99213"
}]
},
"unitPrice": {
"value": 300.00,
"currency": "SAR"
}
}]
}
Secure API access using industry standards:
from brainsait_pyheart import FHIRClient, OAuth2Provider
# Configure OAuth2
oauth = OAuth2Provider(
client_id="my-app",
client_secret="secret",
token_url="https://auth.example.org/token",
scopes=["patient/*.read", "user/*.write"]
)
# Initialize authenticated client
client = FHIRClient(
base_url="https://fhir.example.org",
auth_provider=oauth
)
Instead of individual requests:
# Bad: N requests
for patient_id in patient_ids:
patient = await client.read("Patient", patient_id)
# Good: 1 batch request
bundle = await client.batch([
{"method": "GET", "url": f"Patient/{pid}"}
for pid in patient_ids
])
Handle large result sets efficiently:
# Get first page
results = await client.search("Observation", params={"patient": "12345"})
# Iterate through pages
while results.has_next():
results = await results.next()
# Process results
Cache frequently accessed resources:
from functools import lru_cache
@lru_cache(maxsize=1000)
async def get_patient(patient_id):
return await client.read("Patient", patient_id)
Problem: Assuming all FHIR servers work identically
Solution: Always check the CapabilityStatement:
capability = await client.read("metadata")
# Check supported resources, search parameters, operations
Problem: Treating all errors the same way
Solution: Handle different error types appropriately:
try:
patient = await client.read("Patient", "12345")
except ResourceNotFound:
# Patient doesn't exist - maybe create it
pass
except UnauthorizedError:
# Authentication issue - refresh token
await refresh_auth()
except ServerError:
# Server issue - retry with backoff
await retry_with_backoff()
Problem: Creating profiles that are too restrictive
Solution: Start simple, add constraints gradually based on real needs
Test resource validation:
def test_patient_validation():
patient = Patient(name=[{"family": "Doe"}])
assert patient.is_valid()
invalid_patient = Patient() # Missing required fields
assert not invalid_patient.is_valid()
Test against FHIR test servers:
async def test_patient_crud():
# Create
patient = await client.create(test_patient)
assert patient.id is not None
# Read
retrieved = await client.read("Patient", patient.id)
assert retrieved.name[0].family == "Doe"
# Update
retrieved.telecom = [{"system": "phone", "value": "+966501234567"}]
updated = await client.update(retrieved)
assert len(updated.telecom) == 1
# Delete
await client.delete("Patient", patient.id)
Validate against official FHIR test suites
1. FHIR R5 and Beyond
2. FHIRPath and CQL
3. FHIR Bulk Data
4. International Patient Summary (IPS)
Healthcare interoperability isn’t just about technology - it’s about saving lives through better information sharing. Whether you’re using HL7 v2.x, FHIR, or a hybrid approach, the goal remains the same: getting the right information to the right person at the right time.
After years of implementation experience, my advice is:
The future of healthcare depends on our ability to share information seamlessly. Let’s build it right.
Technical Resources:
Connect: