EHR & Data

A HL7-compliant FHIR data model. Built to fit existing systems.

Every clinical record in FitsPro maps to a standard FHIR resource. Bring your own EHR or EMR; we read from and write to a data shape your existing systems already speak.

FHIR R4 HL7 v2 messaging Webhooks MCP
FHIR resources

The same records your EHR knows.

The FitsPro schema mirrors FHIR R4 resources directly — same field shapes, same identifiers, same lifecycle statuses. Below is the subset most frequently exchanged with external systems.

Patient detail view in FitsPro showing FHIR-aligned record data
  • Patient

    Demographics, contact info, identifiers, managing organization.

  • Practitioner

    NPI, qualifications, telecom, name and role data.

  • Organization

    Clinic / practice entity. Status, billing model, configuration.

  • Location

    Physical sites tied to a managing organization. Address, hours.

  • PractitionerRole

    Links practitioner ↔ organization ↔ location. Availability windows.

  • Encounter

    Visits with type, period, participants, and location references.

  • Appointment

    Scheduled events including remote (telehealth) flag and participant array.

  • Device / DeviceRequest

    Orthotic specifications, lifecycle status, fulfillment tracking.

Multi-tenancy

Organization → Location → PractitionerRole.

A clinic is an Organization with one or more Locations. A practitioner attaches to one or more locations via a PractitionerRole, which carries availability and scope. Role groups — practitioner, manager, administrator, super — govern what each user sees across that hierarchy.

Every patient, encounter, and device request references the managing organization so cross-tenant access never resolves by accident.

Integration paths

Three ways to connect.

FitsPro doesn't require you to abandon your EHR. Most clinics keep their existing system as the source of truth and bring FitsPro in for the foot-care-specific workflows it owns.

  • 01 FHIR R4 API — Read and write FHIR resources directly. Suitable for EHRs already comfortable with FHIR exchange.
  • 02 HL7 v2 messaging — For EHRs that prefer the legacy pipe-delimited message format. Common for ADT (patient demographic) sync.
  • 03 MCP connector — For practitioners building their own agentic workflows. See the MCP docs.
Connect your stack

We'll map your existing schema with you.

Integration discussions happen on the orientation call. Bring a sample of the data you want flowing back and forth, and we'll sketch the integration before you commit.

Get Started MCP connector