Patient master with MRN merge
Deterministic matching acts unattended, probabilistic matching only proposes into a review queue, and every merge is reversible with a named approver.
The systems a provider actually runs on: patient master and MRN merge, scheduling against provider and room rules, clinical documentation, HL7 v2, FHIR and DICOM interfaces, and the eligibility and claims path that decides whether the work gets paid. Access control, audit and retention are first-sprint requirements here.
Tell us what you are building
Healthcare software development builds the systems a provider runs on: the patient index, scheduling, clinical documentation, and the eligibility and claims path that decides whether the work gets paid. What makes it different is that access control, audit and retention are first-sprint requirements, and the FHIR version your payer accepts is set by regulation, not by you.
Our work
We have one healthcare build, and naming it beats implying a relationship we do not have. iCareHeal sits in our portfolio rather than in a case study, so the first card links there. Zyneto holds no certifications and no attestation report, and SOC 2 is an AICPA attestation examination rather than a certification.
Scope
Eight pieces of work. Most engagements are three or four of them, and the first two decide whether the rest can be trusted.
Deterministic matching acts unattended, probabilistic matching only proposes into a review queue, and every merge is reversible with a named approver.
Provider availability, room and equipment, recall and waitlist. Off-the-shelf calendars model none of it, which is why this is usually the largest module.
Notes, orders and charges written once and still attributable later, including after two identities for one person have been linked.
ADT, ORM, ORU, SIU and DFT behind an interface engine, R4.0.1 alongside them rather than replacing them, imaging identity tied to the order.
The portal steps your billing team re-keys today, turned into machine calls. CMS-0057-F sets 1 January 2027 for four payer FHIR APIs.
Regulated scope
The FDA's final guidance on Clinical Decision Support Software, issued 29 January 2026 under docket FDA-2017-D-6569 and superseding the version issued 6 January 2026, sets four Non-Device CDS criteria under section 520(o)(1)(E) of the FD&C Act. Software is outside the device definition only when it meets all four.
Software that acquires, processes or analyses a medical image, an IVD signal or a signal acquisition pattern for a medical purpose is a device function.
Software aimed at patients or caregivers rather than at a healthcare professional is in scope, however modest the feature.
So is software that does not give the clinician enough of the basis for its recommendation for them not to rely primarily on it.
21 CFR 820.10 requires a documented quality system meeting the applicable requirements of ISO 13485. ISO does not perform certification, in ISO's own words.
We determine regulated scope before a build, not at submission. We are not a notified body, a quality system auditor or your regulatory consultant.
Failure modes
Four failure modes worth naming. Naming them is more useful than a list of reasons to pick a vendor.
Two records get combined by whoever noticed, with no approver and no undo. Keep the source identities and make merge reversible.
Every clinician reads every chart because access was modelled on job title alone. Model the relationship, and review every break-glass.
The evidence a regulator wants sits in debug output with the wrong retention and access. Separate them before the first access review.
Conformance testing and enrolment consume weeks nobody billed, so the launch slips without anyone having been slow.
Make or buy
Most providers do not need a new core system. They need the layer around it, and one decision about where the line falls.
A certified clinical system is heavily tested and expensive to own. Replacing one to close a reporting gap is the costliest way to close it.
The patient index, the access model, the audit trail and the payer calls are where the gaps sit, over HL7 v2 and FHIR R4.0.1.
If the incumbent cannot serve the adopted versions on a regulated channel, that is a replacement argument. A feature wish is not.
Integration
Healthcare integration is an identity problem wearing a messaging protocol. Five layers besides FHIR, and the decision that settles each.
| Layer | What it is | The decision that settles it |
|---|---|---|
| HL7 v2 | ADT for admissions, ORM for orders, ORU for results, SIU for scheduling, DFT for charges. Pipe delimited, and what most estates speak today. | Put an interface engine at the boundary, not segment parsing in application code. |
| DICOM | Imaging interchange. Study, series and instance identity has to agree with the order and the accession, which is where imaging identity breaks. | Settle accession identity at acquisition, not in a reconciliation report. |
| Identity | MRN is local, national identifiers are jurisdictional, and neither is globally unique. One person accumulates several at once. | Prefer link over merge, and make merge reversible with an approver. |
| Clinical codes | SNOMED CT for findings, LOINC for observations and lab, ICD for diagnosis and billing, plus the local drug code. | Decide which is authoritative for each field before any mapping is written. |
| Audit trail | Who accessed which record, when and under what justification, immutable and retained to a schedule. An application log serves engineers. | A different system, with different retention and different access from application logging. |
The patient, the identity and the record are three different things, and a system that collapses them causes clinical harm rather than reporting inconvenience. For the control work over all of it, see what HIPAA compliance adds to an application build.
Versions
Every page competing on this search names FHIR. Two of the five we read on 14 November 2026 give a release, both of them R4, and not one gives the patch version. That is the decision. Regulation adopts R4.0.1 and USCDI v3, while R5 is the latest published release and USCDI v7 the current published version. Building to the newest is how an integration fails conformance.
| Release | Where it stands | What it means for your build |
|---|---|---|
| FHIR R4.0.1 | 45 CFR 170.215(a)(1) adopts HL7 FHIR Release 4.0.1 by name. The HL7 directory dates 4.0.0 to 27 December 2018 and the 4.0.1 errata to 30 October 2019. | Adopted. This is the wire format. Read 17 November 2026. |
| FHIR R5, version 5.0.0 | The latest published release, dated 26 March 2023 in the HL7 directory, and Standard for Trial Use rather than normative as a whole. | Published, not adopted. Keep it off a mandated channel. Read 17 November 2026. |
| FHIR Release 6 | Not published. The newest Release 6 artefacts in the HL7 directory are 6.0.0-ballot5 and 6.0.0-snapshot1, both dated 17 July 2026 and both draft. | Draft only. Nothing to build against yet. Read 17 November 2026. |
| US Core STU 6.1.0 | Adopted at 45 CFR 170.215(b)(1)(ii). The STU 3.1.1 adoption expired on 1 January 2026, and US Core 9.0.0 is the current published release. | Build 6.1.0, and ask which release your partner certified. Read 17 November 2026. |
| SMART App Launch 2.0.0 | Adopted at 45 CFR 170.215(c)(2). The SMART App Launch 1.0.0 adoption expired on 1 January 2026. | Adopted. Plan launch and scopes against 2.0.0. Read 17 November 2026. |
| USCDI v3 | Adopted at 45 CFR 170.213. The USCDI v1 July 2020 Errata adoption expired on 1 January 2026, and USCDI v7 was released on 23 July 2026 per the ASTP standards bulletin. | v3 is the adopted data set. v7 is published only. Read 13 November 2026. |
Read from the eCFR text of 45 CFR part 170 and the HL7 FHIR directory, with the date on each row above. The ONC Deregulatory Actions final rule at 91 FR 67916, effective 28 December 2026 except for amendatory instructions 7, 10 and 12, which take effect 1 January 2027, removes the two expired paragraphs and leaves the FHIR 4.0.1 base standard in place. So: speak R4.0.1 on every regulated interface, and keep the internal model version aware. On the payer side of the same APIs, see how insurers build policy and claims systems.
Dates
Not a badge wall. These are the instruments that change the data model, the retention policy or the launch date. Every row was read against its primary source, and each one carries the date it was last read.
| Instrument | What it forces the software to do | When |
|---|---|---|
| CMS-0057-F, 89 FR 8758 | Impacted payers must run four FHIR APIs conformant with 45 CFR 170.215 and the content standard at 170.213: Patient Access with prior authorization information, Provider Access, Payer-to-Payer, and Prior Authorization. | Prior authorization process policies apply since 1 January 2026, all four APIs from 1 January 2027. Read 17 November 2026. |
| HIPAA Security Rule, 45 CFR 164 subpart C | 164.306(d) splits the specifications into Required and Addressable, 19 and 22 of them in the current text. Encryption is Addressable in both places it appears, 164.312(a)(2)(iv) and 164.312(e)(2)(ii): assess it, then implement it or document what you used instead. | In force since 20 April 2005, per 164.318. Read 17 November 2026. |
| Security Rule proposed rule, 90 FR 898, RIN 0945-AA22 | Proposed, not in force. It would end that split, add a written technology asset inventory and network map at 164.308(a)(1)(i), and define multi-factor authentication. | Comments closed 7 March 2025, final action forecast July 2027. No compliance date. Read 17 November 2026. |
| HIPAA privacy, breach and business associate duties | Access at 164.524, amendment at 164.526, accounting of disclosures at 164.528. Breach notice within 60 calendar days of discovery at 164.404(b), and a business associate notifies the covered entity at 164.410. | Privacy Rule since 14 April 2003, breach rule for breaches on or after 23 September 2009. Read 17 November 2026. |
| FDA guidances on device software functions | Clinical Decision Support Software, final, issued 29 January 2026, docket FDA-2017-D-6569. Predetermined change control plans for AI enabled device software functions, final, issued 18 August 2025, docket FDA-2022-D-2628. Mobile medical applications, final, issued 28 September 2022. | The AI lifecycle management guidance of 7 January 2025 is Draft: a recommendation under consultation, not a current expectation. Read 17 November 2026. |
| 21 CFR part 820, ISO 13485 and IEC 62304 | 820.10 requires a documented quality system meeting the applicable requirements of ISO 13485, and 820.7 incorporates ISO 13485:2016, third edition of 1 March 2016. IEC 62304, consolidated edition 1.1 of 26 June 2015, is the software lifecycle standard. | In force. IEC 62304 edition 2.0 is a committee draft, publication forecast 26 October 2028. Read 13 November 2026. |
| European Health Data Space, Regulation (EU) 2025/327 | Article 25 requires a European interoperability software component and a European logging software component in an EHR system, which it calls the harmonised software components of EHR systems. Article 26 treats software offered as a service to a person established in the Union as put into service. | Applies from 26 March 2027, and Articles 25 to 27 from 26 March 2029 for the first three priority categories. Read 17 November 2026. |
| GDPR, Regulation (EU) 2016/679, Articles 9 and 33 | Health data is a special category, lawful only on an Article 9(2) condition identified per purpose. Article 33 gives the controller 72 hours from awareness, and a processor notifies the controller without undue delay. | Applies since 25 May 2018. Read 17 November 2026. |
| India: DPDP Rules 2025, ABDM and NHCX | The Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), phase their obligations: an early tranche on publication, rule 4 one year after, and notice, consent, security safeguards, breach intimation, rights and transfer eighteen months after. ABDM milestones M1 to M3 cover ABHA identity, record linking and consented retrieval, and the live National Health Claims Exchange carries claims as FHIR R4 bundles. | Tranches run from publication of the notification dated 13 November 2025, so they are relative rather than a calendar deadline. Read 13 November 2026. |
Zyneto holds no certifications and no attestation report. We build to the controls and hand you the evidence for your own audit, and we say in discovery when a scope crosses into device territory. A clinical record also outlives the system holding it, so see how a legal hold coexists with a deletion request.
Transparency
We publish the hours module by module, so you can argue with any line before anyone quotes, and a fixed price follows discovery. The scope below is a clinic or polyclinic operations phase one.
Worked example
1,640 hours
Eight modules added up below.
Typical timeline
3 to 5 months
Plus conformance weeks, which move the launch date.
Useful hours
1,160 to 2,270
Every module at its minimum through to every maximum.
| Driver | Hours |
|---|---|
| Whether the scope is regulatedDevice or GxP scope adds that up front and 15 to 30% on every later release. The largest multiplier here. | Adds 25 to 40% |
| HIPAA in scopeApplied across the board, because business associate duties, minimum necessary and audit logging touch everything. | Adds 10 to 15% |
| Number of HL7 feedsIncluding mapping and conformance testing. The second feed is where the interface engine pays for itself. | 80 to 160 each |
| Payer API workEach channel has its own conformance path, and CMS-0057-F puts four FHIR APIs on impacted payers from 1 January 2027. | 150 to 300 each |
| Conformance calendarABDM M1 to M3 and payer conformance testing consume weeks nobody bills, and move the launch date. | Schedule, not hours |
| Module | Hours |
|---|---|
| Discovery and regulated-scope determination | 60 to 120 |
| Identity, access model and audit log | 180 to 320 |
| Patient master with MRN merge | 120 to 220 |
| Scheduling with provider and room rules | 200 to 400 |
| Clinical documentation and charge capture | 250 to 500 |
| HL7 v2 interfaces, first two feeds | 80 to 160 |
| Eligibility and prior authorisation | 150 to 300 |
| Compliance layer, retention and legal hold | 120 to 250 |
Delivery
Five phases, each named by the artefact it produces, and each artefact is one you can ask to see.
Phase 01
Every place PHI enters, rests and leaves, with the interface inventory and a written determination of what is regulated.
Phase 02
Roles, care relationships, break-glass and the audit log as a separate system, agreed before any screen is built.
Phase 03
Deterministic matching, a review queue for probabilistic candidates, and a merge that is reversible with a named approver.
Phase 04
An interface engine at the boundary, R4.0.1 on the regulated channels, the first feeds mapped and conformance tested.
Phase 05
The map, the access model, the audit log design and the test records, as the evidence your own auditor works from.
Release 4.0.1. 45 CFR 170.215(a)(1) adopts HL7 FHIR Release 4.0.1 by name, with US Core STU 6.1.0 and SMART App Launch 2.0.0 beside it, read from the eCFR text on 17 November 2026. R5 has been published since 26 March 2023, and no US regulation adopts it.
Encryption sits in the Addressable column, in both places it appears: 164.312(a)(2)(iv) and 164.312(e)(2)(ii). Under 164.306(d) you assess it and either implement it or document why it is not reasonable and what you did instead. Encrypting anyway is the cheap option; the written assessment is what an auditor asks for. A proposed rule, 90 FR 898, would end that split, and it is not in force.
When it misses any of the four Non-Device CDS criteria in the FDA's final guidance issued 29 January 2026, docket FDA-2017-D-6569. Analysing a medical image or an IVD signal, aiming the software at patients, or withholding the basis for a recommendation each puts it in scope. In the EU, Annex VIII Rule 11 of Regulation (EU) 2017/745 classifies it instead.
In the United States: HIPAA, the 45 CFR part 170 standards (FHIR R4.0.1, US Core 6.1.0, USCDI v3), CMS-0057-F, and the FDA guidances with 21 CFR part 820 for a device. In the EU: GDPR Article 9, EU MDR and the European Health Data Space. In India: the DPDP Rules 2025, ABDM and NHCX. The table above carries each with its date.
Four recur. Duplicate patient records nobody dares merge. Access modelled on job title without the care relationship. HL7 parsed in application code, so every new feed is a regression risk. Conformance testing left out of the plan, which moves the launch date.
Ask which FHIR release they put on the wire, and expect 4.0.1 with the 45 CFR 170.215 citation rather than the bare word FHIR. Ask where encryption sits in their HIPAA control set. Ask for a written regulated-scope determination, the hours module by module, and the artefacts they hand your auditor.
The obligations sit with the covered entity and reach a vendor through the written assurances at 164.502(e) and 164.314(a). What a vendor contributes is the control evidence: the data-flow map, the access model, the audit log design and the test records your auditor works from. SOC 2 is an AICPA attestation examination rather than a certification.
Six questions worth asking any healthcare software development company, this one included.
A vendor who answers FHIR without a release has not read 45 CFR 170.215(a)(1). The answer is 4.0.1, with US Core 6.1.0.
The accurate answer names the Addressable column at 164.312(a)(2)(iv), then shows the written assessment behind the decision.
The four Non-Device CDS criteria applied to your feature list, before the build rather than at submission.
HL7 v2 and FHIR R4.0.1 will coexist for years, and somebody has to own the map between them.
A data-flow map, an access model, an audit log design and test records. A badge is not evidence; those artefacts are.
A total you cannot argue with line by line is not a scope. Every module above shows its own range.
Almost every question on this page resolves to where PHI goes and who may see it. We will map that, say in writing whether any of your scope is regulated, and give you the hours either way.
Real feedback from the people we've proudly partnered with.
Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.
We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.
Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.
Explore further
Patient index, audit log and retention
Clinician, front desk and patient surfaces
Offline-first field and visit apps
Clinical documents, retention and legal hold
Triage and denial worklist assistance
Retrieval over policy and protocol libraries
Claims, adjudication and the payer side
Records scoped to a session, and consent
Every sector we build for, in one place
Guides on clinical systems, patient data controls and the document work that sits beside them, written by the team that builds them.