Serendipity Solutions
Healthcare & system integrations

HL7 and FHIR integration work that survives contact with production data.

Connect clinical and business systems through HL7 messaging, FHIR APIs and file-based workflows. I work with data mapping, field-level logic and vendor constraints so information reaches the right place in the right format.

Nearly 9 years in healthcare technology HL7 & FHIR APIs Cerner experience
Discuss your workflow See capabilities
Capabilities

What this work covers

The list below reflects the kinds of work I have done and continue to do. Each engagement is scoped together.

HL7 interface design

Message flows for ADT, ORU, ORM, MDM and other event types. Interface specifications that survive handover.

FHIR API integration

FHIR resource modelling, REST endpoint design, mapping from existing data formats, terminology alignment.

Data mapping & transformation

Field-level mapping, code translations, deduplication and reconciliation between systems.

Validation & troubleshooting

Catching format and content issues before they reach downstream systems; investigating production failures.

File-based workflows

CSV exchange, PDF document handling, structured intake where APIs are not available.

Working with Cerner

Hands-on experience integrating with Cerner and other HL7-based EHR systems, including vendor-specific constraints.

Business system context

Familiarity with CRM systems and the production / finance modules of business platforms — to understand where information moves.

Legacy modernisation

Replacing fragile point-to-point integrations with maintainable interfaces, or moving data into modern formats.

Possible deliverables (per agreed scope)

  • A data-flow diagram.
  • A field-mapping specification.
  • An interface specification suitable for engineering and audit.
  • Defined validation and acceptance criteria.
  • Handover documentation so your team can operate and extend the work.
Project examples

Examples of projects I can support

Illustrative scenarios — agreed scope per engagement.

Example — Connect patient and appointment workflows

Situation: A healthcare application needs patient demographics and appointment information from an EHR.

My role: Define the exchange workflow, map fields, establish matching and update rules, and configure or coordinate the integration.

Possible deliverables

  • A data-flow diagram.
  • A field-mapping specification.
  • Exception-handling rules.
  • Test scenarios.

Relevant experience: HL7 v2 ADT/SIU, FHIR R4 APIs, and Cerner workflows.

Example — Investigate missing or inconsistent integration data

Situation: Information arrives incomplete, differs between systems, or requires repeated manual correction.

My role: Trace the data from source to destination, review transformation logic, and clarify how missing values and updates should be handled.

Possible deliverables

  • Investigation findings.
  • Revised mapping rules.
  • A prioritised correction plan.
  • Validation scenarios.

Example — Turn an operational problem into implementation-ready requirements

Situation: Business users can explain what is difficult, but developers need precise rules and expected behaviour.

My role: Walk through the actual work with users, identify exceptions, and translate the findings into technical requirements.

Possible deliverables

  • Current and proposed process maps.
  • Business rules.
  • Acceptance criteria.
  • An implementation handoff.

Example — Structure a recurring CSV or PDF exchange

Situation: A partner exchanges files rather than providing a direct API connection.

My role: Define file requirements, transfer steps, validation rules, and how rejected or incomplete information should be handled.

Possible deliverables

  • An exchange specification.
  • A processing workflow.
  • An exception-handling process.

Scope and deliverables are agreed around your systems, team, and priorities.

Discuss your workflow