Core
Patient, Practitioner, Organization, Encounter, Consent and the resources most apps touch first.
FHIR apps
Every clinical app is also a FHIR R4 server.
Your care team works in tables and pages. Your partners, analysts and integrations talk to the same data through standard FHIR R4. No mapping layer to maintain, because the tables are the resources.
GET /metadata
CapabilityStatement · 19 resources from Core
Clinical installed · 45 resources
GET /Patient?family=Okafor
Bundle · searchset · 1 match
POST / transaction
Patient + Observation · 2 created
GET /Observation/obs82/_history
3 versions from the event log
GET /ValueSet/$expand
LOINC vital signs · 9 codes
FHIR packs
54 tables, each one an R4 resource.
Install Core to start. Add Clinical and Financial when the app needs them. The CapabilityStatement updates as packs are installed.
Clinical
Conditions, observations, medications, allergies, procedures, care plans and questionnaires.
Financial
Coverage, claims and explanation of benefit records for eligibility and billing workflows.
The server
The parts of FHIR that integrations actually use.
- Read, search, create, update and delete for every installed resource
- Version read and history, served from the event log
- Transaction and batch bundles
- Search with chains, _include, _revinclude, _elements and _summary
- Terminology: ValueSet expansion and code validation, CodeSystem lookup
- Resource $validate against the installed profiles
- Bulk Data $export for patients and groups
- SMART configuration discovery and OAuth token endpoints
Standard app
OutreachCampaigns, segments
CRMPipelines, deals, notes
CommonPeople, organizations, tasks, activities, events
FHIR app
Clinical26 tables
Financial9 tables
Core19 tables. Patient, Practitioner, Encounter, Consent
FHIR R4 serverOne per app
HealthTable engine
TablesInterfacesAutomationsPermissionsEvent logAI
Triage · Patients
Acuity is anySorted by acuity
NameAcuityStatusNext stepOwner
Maya OkaforHighCall backNurse call by 2:30CR. Chen
Imani BrooksHighNewReview intakePJ. Patel
Daniel PryorMediumIn reviewLab follow upRA. Ruiz
Owen WalshMediumNewMedication questionPJ. Patel
Sofia MarinLowScheduledVisit Thu 10:00CR. Chen
Grace LiuLowClosedNoneRA. Ruiz
For the people doing the work
FHIR underneath. A table on screen.
Nurses and coordinators never see a JSON resource. They see a patient list, a callback queue, a form. FHIR datatypes like CodeableConcept and HumanName render as fields that make sense.
How interfaces workStandards
Coded data from the start.
SNOMED CT
Conditions, findings and procedures.
LOINC
Observations, labs and vital signs.
RxNorm
Medications and prescriptions.
ICD 10
Diagnoses for billing and reporting.
Roadmap
HL7 v2, Consolidated CDA and X12 eligibility and claims are planned and not available today. Formal FHIR conformance testing is also planned.
Bring an integration you need to support.
We will show you how the resources map, what the server returns today and what is on the roadmap.