Skip to main content
Standards-first integration posture

Standards-first,vendor-neutral

FHIR/HL7 when available; Calendar/iCal fallback for small practices. Field-level allowlists and retention/redaction policies keep every adapter safe.

FHIR R4/R5 + HL7v2 pipes switch on when your EHR supports them.
Calendar/iCal adapters cover read/write for independent clinics.
Diagram showing FHIR/HL7 connections with calendar fallback

Standards when you have them, dignity when you don’t

Move safely, leave when you want

Every clinic is on its own timeline. If your systems offer FHIR or HL7, we use them—Appointments, Slots, Schedule, the basics that matter. If they don’t, we don’t force a migration; we operate with a calendar fallback that still enforces rules and leaves a clean audit log. HealthCloud keeps mappings and retention settings you control.

The point of standards isn’t a logo on a slide; it’s the ability to move safely and leave when you want, without vendor lock-in.

What this means

  • FHIR/HL7 when available, Calendar/iCal fallback when not.
  • Allowlist + retention policies set by you in HealthCloud.
  • Audit trails and exit paths by design—no lock-in.

CSV today

Structured exports that match clinic import templates

Standard CSV with columns for:

  • Patient identifier (MRN or external ID)
  • Screening date and time
  • Instrument (PHQ-2, PHQ-9, PHQ-A)
  • Item-level responses (0-3)
  • Total score and severity band
  • Item-9 endorsement flag

FHIR during pilot

Write Observation and Task resources to your sandbox

Observation (item + total)

PHQ item-level and total score as LOINC-coded Observations. Optional QuestionnaireResponse if your EHR supports it.

Task (follow-up)

Item-9 endorsements create Tasks assigned to care team. Status, priority, and notes included.

FHIR objects diagram showing Observation and Task relationships

Adapter pattern + webhooks

Field-level allowlists, retention, and redaction policies baked into every integration.

Field-level control

Each adapter defines an allowlist. We hash or redact anything outside the scope before it hits HealthCloud.

  • Retention: Appointment + Slot data kept 30 days by default.
  • Redaction: Contact info removed from logs after sync.
  • Calendars: iCal tokens stored encrypted + rotated every 30 days.

Webhooks + adapter pattern

Webhooks notify your systems when HealthCloud records change. Adapter scripts translate payloads into whatever your EHR or calendar expects.

Example webhook payload

POST /webhooks/appointment → { id, status, slot.start, slot.end, patient.reference }

Your adapter script transforms this into your EHR's expected format—no PHI travels through webhook URLs.

Mapping example

Simple lookup showing how external fields land in HealthCloud.

External fieldHealthCloud fieldNotes
appointment.identifierreferenceIdAccepts MRN, UUID, or vendor ID
slot.start/endavailabilityWindow24h retention, redacted after sync
patient.phone/emailcontactDetailsField-level allowlist defines what flows in

Additional interoperability standards

Beyond FHIR: HL7, CDA, and Direct messaging

HL7 v2/v3

ADT, ORU, and ORM segments via MLLP or HTTPS with adapter scripts you can review.

CDA + Direct

Generate/consume CDA docs and send via Direct messaging (HISP-certified).

Calendar/iCal fallback

Read/write availability via iCal feeds, ICS invites for confirmations, and redaction after sync.

CloudAIN tie-ins

HealthCloud stores mappings, AgenticCloud syncs, Astra logs every event.

HealthCloud

Stores mappings, retention policies, allowlists, and webhook payloads.

AgenticCloud

Runs sync jobs (FHIR, HL7, calendar) and retries on failure.

Astra (optional)

Event log + replay for high-compliance orgs that need immutable feeds.

Requirements

What we need from your IT team

Sandbox credentials
FHIR endpoint URL, client ID, and secret for test environment. Production credentials only after pilot validation.
Test patients
At least 3 test patient records with MRNs we can write to during pilot.
IT contact
Technical point-of-contact for troubleshooting, credential rotation, and production go-live approval.

Security & governance

Enterprise-grade compliance for clinical data

Encryption

AES-256 at rest, TLS 1.3 in transit

RBAC

Role-based access with audit logging

Audit trail

Every write logged with timestamp and user

BAA available

Business Associate Agreement for HIPAA compliance

Next step

Review the integrations checklist →

Walk through the HealthCloud mappings, AgenticCloud job schedule, and Astra logging expectations before you hand over credentials.

EHR integration dashboard with credential manager

Supports clinicians; not diagnostic. HIPAA compliant with RBAC, audit logging, and encryption. In emergencies, call local services.