Digital cancer care brings together many moving parts: evolving patient needs, multidisciplinary teams, structured clinical programs, and sensitive documentation that must be captured consistently. To support this complexity, platforms need an EHR foundation that expresses clinical reality rather than bends it.

‍

Perci Health is building a virtual-first approach to survivorship and cancer support, delivered through expert-led programs and orchestrated clinical workflows. As their product and operations matured, Perci needed to re-platform their evolving system on a secure, interoperable foundation that could support clinical precision and long-term scale.

‍

They reached out to Vinta to validate Medplum’s fit and translate their care model into clean, build-ready FHIR architecture.

A care model rich in nuance, ready for structure

Perci’s product already served patients with multidisciplinary clinical support, routed through Awell’s workflow engine and a growing internal engineering team. But adopting Medplum required clarity on how encounters, practitioner roles, clinical reasoning, and billing-adjacent logic should be represented in FHIR.

‍

Their questions mirrored those of many fast-growing healthtech teams:

• How should existing workflows map into FHIR, and where should data live?
• Where do encounters begin and end in a virtual-first model?
• How should practitioner roles, teams, and program eligibility be structured?
• Which entities belong in Medplum and which remain under Awell’s orchestration?
• How do we reduce ambiguity now so implementation remains safe later?

A consultancy designed for clinical depth

Over four weeks, we worked closely with Perci’s engineering team to bring structure, clarity, and future-proof thinking to their system. Our process reflected Vinta’s Healthcare Consultancy approach: collaborative, architecture-led, and anchored in the realities of clinical care.

1. Understanding care flows and operational reality

We began with deep-dive workshops into Perci’s Awell-driven pathways, expert roles, program entitlements, and longitudinal patient journeys. This context shaped every FHIR decision that followed.

‍

We aligned on:

• Clinical touchpoints and their documentation needs
• Role boundaries for practitioners and specialists
• Encounter definitions for a virtual, multidisciplinary model
• How data should move among Perci’s apps, Awell, and Medplum

‍

These early sessions reduced ambiguity and built a shared mental model across both teams.

2. Mapping Perci’s universe into FHIR

Next, we translated each conceptual entity into the correct FHIR resource, with careful attention to relationships and constraints.

‍

This included Patients, Practitioners, PractitionerRoles, CareTeams, Appointments, Encounters, Observations, ClinicalImpressions, QuestionnaireResponses, DocumentReferences, Coverage, ChargeItemDefinitions, Accounts, and more.

‍

We clarified where standard profiles fit, where extensions were needed, and how Perci should handle provenance, versioning, and permissions. The result was a unified, conflict-free mapping that engineering and clinical leaders could trust.

Bring clarity to your clinical workflows.
See how a 3-week deep dive can de-risk your EHR decisions.

3. Architecting Medplum to reflect clinical truth

Once the model was defined, we designed Perci’s Medplum architecture. This blueprint covered:

• Resource lifecycles for encounters, sessions, and assessments
• How Awell should interact with Medplum without duplicating responsibility
• Data ownership boundaries between orchestration and the EHR
• Safe patterns for storing clinical artifacts and role-sensitive information

‍

We modeled how the system should behave, not just how it should store data.

4. Delivering a build-ready EHR plan

Every decision culminated in a detailed implementation blueprint:

• Resource schemas and mapping tables
• Integration responsibilities between Awell and Medplum
• Risk flags and compliance considerations
• A phased plan for safe rollout, testing, and clinician onboarding

‍

By the final week, Perci had a clear, validated architectural path and a reference model their team could apply immediately.

Making Perci’s clinical model build-ready

A complete FHIR model for Perci’s care operations

We translated their multidisciplinary programs, clinical assessments, and episodic workflows into a clean and normalized FHIR structure.

A Medplum architecture that matches real clinical practice

The blueprint ensures encounters, documentation, team roles, and patient relationships behave consistently across care flows.

Integration guidance for Awell and surrounding systems

We defined exactly how Awell should read, write, and synchronize information with Medplum.

A roadmap that reduces long-term risk

Instead of discovering problems mid-implementation, Perci now has a validated plan that prevents misalignment, rework, and clinical inconsistencies.

Clarity that accelerates safe implementation

Perci left the consultancy with the confidence to move forward. Their engineering team now understands what belongs in Medplum, how clinical entities relate to one another, and what their EHR must express to support safe, consistent care delivery.

‍

This clarity allows the team to scale faster, reduce ambiguity in the next engineering phase, and build a platform grounded in clinical accuracy.

Planning an EHR or complex care platform?
Learn how our team can help you design a FHIR-ready architecture in 3 weeks.