Boolbyte

For Developers

Seven healthcare workflow agents.
One FHIR-native API.

SMART on FHIRHIPAA-compliantSandbox availableWebhooksHL7 v2
boolbyte.js · intake + scheduling 
const visit = await boolbyte.intake.create({
  patient: {  phone: "+234-XXX-XXXX"  },
  channel: "sms",
  fhir:    {  resourceType: "Patient"  }
});

await boolbyte.scheduling.book({
  visitId: visit.id,
  on: {  noShow: (v) => boolbyte.followUp.schedule(v)  }
});
200 OK · visit_4f21 created · webhook dispatched

The agent suite

Seven agents. Compose any combination.

USE ONE · USE SEVERAL · BUILD A FULL PATHWAY
01

Patient Access

Any channelFirst contactRouting
02

Triage

Urgency scoreProtocol-drivenEscalation
03

Intake

RegistrationHistory collectPre-auth
04

Scheduling

BookingRemindersNo-show recovery
05

Referrals

LettersTrackingCompletion
06

Documentation

Note draftingEncounter recordReview flow
07

Follow-up

Post-dischargeChronic monitorAdherence

Integration surfaces

REST

Workflow API

Trigger any agent via RESTFHIR-native request and response bodiesIdempotent operations. Full audit trail on every call
CONFIG

Agent API

Configure agent behaviour per deploymentCustom decision rules and escalation logicBring your own clinical protocols
FHIR

FHIR Server

Direct read/write on Patient, Encounter, ObservationPractitioner and related FHIR resourcesNo proprietary translation layer
WH

Event Webhooks

Subscribe to every clinical event typeSigned payloads. Idempotent deliveryReplayable from any point in history

API trace · sample care pathway

→ POST /v1/intake.create 201
→ POST /v1/triage.assess 200
→ POST /v1/scheduling.book 201
← WH encounter.created ✓ sig
← WH scheduling.reminder_sent ✓ sig
→ POST /v1/referrals.create 201
→ POST /v1/documentation.draft 200
← WH visit.follow_up_scheduled ✓ sig
8 operations · 3 webhooks · full care pathway covered

Standards & compliance

Built on open standards.
Compliant by default.

FHIR

All data as FHIR resources

SMART on FHIR

OAuth 2.0 EHR authorisation

HL7 v2

Legacy system interoperability

HIPAA BAA

Available for US deployments

E2E Encryption

Transit and at rest

RBAC

All API endpoints

Full Audit Log

Actor, timestamp, payload

No Training Data

Patient data never used for ML

EHR compatibility

Epic native
Cerner native
Athenahealth native
Any FHIR EHR standard
Any HL7 v2 EHR standard
Clearinghouse insurance
SIP / VOIP voice

Sandbox

All 7 agents available
Test patient data included
No production data required
FHIR test server included
Access today no approval queue

What you can build

Healthcare products.
Without rebuilding the infrastructure.

Telehealth platforms
Branded intake, triage, scheduling, and follow-up
SMART on FHIR launch from any existing EHR
Compliant by default no BAA per feature
Patient AccessTriageSchedulingFollow-up
EHR extensions
Documentation, referrals, and follow-up alongside existing records
No core system replacement
Role-based access maps to existing clinical roles
DocumentationReferralsFollow-up
Insurer care management
Member triage and care coordination via API
Claims pre-auth check integrated into intake flow
Chronic population monitoring via follow-up agent
TriageIntakeSchedulingFollow-up
Chronic disease programmes
Medication adherence and scheduled check-ins
Escalation logic when monitoring thresholds are missed
Patient history always current before each encounter
Follow-upIntake
Clinical research tooling
Structured data collection on FHIR-native backend
Protocol-driven follow-up per trial arm
Consent management and full audit trail included
DocumentationIntakeFollow-up
Public health platforms
Community outreach and intake at population scale
Coverage tracking across facilities and geographies
Follow-up without proportional workforce growth
Patient AccessFollow-upScheduling

Build something patients deserve.

Healthcare workflow infrastructure. Standardised. Compliant. Available via API.

Access the sandbox View the documentation

Technical question? Get in touch directly