Built for the team that has to prove it works before go-live
If your job is to sign off on a go-live, approve an upgrade, or certify a new interface, "it worked in the demo" is not evidence. You need to know what happens when a lab sends a code your system has never seen, when a note carries characters that break a parser, when every hospital stamps its own local time, and when a receiving system has to decide, on its own, what an unfamiliar result means. MediFlow generates that traffic, synthetic patients sending real HL7 v2 and FHIR R4 the way hospitals actually send it, so you find the defect before a patient does.
How a test run works
Choose the hospitals and the format
One hospital to test a single channel, or the whole network to rehearse a regional platform. HL7 v2, FHIR R4, or both.
MediFlow seals the answer key
What every message really means is written down and sealed before anything is sent, so nobody can tune the result afterwards.
Your system receives real traffic
Complete patient journeys in each hospital's own codes, identifiers and local time, over the channels you already run.
Every outcome is scored
Resolved correctly, held for a person, wrong, or a false alert, against the sealed key. Wrong and false alert fail the run.
Four teams, four different things to prove
The new or replacement system handles the full range of message types and patient journeys a live hospital produces, not a curated sample.
Every channel (ADT, ORU, orders, pharmacy, billing) parses, routes and acknowledges correctly, including the awkward ones: local codes, special characters, unfamiliar identifier formats.
A result coded by someone else's local system still lands as the right test, on the right specimen, in the right units, in your system.
The whole cutover, registration through results, orders, notes, billing and claims, behaves the way the plan says it will, with evidence to show a steering committee.
HL7 and FHIR, side by side
Most hospitals run both. Every MediFlow send chooses its format, so the same patient can be sent over HL7 v2, over FHIR R4, or over both, and you can see whether your system treats them the same way.
As your interface engine already sees it
Full message workflows with acknowledgements, from registration through results, notes, orders and billing.
Transaction bundles, confirmed on receipt
Patient, Encounter and Observations in one bundle. A delivery counts only when a separate read of the receiver confirms it was committed.
Lab results go over FHIR today. Diagnoses, charges, medications and immunizations stay on HL7 while their FHIR versions are built.
The answer stays on our side
A test that hands your system the standard code proves nothing about mapping. Each simulated hospital sends its own local codes and names, the way a real laboratory does. The standard code is the answer: it is kept in a sealed answer key and never sent.
Every HL7 message and FHIR bundle is checked before it leaves, and one that carries the answer is refused, not repaired. When a test does need the standard code on the wire, it is switched on deliberately, and every such message is marked so the receiver and the scorer both know.
The kind of defect this is built to catch
22 simulated hospitals, each with its own habits
A single anonymous test feed cannot tell you what happens when a dozen critical-access hospitals each code potassium a little differently, or when a rural hospital's accession numbers do not look like a regional referral center's. MediFlow's registry holds 22 simulated hospitals, 21 rural and critical-access hospitals plus a CareCompile reference hospital, with 14 switched on at any time.
Each hospital keeps its own MRN, visit and accession formats, its own local codes and names, and its own local time with its own offset. Send as a single hospital to test one channel, or run all of them together to rehearse a regional platform, with results reported per hospital.
Everything a real hospital sends, not a curated sample
Codes are checked against the official LOINC, ICD-10-CM, RxNorm and CVX releases before they ship, so a rejection in your test run is your system's behavior, not a symptom of bad test data. See validated test data for how that check is enforced.
Patient flow
Results and notes
Orders and pharmacy
Billing and claims
Messy on purpose, because production is messy
A clean, well-formed test file is easy to build and tells you very little. MediFlow keeps the parts of real hospital data that usually get sanded off a demo.
Local codes, not standard ones
Sent as the hospital's own code, because that is what your mapping layer will actually meet.
Free text with HL7 special characters
The escaping bugs that only show up once a note has an ampersand or a pipe in it.
Each hospital's own local time
Stamped with its UTC offset, so a receiver that ignores the offset is caught rather than silently hours off.
For lab informatics: a scored semantic bench
Beyond whether a code is valid, the bench asks whether your system understood it: cases across potassium, sodium, glucose, creatinine and hemoglobin and more, each hospital coding the same test its own way, with deliberate traps such as a urine result given a blood-sounding name, one hospital reusing another's code for a different test, and results reported per twenty-four hours instead of per sample. Every case is graded against an answer key sealed before the run, over HL7 or FHIR. That is a number a lab informatics team can bring to a go-live review, not an impression.
What you bring to a go-live decision
Complete patient journeys
Registration through results, orders, notes and billing, for as many synthetic patients as the test needs.
Per-hospital results
A regional platform sees which hospital's traffic mapped cleanly and which one did not.
An answer key for every run
A clean pass means something, and a failure points at a defect class, not a mystery.
No real patient data
The rehearsal itself never becomes a privacy question.
Tell us what you need to trust
Describe the workflow, interface or release you are validating. We define the synthetic patients, the interface profile, the expected outcomes and the evidence you get back. Access is by contract through CareCompile. Reply within one business day.