RUCEL/ SYSTEMS

Personal portfolio

Fullstack Engineer..

Software for people. Across healthcare, data and AI.

Healthcare·Data·AI Systems
Selected work
Rucel Tsafack, seated in a black hoodie
HEALTHCARE · DATA · AI
01 / IDENTITY

Rucel Tsafack

My starting point is software: a thoughtful interface, a clear API contract, a data model you can reason about. The work gets interesting when those pieces come together.

02 / FOCUS

Python · TypeScript · Healthcare interoperability

Behind every field is a clinical context. I explore how to preserve that context across system boundaries, through explicit references, meaningful errors and carefully designed data models.

Selected work

Ideas, made into considered systems.

Four architecture studies exploring data, interfaces and the decisions between them.

VOICE DOCUMENTATION / INTEROPERABILITY

Voice → structured clinical data → FHIR

  1. 01Voice input
  2. 02Encrypted audio store
  3. 03faster-whisper
  4. 04Ollama extraction
  5. 05Grounding + canonical model
  6. 06Human approval
The language model is not a FHIR authoring authority. It is a constrained extraction assistant.

Architecture study

Vital Mapper

A speech-assisted nursing documentation platform that turns spoken observations into grounded, reviewable clinical structure and forwards approved records through a versioned interoperability gateway.

Python · FastAPI · React · TypeScript

View case study

FHIR-NATIVE CLINICAL MONITORING

Structured healthcare data as system architecture

Patient.identifierEncounterObservationMonitoring view

LOINC 8867-4 · 85354-9 · 8310-5

The backend owns controlled FHIR access. The frontend receives only the data and actions its session is permitted to use.

Architecture study

Monitoring Pflege

A containerized FHIR-native nursing documentation and monitoring application with controlled clinical writes, trends, BFF authentication and an internal HAPI FHIR boundary.

React · TypeScript · Vite · FastAPI

View case study
Clinical knowledge retrieval

What is this answer based on?

An answer is only as traceable as its sources.

source.documentanswer.citations

Source passage

Each statement stays linked to its original document and version.
document_id
chunk_id
source_version
Concept view · Answer and provenance, designed together

Architecture study

Clinical Knowledge Retrieval

A retrieval pipeline designed around source traceability, constrained outputs, and local-first experimentation.

Python · FastAPI · ChromaDB · Ollama

View case study

Interoperability

Same information. A shared language.

HL7 v2.5
PID|1||SYN-1042
MUSTER^AVA
19890514
FHIR R4
Patient.identifier
Patient.name
Patient.birthDate
Mapping study · From HL7 v2 to FHIR R4

Architecture study

HL7 v2 → FHIR Integration

A deterministic admission and result transformation with explicit field mappings and resolvable FHIR references.

HL7 v2.5 · FHIR R4 · Python · Pydantic

View case study

HEALTHCARE SYSTEMS ECOSYSTEM

From clinical input to structured care data.

Vital Mapper turns nursing language into grounded, reviewable structure. After approval, its versioned gateway contract reaches Monitoring Pflege, which controls the FHIR mapping, context and monitoring view.

  1. 01Nurse voice
  2. 02Vital Mapper
  3. 03Grounded clinical data
  4. 04Interop gateway
  5. 05Monitoring Pflege
  6. 06FHIR monitoring
Implemented integration path · synthetic examples shown publicly

My focus

Healthcare is software. With harder constraints.

Behind every field is a clinical context. I explore how to preserve that context across system boundaries, through explicit references, meaningful errors and carefully designed data models.

FHIR R4 · HL7 v2 · Clinical APIs · HAPI FHIR · Clinical data modeling

INTERACTIVE ENGINEERING STORY

Interoperability Lab

One clinical fact. Two standards. One canonical model in between.

Use synthetic data only. Inputs are processed locally and are not stored.
01

Clinical data

Synthetic data only. Data entered here is for demonstration purposes.

Patient
Admission optional
01Normalizevalidation · trim · types
02Canonical clinical modelpatient + encounter
P-1001Mustermannfemale
03Map
03

Representations

Choose a field to follow its journey.

CANONICAL → TWO VIEWS
Explore mapping

Choose a source or target. The connection works both ways.

FORMCANONICALFHIR R4 ↔ HL7 v2.5

Choose a source or target. The connection works both ways.

Active mappingPatient identifier
FHIRPatient.identifier[0].valueHL7PID-3

Patient.identifier holds the business identifier. In HL7, PID-3 is the Patient Identifier List.

Approach

From the interface to the database.

Backend

I design APIs around clear domain boundaries, validated inputs and predictable behavior.

Python · FastAPI · Django · PostgreSQL

Frontend

I make complex workflows understandable through accessible interfaces and deliberate state design.

TypeScript · React · Angular · Accessibility

AI & Data

I explore AI applications whose answers can be traced back to sources, data and evaluation.

RAG · Embeddings · Structured outputs · Evaluation

Healthcare Engineering

I model clinical information so its meaning survives the journey between systems.

FHIR · HL7 v2 · Interoperability · Data modeling

Rucel Tsafack, seated in a black hoodie
Rucel Tsafack · Fullstack Engineer

About me

I’m Rucel. I like understanding what happens behind an interface.

My starting point is software: a thoughtful interface, a clear API contract, a data model you can reason about. The work gets interesting when those pieces come together.

Healthcare gives that work a concrete direction. I explore how clinical information travels between systems, and how data and AI can build on a reliable technical foundation.

I’m based in Bad Segeberg, Germany, and open to working together on site or remotely.

Contact

What would you like to build?

A project, a technical question or an opportunity to work together. I’d be glad to hear from you.

Get in touch