The practice

Six services, one discipline: durable systems for population health.

Parker DHC does not sell frameworks or platforms. It sells a specific way of thinking about digital-health architecture, carried by one senior practitioner and, when needed, by a bench of trusted associates. Below is the shape of the practice, broken into six services that are usually delivered together.

Enterprise & reference architecture

Reference architecture that survives the programme.

National reference architectures, federated EHR blueprints, and system-of-systems designs: the kind of artefact that outlives a minister, a vendor, and often the sponsoring agency itself.

What

National and jurisdictional reference architectures
Federated / distributed EHR blueprints (viewer + registry + repository patterns)
Master person/patient/provider indexing designs
Consent, identity, and privacy architecture at population scale
Cross-border and cross-jurisdictional integration patterns

How

Every engagement starts with a written architecture principles document: around twenty numbered principles, agreed by the sponsor before any diagram is drawn. Every subsequent design decision is traceable back to those principles.

Who it's for

Chief architects, CIOs, national programme executives, and boards asking "is our architecture actually going to hold?"

Standards & interoperability

Standards chosen so they can actually be implemented.

HL7 v2, CDA, and FHIR; SNOMED CT, LOINC, ICD; ISO/TC 215 profiles. Ron's work is less about which standard to pick and more about the shape of the profile you build on top of it.

What

Interoperability strategy across a national or programme portfolio
FHIR profile design, ballot preparation, and IG development
Terminology governance (SNOMED CT, LOINC, ICD, national extensions)
Standards development organisation (SDO) engagement strategy
Conformance and certification frameworks

How

The standards decision is treated as a change-management problem, not a technology one. The output is not just a chosen standard; it is a governance model, a versioning plan, and a shortlist of the ten implementers who will actually build against it.

Who it's for

National standards agencies, digital-health authorities, SDO working groups, HTA bodies, and integration platform teams.

National blueprints

Country-level platform plans, phased and financeable.

From a digital-health strategy paper to a platform that a ministry can actually procure. Ron has done this on four continents, always in partnership with local architects and local delivery capacity.

What

National digital-health platform blueprints (aligned to WHO/ITU reference model)
Multi-year implementation roadmaps with phased financeable tranches
Total-cost-of-ownership modelling and donor-fundable cost cases
Local systems integrator / vendor market mapping
Handover plans for national architecture teams to own the blueprint

How

The blueprint is designed backwards from the ministry's procurement cycle, not forwards from a technology stack. If a jurisdiction cannot procure and operate what is designed, the design is wrong.

Who it's for

Ministries of health, national digital-health authorities, and the donor programmes and multilaterals that co-finance them.

Programme advisory

Independent counsel to executives, boards, and steering committees.

Confidential, on-call advisory to leaders inside complex digital-health programmes, often at the moment the programme is turning, not at the moment it is being launched.

What

Executive briefings and board papers on architecture, standards, or risk
Independent expert reviews (health-check assessments) of in-flight programmes
Procurement advisory (evaluation frameworks, vendor shortlisting, contract structure)
Steering committee facilitation on contested technical decisions
Post-mortem and lessons-learned engagements when a programme has stumbled

How

Ron works alongside the executive, not in place of them. The deliverable is usually a short, sharply argued paper (not a slide deck) that the executive can put their own name on.

Who it's for

CIOs, chief architects, programme directors, boards, oversight committees, and their legal or governance staff.

Standards governance

Councils, working groups, and the machinery of durable standards.

The reason a standards portfolio holds together over decades is not the standards themselves; it is the councils, editorial groups, and change-control that steward them. Ron has designed and run several such structures.

What

Design of national and cross-jurisdictional standards councils
Working-group charters, editorial workflows, and ballot procedures
Change-management and versioning policy for standards portfolios
Conflict-resolution and consensus-forming for contested standards
Mentoring the next generation of standards leaders

How

Every governance design is built around who has to say yes, who has to say no, and who has to live with the answer. The structural detail matters (quorum, tie-break, appeal) because that is what keeps politics out of the technical decisions.

Who it's for

National standards bodies, HL7 affiliates, ISO delegations, and multi-stakeholder programmes needing a durable governance spine.

Capacity building

Teaching the practice to the people who will do it next.

Multi-week and multi-year capacity-building programmes for national architecture teams, turning graduate analysts into architects who can hold their own in a WHO meeting.

What

Curriculum design for national digital-health architecture teams
Multi-day executive workshops on architecture, standards, and governance
Mentoring individual chief architects and standards leads
Design-critique clinics on live architecture artefacts
Train-the-trainer programmes to make capacity building self-sustaining

How

The work is always structured so that the local team owns the artefacts by the end. Ron's explicit measure of success: the client should not need to hire him for the same problem twice.

Who it's for

National digital-health authorities, ministries, university programmes, and donor-funded capacity initiatives.

Working style

How the practice actually runs.

Six habits that have held up over four decades of complex programmes on four continents.

Written before drawn

Every architecture decision is a paragraph before it is a diagram. Diagrams reify assumptions; sentences expose them.

Principle-anchored

Every engagement starts with a signed principles document. Every subsequent decision is traced to a principle: no principle, no decision.

Small teams, senior time

Parker DHC engagements are led personally by Ron. When associates are brought in, they are senior peers, not junior labour.

Ministry-clock, not vendor-clock

The pace of the engagement is set by the client's governance cycle, not by an artificial delivery cadence imposed from outside.

Handover as measure of success

The last two weeks of every engagement are structured around the client's own team owning the artefact. If they cannot maintain it, the engagement failed.

Discreet on attribution

Clients and countries are not named unless explicit permission is granted. The reputation of the practice depends on that discipline.

Which service fits?

A thirty-minute call is usually enough to know.

Bring one question or one dilemma from your current programme. Ron will tell you whether Parker DHC is a fit, and if not, will usually name someone who is.

Request a briefing Email ron@parkerdhc.com