HC-DATA-041 / MERIDIAN HEALTH NETWORK
Control survived the cutover
3.4 million patient records moved through four acceptance gates without losing operating ownership.
Meridian Health Network
Twelve applications held overlapping patient, scheduling, billing, document, and audit records. Contractual timing was fixed, but future-use and archive-access decisions were not.
11 hospitals · 3.4M patient records · 2023 · 9 months · 8-person delivery team
The problem beneath the brief
The initial program treated migration as a volume exercise. It could count records but could not explain which source remained authoritative, who approved disposition, or how users would reach retained records after cutover.
- 3.4M
- patient records dispositionedaccepted reconciliation and disposition register
- 4
- acceptance gatesrelease and handoff record
- 2
- pre-cutover blockers caughtexception and decision log
Risk constraints
What could not be traded away.
- clinical continuity during cutover
- minimum-necessary access
- retention by record class
- provenance across transformed records
- recovery without reopening the retiring platform
Findings
What inspection changed.
- three sources claimed authority over the same appointment state
- an inherited entitlement crossed an intended archive boundary
- two retained workflows depended on a service omitted from the first recovery plan
Named team and role pattern
The people attached to this engagement.
- Maya Raines · senior delivery lead
- data architect
- application analyst
- integration lead
- quality lead
- security reviewer
- clinical workflow reviewer
Architecture
The operating system we installed.
- 01record-class disposition registerfour acceptance gates
- 02versioned mappings and reconciliation ledgerdual approval for disposition changes
- 03read-only archive with role-scoped accesssampled content validation
- 04event and exception audit streamaccess-denial tests
- 05cutover and rollback orchestrationrestore rehearsal
Delivery sequence
Four phases. Evidence at every gate.
- 01
Frame
Define the decision, outcome, work products, authority, dependencies, exclusions, and acceptance evidence.
A named sponsor and principal approve the bounded charter. - 02
Assemble
Inspect the operating reality, then assemble named specialists, context, access, controls, and a delivery plan around the actual work.
The client approves the named team, evidence plan, role boundaries, and stop conditions. - 03
Govern
Build and operate the smallest coherent change with versioned decisions, quality evidence, escalation, and acceptance attached.
The integrated state meets the agreed evidence threshold and every material exception has an owner. - 04
Transfer
Rehearse recovery, resolve exceptions, accept the work, remove temporary access, and transfer operating ownership.
The receiving owner signs the handoff with open limits visible.
Complications
Where the plan had to become more honest.
- A clean aggregate count hid duplicate clinical documents with different provenance.
- The first restore rehearsal recovered the archive but not the identity dependency required to open it.
Outcomes
What changed—and what the record proves.
- Every retained record class had an approved future-use decision and receiving owner.
- Two release blockers were found before cutover and resolved before the gate reopened.
- The retiring environment closed with no unresolved critical exception in the handoff record.
Lessons
What we would carry into the next system.
- Future use is a business and domain decision before it is a mapping decision.
- Reconciliation must prove meaning and access, not only row counts.
- A recoverable archive includes identity, documentation, ownership, and practiced access.
“The migration stopped being a data move and became an operating handoff we could defend.”
Handoff
The engagement ended with an operating owner.
- 01accepted archive and mappings
- 02open low-severity exceptions with owners
- 03access and escalation matrix
- 04quarterly restore rehearsal
- 05retention-review calendar
Start with the decision
Bring the priority. We will help bound the work.
If the decisions or constraints look familiar, start with the operating reality—not a preselected solution.
Start a conversation.