Design an Anti-Corruption Layer for a Legacy Hospital EHR

FreeVerified credential4 weeksAdvanced

Overview

What this challenge is about.

Map legacy EHR HL7 v2 data to clean domain events, fix anti-patterns, and validate with property-based tests to earn a verifiable certificate.

The scenario

The healthcare network (around USD 1.8B revenue, HIPAA + HITECH compliance) cannot replace the EHR for at least 5 years — the new platform must coexist without inheriting its data model.

CredentialBlockchain-anchored

ShareableLinkedIn-ready

LanguageEnglish

PaceSelf-paced

The Brief

What you'll do, and what you'll demonstrate.

Design and prototype an Anti-Corruption Layer translating a legacy HL7 v2 EHR feed into a clean domain model the modern care-coordination platform can build on safely.

Earning criteria — what you'll demonstrate

Design an Anti-Corruption Layer protecting a clean domain from legacy contamination
Translate legacy data models without leaking their concepts into the new design
Apply property-based testing to translation correctness
Document translation rules in a form ops + clinical staff can audit

Program Fit

Where this fits in your program.

Sharpens the same skills your degree expects you to demonstrate.

Domain-Driven Design

Master · Software Engineering

Strong alignment

This challenge maps to Domain-Driven Design at the Master level. It sharpens the same practical skills your coursework expects — but in a real industry context with actual constraints and deliverables.

Skills

Skills you'll demonstrate.

Each one shows up on your verified credential.

Careers

Career paths this challenge builds toward

Completing this challenge demonstrates skills that transfer directly to these roles:

Career paths this builds toward

Canonical roles

Systems Architect
Systems architects make the decisions whose consequences are felt for years. The role is about choosing: which cloud provider, which integration pattern, which trade-off between cost and reliability deserves an Architecture Decision Record so the next team understands the reasoning. You'll work in C4 diagrams, ArchiMate models, and the AWS or Azure Well-Architected Framework, but the real artifact is clarity of thought. Strong architects know when to standardize and when to let a team diverge, and they write documents that survive a leadership change. Students drawn here usually loved their distributed systems course and are patient enough to think before they build. Growth happens through scars: owning architectures end-to-end, watching them strain under real load, and learning which abstractions earned their place.
Platform & Infrastructure

One more thing

You can put a credential on your CV by Friday.

Start this challenge