MedFlow SKG
For multi-site clinic chains & private hospital groups

Data interoperability for healthcare chains

Own your patient data,
free from HIS vendor lock-in

MedFlow syncs data from the software you already use into a standards-based FHIR Storage hosted at your hospital. Your current systems stay as they are.

Keep your systemsHIS, EMR, RIS and LIS run as before.
Data stays at the hospitalFHIR Storage runs on the hospital’s own server.
Ready in 1–2 monthsA 30-day trial run before acceptance.
Current software
BN_HOTENNGUYEN VAN AN
NGSINH19800315
F011
SO_CCCD079 080 001 234
MA_KCBCS1-0000361
TT_XN045.8 / 4.1-5.9
FHIR Storage
Patient.nameNguyễn Văn An
·birthDate1980-03-15
·gendermale
·identifierNat. ID 079080001234
·identifierCS1-0000361
Observation5.8 mmol/L — normal

The same patient. Left: the HIS vendor’s own conventions. Right: the FHIR standard, readable by any compliant software.

01The problem

The data belongs to the hospital, but the hospital can’t use it

  1. 01

    New software has to wait for the HIS vendor

    Medical records, booking apps and result portals all need patient data. HIS vendors often won’t open it, or open it on their own price and timeline.

  2. 02

    Every branch keeps its own record

    Doctors can’t see results from other branches. Patients repeat tests or carry their own papers.

  3. 03

    Every new site adds another system

    New or acquired sites often run different software. Chain-wide reports are still compiled by hand.

02The solution

Keep your systems, add one shared FHIR Storage

MedFlow syncs data into the FHIR Storage automatically. New software connects there, without going through your current vendors.

Vendor-specific link MedFlow

Today

One patient, two different IDs no single place holds the full record A-00123 B-2024-778 EHR HIS won’t share data Each branch: HIS, LIS, RIS from its own vendors its own data, catalogs, patient IDs linked in vendor-specific ways BRANCH A HIS A + EMR vendor-specific data patient ID: A-00123 LIS A RIS A orders ↔ results proprietary link proprietary link BRANCH B HIS B + EMR vendor-specific data patient ID: B-2024-778 LIS B RIS B orders ↔ results proprietary link proprietary link
Each branch runs its own HIS, LIS and RIS. One patient carries several IDs, and no single place holds the full record.

With MedFlow

Shared FHIR Storage · hospital-owned one ID per patient, matched by national ID branch IDs kept: A-00123 · B-2024-778 EHR portal one patient, every branch FHIR API MedFlow: no HIS vendor API needed never writes to the HIS HIS–LIS–RIS links untouched BRANCH A HIS A + EMR vendor-specific data patient ID: A-00123 LIS A RIS A orders ↔ results proprietary link proprietary link MedFlow continuous sync read-only BRANCH B HIS B + EMR vendor-specific data patient ID: B-2024-778 LIS B RIS B orders ↔ results proprietary link proprietary link MedFlow continuous sync read-only
Every branch’s data lands in one shared FHIR Storage, standardized, with one ID per patient. Ready to power an EHR portal. The HIS doesn’t change.
About FHIR

The international standard for exchanging healthcare data. Vietnam’s Ministry of Health digital architecture framework (Decision 2146/QĐ-BYT, 15 July 2026) adopts HL7® FHIR® R4.

The hospital owns the FHIR Storage. MedFlow only handles the sync.

03Benefits

Integrate on the hospital’s own schedule

Electronic medical records

Data flows straight into your EMR, no HIS API required.

Chain-wide patient record

Doctors at any branch see visit history, lab results and imaging.

Patient app

Booking and results for every branch in one app.

HL7 FHIR FHIR Storage Chain-wide data in FHIR R4 Hospital-owned

Management reporting

Chain-wide figures updated daily, no manual consolidation.

Insurers and partners

Share standard data with insurers and lab partners.

Growing the chain

New sites sync into the same place, whatever software they run.

04Safety and ownership

Three common questions

Will it affect clinical operations?

No. MedFlow only reads. It changes nothing and installs nothing on running systems.
  • Historical sync runs off-peak and pauses automatically if the system slows down.

Does patient data leave the hospital?

No. Data only goes to the FHIR Storage on the hospital’s own infrastructure.
  • Reports sent outside contain aggregate figures only, never patient information.

Will the hospital depend on the implementation partner?

No. The hospital owns the FHIR Storage and holds top-level admin rights.
  • If the contract ends: The FHIR Storage keeps running; only new syncing stops.
  • If the partner ceases operations: The FHIR Storage runs on open-source software with no license fees. The sync source code is handed over under an escrow arrangement.

05Implementation

The hospital prepares, MedFlow delivers

The hospital is mainly involved in the first two phases, then reviews results and trials the system.

Prerequisites

  1. Maintenance contract allows read access to dataThe HIS vendor doesn’t need to open an API or do any extra work.
  2. Database can enable change loggingConfirmed during the feasibility check.
  3. A server owned by the hospitalThe FHIR Storage runs on it.
  4. Each site can reach the FHIR StorageNo network link between sites needed.
  5. One IT staff member in chargeSingle point of contact.

Phases

1 dayFeasibility check
1–2 monthsPreparation, survey, design, FHIR Storage build
30 days or moreTrial run and acceptance
YearlyOperations
Phase 0

Feasibility check

Know whether it can be deployed, before signing.

1 day · Free
  1. MedFlowProvides the tool
  2. HospitalCreates a read-only account, runs the tool
  3. MedFlowAnalyzes and reports
Outcome

Feasibility report: readiness, what to prepare, recommended server specs.

Move to phase 1 whenThe hospital decides to proceed and both sides sign.

Phase 1

Preparation and survey

Infrastructure ready, data understood.

Phases 1 + 2: 1–2 months
  1. MedFlowGuides preparation
  2. HospitalGrants read access, prepares the server
  3. MedFlowSurveys data quality
  4. HospitalChecks 30 sample records
Outcome

Readiness sign-off and a data quality report: records missing a national ID, duplicates…

Move to phase 2 whenThe hospital confirms the survey results and the server is ready.

Phase 2

Design and build the FHIR Storage

A FHIR Storage holding the full history.

Phases 1 + 2: 1–2 months
  1. MedFlowDesigns the data mapping
  2. HospitalApproves design and acceptance criteria
  3. MedFlowBuilds the FHIR Storage, loads history
Outcome

A FHIR Storage with full history, plus a reconciliation report against the source systems.

Move to phase 3 whenReconciled figures match the source systems.

Phase 3

Trial run and acceptance

Prove the FHIR Storage works under real conditions.

At least 30 days
  1. HospitalUses it for real
  2. MedFlowDaily checks, sync cut-off test
  3. HospitalSigns acceptance
Outcome

Criteria met for 30 consecutive days. Handover of admin rights, runbooks and a full data export tool.

Move to phase 4 whenBoth sides sign the acceptance record.

Phase 4

Operations

Data stays complete and accurate.

Annual contract
  1. MedFlowDaily monitoring
  2. HospitalGives notice before software upgrades
  3. MedFlowAdapts to changes
Outcome

Quarterly data quality report for the board.

Next step

Start with a one-day feasibility check

Free, run by the hospital’s IT team inside its own network. The report contains no patient information.