← DPI-H Reference Architecture (draft v1.0, public review)
Generated 2026-11-17 12:20 UTC from the comment store. Open = not yet decided. Editing = decided, and the change is being made on a feature branch. Closed = incorporated, duplicate or withdrawn.
| Id | Change | Committee | Status | Comments | Issue | PR | |
|---|---|---|---|---|---|---|---|
| CS-001 | Apply editorial and clarity revisions to the executive summaryrequirements- Complete incomplete sentences, define DPI-F at first use, and simplify the flagged wording its 14 comments, in full | Editorial 14 of 14 | proposed | 14 | Discuss | show its comments | |
| CS-002 | Broaden the executive summary's coverage of the subjectrequirements- Expand the summary to cover purpose, the two-layer architecture, components and implementation its 6 comments, in full | Editorial 3 of 6 Core architects 2WHO 1 | proposed | 6 | Discuss | show its comments | |
| CS-003 | Extend Phase 1 of the planning figure to the data landscaperequirements- Extend the Phase 1 inventory step to data workflows and uses, in prose and in Figure 1 its 4 comments, in full | Editorial 3 of 4 Core architects 1 | proposed | 4 | Discuss | show its comments | |
| CS-004 | Broaden the named audiences with role-based reading pathsrequirements- Provide a non-technical summary or companion for clinical and patient audiences its 8 comments, in full | Core architects 4 of 8 Editorial 4 | editing | 8 | #21 | #16 | show its comments |
| CS-005 | Apply plain-language editorial revisions to section 1.1requirements- Revise the flagged sentences and headings in 1.1 for readability without changing meaning its 18 comments, in full | Editorial 17 of 18 No 1 | proposed | 18 | Discuss | show its comments | |
| CS-006 | Present the illustrative DPI country cases in balanced contextrequirements- Add context, documented benefits, known limitations and safeguards for Aadhaar, CoWIN and X-Road its 3 comments, in full | Core architects 2 of 3 No 1 | proposed | 3 | Discuss | show its comments | |
| CS-007 | Present the DPI-H definition as a working definitionrequirements- Introduce DPI-H as the working definition adopted for this guidance its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-008 | State the document's normative status and what it does not deciderequirements- Replace or qualify 'authoritative reference point' so it matches the adaptable, non-prescriptive intent its 3 comments, in full | Core architects 2 of 3 Editorial 1 | proposed | 3 | Discuss | show its comments | |
| CS-009 | Clarify health identification's independence from civil ID in 1.2.1requirements- State that a health identifier and essential care must not require civil ID its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-010 | Rephrase 1.2.1 sentences for readabilityrequirements- Simplify the flagged sentences in 1.2.1 without changing meaning its 2 comments, in full | Editorial 2 of 2 | proposed | 2 | Discuss | show its comments | |
| CS-011 | Guide health use of partial or absent foundational DPIrequirements- Give prominence to proceeding without waiting for foundational DPI its 6 comments, in full | Core architects 5 of 6 Editorial 1 | proposed | 6 | Discuss | show its comments | |
| CS-012 | Present population health statistics as a primary use of health datarequirements- Rebalance 1.2.3 so statistical and epidemiological uses come before financing uses its 1 comment, in full | Core architects 1 of 1 | proposed | 1 | Discuss | show its comments | |
| CS-013 | Strengthen the Chapter 1 analysis of fragmentation and its costsrequirements- Bring the structural-incentives analysis forward as framing its 7 comments, in full | Core architects 6 of 7 Editorial 1 | proposed | 7 | Discuss | show its comments | |
| CS-014 | Broaden the measures of architecture value and success in Chapter 1requirements- Add a measure of whether receiving actors act appropriately on exchanged information, alongside conformance metrics its 3 comments, in full | Core architects 2 of 3 Clinical 1 | proposed | 3 | Discuss | show its comments | |
| CS-015 | Add principles on information availability and metadata-only coordinationrequirements- Describe coordination that confirms events and state without moving clinical content its 2 comments, in full | Core architects 2 of 2 | proposed | 2 | Discuss | show its comments | |
| CS-016 | Add trust and accountable public governance to the principlesrequirements- State that architecture enables but does not manufacture trust; name transparency and redress conditions its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-017 | Map the principles to design principles and protected invariantsrequirements- Show which Section 1.4 principles each Section 2.3 design principle operationalises its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-018 | Add a right to connect for conformant participantsrequirements- State that conformant participants may connect on published, non-discriminatory terms with appeal its 1 comment, in full | Core architects 1 of 1 | proposed | 1 | Discuss | show its comments | |
| CS-019 | Revise the continuity-of-care goal and its mappingsrequirements- Add referral, transition-of-care, medication reconciliation and scheduling capabilities as operational dependencies its 14 comments, in full | Clinical 10 of 14 Core architects 2Editorial 2 | proposed | 14 | Discuss | show its comments | |
| CS-020 | Broaden the public health goal toward health-system resiliencerequirements- Reframe the goal toward health-system resilience, distinguishing surveillance from preparedness, response and recovery its 18 comments, in full | Core architects 15 of 18 WHO 2Supply chain 1 | proposed | 18 | Discuss | show its comments | |
| CS-021 | Align the health workforce goal with NHWA and a system perspectiverequirements- Add the health-system planning perspective and equitable distribution its 25 comments, in full | Core architects 21 of 25 WHO 2Metadata registries 1Financial systems 1 | editing | 25 | #20 | #16 | show its comments |
| CS-022 | Consider a shared registry of identified subjects of interestrequirements- Discuss whether linking identified subjects for reporting, auditing and registries needs a shared DPI component its 1 comment, in full | No 1 of 1 | proposed | 1 | Discuss | show its comments | |
| CS-023 | Document how the goals were selected and mapped to componentsrequirements- Describe participants, evidence, steps and validation its 8 comments, in full | Core architects 6 of 8 WHO 1No 1 | proposed | 8 | Discuss | show its comments | |
| CS-024 | Address decentralised and subnational implementation settingsrequirements- Describe implementation where responsibility is shared across national, state and local levels its 8 comments, in full | Core architects 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-025 | Clarify the boundary between DPI-H and point-of-service applicationsrequirements- Add a short 'what is and is not a DPI-H component' summary at the start of 3.5 with examples its 6 comments, in full | Core architects 6 of 6 | proposed | 6 | Discuss | show its comments | |
| CS-026 | Give criteria for prioritising and sequencing componentsrequirements- Indicate which components are a baseline and which become relevant by national goals and maturity its 7 comments, in full | Core architects 6 of 7 No 1 | proposed | 7 | Discuss | show its comments | |
| CS-027 | Clarify terms and wording in 2.2.1requirements- Fix the sentence after 'the means to exchange data between them' (punctuation, capitalisation) so the interdependence point reads clearly its 4 comments, in full | Core architects 2 of 4 Editorial 2 | proposed | 4 | Discuss | show its comments | |
| CS-028 | Define what 'open technologies' and 'open content' meanrequirements- Define whether 'open technologies' means open source, openly documented or royalty-free technology its 3 comments, in full | Metadata registries 1 of 3 WHO 1Core architects 1 | proposed | 3 | Discuss | show its comments | |
| CS-029 | Revise Table 2.2 rows and component columnrequirements- Reconcile Table 2.2 (LIMR as a later enabler) with 4.3.1 and the architecture-placement guidance its 6 comments, in full | Core architects 4 of 6 Metadata registries 2 | proposed | 6 | Discuss | show its comments | |
| CS-030 | Apply minor editorial fixes to the Chapter 2 introduction and Figure 2.2requirements- Replace 'semantic and terminology services' with the named components and semantic governance its 3 comments, in full | Editorial 2 of 3 Core architects 1 | proposed | 3 | Discuss | show its comments | |
| CS-031 | Define REDDHI once with one consistent foundational corerequirements- Give a concise definition stating that REDDHI names a state of maturity, not a set of components its 13 comments, in full | Core architects 12 of 13 WHO 1 | proposed | 13 | Discuss | show its comments | |
| CS-032 | Provide REDDHI maturity stages with measurable markersrequirements- Define maturity stages (e.g. foundational, intermediate, advanced) without making REDDHI a one-time certification its 10 comments, in full | Core architects 10 of 10 | proposed | 10 | Discuss | show its comments | |
| CS-033 | Replace 'HMIS is not foundational' with a contextual classification testrequirements- Remove the categorical statement and give a functional test for when a shared HMIS/RHIS platform is foundational its 9 comments, in full | Core architects 8 of 9 Editorial 1 | proposed | 9 | Discuss | show its comments | |
| CS-034 | Extend and present the goal articulation structure consistentlyrequirements- Add assumptions, risks, indicators and dependencies its 4 comments, in full | Core architects 2 of 4 Editorial 2 | proposed | 4 | Discuss | show its comments | |
| CS-035 | Apply minor editorial fixes in section 2.4requirements- Clarify or replace the term its 3 comments, in full | Editorial 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-036 | Revise the health financing goal and Table 2.4 capabilitiesrequirements- Consider the proposed redraft of 2.4.2 and Table 2.4 its 9 comments, in full | Financial systems 6 of 9 Core architects 1Editorial 1No 1 | proposed | 9 | Discuss | show its comments | |
| CS-037 | Carry the 'financing DPI-H versus DPI-H for financing' distinction throughrequirements- State the distinction as a principle and apply it in Chapters 1 and 4 its 3 comments, in full | Core architects 2 of 3 Financial systems 1 | proposed | 3 | Discuss | show its comments | |
| CS-038 | Define accountability and data-responsibility roles for componentsrequirements- Define accountability across the LHR service, contributors and stewards its 7 comments, in full | Core architects 4 of 7 Clinical 3 | proposed | 7 | Discuss | show its comments | |
| CS-039 | Explain the ArchiMate notation and add a non-technical entry pointrequirements- Explain why the selected subset suffices and what it excludes its 18 comments, in full | Core architects 11 of 18 Editorial 7 | proposed | 18 | Discuss | show its comments | |
| CS-040 | Correct ArchiMate element definitions and relationships in 3.1 and 3.7requirements- Use composition for whole-part and access for data objects its 8 comments, in full | Core architects 6 of 8 Editorial 2 | proposed | 8 | Discuss | show its comments | |
| CS-041 | Broaden the architecture description method in 3.2requirements- Introduce the many-to-many relation between elements and systems when the two-layer model is first described its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-042 | Clarify how the reference architecture relates to country architecturesrequirements- State what an enterprise architecture is and how this reference architecture complements it its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-043 | Revise the personal access goal to cover channels and data rightsrequirements- Qualify the rights statement as subject to applicable law its 19 comments, in full | Core architects 12 of 19 Clinical 7 | proposed | 19 | Discuss | show its comments | |
| CS-044 | Clarify governance levels, delegated authority and the strategic rolerequirements- Resolve the tension between 'does not manage operations' and the monitoring/fee-adjustment actions in 3.4.3 its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-045 | Add safeguards where governance roles are concentratedrequirements- State that mandate and execution remain logically separated even when housed in one body in early-stage settings its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-046 | Define escalation, dispute-resolution and enforcement routesrequirements- Add triggers for patient-safety events, privacy breaches, systemic data-quality failure, legal non-compliance, supplier failure and inequitable access its 5 comments, in full | Core architects 4 of 5 Clinical 1 | proposed | 5 | Discuss | show its comments | |
| CS-047 | Define monitoring, review cycles and public reporting in governancerequirements- Extend operational monitoring to point-of-care consequences (workarounds, delayed care, near misses) its 11 comments, in full | Core architects 9 of 11 Clinical 1No 1 | proposed | 11 | Discuss | show its comments | |
| CS-048 | Specify how representation translates into decision influencerequirements- Describe mechanisms that give represented groups genuine influence (decision rights, transparent selection, agenda-setting, feedback obligations) its 8 comments, in full | Core architects 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-049 | Add legal authority and legal instruments to governance guidancerequirements- Add institutional and legal preconditions to the starting-point assessment its 9 comments, in full | Core architects 9 of 9 | proposed | 9 | Discuss | show its comments | |
| CS-050 | Revise the commons-governance principles in 3.4.2requirements- Keep the subsidiarity bullet to 'authority at the lowest effective level' and move mandate/execution matching to the next principle its 7 comments, in full | Core architects 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-051 | Allow authoritative registry responsibility to be distributedrequirements- Replace 'single accountable source' with clearly defined authoritative responsibility that may be distributed across recognised sources its 7 comments, in full | Supply chain 3 of 7 Core architects 3No 1 | proposed | 7 | Discuss | show its comments | |
| CS-052 | Apply minor editorial and structural fixes in 3.4requirements- Shorten the governance definition and add a plain-language summary for non-specialist readers its 3 comments, in full | Editorial 2 of 3 No 1 | proposed | 3 | Discuss | show its comments | |
| CS-053 | Expand regional governance and operation modelsrequirements- Distinguish components governed regionally but operated nationally from components operated once regionally as a shared service its 6 comments, in full | Core architects 6 of 6 | proposed | 6 | Discuss | show its comments | |
| CS-054 | Provide governance maturity assessment dimensionsrequirements- Describe dimensions, evidence and link to sequencing for governance maturity assessment its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-055 | Clarify SGI as an institutional capability with an operating modelrequirements- State at the start of Appendix F that SGI is an institutional and operational framework supported by tools, not a single software platform its 21 comments, in full | Metadata registries 15 of 21 Core architects 3Editorial 3 | proposed | 21 | Discuss | show its comments | |
| CS-056 | Present terminology governance as federated with international SDOsrequirements- Define the TS as a governed capability that may host, federate, mirror or provide access to sources its 19 comments, in full | Metadata registries 18 of 19 WHO 1 | proposed | 19 | Discuss | show its comments | |
| CS-057 | Define the artefact types SGI governsrequirements- Enumerate governed artefact types (terminologies, value sets, logical models, IGs/profiles, mappings, identifier systems, indicators, computable guidelines, benefit rules) its 10 comments, in full | Metadata registries 9 of 10 Core architects 1 | proposed | 10 | Discuss | show its comments | |
| CS-058 | Explain how SGI decisions become machine-checkable runtime constraintsrequirements- Describe how approved semantic constraints are published in computable form and enforced by validation of data instances its 4 comments, in full | Metadata registries 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-059 | Clarify where AI, CDSE, LIMR and SGI sit relative to each otherrequirements- Clarify the relation between AI models and the CDSE its 10 comments, in full | Core architects 7 of 10 Metadata registries 1Clinical 1No 1 | proposed | 10 | Discuss | show its comments | |
| CS-060 | Apply minor editorial fixes in 3.5requirements- Delete the trailing fragment 'person-centred that' and the duplicated 'that that' its 5 comments, in full | Editorial 4 of 5 No 1 | proposed | 5 | Discuss | show its comments | |
| CS-061 | Revise the criteria for designating DPI-H componentsrequirements- Define 'foundational health system functions' more precisely, e.g. with a dependency or irreplaceability test its 16 comments, in full | Core architects 15 of 16 Editorial 1 | proposed | 16 | Discuss | show its comments | |
| CS-062 | Add an assessment matrix and overview table for the componentsrequirements- Show, per component, how each defining criterion is met, including partial compliance its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-063 | Extend the component description templaterequirements- Add fields for accountable authority, operating model, prerequisites and dependencies, non-functional requirements and risks its 8 comments, in full | Core architects 6 of 8 Supply chain 1Clinical 1 | proposed | 8 | Discuss | show its comments | |
| CS-064 | Clarify the shared data layer's scope and data responsibilitiesrequirements- Recognise that interoperability can be achieved through data-level integration as well as exchange topology its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-065 | Describe the component catalogue as open to governed extensionrequirements- State that the two layers are the current release's component set, with criteria and a process for adding components its 2 comments, in full | Core architects 2 of 2 | proposed | 2 | Discuss | show its comments | |
| CS-066 | Correct the LIMR versus Terminology Service distinctionrequirements- Separate governance, content repositories, authoring tools and runtime services its 10 comments, in full | Metadata registries 10 of 10 | proposed | 10 | Discuss | show its comments | |
| CS-067 | Broaden Terminology Service scope and conformance referencesrequirements- Include UCUM and unit validation in the example and terminology list its 4 comments, in full | Metadata registries 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-068 | Normalise component granularity and namingrequirements- Define CDSE, surveillance platform and HMIS as bounded capabilities at a similar level its 10 comments, in full | Core architects 5 of 10 Editorial 4Clinical 1 | proposed | 10 | Discuss | show its comments | |
| CS-069 | Address shared care planning and ownership of care coordinationrequirements- Assess a governed shared, multi-professional care plan as a component with its own governance and exchange rules its 4 comments, in full | Clinical 3 of 4 Core architects 1 | proposed | 4 | Discuss | show its comments | |
| CS-070 | Expand the remedy for interoperable silosrequirements- State that local extensions must keep exchanged data conformant to the national minimum model its 5 comments, in full | Core architects 3 of 5 Metadata registries 1Editorial 1 | proposed | 5 | Discuss | show its comments | |
| CS-071 | Address long-term archiving and retrieval of digital health recordsrequirements- Add guidance on long-term archiving, including preserving readability of records and supporting system/version registries its 1 comment, in full | No 1 of 1 | proposed | 1 | Discuss | show its comments | |
| CS-072 | Govern adapters and transformations that may alter meaningrequirements- Allow systems internal models provided boundaries are conformant and meaning-preserving its 10 comments, in full | Metadata registries 7 of 10 Core architects 3 | proposed | 10 | Discuss | show its comments | |
| CS-073 | Decompose mediation into placeable, composable capabilitiesrequirements- Decompose interoperability/mediation into capabilities (routing, transformation, discovery, audit, trust) its 9 comments, in full | Core architects 9 of 9 | proposed | 9 | Discuss | show its comments | |
| CS-074 | Define the boundary and joint governance with foundational DPI exchangerequirements- Define a capability boundary; countries map what foundational DPI already provides its 12 comments, in full | Core architects 11 of 12 Metadata registries 1 | proposed | 12 | Discuss | show its comments | |
| CS-075 | Correct Figure 3.6 and show conformance points per exchange patternrequirements- Reword the dashed-line legend to acknowledge that logs and registry interactions may carry sensitive metadata its 2 comments, in full | Core architects 2 of 2 | proposed | 2 | Discuss | show its comments | |
| CS-076 | Specify trust governance and cross-jurisdiction trust frameworksrequirements- State what GDHCN participation provides (issuer trust, document integrity) and what it does not its 7 comments, in full | Core architects 6 of 7 WHO 1 | proposed | 7 | Discuss | show its comments | |
| CS-077 | Complete and harmonise the cross-border exchange requirementsrequirements- Apply harmonised normative terminology and identify essential versus use-case-dependent requirements its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-078 | Describe co-design of implementation with national authoritiesrequirements- Keep the WHO/national division of responsibility but describe engaging national authorities in shaping the implementation plan its 1 comment, in full | Core architects 1 of 1 | proposed | 1 | Discuss | show its comments | |
| CS-079 | Temper claims about tested components and mechanical assessmentrequirements- Replace the 'arrive tested' wording with a statement that reusable test specifications and evidence reduce but do not replace local verification its 11 comments, in full | Core architects 11 of 11 | proposed | 11 | Discuss | show its comments | |
| CS-080 | Define conformance assessment dimensions, evidence and resultsrequirements- Avoid an undifferentiated coverage percentage as the principal adoption measure; report by layer, capability and criticality its 18 comments, in full | Core architects 18 of 18 | proposed | 18 | Discuss | show its comments | |
| CS-081 | Define the adopt/adapt/map method and mapping relationship typesrequirements- Define how national elements (including those in other frameworks/notations) are mapped to reference elements its 12 comments, in full | Core architects 9 of 12 Editorial 3 | proposed | 12 | Discuss | show its comments | |
| CS-082 | Separate outcome contribution from technical conformancerequirements- Clarify that outcome monitoring assesses architecture contribution, not attribution, alongside policy and service factors its 6 comments, in full | Core architects 6 of 6 | proposed | 6 | Discuss | show its comments | |
| CS-083 | Specify national profile selection, including security profilesrequirements- Require countries to record selected profile, version, options, national extensions and applicable tests its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-084 | Generalise the 3.7 interaction model and transaction specificationrequirements- Use provider/consumer for service direction; reserve initiator/responder for transaction patterns its 11 comments, in full | Core architects 10 of 11 Editorial 1 | proposed | 11 | Discuss | show its comments | |
| CS-085 | Define a full testing taxonomy and conformance lifecyclerequirements- Distinguish conformance, interoperability, performance/resilience, security, clinical-safety, usability/accessibility and operational acceptance testing its 16 comments, in full | Core architects 14 of 16 Clinical 2 | proposed | 16 | Discuss | show its comments | |
| CS-086 | Provide shared conformance infrastructure and certification governancerequirements- Recommend regional/hosted test services, reusable validators and simulators, and mutual recognition of results its 10 comments, in full | Core architects 10 of 10 | proposed | 10 | Discuss | show its comments | |
| CS-087 | Commit to machine-readable conformance packages per componentrequirements- State that each component requires a national implementation guide naming profiles, versions, actors and operations its 14 comments, in full | Core architects 11 of 14 Metadata registries 1Supply chain 1Clinical 1 | proposed | 14 | Discuss | show its comments | |
| CS-088 | Broaden the current-state assessment in 4.1 and Phase 1requirements- Add work-practice methods (observation, workflow mapping) its 11 comments, in full | Core architects 11 of 11 | proposed | 11 | Discuss | show its comments | |
| CS-089 | Base legacy disposition and transition on structured assessmentrequirements- Make integration conditional on assessment of safety, data quality, security, supportability and cost, not age alone its 13 comments, in full | Core architects 12 of 13 No 1 | proposed | 13 | Discuss | show its comments | |
| CS-090 | Base use-case selection and data models on priority workflowsrequirements- State that information needs are derived from purposes, actors, workflows and decisions its 11 comments, in full | Core architects 9 of 11 Metadata registries 1Clinical 1 | proposed | 11 | Discuss | show its comments | |
| CS-091 | Define the national roadmap's minimum contents and Chapter 4 outputsrequirements- Define minimum structure, governance and update cadence linked to budget cycles its 5 comments, in full | Core architects 4 of 5 Editorial 1 | proposed | 5 | Discuss | show its comments | |
| CS-092 | Present entry points as archetypes with assessable dimensionsrequirements- State that a country can match more than one entry point and explain sequencing when they co-occur its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-093 | Present phases as concurrent workstreams with entry and exit criteriarequirements- Show governance, financing, capacity and other threads running across phases rather than as gates its 9 comments, in full | Core architects 8 of 9 Editorial 1 | proposed | 9 | Discuss | show its comments | |
| CS-094 | Recast the national digital architect as an institutional functionrequirements- Describe a multidisciplinary, institutionally mandated architecture function rather than an individual its 11 comments, in full | Core architects 10 of 11 Editorial 1 | proposed | 11 | Discuss | show its comments | |
| CS-095 | Add a DIIG-to-DPI-H crosswalkrequirements- Map DIIG stages to DPI-H activities, outputs, decision points and roles its 1 comment, in full | Core architects 1 of 1 | proposed | 1 | Discuss | show its comments | |
| CS-096 | Clarify selection criteria for Phase 2 and Phase 3 deploymentsrequirements- Give criteria for selecting the first systems to connect so the demonstration is representative its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-097 | Renumber the duplicated section 4.3.4 and following subsectionsrequirements- Renumber 'Interoperability Implementation Pathways' as 4.3.5 and 'Minimum Conformance and Testing' as 4.3.6 its 8 comments, in full | Editorial 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-098 | Specify the national implementation package and profile templaterequirements- List the minimum artefacts a country should produce its 6 comments, in full | Core architects 5 of 6 Metadata registries 1 | proposed | 6 | Discuss | show its comments | |
| CS-099 | Define transitional data formats and migration pathsrequirements- Give examples of simpler exchange mechanisms and how they progress to target conformance its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-100 | Make minimum datasets proportionate and purpose-limitedrequirements- Require a documented purpose for each mandatory element its 6 comments, in full | Core architects 5 of 6 No 1 | proposed | 6 | Discuss | show its comments | |
| CS-101 | Govern civil-registration event updates to health registriesrequirements- Require matching, verification and exception handling before authoritative updates its 3 comments, in full | Core architects 2 of 3 WHO 1 | proposed | 3 | Discuss | show its comments | |
| CS-102 | Give balanced criteria for centralised, federated or hybrid topologyrequirements- Add pragmatic decision factors (capacity, landscape, funding, political economy) its 19 comments, in full | Core architects 16 of 19 Editorial 2No 1 | proposed | 19 | Discuss | show its comments | |
| CS-103 | Define service levels and operational readiness for shared componentsrequirements- Replace unquantified 'high availability, low latency' with service classes its 9 comments, in full | Core architects 7 of 9 Supply chain 1Clinical 1 | proposed | 9 | Discuss | show its comments | |
| CS-104 | Strengthen the evaluation design in 4.4requirements- Replace attribution language with contribution-oriented wording and proportionate evaluation methods its 7 comments, in full | Core architects 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-105 | Broaden the 4.4 measures to effective use, sustainability and outcomesrequirements- Include patient and workforce experience, safety, equity and trust, disaggregated its 9 comments, in full | Core architects 8 of 9 No 1 | proposed | 9 | Discuss | show its comments | |
| CS-106 | Broaden the specialist roles and modelling roles in 4.5.2requirements- Add or locate missing capabilities (AI governance, platform operations, service and product management, procurement, clinical safety, cybersecurity operations) its 12 comments, in full | Core architects 8 of 12 Metadata registries 3Editorial 1 | proposed | 12 | Discuss | show its comments | |
| CS-107 | Add capacity patterns for small and resource-limited settingsrequirements- Give indicative capability-team patterns for early, intermediate and mature settings its 8 comments, in full | Core architects 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-108 | Add a responsibility-assignment matrix for Chapter 4 actorsrequirements- Show for each actor what it decides, produces, reviews, approves, operates or funds its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-109 | Expand change-management guidance in 4.5.3requirements- Add a structured change-management approach (co-design, workflow redesign, support, adoption measurement) its 2 comments, in full | Core architects 2 of 2 | proposed | 2 | Discuss | show its comments | |
| CS-110 | Distinguish capital from recurrent costs with a lifecycle cost frameworkrequirements- Present DPI-H as needing capital and protected recurrent expenditure its 18 comments, in full | Core architects 14 of 18 Financial systems 4 | proposed | 18 | Discuss | show its comments | |
| CS-111 | Broaden and make assessable the sustainability dimensionsrequirements- Add indicators and an assessment checklist per dimension its 6 comments, in full | Core architects 5 of 6 Financial systems 1 | proposed | 6 | Discuss | show its comments | |
| CS-112 | Guide the transition from donor to accountable domestic financingrequirements- Describe a phased transition with milestones its 10 comments, in full | Core architects 9 of 10 Financial systems 1 | proposed | 10 | Discuss | show its comments | |
| CS-113 | Strengthen national coordination of development partnersrequirements- Assign coordination to the strategic governance body, supported by architecture its 7 comments, in full | Core architects 6 of 7 Clinical 1 | proposed | 7 | Discuss | show its comments | |
| CS-114 | Add equity safeguards to fees and tariffs for shared servicesrequirements- Require that fees or contributions for shared infrastructure protect essential use and low-resource participants its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-115 | Expand the financing instruments named in 4.6requirements- Mention MDB instruments, regional/shared financing and relevant regional funds as options its 7 comments, in full | Core architects 5 of 7 Financial systems 2 | proposed | 7 | Discuss | show its comments | |
| CS-116 | Strengthen the investment case with evidence and a broader value caserequirements- Add documented, quantified examples with their limitations its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-117 | Add guidance and safeguards for private-sector participationrequirements- Add a section on private-sector specifics and protective engagement principles its 4 comments, in full | Core architects 3 of 4 No 1 | proposed | 4 | Discuss | show its comments | |
| CS-118 | Keep Chapter 5 durable by presenting AI technologies as illustrativerequirements- Lead with durable principles; present skills, agents and MCP as illustrative examples its 11 comments, in full | Core architects 9 of 11 Editorial 1No 1 | proposed | 11 | Discuss | show its comments | |
| CS-119 | Broaden the foundations listed as AI enablers in 5.2requirements- Make the enabler list illustrative or add facility, workforce, product and provenance infrastructure its 5 comments, in full | Metadata registries 3 of 5 Core architects 2 | proposed | 5 | Discuss | show its comments | |
| CS-120 | Require identity, authority and a register for AI agentsrequirements- Require agents to carry verifiable delegated identities attributable to an accountable entity its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-121 | Add safeguards and data prerequisites to the AI use cases in 5.3requirements- For each example (claims, supply forecasting, product mapping, clinical support, settlement mapping, document extraction) note data prerequisites, evidence and validation needed its 7 comments, in full | Core architects 3 of 7 Metadata registries 1Supply chain 1Financial systems 1Clinical 1 | proposed | 7 | Discuss | show its comments | |
| CS-122 | Add risk-tiered AI evaluation and use-case classificationrequirements- Define evaluation as layered (technical, clinical, human factors, security, real-world monitoring) and use plain terminology in place of 'evals' its 9 comments, in full | Core architects 8 of 9 Editorial 1 | proposed | 9 | Discuss | show its comments | |
| CS-123 | Provide an AI readiness framework and adoption pathwaysrequirements- Clarify that bounded AI use cases may proceed before the full foundation is mature its 10 comments, in full | Core architects 10 of 10 | proposed | 10 | Discuss | show its comments | |
| CS-124 | Address AI equity and subgroup performancerequirements- Require representative data and subgroup performance reporting (age, sex, disability, language, setting) its 8 comments, in full | Core architects 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-125 | Include privacy-preserving and federated options for AI data accessrequirements- Mention privacy-preserving distributed learning as an option alongside nationally hosted models its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-126 | Add AI financing, total-cost and procurement guidancerequirements- Describe AI total cost of ownership across the lifecycle, compared with non-AI alternatives, including environmental cost its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-127 | Define 'sovereign models' and realistic AI hosting optionsrequirements- Define the sovereignty dimensions intended and avoid implying domestic hosting alone ensures control its 8 comments, in full | Core architects 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-128 | Defer to national AI definitions and existing lawrequirements- State that the AI definition is broad and functional and that national definitions and risk classes apply its 2 comments, in full | Core architects 2 of 2 | proposed | 2 | Discuss | show its comments | |
| CS-129 | Broaden the 5.5 adaptability guidance beyond AIrequirements- Add data portability, versioning, governed semantics and trust to interface flexibility its 6 comments, in full | Core architects 6 of 6 | proposed | 6 | Discuss | show its comments | |
| CS-130 | Complete and correct the glossaryrequirements- Fill in 'Health Information Exchange' and 'Repository' and resolve '[Under review]' entries, or state which remain open its 9 comments, in full | Editorial 5 of 9 Metadata registries 3No 1 | proposed | 9 | Discuss | show its comments | |
| CS-131 | Complete the acronym listrequirements- Add API, TOGAF, ArchiMate, ICF, ICHI, MMS and WHO-FIC; consider glossary entries its 8 comments, in full | Editorial 5 of 8 Metadata registries 2WHO 1 | proposed | 8 | Discuss | show its comments | |
| CS-132 | Complete and standardise the reference listrequirements- Provide the consolidated reference list now, covering every in-text citation its 16 comments, in full | Editorial 8 of 16 WHO 4Core architects 4 | proposed | 16 | Discuss | show its comments | |
| CS-133 | Explain how the Appendix A stakeholder table is used and adaptedrequirements- Introduce the purpose of the stakeholder table and state that it is illustrative its 9 comments, in full | Core architects 7 of 9 Editorial 2 | proposed | 9 | Discuss | show its comments | |
| CS-134 | Expand and refine Appendix A stakeholder categoriesrequirements- Add missing categories (commercial suppliers, standards bodies, data-protection authorities, finance, supply-chain actors) its 14 comments, in full | Core architects 11 of 14 Metadata registries 1Supply chain 1Financial systems 1 | proposed | 14 | Discuss | show its comments | |
| CS-135 | Rework the Appendix B goal-to-building-block mappingrequirements- Explain the purpose and limits of the mapping its 18 comments, in full | Core architects 12 of 18 Supply chain 2WHO 2Clinical 1Editorial 1 | proposed | 18 | Discuss | show its comments | |
| CS-136 | Reframe the Client Registry definition around governed, uncertain identityrequirements- Describe records as possibly provisional, incomplete or at differing assurance levels, reconciled later its 9 comments, in full | Core architects 8 of 9 Financial systems 1 | proposed | 9 | Discuss | show its comments | |
| CS-137 | Present health identifiers as options relative to foundational IDrequirements- State the required outcome as reliable cross-system identification, achievable by national, federated or multiple linked identifiers its 14 comments, in full | Core architects 13 of 14 Editorial 1 | proposed | 14 | Discuss | show its comments | |
| CS-138 | Specify safeguards and governance for identity-linkage decisionsrequirements- Widen the risk statement beyond deterrence from care to surveillance, function creep, discrimination and non-health access its 6 comments, in full | Core architects 6 of 6 | proposed | 6 | Discuss | show its comments | |
| CS-139 | Ensure registration or matching gaps never block essential carerequirements- State that essential care must not depend on prior registration, a foundational ID or real-time matching its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-140 | Revise the Client Registry minimum dataset for necessity and inclusionrequirements- Distinguish schema support, conditional requirement and mandatory presence; allow documented absent-data reasons its 10 comments, in full | Core architects 9 of 10 Metadata registries 1 | proposed | 10 | Discuss | show its comments | |
| CS-141 | Model person relationships as conditional, role-based and restrictedrequirements- Make household, family and guardian relationships conditional on defined use cases its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-142 | Treat biometrics and photos as high-risk optional identity mechanismsrequirements- Separate identity resolution, verification, authentication and biometric matching, and say which the registry provides its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-143 | Specify client-registry matching quality, adjudication and equityrequirements- Define matching thresholds, confidence representation and minimum operational controls for linking and deduplication its 7 comments, in full | Core architects 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-144 | Preserve history in Client Registry record lifecycle and notificationsrequirements- State that merging creates one active reference while preserving source records, identifiers and provenance its 7 comments, in full | Core architects 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-145 | Tighten Client Registry data protection and query responsesrequirements- Correct 'pseudo-anonymisation' to 'pseudonymisation' and note pseudonymised data remains personal data its 7 comments, in full | Core architects 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-146 | Define Facility Registry entity types and the MFL relationshiprequirements- Add an entity model distinguishing organisations, facilities, locations, service sites, mobile and temporary services, mapped to mCSD/FHIR its 8 comments, in full | Core architects 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-147 | Model facility relationships beyond fixed hierarchiesrequirements- Explain 'multi-axial hierarchy' in plain language its 8 comments, in full | Core architects 7 of 8 Editorial 1 | proposed | 8 | Discuss | show its comments | |
| CS-148 | Specify facility location precision and restricted disclosurerequirements- Model coordinates, address, geometry and administrative assignment separately with source and precision its 9 comments, in full | Core architects 9 of 9 | proposed | 9 | Discuss | show its comments | |
| CS-149 | Define the facility temporal, status and publication-state modelrequirements- Describe the CGR as a potential cross-sector capability, with an interim path where none exists its 15 comments, in full | Core architects 15 of 15 | proposed | 15 | Discuss | show its comments | |
| CS-150 | Refine facility data elements, separating readiness and financing datarequirements- Keep mandatory signature data distinct from conditional service-readiness attributes its 16 comments, in full | Core architects 12 of 16 Metadata registries 2Financial systems 2 | proposed | 16 | Discuss | show its comments | |
| CS-151 | Define facility data stewardship and change governancerequirements- Add an attribute-level stewardship matrix; use the Section 3.4 responsibility model its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-152 | Define workforce categories beyond licensed professionalsrequirements- Define the registry as covering roles, qualifications, registrations, licences and other recognised authorisations its 17 comments, in full | Core architects 17 of 17 | proposed | 17 | Discuss | show its comments | |
| CS-153 | Position the Workforce Registry within an NHWA-aligned information systemrequirements- Say what the registry is not: employment, payroll, HR actions and detailed learning records its 24 comments, in full | Core architects 18 of 24 WHO 3Metadata registries 2Editorial 1 | proposed | 24 | Discuss | show its comments | |
| CS-154 | Define source authority and reconciliation for workforce datarequirements- Identify the authoritative source per profession and attribute, distinguishing source data from consolidated copies its 7 comments, in full | Core architects 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-155 | Specify workforce identifier and identity-assurance rulesrequirements- Permit a national identifier, linked professional identifiers or a federated arrangement its 7 comments, in full | Core architects 6 of 7 Editorial 1 | proposed | 7 | Discuss | show its comments | |
| CS-156 | Align occupation classification with national classifications mapped to ISCOrequirements- Use national occupation classifications mapped to ISCO and the WHO health-worker classification, per the NHWA approach its 11 comments, in full | Metadata registries 10 of 11 Editorial 1 | proposed | 11 | Discuss | show its comments | |
| CS-157 | Broaden the licence and qualification model in the Workforce Registryrequirements- Use a governed licence-status value set including not applicable, provisional, restricted and relicensed states its 24 comments, in full | Core architects 22 of 24 Metadata registries 1WHO 1 | proposed | 24 | Discuss | show its comments | |
| CS-158 | Replace primary/secondary affiliation with typed, dated affiliationsrequirements- Model repeatable affiliations by role, organisation, facility, status, period and source, including dual practice its 16 comments, in full | Core architects 13 of 16 Metadata registries 2Editorial 1 | proposed | 16 | Discuss | show its comments | |
| CS-159 | Define workforce credential verification and status propagationrequirements- State the limits of registration checks versus competence, privileges and task authorisation its 13 comments, in full | Core architects 12 of 13 Metadata registries 1 | proposed | 13 | Discuss | show its comments | |
| CS-160 | Minimise personal data in the workforce registry datasetrequirements- Document purpose and source for each data element its 9 comments, in full | Core architects 9 of 9 | proposed | 9 | Discuss | show its comments | |
| CS-161 | Control access, disclosure and correction of workforce datarequirements- Describe multisectoral, multistakeholder governance of the wider HRHIS, including private-sector participation and safeguards its 14 comments, in full | Core architects 14 of 14 | proposed | 14 | Discuss | show its comments | |
| CS-162 | Align workforce and facility discovery with mCSD and federated exchangerequirements- Align entity boundaries with mCSD organisations, locations, roles and services its 7 comments, in full | Core architects 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-163 | Define Product Registry scope and content boundaryrequirements- State criteria for foundational data (authority, stability, reuse, identification) its 18 comments, in full | Supply chain 16 of 18 Core architects 1Editorial 1 | proposed | 18 | Discuss | show its comments | |
| CS-164 | Clarify Product Registry authority, identifiers and submission trustrequirements- State whether the registry is the regulatory source, a master-data hub or a federated view its 13 comments, in full | Supply chain 13 of 13 | discussing | 13 | #22 | show its comments | |
| CS-165 | Replace the fixed registry-first sequence with capability-based adoptionrequirements- Allow existing catalogues or regulatory databases to become the authoritative source where suitable its 4 comments, in full | Supply chain 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-166 | Restructure the Product Registry data model by product classrequirements- Model units, strength, routes, storage conditions and classifications as structured, governed attributes its 23 comments, in full | Supply chain 20 of 23 Metadata registries 3 | proposed | 23 | Discuss | show its comments | |
| CS-167 | Correct the roles of product classifications, dictionaries and codingrequirements- State the purpose and product level of UNSPSC, GPC, ATC and WHODrug; they are not identifiers its 8 comments, in full | Metadata registries 5 of 8 Supply chain 3 | proposed | 8 | Discuss | show its comments | |
| CS-168 | Strengthen Product Registry versioning, lifecycle and provisional recordsrequirements- Define separate product, packaging, regulatory, item and publication statuses its 7 comments, in full | Supply chain 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-169 | Specify Product Registry interfaces and access profilesrequirements- Reference a national Product Registry implementation guide for APIs, events and bulk access its 4 comments, in full | Supply chain 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-170 | Define the LHR as governed longitudinal access, not a storerequirements- Justify the LHR's place in the foundational layer and distinguish it visually from registries its 22 comments, in full | Clinical 18 of 22 Core architects 3Editorial 1 | proposed | 22 | Discuss | show its comments | |
| CS-171 | Recognise research and biobank systems as governed data sourcesrequirements- Recognise research, LIMS and biorepository systems as functional applications and potential sources outside the core layer its 9 comments, in full | Clinical 7 of 9 Metadata registries 1Core architects 1 | proposed | 9 | Discuss | show its comments | |
| CS-172 | Specify who may access LHR data and howrequirements- Include authorised representatives and supported decision-making in access and control its 11 comments, in full | Clinical 11 of 11 | proposed | 11 | Discuss | show its comments | |
| CS-173 | Define LHR acceptance levels and a minimum dataset by levelrequirements- Specify governed models for allergies, medications, diagnoses, results, procedures/encounters and documents, including status and provenance its 16 comments, in full | Clinical 13 of 16 Metadata registries 2Core architects 1 | proposed | 16 | Discuss | show its comments | |
| CS-174 | Specify LHR provenance, correction, provisional identity and erasurerequirements- Require each item to keep its model/profile, terminology system, version and validation status its 14 comments, in full | Clinical 10 of 14 Metadata registries 4 | proposed | 14 | Discuss | show its comments | |
| CS-175 | Define conflict resolution for offline LHR synchronisationrequirements- Specify detection and resolution of concurrent edits across offline or federated nodes its 3 comments, in full | Clinical 2 of 3 Core architects 1 | proposed | 3 | Discuss | show its comments | |
| CS-176 | Specify LHR retrieval completeness and event handlingrequirements- Publish a retrieval profile with partial-result and source-availability indicators its 4 comments, in full | Clinical 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-177 | Define LHR boundaries with immunisation registries and workflow systemsrequirements- Define source authority and reconciliation between LHR and immunisation registries its 2 comments, in full | Clinical 2 of 2 | proposed | 2 | Discuss | show its comments | |
| CS-178 | Define terminology and SGI roles, decision rights and approvalrequirements- Define domain-specific reviewer qualifications, conflict-of-interest rules and multidisciplinary review its 12 comments, in full | Metadata registries 11 of 12 WHO 1 | editing | 12 | #19 | #16 | show its comments |
| CS-179 | Specify LIMR artefacts, modelling method and metadatarequirements- Require publication of machine-readable validation artefacts where feasible its 9 comments, in full | Metadata registries 9 of 9 | proposed | 9 | Discuss | show its comments | |
| CS-180 | Clarify LIMR scope, name, governance and consumer notificationrequirements- Require release and deprecation notifications to registered consumers its 6 comments, in full | Metadata registries 6 of 6 | proposed | 6 | Discuss | show its comments | |
| CS-181 | Define the CDSE boundary, deployment options and knowledge artefactsrequirements- Present decision support as a logical capability that may run as a shared service, embedded locally or on-device, consuming the same governed artefacts its 16 comments, in full | Clinical 15 of 16 No 1 | proposed | 16 | Discuss | show its comments | |
| CS-182 | Describe HMIS scope as a multi-source aggregate-data platformrequirements- Do not present the LHR as the primary source of aggregates its 11 comments, in full | Core architects 10 of 11 Metadata registries 1 | proposed | 11 | Discuss | show its comments | |
| CS-183 | Require governed indicator definitions and information-to-action in HMISrequirements- Require an indicator metadata model (numerator, denominator, disaggregation, period, source) its 8 comments, in full | Core architects 6 of 8 Metadata registries 2 | proposed | 8 | Discuss | show its comments | |
| CS-184 | Require disclosure control for aggregate and published health datarequirements- Require aggregation thresholds, suppression and approved disaggregation for small populations its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-185 | Define the shared surveillance capabilities that qualify as DPI-Hrequirements- Apply the component-selection criteria to the PHSP and define its scope as modular capabilities with progressive implementation its 15 comments, in full | Core architects 13 of 15 Metadata registries 2 | proposed | 15 | Discuss | show its comments | |
| CS-186 | Minimise surveillance data and make identity linkage conditionalrequirements- Replace universal LHR integration and verified-identity linkage with conditions set by national architecture and use case its 12 comments, in full | Core architects 12 of 12 | proposed | 12 | Discuss | show its comments | |
| CS-187 | Define accountable alert handling and IHR-based reportingrequirements- Replace 'immediate/real-time' with condition-specific deadlines and failure handling its 6 comments, in full | Core architects 5 of 6 WHO 1 | proposed | 6 | Discuss | show its comments | |
| CS-188 | Bound the Benefits Package Registry against scheme operationsrequirements- Distinguish the Benefits Package Registry and other registries from enrolment, contracting, claims and payment systems its 22 comments, in full | Financial systems 22 of 22 | editing | 22 | #18 | #16 | show its comments |
| CS-189 | Restructure the Benefits Package Registry data modelrequirements- Define a rule model with terminology bindings, distinguishing computable rules from human-interpreted policy its 9 comments, in full | Financial systems 9 of 9 | proposed | 9 | Discuss | show its comments | |
| CS-190 | Define authority, review and public presentation of benefit packagesrequirements- Support multiple scheme authorities with federated publication its 9 comments, in full | Financial systems 8 of 9 Editorial 1 | proposed | 9 | Discuss | show its comments | |
| CS-191 | Scope the Supplier Registry as a health layer over cross-sector identitiesrequirements- Build on authoritative business, tax and procurement identities where available rather than duplicating them its 15 comments, in full | Supply chain 15 of 15 | proposed | 15 | Discuss | show its comments | |
| CS-192 | Apply minimisation and access tiers to Supplier Registry datarequirements- Define public and restricted fields its 4 comments, in full | Supply chain 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-193 | Restructure the Appendix C introductionrequirements- Add a summary matrix of components, purposes and dependencies its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-194 | Fix editorial errors in the registry sectionsrequirements- Correct grammar and remove the duplicate bullet in the Facility Registry its 5 comments, in full | Editorial 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-195 | Add traceability from requirements to source specifications and artefactsrequirements- Show model, binding, profile, validation and deployed version links with identifiers its 9 comments, in full | Metadata registries 5 of 9 Core architects 4 | proposed | 9 | Discuss | show its comments | |
| CS-196 | Govern inbound updates and bulk import into registriesrequirements- Distinguish proposals from authoritative updates and define precedence and acknowledgement its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-197 | Define progressive maturity levels for each foundational componentrequirements- Give every component the same maturity structure, from a governed baseline to advanced capability its 12 comments, in full | Core architects 5 of 12 Metadata registries 3Supply chain 2Clinical 2 | proposed | 12 | Discuss | show its comments | |
| CS-198 | Clarify the purpose and non-endorsement status of the D.1 tool listrequirements- State that the list is illustrative, non-exhaustive and not an endorsement or evidence of conformance its 7 comments, in full | WHO 3 of 7 Core architects 3Editorial 1 | proposed | 7 | Discuss | show its comments | |
| CS-199 | Describe each listed tool with dated attributes and capability coveragerequirements- Add per-tool fields: supported standards/profiles, conformance evidence, version and date assessed its 20 comments, in full | Core architects 12 of 20 Metadata registries 4Clinical 2Financial systems 1Editorial 1 | proposed | 20 | Discuss | show its comments | |
| CS-200 | Restructure Appendix D as evidenced, dated illustrative casesrequirements- Use one case template for every example its 18 comments, in full | Core architects 10 of 18 WHO 6Editorial 2 | proposed | 18 | Discuss | show its comments | |
| CS-201 | Add context, transferability and mappings to each country examplerequirements- Add a context box and transferability limits per example its 15 comments, in full | Core architects 15 of 15 | proposed | 15 | Discuss | show its comments | |
| CS-202 | Include unsuccessful and partial implementation casesrequirements- Add documented negative or partial cases read against design choices its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-203 | Widen the geographic and income coverage of the examplesrequirements- Address the imbalance across regions and income levels its 11 comments, in full | Core architects 6 of 11 Editorial 3Metadata registries 1Financial systems 1 | proposed | 11 | Discuss | show its comments | |
| CS-204 | Revise the Australia examplerequirements- Distinguish My Health Record, identifier, terminology, e-prescribing and state services its 7 comments, in full | Core architects 4 of 7 Metadata registries 3 | proposed | 7 | Discuss | show its comments | |
| CS-205 | Revise the Denmark examplerequirements- Map portal, data network, medication, registries and regional EHRs separately its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-206 | Revise the Estonia examplerequirements- Separate health services from the X-Road exchange layer its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-207 | Revise the India examplerequirements- Map ABDM building blocks separately and distinguish identity from health identity its 6 comments, in full | Core architects 4 of 6 Editorial 1No 1 | proposed | 6 | Discuss | show its comments | |
| CS-208 | Revise the Kenya examplerequirements- Map initiatives separately and their integration its 4 comments, in full | Core architects 3 of 4 Editorial 1 | proposed | 4 | Discuss | show its comments | |
| CS-209 | Revise the Nigeria examplerequirements- Explain federal-state division of responsibility its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-210 | Revise the Rwanda examplerequirements- Map systems separately with status its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-211 | Revise the Spain and Catalonia examplesrequirements- Distinguish central coordination from regional operation its 6 comments, in full | Core architects 6 of 6 | proposed | 6 | Discuss | show its comments | |
| CS-212 | Revise the Tanzania examplerequirements- Separate architecture from products its 3 comments, in full | Core architects 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-213 | Revise the Uganda examplerequirements- Correct component mapping (PHSP/eIDSR on DHIS2) its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-214 | Revise the England examplerequirements- Title it England, not the UK its 5 comments, in full | Core architects 3 of 5 Metadata registries 1Editorial 1 | proposed | 5 | Discuss | show its comments | |
| CS-215 | Revise the United States examplerequirements- Present it as interoperability governance and network federation its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-216 | Specify the regional surveillance example preciselyrequirements- Name the infrastructure, its purpose, legal basis and participating authorities, separating surveillance from clinical exchange and EHDS its 8 comments, in full | Core architects 5 of 8 WHO 2Metadata registries 1 | proposed | 8 | Discuss | show its comments | |
| CS-217 | Specify the SMART Guidelines pilot example preciselyrequirements- Label maturity (pilot to routine), domains, countries, dates and scale its 10 comments, in full | Core architects 4 of 10 WHO 3Clinical 2Metadata registries 1 | proposed | 10 | Discuss | show its comments | |
| CS-218 | Explain the purpose and reading of the Appendix E mappingsrequirements- Say the tables are one reference decomposition, not the only valid architecture its 9 comments, in full | Core architects 6 of 9 Editorial 3 | proposed | 9 | Discuss | show its comments | |
| CS-219 | Enrich mapped relationships with layer, status and dependenciesrequirements- Show for each element whether it is foundational shared data layer, business-services layer, DPI-F dependency, operational application, or cross-cutting governance its 14 comments, in full | Core architects 14 of 14 | proposed | 14 | Discuss | show its comments | |
| CS-220 | Publish Appendix E from a versioned model with persistent identifiersrequirements- Use the formal model's canonical element names and persistent identifiers throughout the appendix its 8 comments, in full | Editorial 4 of 8 Core architects 3WHO 1 | proposed | 8 | Discuss | show its comments | |
| CS-221 | Add country adoption and cross-goal reuse views to Appendix Erequirements- Provide a way to classify each reference element as adopted, adapted, mapped, deferred, not applicable or gap, with rationale its 5 comments, in full | Core architects 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-222 | Represent equity as mapped capabilities and indicators in every goalrequirements- Add equity-related capabilities, affected populations and disaggregated indicators to each goal its 5 comments, in full | Core architects 3 of 5 Supply chain 1Financial systems 1 | proposed | 5 | Discuss | show its comments | |
| CS-223 | Link each goal to outcome indicators and scenario testsrequirements- Give each goal indicators beyond the existence of components its 14 comments, in full | Core architects 8 of 14 Supply chain 2Financial systems 2Clinical 2 | proposed | 14 | Discuss | show its comments | |
| CS-224 | Decompose cross-cutting enablers in the goal mappingsrequirements- Replace the single interoperability box with its underlying services (discovery, trust, routing, validation, semantics, mapping) its 17 comments, in full | Core architects 12 of 17 Metadata registries 3Financial systems 1Clinical 1 | proposed | 17 | Discuss | show its comments | |
| CS-225 | Complete the Goal 1 description of shared data foundationsrequirements- Add the Logical Information Model Repository to the Goal 1 component list its 5 comments, in full | Core architects 3 of 5 Metadata registries 1WHO 1 | proposed | 5 | Discuss | show its comments | |
| CS-226 | Separate supply-chain reference data from operational systems in Goal 5requirements- Distinguish Product/Supplier/Facility registries from procurement, inventory, traceability and forecasting systems its 11 comments, in full | Supply chain 9 of 11 Metadata registries 1Core architects 1 | proposed | 11 | Discuss | show its comments | |
| CS-227 | Map SGI capabilities to components, goals and available resourcesrequirements- Distinguish SGI governance capabilities from the Terminology Service, LIMR and other components and organisations that realise them its 7 comments, in full | Metadata registries 7 of 7 | proposed | 7 | Discuss | show its comments | |
| CS-228 | Make SGI capabilities assessable with outputs and quality measuresrequirements- Separate monitoring of governance process, content quality, implementation conformance and adoption its 15 comments, in full | Metadata registries 15 of 15 | proposed | 15 | Discuss | show its comments | |
| CS-229 | Specify request intake and content development for semantic changesrequirements- Define standard request types and minimum information, and support channels beyond a single online portal its 12 comments, in full | Metadata registries 12 of 12 | proposed | 12 | Discuss | show its comments | |
| CS-230 | Govern reuse, national extensions, local variation and bindingsrequirements- Prefer governed reference and specialisation over copying external content, with provenance and upstream tracking its 5 comments, in full | Metadata registries 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-231 | Secure semantic artefacts: integrity, provenance, access and licensingrequirements- Require trusted publication with checksums or signatures and publisher verification its 8 comments, in full | Metadata registries 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-232 | Define conformance domains and validation services for semantic artefactsrequirements- Distinguish conformance of artefacts, implementations, exchanged data and operational use, with evidence and authority for each its 5 comments, in full | Metadata registries 5 of 5 | proposed | 5 | Discuss | show its comments | |
| CS-233 | Define SGI feedback and remediation loops from implementationrequirements- Require structured feedback tied to artefact, version, system and use case its 10 comments, in full | Metadata registries 10 of 10 | proposed | 10 | Discuss | show its comments | |
| CS-234 | Distinguish consent from the lawful basis for processingrequirements- Refer to access policy based on lawful basis, purpose and consent where relevant its 11 comments, in full | Clinical 6 of 11 Core architects 5 | proposed | 11 | Discuss | show its comments | |
| CS-235 | Specify consent and permissions as a first-class cross-cutting capabilityrequirements- Give consent and authorisation a service profile comparable to named components: representation, lifecycle, revocation, delegated authority, audit its 12 comments, in full | Core architects 11 of 12 Clinical 1 | proposed | 12 | Discuss | show its comments | |
| CS-236 | Model delegated and supported agency as a governed relationshiprequirements- Distinguish a relationship record from current authority to act its 4 comments, in full | Core architects 3 of 4 Clinical 1 | discussing | 4 | #10 | #9 | show its comments |
| CS-237 | Extend equity and digital-inclusion safeguards across the guidancerequirements- Address variation in functional ability, language, literacy and digital capability as architectural concerns its 11 comments, in full | Core architects 11 of 11 | discussing | 11 | #11 | #9 | show its comments |
| CS-238 | Define a minimum security, privacy and audit baselinerequirements- Require policy-based access beyond role-based control its 20 comments, in full | Core architects 18 of 20 Clinical 2 | proposed | 20 | Discuss | show its comments | |
| CS-239 | Treat offline-first and low-connectivity operation as a core design conditionrequirements- Set minimum offline-first requirements (local capture, store-and-forward, sync, deduplication, reconciliation) where connectivity is intermittent its 15 comments, in full | Core architects 15 of 15 | proposed | 15 | Discuss | show its comments | |
| CS-240 | Support package-based and offline distribution of reference contentrequirements- Define a minimum publication package (usage guidance, examples, test data, limitations, licence, dependencies, support contact, fitness-for-purpose) its 21 comments, in full | Metadata registries 18 of 21 Supply chain 2Core architects 1 | proposed | 21 | Discuss | show its comments | |
| CS-241 | Reframe sovereignty as effective control, portability and supplier exitrequirements- Define minimum exit rights and the evidence demonstrating portability its 10 comments, in full | Core architects 10 of 10 | proposed | 10 | Discuss | show its comments | |
| CS-242 | Link the local-capacity principle to national capacity developmentrequirements- Point to structured national capacity programmes (competency, mentoring, communities of practice, retention) its 6 comments, in full | Core architects 5 of 6 No 1 | proposed | 6 | Discuss | show its comments | |
| CS-243 | Make data-quality governance actionablerequirements- Make data-quality criteria use-case and risk specific its 4 comments, in full | Core architects 4 of 4 | proposed | 4 | Discuss | show its comments | |
| CS-244 | Broaden the ethics principle beyond secondary use and AI trainingrequirements- Emphasise privacy protection in secondary use at scale its 2 comments, in full | Core architects 1 of 2 No 1 | proposed | 2 | Discuss | show its comments | |
| CS-245 | Recognise implementation-led pathways alongside central architecturerequirements- Acknowledge that capabilities often emerge from local implementations and are standardised after proving value its 11 comments, in full | Core architects 8 of 11 No 3 | proposed | 11 | Discuss | show its comments | |
| CS-246 | Define a minimum viable starting package and progressive pathwayrequirements- Integrate REDDHI, interoperability, SGI, SMART Guidelines, epidemiological intelligence and AI maturity into one framework its 12 comments, in full | Core architects 10 of 12 Editorial 1No 1 | proposed | 12 | Discuss | show its comments | |
| CS-247 | Preserve the provenance and status of AI-generated informationrequirements- Require systems to distinguish observed, asserted, calculated and inferred information its 6 comments, in full | Core architects 5 of 6 Metadata registries 1 | proposed | 6 | Discuss | show its comments | |
| CS-248 | Qualify claims about AI benefits and 'foundations first'requirements- Replace categorical claims (amplifies, ensures, is what allows) with measured wording its 12 comments, in full | Core architects 7 of 12 Editorial 3Metadata registries 2 | proposed | 12 | Discuss | show its comments | |
| CS-249 | Require effective, not nominal, human oversight of AIrequirements- Define assistive use by the system's actual role and influence its 16 comments, in full | Core architects 15 of 16 No 1 | proposed | 16 | Discuss | show its comments | |
| CS-250 | Define AI lifecycle governance and post-deployment controlsrequirements- Consolidate the safeguards already named in 5.4 into a testable minimum control checklist (or cross-reference one) its 18 comments, in full | Core architects 15 of 18 Clinical 2No 1 | proposed | 18 | Discuss | show its comments | |
| CS-251 | Address diagnostic imaging in the architecturerequirements- State that exchange references imaging studies while image transport uses specialised standards its 3 comments, in full | Clinical 1 of 3 Core architects 1No 1 | proposed | 3 | Discuss | show its comments | |
| CS-252 | Strengthen governed secondary use of health datarequirements- Qualify 'capture once, use many times' with purpose and minimisation its 5 comments, in full | Core architects 3 of 5 Clinical 2 | proposed | 5 | Discuss | show its comments | |
| CS-253 | Name the custodian, versioning and change process of the architecturerequirements- State where each artefact is published, its version and maintainer its 7 comments, in full | Core architects 4 of 7 WHO 3 | proposed | 7 | Discuss | show its comments | |
| CS-254 | Fix figure, table, footnote, page and cross-reference numberingrequirements- Replace 'Annex [X]' with the actual appendix reference its 10 comments, in full | Editorial 9 of 10 Core architects 1 | proposed | 10 | Discuss | show its comments | |
| CS-255 | Make integrated, long-term and social care explicitrequirements- Include integrated, long-term and social care in the framing and priority use cases its 3 comments, in full | Clinical 3 of 3 | proposed | 3 | Discuss | show its comments | |
| CS-256 | Address closing the loop on clinical workflows across systemsrequirements- Add a principle that DPI-H supports resolution of clinical workflows, not only transmission its 4 comments, in full | Clinical 3 of 4 Core architects 1 | proposed | 4 | Discuss | show its comments | |
| CS-257 | Acknowledge the limits of structuring clinical informationrequirements- Recognise interpretive and narrative clinical information as first-class, not text awaiting structure its 2 comments, in full | Clinical 1 of 2 Core architects 1 | proposed | 2 | Discuss | show its comments | |
| CS-258 | Define 'actor' once and align roles with SMART Guidelines personasrequirements- Explain modelling an actor role as an Application Component as a deliberate IHE-compatible convention its 11 comments, in full | Core architects 9 of 11 Metadata registries 1Editorial 1 | proposed | 11 | Discuss | show its comments | |
| CS-259 | Address omitted care services and data sourcesrequirements- Cite the IPC teledermatology consensus statements where relevant its 4 comments, in full | Core architects 3 of 4 Clinical 1 | proposed | 4 | Discuss | show its comments | |
| CS-260 | Link procurement to conformance with published national profilesrequirements- Make national profiles, test artefacts and tooling Phase 1/early Phase 2 outputs its 8 comments, in full | Core architects 7 of 8 Editorial 1 | proposed | 8 | Discuss | show its comments | |
| CS-261 | Explain alignment with GDPR, the EHDS and MyHealth@EUrequirements- Name the EHDS Regulation and MyHealth@EU where cross-border and regional exchange is discussed its 8 comments, in full | Core architects 8 of 8 | proposed | 8 | Discuss | show its comments | |
| CS-262 | Adopt a global-core, national-extension policy for standards and profilesrequirements- Require schema extensions to follow a governed national process with definitions, bindings and conformance its 18 comments, in full | Core architects 11 of 18 Metadata registries 7 | proposed | 18 | Discuss | show its comments | |
| CS-263 | Extend the interoperability definition to workflow and pragmatic levelsrequirements- Add a concise definition of interoperability at the start of 3.6 its 12 comments, in full | Core architects 8 of 12 Metadata registries 3Editorial 1 | proposed | 12 | Discuss | show its comments | |
| CS-264 | Treat the clinical-data persistence layer and openEHR explicitlyrequirements- Add a subsection to 3.6 on the persistence layer and what a country decides when choosing how clinical data are held its 15 comments, in full | Metadata registries 12 of 15 Core architects 2Clinical 1 | proposed | 15 | Discuss | show its comments | |
| CS-265 | Clarify FHIR's role relative to the logical model and technology neutralityrequirements- State FHIR is recommended for relevant health-information exchange, with other standards where more suitable its 16 comments, in full | Core architects 8 of 16 Metadata registries 7No 1 | proposed | 16 | Discuss | show its comments | |
| CS-266 | Clarify the two DPI-H layers and their depiction in figuresrequirements- State what 'two layers' covers relative to applications, foundational DPI and cross-cutting enablers in later figures its 15 comments, in full | Core architects 12 of 15 Editorial 2Financial systems 1 | proposed | 15 | Discuss | show its comments | |
| CS-267 | Classify CRVS and geospatial registries consistently as foundational DPIrequirements- Use one classification of foundational DPI, cross-sector authoritative systems and DPI-H throughout its 5 comments, in full | Core architects 4 of 5 WHO 1 | proposed | 5 | Discuss | show its comments | |
| CS-268 | Address organisation identity across facility, workforce and supplier registriesrequirements- Assess whether a shared organisation registry or identifier capability is needed, or where it comes from its 9 comments, in full | Core architects 6 of 9 Supply chain 3 | proposed | 9 | Discuss | show its comments | |
| CS-269 | Define common patterns for identifiers, provenance, versions and validityrequirements- Require assigning authority, type, status, period and provenance for every identifier its 19 comments, in full | Core architects 14 of 19 Metadata registries 2Supply chain 2No 1 | proposed | 19 | Discuss | show its comments | |
| CS-270 | State that components are logical capabilities, not productsrequirements- Add a note that one platform may realise several components and one component may span systems its 11 comments, in full | Core architects 11 of 11 | proposed | 11 | Discuss | show its comments | |
| CS-271 | Define a pathway for person-generated and patient-reported datarequirements- Describe an optional pathway for citizen- and device-generated data under consent its 6 comments, in full | Clinical 3 of 6 Core architects 3 | proposed | 6 | Discuss | show its comments | |
| CS-272 | Embed clinical safety accountability in governance and decision supportrequirements- State that only suitable recommendations are made computable and that clinical judgement remains its 18 comments, in full | Clinical 15 of 18 Metadata registries 3 | proposed | 18 | Discuss | show its comments | |
| CS-273 | Define a minimum SGI baseline and progressive maturity levelsrequirements- Identify the minimum SGI capabilities needed before a country publishes national terminology, models or IGs, and mark which belong to the REDDHI baseline its 20 comments, in full | Metadata registries 20 of 20 | proposed | 20 | Discuss | show its comments | |
| CS-274 | Define one lifecycle, versioning and impact process for semantic artefactsrequirements- Establish controlled publication statuses (draft, trial use, normative, deprecated, retired) with permitted uses its 39 comments, in full | Metadata registries 37 of 39 Core architects 1Editorial 1 | proposed | 39 | Discuss | show its comments | |
| CS-275 | Govern terminology mappings as artefacts with equivalence and provenancerequirements- State that maps between SNOMED CT, ICD-11 and LOINC are needed and governed, with context and equivalence properties its 10 comments, in full | Metadata registries 9 of 10 No 1 | proposed | 10 | Discuss | show its comments | |
| CS-276 | Address multilingual and localisation requirements for semantic contentrequirements- Treat language, accessibility, local concepts and inclusive participation as obligations across the lifecycle its 13 comments, in full | Metadata registries 12 of 13 Supply chain 1 | proposed | 13 | Discuss | show its comments | |
| CS-277 | Describe terminology licensing accurately and consistentlyrequirements- Distinguish international releases, authorised extensions and separately identified local additions its 19 comments, in full | Metadata registries 19 of 19 | proposed | 19 | Discuss | show its comments | |
| CS-278 | Describe the role of ICD-11 and WHO-FIC where standards are namedrequirements- Name ICD-11 (not 'ICD') and its role in the 2.2.2 open-standards list its 27 comments, in full | Metadata registries 24 of 27 WHO 3 | editing | 27 | #17 | #16 | show its comments |
| CS-279 | Explain the complementary roles of SNOMED CT, ICD-11 and LOINCrequirements- State that the core terminology standards are complementary, each covering a distinct domain, not interchangeable alternatives its 12 comments, in full | Metadata registries 9 of 12 Core architects 1Editorial 1No 1 | proposed | 12 | Discuss | show its comments | |
| CS-280 | Support or qualify outcome and benefit claimsrequirements- Cite evidence or label claims as recognised risks or expected benefits its 26 comments, in full | Core architects 10 of 26 Editorial 8Clinical 4Supply chain 2Metadata registries 1Financial systems 1 | proposed | 26 | Discuss | show its comments | |
| CS-281 | Apply SHALL/SHOULD/MAY normative keywords consistentlyrequirements- Replace Required/Recommended with the convention of Section 3.5.2 its 16 comments, in full | Core architects 13 of 16 Metadata registries 1Supply chain 1Editorial 1 | proposed | 16 | Discuss | show its comments | |
| CS-282 | Qualify the Digital Adaptation Kits as an example of centralised metadatarequirements- Revisit whether DAKs illustrate centralised metadata, given they lack a shared metadata repository and common data element definitions its 1 comment, in full | Metadata registries 1 of 1 | proposed | 1 | Discuss | show its comments | |
| CS-283 | Apply a single house style for spelling and punctuationrequirements- Choose one English spelling convention and apply it throughout its 3 comments, in full | Editorial 2 of 3 WHO 1 | proposed | 3 | Discuss | show its comments | |
| CS-284 | Make the narrative shorter and easier to navigaterequirements- Add an executive summary and a short structural overview near the front its 5 comments, in full | Editorial 4 of 5 Core architects 1 | proposed | 5 | Discuss | show its comments | |
| CS-285 | Explain the unclear terms in the health workforce registry section and tablerequirements- Define or explain each term a reviewer could not interpret in the registry description and its data table its 6 comments, in full | Editorial 5 of 6 Core architects 1 | proposed | 6 | Discuss | show its comments | |
| CS-286 | Treat existing standards and current constraints as revisable, not fixedrequirements- Say that established standards and present-day constraints (such as cross-border care arrangements) are starting points, not permanent limits its 2 comments, in full | No 2 of 2 | proposed | 2 | Discuss | show its comments | |
| CS-287 | Add a worked example on health service management and accountabilityrequirements- Add an example to the goal articulation in 2.4.2 showing how a health service management and accountability goal is expressed and what it needs from the infrastructure its 1 comment, in full | Core architects 1 of 1 | proposed | 1 | Discuss | show its comments | |
| CS-288 | Describe the path from today's open health data standards to the semantic modelrequirements- Explain how countries move from the open standards they use today towards the semantic model the guidance defines its 1 comment, in full | Metadata registries 1 of 1 | proposed | 1 | Discuss | show its comments |
Tick comments to group them.
| Select | Ref | Status | Type | Committee | Where | Comment | Recommendations | Decision | Change-set | Links |
|---|---|---|---|---|---|---|---|---|---|---|
| PC-0001✎ edit📣 feedback | triaged | general | Metadata registries WHO Core architects agent, low |
4.3.2 Actors and Roles: Defining Who Participates Section 4.3.2: We need to align Role, Actor, Persona, etc. across the WHO SMART Guidelines, this Reference Architecture, |
Section 4.3.2: We need to align Role, Actor, Persona, etc. across the WHO SMART Guidelines, this Reference Architecture…Section 4.3.2: We need to align Role, Actor, Persona, etc. across the WHO SMART Guidelines, this Reference Architecture, and the knowledge graph. litlfred |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | |
| PC-0002✎ edit📣 feedback | received | technical | Metadata registries human |
Terminology Service §Appendix C (Terminology Service; Public Health Surveillance Platform; Logical Information Model Repository); Appendix F p.69 / 170 / 176 / 226 / 241–242 l.Terminology Service requirements 21 and 24; Public Health Surveillance Platform requirements 18 and 19; Logical Information Model Repository requirement 7; Appendix F p.241 L4–7 and Table F |
The draft names this hazard itself: without semantic governance, "the same coded value is interpreted differently by di…The draft names this hazard itself: without semantic governance, "the same coded value is interpreted differently by different systems, or systems maintain inconsistent local copies of code systems, making aggregation and comparison unreliable" (p.69). The contract the requirements then write is asymmetric. Two components are Required to consume a capability the provider is only advised to offer. Public Health Surveillance Platform requirement 18 is Required: the platform "shall subscribe to update notifications from the Terminology Service to ensure surveillance case definitions and reporting forms remain aligned with current terminology versions as international standards evolve" (p.226). Logical Information Model Repository requirement 7 is Required on the same pattern (p.176). The corresponding provider capability, requirement 21, by which a consuming system learns that an artefact was "updated, deprecated, or retired", is Recommended (p.170). The nearest thing the draft does require is Public Health Surveillance Platform requirement 19 (p.226, Required), which monitors the "timeliness, completeness, and quality of surveillance data submissions" with alerts on threshold breach. That is a check on the volume, timeliness and quality of submissions. Its thresholds are set nationally, so whether the silent absence of one newly notifiable condition registers depends on how finely they are configured. Nothing in the requirement obliges that granularity, and nothing in it requires the platform to establish that a particular consumer has received a particular published change. A detection that depends on how an implementer happens to configure a threshold is not the same as a requirement that the state be demonstrable. Appendix F carries many of the enabling capabilities but is "illustrative reference material rather than a specification" (p.241). Gap detection, replay, resynchronisation, omission, cursor, sequence number, manifest and checksum return no occurrences anywhere in the draft. The reasoning, a worked case and the measurement proposal are set out in the companion paper attached to this submission. Suggested revision: Add a Required, transport-neutral requirement to the Terminology Service alongside requirements 21 and 24. Proposed wording: "The TS shall provide a means by which a consuming system can obtain a complete and explicitly identified copy of the terminology content it depends on, determine whether that copy is a release currently applicable to its context, and detect and recover from a change that has not reached it. The means is not prescribed: an application programming interface, a subscription, a periodic release package, syndication or a bulk export may each satisfy this requirement, and a country distributing by release package requires no change-stream capability." Make the obligation reciprocal: where a component is Required to subscribe, as the surveillance platform and the information-model repository are, the Terminology Service should be Required to provide the mechanism they are Required to use. And extend terminology conformance testing across the producer–consumer boundary rather than against the service alone, with tests appropriate to each route: for replacement delivery, that a consumer can take a fresh complete copy and verify its identity and completeness against the published package identity; for incremental delivery, that omission and duplication are detected, that a recorded position can be resumed from, and that an unserviceable position produces an explicit condition with a route to a complete copy rather than a silent resumption. Vsevolod Shabad, University of Liverpool, United Kingdom |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | |
| PC-0003✎ edit📣 feedback | received | technical | Metadata registries human |
Terminology Service §Appendix C (Terminology Service; Lifelong Health Record) / 3.5 p.159 / 167 / 168 / 169 / 170 l.Terminology Service requirement 3 (TSF-3, p.167), requirement 8 (TSF-4, p.168) and requirement 13 (TSWF-3, p.169); Lifelong Health Record requirement 3 (SHRF-7, p.159); p.170 L147–151 anchor: medium |
The draft is deliberate about versioning at the source. Requirement 3 requires the Terminology Service to "maintain ful…The draft is deliberate about versioning at the source. Requirement 3 requires the Terminology Service to "maintain full version history of code systems, supporting concurrent active versions, defined lifecycle states (draft, active, deprecated, retired), and consumer-specified version requests", and explains the choice: "DPI-H elevates this to Required where OpenHIE treats it as a Recommendation; versioning is essential for a governance-grade national terminology service to honour backwards compatibility obligations" (p.167). Requirement 8 does the same for value sets, and the summary of departures from OpenHIE confirms it (p.170, L147–151). What is not stated is what version and temporal context a consuming system must retain with coded data when interpretation is version-dependent. A service able to reconstruct every release does not help a historical clinical record that carries a bare code, and therefore does not identify which meaning, which value-set membership, which display or which mapping applied when the record was created. The record side of the draft shows how close it already is. The Lifelong Health Record must "record and version all updates to clinical data; records shall never be deleted, only marked as such; no previous version of a record shall be overwritten; all prior versions shall remain retrievable" (requirement 3, SHRF-7, p.159, Required). That is immutability of the record. It is not immutability of the record's interpretation: every prior version of the entry is retrievable, and the requirement does not ensure that any of them carries, or can resolve, the code-system version, expansion or map that governed its meaning when it was written. An effective date alone would not close this. Publication time, the period during which an artefact is approved for use, the version a consumer actually applied, and the time a notification was delivered are four different facts, and reconstructing a past interpretation needs more than one of them. The service can already do the work. Requirement 13 obliges the Terminology Service to "expand value sets into the explicit list of concepts they contain at a given point in time, accounting for the version of the underlying code systems and the expansion parameters supplied by the consumer" (p.169, Required). Reconstructing a past reading is therefore an available operation – but only to a caller who still holds the parameters it needs, and nothing requires the record to retain them. Suggested revision: Add a Required temporal-provenance requirement: published code systems, value sets and concept maps carry stable identifiers, explicit business versions, release dates and, where applicable, effective periods, and a published expansion carries its own identifier, the time at which it was produced, and the parameters and underlying code-system versions used to produce it – requirement 13 already names those inputs; and, where clinical or operational interpretation depends on a terminology release or a governing profile, the record preserves or can resolve the code-system version together with the identifiers, versions and temporal context of the profile, value-set expansion or map on which that interpretation depended. Stating the condition this way keeps the requirement bounded: it does not ask every coded value to carry an expansion version regardless of context, and it does not disturb the concurrent active versions the draft permits. A change should not silently assign a materially different meaning to an existing versionless identifier, but should create an explicitly distinguishable version or identifier while preserving access to the prior meaning. The architecture is standards-neutral and need not name FHIR elements, but the semantic equivalents are what this requires: a business version, a revision date and an effective period on each of CodeSystem, ValueSet and ConceptMap; for an expansion, its own identifier with the timestamp and the parameters and underlying code-system versions that produced it; and Coding.version travelling with the coded value wherever interpretation is version-dependent. FHIR's own guidance against changing the meaning of an existing code is the practice being asked for. Extend conformance testing to include retrospective interpretation of a record created under a prior active version. Vsevolod Shabad, University of Liverpool, United Kingdom |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | |
| PC-0004✎ edit📣 feedback | received | technical | Supply chain human |
Product Registry §Appendix C (Health Facility Registry; Product Registry; Supplier Registry) p.132 / 149 / 193 / 196 l.Health Facility Registry requirement 22; Product Registry requirement 16 and note at p.149 L481–483; Supplier Registry p.193 L93 and requirement 18 anchor: medium |
The note beneath the Product Registry table states that "Cross-cutting requirements (audit logging, subscription and no…The note beneath the Product Registry table states that "Cross-cutting requirements (audit logging, subscription and notification, performance and availability) apply consistently across all registry components" (p.149, L481–483), and the Supplier Registry is described as completing "the three-pillar master data foundation for health supply chain operations alongside the Product Registry and the Health Facility Registry" (p.193, L93). Two of those three pillars are required to be designed for high availability: the Product Registry, on the ground that supply-chain systems at all levels depend on product master data for operational transactions (p.149, requirement 16), and the Health Facility Registry, because facility identity and location data are referenced across supply chain, clinical, financial and surveillance domains (p.132, requirement 22). The Supplier Registry alone is required to be designed for "adequate availability" – the only occurrence of that phrase in the document – on closely parallel reasoning, adding regulatory verification (p.196, requirement 18). Where the draft grades a component lower elsewhere it gives its reason: the Logical Information Model Repository is set at "sufficient reliability and performance" because design-time access is typically less latency-sensitive (p.178, requirement 17). No reason is given here. The difference may be intentional. But neither "high" nor "adequate" defines a testable service level, and recovery objectives are a different measure: the Lifelong Health Record's "defined recovery time and recovery point objectives" (p.162, requirement 21) address recovery from failure, not availability, response time, or how stale a cached copy may become. Suggested revision: Either align the Supplier Registry with the other two pillars at high availability, or state the architectural reason for the lower grade as explicitly as the Logical Information Model Repository's reason is stated. In either case, require countries to define measurable service objectives appropriate to the use case, covering availability, response time, maximum acceptable staleness where cached reference data is used, and recovery time and recovery point objectives. Section 3.6.5 asks that requirements be made testable so vendor claims can be validated in procurement; a grade expressed as an adjective cannot be. Vsevolod Shabad, University of Liverpool, United Kingdom |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | |
| PC-0005✎ edit📣 feedback | triaged | technical | Core architects human |
2.3 DPI-H Reference Architecture Design Principles §Principle IX; 3.6.5; 4.3.5 p.35–36 / 78 / 98 l.Principle IX L392–427; 3.6.5 L955–959; 4.3.5 L400–401 anchor: low |
Principle IX makes trust and security architectural properties while appropriately leaving "the specific controls, conf…Principle IX makes trust and security architectural properties while appropriately leaving "the specific controls, configurations, and operational practices" to implementation and national security policy (L426–427). The procurement and conformance material nevertheless supplies no common supplier-assurance baseline against which a country can evaluate how a DPI-H software component was built and how it will be maintained. Section 3.6.5 asks that requirements be testable "so that countries can validate conformance – including the claims of vendors – before and during procurement" (L955–959), and section 4.3.5 asks countries to "establish minimum conformance requirements for each DPI-H component and define the testing mechanisms through which conformance is assessed" (L400–401) – but both concern conformance to interoperability and information-model profiles. Appendix C commonly requires access control and audit logging, which are properties of the running system. Across the draft there is no occurrence of software bill of materials, vulnerability, secure development, penetration testing or end-of-support. A component can therefore satisfy its information-model and access-control requirements without the guidance asking the supplier to identify its material dependencies, state how long the version will be supported, provide a route for reporting a vulnerability, or show how a security defect reaches deployed installations as a trusted update. This is a completeness gap in the common architecture rather than a request for WHO to prescribe a national control framework, and it sits on a different axis from interoperability conformance. Suggested revision: Add a risk-proportionate supplier software-assurance baseline to Principle IX, and cross-reference it from the procurement and conformance guidance rather than placing it inside section 4.3.5, which addresses interoperability profiles. The baseline should ask for evidence covering: supported versions and end-of-support dates; material third-party dependencies through a software bill of materials or equivalent inventory; a coordinated vulnerability-disclosure route; triage and remediation expectations proportionate to severity and clinical criticality; an authenticated mechanism for delivering security updates to deployed installations; and a secure development and maintenance lifecycle. IEC 81001-5-1 may be referenced for health-software lifecycle activities and NIST SP 800-218 for outcome-based secure-development practices and purchaser-supplier communication. They are not interchangeable and neither should be presented as a mandatory control set: IEC 81001-5-1 governs lifecycle activities and expressly excludes the content of accompanying documentation, so citing it does not by itself procure a dependency inventory. Conformance should assess declared evidence and lifecycle commitments rather than possession of a certificate. Vsevolod Shabad, University of Liverpool, United Kingdom |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | |
| PC-0006✎ edit📣 feedback | received | editorial | Editorial human |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4–4.3.5 p.96–98 l.L339; L369; L398 |
Two consecutive subsections carry the same number. "Integration Interfaces with Foundational DPI" begins as section 4.3…Two consecutive subsections carry the same number. "Integration Interfaces with Foundational DPI" begins as section 4.3.4 at L339 (p.96), and "Interoperability Implementation Pathways" begins as section 4.3.4 at L369 (p.97). "Minimum Conformance and Testing" then appears as 4.3.5 at L398 (p.98). The duplication is reproduced in the table of contents, so a reference to "section 4.3.4" is ambiguous. Suggested revision: Renumber "Interoperability Implementation Pathways" as 4.3.5 and "Minimum Conformance and Testing" as 4.3.6, in both the body and the table of contents. Vsevolod Shabad, University of Liverpool, United Kingdom |
none | not yet | CS-097 discuss | in the document all mentions on GitHub record | |
| PC-0007✎ edit📣 feedback | triaged | technical | Core architects human |
4.4.2 Tracking progress over time §4.4.2 p.99 l.L451–453 ("Standards conformance" bullet) |
The progress dimensions are well chosen, but the standards-conformance dimension measures a property of deployment rath…The progress dimensions are well chosen, but the standards-conformance dimension measures a property of deployment rather than a property of present state. It asks whether components "conform to open standards, expose standard APIs, and use governed terminology and data models" (p.99, L451–453). A system can satisfy all three while holding a superseded version of the terminology it uses: it conforms, it exposes the API, and it uses the governed artefact – just not the release currently applicable to it. That is the failure raised in comment 1, and it is invisible to this indicator as written. Suggested revision: Extend the "Standards conformance" bullet with a currency clause. Proposed wording, to be appended to the existing bullet: "...and whether deployed components can demonstrate that they hold a version of the governed terminology and data models that is currently applicable to their context." Vsevolod Shabad, University of Liverpool, United Kingdom |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | |
| PC-0008✎ edit📣 feedback | triaged | technical | Core architects human |
5.1 Emerging technologies and the foundations they depend on §5.1 p.114 l.3-17 anchor: medium |
The guidance names image interpretation as an AI use case but does not identify the imaging-data and workflow foundatio…The guidance names image interpretation as an AI use case but does not identify the imaging-data and workflow foundations required for safe deployment. Generic clinical-data exchange is insufficient for large diagnostic images, imaging metadata and report-return workflows. Suggested revision: Add diagnostic-imaging interoperability as an explicit implementation pattern, covering DICOM and DICOMweb, PACS and RIS integration, FHIR imaging references and diagnostic reports, large-object transfer, store-and-forward operation, and continuity across facilities. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-251 discuss | in the document all mentions on GitHub record | |
| PC-0009✎ edit📣 feedback | received | technical | No human |
5.2 Why data foundations determine what AI can deliver §5.2 p.115-116 l.42-70 anchor: medium |
The section correctly stresses trusted data foundations but does not distinguish structured clinical-data exchange from…The section correctly stresses trusted data foundations but does not distinguish structured clinical-data exchange from the transport, storage and lifecycle management of diagnostic images. Suggested revision: State that health-information exchange should support references to imaging studies and reports, while image transport and storage may use specialised standards and repositories. Include consent, provenance, retention and access controls across both layers. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-251 discuss | in the document all mentions on GitHub record | |
| PC-0010✎ edit📣 feedback | received | technical | No human |
5.4.2 Trustworthy AI in a health setting §5.3-5.4.2 p.117-118 l.109-169 anchor: medium |
Human oversight is stated as a principle, but the draft does not translate it into minimum operational controls for pro…Human oversight is stated as a principle, but the draft does not translate it into minimum operational controls for production clinical AI. Suggested revision: Add minimum controls for clinical AI: named clinical accountability, model and workflow versioning, continuous quality monitoring, drift surveillance, auditable overrides, incident reporting, escalation thresholds and a safe fallback when AI or connectivity is unavailable. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | |
| PC-0011✎ edit📣 feedback | received | technical | No human |
5.2 Why data foundations determine what AI can deliver §5.2-5.3 p.116-117 l.85-138 anchor: medium |
The architecture discusses agents, assistive AI and clinical applications but does not clearly represent orchestration …The architecture discusses agents, assistive AI and clinical applications but does not clearly represent orchestration among a local facility, an AI service and a remote specialist. A model output is not a completed clinical service. Suggested revision: Add a workflow-orchestration pattern that records task assignment, priority, status, clinician acceptance, critical-result communication, exception handling and final responsibility across distributed teams. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | |
| PC-0012✎ edit📣 feedback | received | technical | Metadata registries human |
Health Workforce Registry §Appendix C: HWR §5 p.148-150 l.5-20 anchor: medium |
The Health Workforce Registry supports identity, credentials, affiliations and service discovery, but virtual and distr…The Health Workforce Registry supports identity, credentials, affiliations and service discovery, but virtual and distributed service models require operational attributes that can change by assignment and time. Suggested revision: Support multiple concurrent affiliations, remote-service jurisdictions, facility privileges, specialty and subspecialty, licence validity at assignment time, language, availability and capacity signals, while protecting sensitive workforce data. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | |
| PC-0013✎ edit📣 feedback | received | technical | Metadata registries litlfred |
Health Workforce Registry §Appendix C: HWR §5 p.148-150 l.8-20 anchor: medium |
Real-time credential verification and audit logging are specified, but the draft does not explicitly connect the creden…Real-time credential verification and audit logging are specified, but the draft does not explicitly connect the credential and privilege used to the individual clinical transaction. Suggested revision: Allow a service to record which verified credential and facility privilege authorised a professional to act on a case, including the verification timestamp, expiry and revocation handling. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | |
| PC-0014✎ edit📣 feedback | received | technical | No human |
Australia §Appendix D.2: India p.242 l.118-126 |
The India example describes federation and consent but could better address delivery of specialist capacity across hete…The India example describes federation and consent but could better address delivery of specialist capacity across heterogeneous states and facilities. Suggested revision: Add an implementation note on federated diagnostic workflows that connect local facilities to remote qualified specialists, with consent, provenance, report return, critical-result communication and subnational policy variation. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-207 discuss | in the document all mentions on GitHub record | |
| PC-0015✎ edit📣 feedback | received | technical | No human |
Benefits Package Registry §Appendix C: CDSE §5 p.199 l.22-25 |
The CDSE requirements cover fail-safe behaviour, audit logging, availability and low-connectivity degradation, but they…The CDSE requirements cover fail-safe behaviour, audit logging, availability and low-connectivity degradation, but they do not require queue persistence, manual routing or post-recovery reconciliation for safety-critical workflows. Suggested revision: Require queue persistence, recovery procedures, manual routing and post-recovery reconciliation so that failed or delayed tasks cannot be silently lost during network interruption, model outage or integration failure. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | |
| PC-0016✎ edit📣 feedback | received | technical | No human |
4.4 Measuring Progress and Impact §4.4 p.108-110 l.409-463 anchor: medium |
The measurement framework covers coverage, conformance, governance maturity and outcome linkage, but model accuracy alo…The measurement framework covers coverage, conformance, governance maturity and outcome linkage, but model accuracy alone is insufficient for AI-enabled service evaluation. Suggested revision: Add an implementation measurement set spanning access, turnaround time, quality, override and incident rates, workforce effects, cost, equity and service continuity, disaggregated where appropriate. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | |
| PC-0017✎ edit📣 feedback | triaged | technical | Core architects human |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.100 l.93-101 |
The draft makes the right to move non-negotiable but does not specify the evidence required to demonstrate practical po…The draft makes the right to move non-negotiable but does not specify the evidence required to demonstrate practical portability from a supplier-controlled system. Suggested revision: Require exportable data, standard interfaces, configuration and model documentation, audit-log retention, clear data rights and a tested transition plan as evidence that systems can be replaced or migrated without lock-in. Kalyan Sivasailam, 5C Network, India |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | |
| PC-0018✎ edit📣 feedback | triaged | technical | Core architects WHO human |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 anchor: medium |
The specialists identified under the Roles and Skills Needed to Build and Govern the Architecture (section 4.5.2) are s…The specialists identified under the Roles and Skills Needed to Build and Govern the Architecture (section 4.5.2) are scarce in most low-income and small island developing states. Suggested revision: The guidance should say what can be shared regionally or outsourced. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-107 discuss | in the document all mentions on GitHub record | |
| PC-0019✎ edit📣 feedback | triaged | technical | Core architects WHO human |
4.6.1 The Investment Case §4.6.1 anchor: medium |
Section 4.6.1 builds the investment case.Section 4.6.1 builds the investment case. Suggested revision: Might be a good opportunity to name a tool to operationalize (e.g. a digital health investment taxonomy), one a Ministry of Finance can act on directly. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0020✎ edit📣 feedback | received | technical | Core architects litlfred |
4.6.2 Sustainability by Design §4.6.2 anchor: medium |
Section 4.6.3 mentions private hosting and app development "bounded so government retains ownership," but doesn't name …Section 4.6.3 mentions private hosting and app development "bounded so government retains ownership," but doesn't name the underlying risk. Suggested revision: Recommend adding a country-driven principle, cautioning against firms using country engagements to access markets without delivering measurable country benefit. (Worth noting section 5.4.4 warns against vendor and donor pressure to invest in AI before foundations are ready, but that's about premature investment and not about first principles of engagement. Also, only the AI-specific caution appears.) Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-117 discuss | in the document all mentions on GitHub record | |
| PC-0021✎ edit📣 feedback | received | technical | Core architects WHO human |
4.6.3 Approaches to Financing §4.6.3 anchor: medium |
The approaches to financing (section 4.6.3.) includes budget lines, blended arrangements, scheme contributions, private…The approaches to financing (section 4.6.3.) includes budget lines, blended arrangements, scheme contributions, private hosting, pooled programme investments; but it does not specifically mention MDB instruments such as sovereign lending, results-based lending, or policy-based operations. Regional and shared financing is also not addressed, which may apply to small island states where regional public foods financing and shared hosting may be the most affordable route. Suggested revision: Consider incorporating a common investment taxonomy to map and package 'invisible' foundational blocks (like standards, SGI, and registries) into standard, investable capital assets. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-115 discuss | in the document all mentions on GitHub record | |
| PC-0022✎ edit📣 feedback | received | technical | Editorial human |
5.2 Why data foundations determine what AI can deliver §5.2 anchor: medium |
Section 5.2 argues that AI performance depends entirely on the data foundation, and 5.4.4's naming of commercial and po…Section 5.2 argues that AI performance depends entirely on the data foundation, and 5.4.4's naming of commercial and political pressure to skip ahead, are more rigorous than most guidance in this space. This aligns well with ADB. Suggested revision: May cross-reference this chapter's foundations-first logic back into the financing case in 4.6.1, since it strengthens the argument for DPI-H to Ministries of Finance. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | |
| PC-0023✎ edit📣 feedback | received | technical | Editorial WHO human |
3.7.1 Purpose §Is the purpose, scope and intended audience of the guidance clear, and is it relevant to your context (country, organisation, role)? anchor: medium |
The purpose and scope are clear and the document is relevant to ADB’s operational agenda and ADB’s new health strategy.…The purpose and scope are clear and the document is relevant to ADB’s operational agenda and ADB’s new health strategy. However, it is unclear whether this is a normative WHO/ITU product that Member States are expected to align to, a technical reference, or an advocacy document. Suggested revision: It would help to make a short statement on the relationship of the DPI-H architecture and guidance to the forthcoming Global Strategy on Digital Health 2028-2033. The intended audience matrix in page 4 only refers to ‘Health Ministries,’ although Ministries of Finance and National Planning Agencies appear in the narrative as important stakeholders. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-008 discuss | in the document all mentions on GitHub record | |
| PC-0024✎ edit📣 feedback | received | technical | Editorial human |
unplaced §Is the level of detail appropriate for its intended readers — ministries and DPI authorities, enterprise architects and technical teams, procurement, and development partners? |
Procurement teams are named as an audience but there is no annex specific to this audience, and no guidance on how to s…Procurement teams are named as an audience but there is no annex specific to this audience, and no guidance on how to structure digital procurement inside public financial management systems. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-260 discuss | all mentions on GitHub record | |
| PC-0025✎ edit📣 feedback | received | technical | No human |
unplaced §Is the distinction between foundational DPI (DPI-F) and health-specific DPI (DPI-H) clear and useful? |
The distinction between DPI-F and DPI-H is clear and useful.The distinction between DPI-F and DPI-H is clear and useful. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | none | all mentions on GitHub record | |
| PC-0026✎ edit📣 feedback | received | technical | Financial systems WHO human |
2.1 The Reference Architecture Scope §Is the two-layer DPI-H architecture clear and appropriate? anchor: medium |
The layers may be taken by readers as a guide for sequencing, when in some cases, some component functions may be found…The layers may be taken by readers as a guide for sequencing, when in some cases, some component functions may be foundational instead of belonging to the business service layer. For example, The Benefits Package Registry currently sits at the business services layer of the DPI-H reference architecture. In Indonesia and the Philippines where there is one national scheme or a dominant single payer that covers most/all of the population, the Benefits Package Registry determines whether a facility can be contracted or a claim can be paid and therefore behaves more like foundational reference data than a business service. Suggested revision: Suggest adding a line to acknowledge that in some cases, some component functions may be foundational instead of belonging to the business service layer (Suggest adding a line acknowledging this) Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | |
| PC-0027✎ edit📣 feedback | received | technical | Core architects human |
unplaced §Based on your knowledge of country needs, do the DPI-H components represent the right set for national digital health infrastructure? |
Civil registration appears only as an illustration under the birth-event-publish-subscribe example. CRVS should be name…Civil registration appears only as an illustration under the birth-event-publish-subscribe example. CRVS should be named as a foundational dependency. Legal identity established at birth is what allows a person to enter UHC beneficiary rolls, and death registration helps protect the system from “ghost patients.” On cybersecurity operations: Security is treated as a design principle but not as a standing operational capability that has recurring costs. A security operations and incident-response function is an institutional requirement that ministries need to secure continuous funding for. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-238 discuss | all mentions on GitHub record | |
| PC-0028✎ edit📣 feedback | received | technical | WHO human |
2.2 Resilient Essential Data and Digital Health Infrastructure (REDDHI) §Is REDDHI — framed as a direction of travel with a minimum starting set of components — a helpful concept? |
The fixed cost of hosting the minimum starting set of components may exceed what is affordable for small states and cou…The fixed cost of hosting the minimum starting set of components may exceed what is affordable for small states and countries in fragile settings. Also, there are already several acronyms in the document (e.g. DPI, DPI-F, DPI-H, full-STAC, DIIG, DHP, and now REDDHI). Suggested revision: Options for a shared or regional model for REDDHI may be explored. If the concept of REDDHI is “the minimum shared foundation of DPI-H", then perhaps it can just be named descriptively (e.g. DPI-H foundational core) rather than introducing another acronym. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | |
| PC-0029✎ edit📣 feedback | received | technical | No human |
1.5.1 The Health Sector Goals §Are the mappings of components to the seven priority health goals accurate and complete? anchor: medium |
Goal 6 on health financing is framed too narrowly. It is currently described mainly in efficiency terms (e.g. claims va…Goal 6 on health financing is framed too narrowly. It is currently described mainly in efficiency terms (e.g. claims validation, provider payment, reduced leakages). It omits other important functions of health financing such as revenue raising (e.g. contribution collection, subsidy targeting) and pooling (e.g. budget flows with PFM). None of the goals address ageing and long-term care. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | |
| PC-0030✎ edit📣 feedback | received | technical | Metadata registries human |
3.4.5 Semantic Governance Infrastructure §Is interoperability, treated as a cross-cutting property rather than a single component, clear and workable, and is the semantic governance infrastructure adequately described? anchor: medium |
The WHO draft introduces the Semantic Governance Infrastructure (SGI) and the Logical Information Model Repository (LIM…The WHO draft introduces the Semantic Governance Infrastructure (SGI) and the Logical Information Model Repository (LIMR) to address limitations of existing frameworks. However, establishing SGI/LIMR workflows is resource-intensive and requires scarce specialized clinical informaticians. Suggested revision: The guidance could frame LIMR and SGI as progressive enablers with clear maturity pathways, rather than binary, mandatory runtime prerequisites, to prevent penalizing low-maturity countries and Small Island Developing States in their conformance scoring. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | |
| PC-0031✎ edit📣 feedback | received | technical | Editorial human |
4.2 Charting a Path to REDDHI §Are the implementation pathways realistic and adaptable to different starting points and levels of resource? |
The four entry points are good and practical guidance, although the indicative timeframes are optimistic. Often, legal …The four entry points are good and practical guidance, although the indicative timeframes are optimistic. Often, legal and regulatory reform, procurement, and institutional establishments take time and will exceed these timelines. Unrealistic timelines may result in unrealistic planning and project design. Suggested revision: These programmes span multiple administrations. It would be helpful for the guidance to say how commitments can be made to survive a change in the administration / a change in minister (e.g. legal basis, protected budget lines, institutional home) Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | |
| PC-0032✎ edit📣 feedback | received | general | Editorial human |
D.2 Country implementation examples §Are the country and regional implementation examples accurate and useful? Please flag any inaccuracies, with a source where possible. |
There is geographic imbalance in the country examples. There is no Southeast Asian, Pacific, or Central/West Asian exam…There is geographic imbalance in the country examples. There is no Southeast Asian, Pacific, or Central/West Asian example. Moreover, of the 13 countries, 7 are high-income. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0033✎ edit📣 feedback | received | editorial | WHO Editorial human |
unplaced §Is the language clear, measured and free of unnecessary jargon? |
British and US english spelling are mixed in some places.British and US english spelling are mixed in some places. Some architecture terms are used before they are defined (e.g. Support qualifier, Application Interaction). Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-283 discuss | all mentions on GitHub record | |
| PC-0034✎ edit📣 feedback | received | technical | No human |
unplaced §Is anything important missing, or is any part unclear or hard to follow? |
More emphasis on clear, protective private sector engagement principles.More emphasis on clear, protective private sector engagement principles. Akihito Watabe, Asian Development Bank, Multiple settings / Asia and the Pacific |
none | not yet | CS-117 discuss | all mentions on GitHub record | |
| PC-0035✎ edit📣 feedback | triaged | general | Core architects human |
2.3 DPI-H Reference Architecture Design Principles §1.4 — VII. Equity and Inclusion p.44 l.325–343 |
The equity principle is strong on geographic, connectivity and institutional constraints, but it does not address user-…The equity principle is strong on geographic, connectivity and institutional constraints, but it does not address user-side capability constraints. Across the life course, people may experience changes in vision, hearing, dexterity, cognition, language, literacy and digital confidence. Unless these are treated as architectural concerns, a service may be technically available yet practically unusable. ITU-T F.780.2 already recognises accessibility requirements for telehealth services, including older persons with age-related disabilities. Suggested revision: Add after line 343: “Equity and inclusion also require the architecture to accommodate variation in functional ability, disability, language, literacy and digital capability across the life course. Countries should require age-inclusive and accessible interaction patterns, multimodal channels, low-complexity workflows and assisted-access pathways, so that participation in DPI-H does not depend on independent use of a smartphone or any single digital channel." Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | |
| PC-0036✎ edit📣 feedback | triaged | technical | Core architects human |
2.3 DPI-H Reference Architecture Design Principles §1.4 — VIII. Data Ownership, Access, and Control p.44–45 l.346–360 |
The section treats individual agency mainly as direct personal action. In practice, some people exercise agency with su…The section treats individual agency mainly as direct personal action. In practice, some people exercise agency with support or through an authorised representative, including during temporary illness, disability, cognitive decline or other changes in functional ability. Without a standard delegation model, countries and applications will recreate proxy access inconsistently, increasing privacy, safety and exclusion risks. Suggested revision: Add after line 370: “While the legal rules governing representation remain matters for national law and policy, the architecture should be capable of representing and enforcing supported and delegated access where permitted by law. It should distinguish assistance provided under the individual’s direction from authority exercised by an authorised representative, and support granular, purpose-limited, time-bound where appropriate, revocable and auditable permissions, including verification of the representative and the source of authority. Countries should also assess whether existing legal and regulatory frameworks adequately support these arrangements and undertake necessary reforms where gaps are identified.” Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-236 #10 | in the document all mentions on GitHub record | |
| PC-0037✎ edit📣 feedback | received | general | Clinical human |
1.5.1 The Health Sector Goals §1.5.1 — The Health Sector Goals p.32 l.477–488 |
At this point, the goals on continuity of care and personal health records are framed primarily around clinicians and i…At this point, the goals on continuity of care and personal health records are framed primarily around clinicians and individuals acting independently. Although later sections refer more broadly to coordination across providers and settings, the guidance does not explicitly incorporate home and community care, rehabilitation, long-term care, social-care services or the legitimate participation of carers. Population ageing makes this omission increasingly consequential, although the requirement applies across the life course. WHO’s ICOPE approach recognises person-centred assessment, personalised care planning, community-based care, social support and support for carers. Suggested revision: Revise the third goal to state that clinicians, health and care workers, individuals and appropriately authorised carers need governed access to relevant information and shared care plans across settings. State explicitly that continuity of care should extend across hospitals, primary care, rehabilitation, home and community care, long-term care and relevant social-care services. Revise the fourth goal to clarify that individuals may access and exercise control over their records directly, with support, or through an authorised representative where permitted, with access governed by consent, role and applicable legal authority. Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-255 discuss | in the document all mentions on GitHub record | |
| PC-0038✎ edit📣 feedback | received | general | Core architects human |
3.4.2 Governance principles §3.4.2 — Governance principles p.64 l.258–265 anchor: medium |
The inclusive-representation principle does not explicitly include older people, persons with disabilities, people with…The inclusive-representation principle does not explicitly include older people, persons with disabilities, people with limited digital capability, or unpaid and family caregivers. Although caregivers are listed as stakeholders elsewhere in the guidance, these groups are not clearly represented in the governance provisions. They may face distinctive barriers involving identity verification, accessibility, consent, assisted or delegated access, and continuity of care. Governance processes based mainly on digitally confident users may therefore overlook how the infrastructure functions for people who require assistance. Suggested revision: Revise the examples in lines 260–261 to include “older people, persons with disabilities, people with limited digital capability, and unpaid or family caregivers.” In lines 321–327, add that governance bodies should establish mechanisms for obtaining and acting on evidence from people who use assisted or delegated access, including older people, persons with disabilities and caregivers, rather than relying principally on digitally confident users or organisational representatives. Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-048 discuss | in the document all mentions on GitHub record | |
| PC-0039✎ edit📣 feedback | received | general | Clinical human |
3.3 The reference architecture in practice §3.3 — Reference architecture in practice p.61 l.180–190 anchor: medium |
The example correctly identifies comprehensive needs assessment and shared care planning, but the resulting capabilitie…The example correctly identifies comprehensive needs assessment and shared care planning, but the resulting capabilities are described as being surfaced only to health workers. Shared care planning is incomplete when the individual, authorised caregiver and relevant health or social care worker cannot see the plan, understand assigned actions and receive updates according to their role. Suggested revision: Add after line 187: “Where care is shared across settings, relevant care-plan information, actions and notifications should also be available to the individual, authorised caregivers, and health and social care workers according to consent, role, purpose and applicable law.” Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | |
| PC-0040✎ edit📣 feedback | received | general | Core architects human |
4.1.2 Assessing Where You Are §4.1.2 — Assessing Where You Are p.98–99 l.28–61 anchor: medium |
The proposed current-state assessment inventories systems, foundational DPI, governance and priority goals, but it does…The proposed current-state assessment inventories systems, foundational DPI, governance and priority goals, but it does not assess whether people can actually use the resulting access channels. A country may have broad identity and connectivity coverage while still excluding older people, persons with disabilities, people with low literacy, those without suitable devices, and those who rely on trusted intermediaries. Suggested revision: Add a fifth assessment question: “Who can actually use the infrastructure and through which channels?” Countries should assess population age structure, disability and functional-access needs, language and literacy, digital capability, device and affordability constraints, authentication failure, availability of non-digital and assisted channels, and the capacity of trusted intermediaries. The roadmap should identify the access gaps and the investments required to close them. Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | |
| PC-0041✎ edit📣 feedback | received | technical | Core architects human |
4.3.2 Actors and Roles: Defining Who Participates §4.3.2 — Actors and Roles: Defining Who Participates p.105–106 l.285–305 |
The section requires a minimum actor and role set, but the examples remain institution-centred. A national role schema …The section requires a minimum actor and role set, but the examples remain institution-centred. A national role schema should distinguish the individual from people acting with or for the individual. Relationship alone must not confer access: a spouse, adult child, caregiver, legal guardian and assisted-access agent may each have different authority, scope and duration. Suggested revision: Add to the minimum actor set: individual; supported user; authorised representative or proxy; informal caregiver; legal guardian; health or social care worker; and assisted-access intermediary. Require each authority to be represented separately from the relationship, with scope, purpose, duration, permitted actions, provenance and revocation. Standards-based patterns such as HL7 FHIR Consent and RelatedPerson should be used where applicable. Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-236 #10 | in the document all mentions on GitHub record | |
| PC-0042✎ edit📣 feedback | received | technical | Core architects human |
4.4.2 Tracking progress over time §4.4.1–4.4.2 — Measuring Progress and Impact p.109–110 l.427–460 |
The measurement framework tracks component coverage, conformance, governance maturity and outcomes, but it lacks a meas…The measurement framework tracks component coverage, conformance, governance maturity and outcomes, but it lacks a measure of successful human access. Geographic or population reach does not show whether people can authenticate, understand the interface, complete a task, use an authorised representative, or obtain redress when access fails. Suggested revision: Add a fifth dimension, “equitable access and effective use”. Indicators should include successful authentication and task completion, abandonment and support requests, availability and use of assisted or delegated access, accessibility conformance, grievance resolution, and inappropriate exclusion. Results should be disaggregated by age, disability or functional-access need, language, geography and care setting while protecting privacy. Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | |
| PC-0043✎ edit📣 feedback | received | technical | Clinical human |
Lifelong Health Record §Appendix C — Lifelong Health Record, 1. What it is p.165 l.7–20 anchor: medium |
The definition states that the LHR is accessible to authorised health workers, systems and individuals. It does not exp…The definition states that the LHR is accessible to authorised health workers, systems and individuals. It does not explicitly include authorised representatives, caregivers or care workers, even though these actors may be essential to continuity of care. The phrase “meaningful control of the individual” should also recognise direct, supported and legally delegated exercise of that control. Suggested revision: Revise lines 13–20 to include “authorised health and care workers, systems, individuals and their authorised representatives”. Add: “Meaningful control may be exercised directly, with decision support, or through a legally authorised representative, with the scope and provenance of that authority recorded and auditable.” Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | |
| PC-0044✎ edit📣 feedback | received | technical | Clinical human |
Lifelong Health Record §Appendix C — Lifelong Health Record, 4. How it connects p.168–169 l.138–141; 176–179 |
Person-facing access tools are placed outside DPI-H, which is a reasonable component boundary, but the guidance provide…Person-facing access tools are placed outside DPI-H, which is a reasonable component boundary, but the guidance provides no shared access-layer requirements for those tools. Without a cross-cutting profile, every portal, wallet and mobile application may implement accessibility, authentication, consent and proxy access differently, recreating fragmentation at the human-access layer. Suggested revision: Introduce a cross-cutting “Person Access and Delegation Profile” applicable to all person-facing tools that connect to the LHR. It should define minimum requirements for accessible and multilingual interaction, alternative authentication, low-complexity workflows, consent and delegation, notifications, audit visibility, assisted access and conformance testing. The profile need not make the portal itself a DPI-H component. Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | |
| PC-0045✎ edit📣 feedback | received | technical | Clinical human |
C Appendix C: DPI-H Application Component Descriptions §Appendix C — Lifelong Health Record, Functional requirements p.171 l.Requirements 13–15 anchor: medium |
The functional requirements cover professional role-based access, consent integration and direct individual access, but…The functional requirements cover professional role-based access, consent integration and direct individual access, but omit delegated and supported access. This leaves a major gap for children, adults temporarily unable to act, older people with changing capability, persons with disabilities and anyone who chooses a trusted representative. Suggested revision: Add a Required functional requirement: “Delegated and supported access. The LHR shall support an individual granting, reviewing, limiting and revoking access to one or more authorised representatives. Delegations shall specify scope, purpose, duration and permitted actions; distinguish viewing from acting or contributing; verify both parties and the source of authority; support legal guardianship and supported decision-making where applicable; and produce a complete audit trail visible to the individual and governance authority. Implementations should use standards-based representations such as FHIR Consent and RelatedPerson where applicable.” Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-236 #10 | in the document all mentions on GitHub record | |
| PC-0046✎ edit📣 feedback | received | technical | Clinical human |
Logical Information Model Repository §Appendix C — Lifelong Health Record, Governance p.173 l.203–214 (items 3–4) |
The governance section requires understandable consent and a documented access policy, but does not address supported d…The governance section requires understandable consent and a documented access policy, but does not address supported decision-making, changes in decision-making capacity, guardianship, disputes over authority, safeguarding against coercion or abuse, or the end of a delegation. These are governance questions that cannot safely be left to each application. Suggested revision: Expand consent and access governance to require rules for creating, verifying, reviewing, suspending and terminating representative authority; recording the legal or consensual basis; handling temporary and fluctuating capacity; resolving disputes; preventing coercion and misuse; providing user-visible logs and alerts; and offering accessible complaint and redress mechanisms. Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | |
| PC-0047✎ edit📣 feedback | received | technical | Core architects human |
5.4.3 Equity and safety §5.4.3 — Equity and safety p.119 l.170–176 anchor: medium |
The AI equity section refers generally to representative data but does not identify age as a material dimension. Older …The AI equity section refers generally to representative data but does not identify age as a material dimension. Older people are often under-represented in datasets and may differ in multimorbidity, medication patterns, physiology, disability, communication and care setting. Aggregate performance can therefore conceal age-related error or exclusion. Suggested revision: Add: “AI evaluation datasets and performance reporting should be examined across age groups, disability and functional-access needs, sex, language and care setting, including community and long-term-care settings. Countries should test for age-related under-performance, inaccessible interaction and automation that inappropriately substitutes for human support or informed decision-making.” Shamir Chakrabarty, AgeTech Asia / Intellia Holdings Sdn.Bhd, Malaysia |
none | not yet | CS-124 discuss | in the document all mentions on GitHub record | |
| PC-0048✎ edit📣 feedback | triaged | editorial | No human |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §1.1.2 p.9 l.35-38 |
The DPI approach seems to lean more to the former than the latter building or evolving existing resources rather than r…The DPI approach seems to lean more to the former than the latter building or evolving existing resources rather than reimaging the entire ecosystem Suggested revision: Make a clear distinction between interoperability as exchange as opposed to interoperability through shared/common platforms/components by specific systems used for specific delivery in the system as a whole Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-245 discuss | in the document all mentions on GitHub record | |
| PC-0049✎ edit📣 feedback | triaged | editorial | No human |
1.1.3 Building on existing foundations §1.1.3 p.10 l.82-86 |
The agnostic nature of the DPI approach is clear in the text but what is not clear is whether the recommendations inten…The agnostic nature of the DPI approach is clear in the text but what is not clear is whether the recommendations intend (as they imply) to apply to specific delivery approachs, systems, technologies or standards in terms of the concept of building on the installed base Suggested revision: Clarify to what extent the DPI approach leans towards reuse of existing specific standards, their modification or rewriting/fresh development (if desired making it clear this is where necessary to fulfil objectives without compromising but informed by any/all existing approaches) Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-245 discuss | in the document all mentions on GitHub record | |
| PC-0050✎ edit📣 feedback | triaged | editorial | No human |
1.1.3 Building on existing foundations §1.1.3 p.11 l.103 |
The three examples govern domains/functions that are not of equal in priority from a health perspectiveThe three examples govern domains/functions that are not of equal in priority from a health perspective Suggested revision: If not clear any where else in the document I would advocate for an highlight a hierarchy of importance for different components of a complete system…..of these three (subject) ID is more foundational by several levels than a payment system and data exchange arguably sits alongside in priority terms (before getting in to whether exchange rather than access control should be the future model for the primary data of interest relating directly to the subject Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-006 discuss | in the document all mentions on GitHub record | |
| PC-0051✎ edit📣 feedback | triaged | editorial | No human |
1.1.3 Building on existing foundations §1.1.3 p.11 l.103-113 |
In highlighting ID no mention is made of the privacy, control and safety concerns that tend to arise with respect to di…In highlighting ID no mention is made of the privacy, control and safety concerns that tend to arise with respect to digital ID in many jurisdictions. This becomes particularly pertinent when addressing health needs and the issue of linkage arises Suggested revision: If not addressed elsewhere I would recommend some commentary on this issue as confidentiality has broken many a health data project at scale Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-0052✎ edit📣 feedback | received | technical | No human |
1.1.3 Building on existing foundations §1.1.3 p.11 l.Box 1.1 anchor: medium |
"Every person has a right to their own health record" over simplifies the reality of what a health record is and what i…"Every person has a right to their own health record" over simplifies the reality of what a health record is and what it contains Suggested revision: Would suggest "Every person has rights over their own health record" to reflect both the legal status of data and the limitations data subjects have in this context Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0053✎ edit📣 feedback | received | technical | No human |
1.2.2 Data exchange DPI and Interoperability in the health sector §1.2.2 p.15 l.Box 1.3 anchor: medium |
On both counts there is a pre-supposition that existing realities (a standard in one case and the existence of cross-bo…On both counts there is a pre-supposition that existing realities (a standard in one case and the existence of cross-border care on the other) are immutable in theory or the long term Suggested revision: If this is conceded, make it clear that in both cases there may be compromises to enable delivery today that must either be accepted with their perpetual limitations or solved by interim approaches while alternatives are actively pursued in parallel Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-286 discuss | in the document all mentions on GitHub record | |
| PC-0054✎ edit📣 feedback | received | technical | No human |
1.5 The Seven Priority Health Sector Goals §1.5 p.21 l.440-8 |
Near-real time reporting, auditing and registries require the linking of the data as conceived under a DPI approach wi…Near-real time reporting, auditing and registries require the linking of the data as conceived under a DPI approach with a generally missing component that should be shared namely the identified subjects of interest (whether persons or other) Suggested revision: The infrastructure to maintain this could be another DPI component or is analgous to other components (such as ID, terminology registers etc) Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-022 discuss | in the document all mentions on GitHub record | |
| PC-0055✎ edit📣 feedback | received | editorial | No human |
1.5.1 The Health Sector Goals §1.5.1 p.22 l.464 |
The notion that data be "captured once and used many times" is valid but needs qualification against the common asserti…The notion that data be "captured once and used many times" is valid but needs qualification against the common assertion that the structure of the data/metadata is governed by its intended purpose Suggested revision: In a health context there is a lack of clarity in every context I am aware of what the true intended purpose is even if on inspection it is nearly always not primarily for the delivery of individual care. Much of the DPI draft goes beyond just this component of healthcare data but I submit that it should be the foundational intent and top of a necessary hierarchy of intended uses so that the data design (of both the more generi DPI and domain specific health data). Nearly all the goals would be better served by clarity on this (and by prioritising direct care in the design as suggested) Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-100 discuss | in the document all mentions on GitHub record | |
| PC-0056✎ edit📣 feedback | received | editorial | No human |
2.2.2 The enabling conditions for REDDHI §2.2.2 p.28-29 l.148-151 |
HL7-FIHR, SNOMED CT and LOINC are international standards and are currently perhaps the most established but not necess…HL7-FIHR, SNOMED CT and LOINC are international standards and are currently perhaps the most established but not necessarily refined Suggested revision: Listing them specifically implies they are optimal but would recommend rewording to make it clear none of them may be optimal or long term sustainable. Similar disclaimer to the foot note regarding the proprietary status of SNOMED-CT…..standards lock in is as potential an issue as vendor lock-in. HL7-FIHR has its own financial model that could be similarly commented on as SNOMED-CT Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | |
| PC-0057✎ edit📣 feedback | received | technical | No human |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.32 l.240-263 |
There are some potential contradictions in this section for example: potentially around the DPI-H approach being advoca…There are some potential contradictions in this section for example: potentially around the DPI-H approach being advocated versus comments about connectivity downtime, different potential interpretations/implementations of federation than the one described, a lack of acknowledgement of the same scaling problem for a federated model as described as was outlined 1.3.1 justifyinf the DPI-H approach Suggested revision: I would expound more on the challenge of delivering true interoprability, what some have described as operability or simply again the need to define the hierarchy of outputs (which as in other comments I would advocate for putting individual direct care at the top of and designing the entire system appropriately) Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | |
| PC-0058✎ edit📣 feedback | received | editorial | No human |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.33 l.286-301 |
The DPI-H approach in general and the section on modularity imply that a single development trajectory can overcome the…The DPI-H approach in general and the section on modularity imply that a single development trajectory can overcome the need to deliver solutions now while building the long term sustainable architecture the DPI-H approach aims for Suggested revision: Modularity can produce the same vertical type design or simply prove to difficult while trying to deliver without emphasising this risk or the (potential) need for parallel development approaches where the ideal/theoretical can be both conceived/developed and inform the immediate operational delivery. The first line (286) also defaults to recommending relying on any installed base (even at DPI-H or architectural level) which carries the same risk. Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-245 discuss | in the document all mentions on GitHub record | |
| PC-0059✎ edit📣 feedback | received | editorial | No human |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.33 l.304-322 |
Agree in principle however the building of foundations that does not develop the expertise to use a proven foundational…Agree in principle however the building of foundations that does not develop the expertise to use a proven foundational approach due to lack of local expertise risks locking a particular nation into a static, flawed or out dated foundation Suggested revision: Would suggest refining the section to reflect this and also the separation of delivery of operational systems versus the conceptual design of ideals which must and should be done informed by global expertise even if it can only proceed under local expertise as advocated. This would fit with the parallel approach to development I have suggested in other sections (unconstrained ideal versus pragmatic operational delivery) Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-242 discuss | in the document all mentions on GitHub record | |
| PC-0060✎ edit📣 feedback | received | editorial | No human |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.36-37 l.436-445 |
De-identification used appropriately but the implications of data access at scale for secondary uses can't be under emp…De-identification used appropriately but the implications of data access at scale for secondary uses can't be under emphasised Suggested revision: The default should be to protect privacy and given that de-identification is the best achievable situation in any patient level data more should probably be said on approaches to secondary use that prevent direct access to patient level data as well again emphasising the prioritisation of the architectural design for individual direct care over and above any other use Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-244 discuss | in the document all mentions on GitHub record | |
| PC-0061✎ edit📣 feedback | received | technical | No human |
2.4 Methodology: Mapping Health Goals to DPI-H §2.4 p.37-38 l.457-466 |
There is perhaps a need between available technology and generic health system goals to separately (rather than directl…There is perhaps a need between available technology and generic health system goals to separately (rather than directly associated with) describe the generic capabilities specific technologies should fulfil so that the tendency to look for off the shelf solutions is minimised Suggested revision: Goals should determine capabilities which should be fulfilled by technologies. The work already undertaken and described in 467-473 appears to be too tied to delivery and does not achieve sufficient separation between defining/developing an ideal and delivering working solutions (the currrent status quo) Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-023 discuss | in the document all mentions on GitHub record | |
| PC-0062✎ edit📣 feedback | received | technical | No human |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.392-394 |
Implication that this is a static/piecemeal process rather than one that should be established as a live processImplication that this is a static/piecemeal process rather than one that should be established as a live process Suggested revision: Incorporate a view that in an ideal system the "change requests" like incident reports should be embedded in the operational/delivery systems that are not covered by the DPI-H architecture. A commentrary on the criticality of referencing the numan components of the system as well as the optimal human-machine interactions and the mutual interdependency of the DPI-H and serviced operational systems would be appropriate in the context of the SGI discussion (including the section that follows this one) Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | |
| PC-0063✎ edit📣 feedback | received | technical | No human |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.638-650 |
Definition of singular, multiple or complex nature of each of the 5 components decribed should be elaboratedDefinition of singular, multiple or complex nature of each of the 5 components decribed should be elaborated Suggested revision: Client and facility registries are singular entities (even if they might be split/federated). The Facilities might also fall under different national systems (for example in the UK this might under Companies house for a private provider though this would need CH to become more sophisticated to be part of the generic DPI). A commercial registry (like CH) would itself be dependent on a person ID (generic DPI) and be prerequisite for the product registry (which would also need to cope with non-commercial sources of "product"). Workforce will likely fall mostly under professional regulators as the logical single controlling entity again a generic if health industry specific one for health professionals and needing something to cover other staff for other purposes (direct care and otherwise) The life long health record as described is a complex entity that would be worthy of its own equivalent architectural description as it (defined for individual direct care) should be the central component of the DPI-H served by the others and as elsewhere recommended the priority of an ideal architecture (over secondary use cases). Some of this is touched on in 652-659 but could do with broader exposition Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-051 discuss | in the document all mentions on GitHub record | |
| PC-0064✎ edit📣 feedback | received | editorial | No human |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.663+665 |
Minor point but all subsequent references plcae LIMR before TSMinor point but all subsequent references plcae LIMR before TS Suggested revision: Reverse the order of these two definitions Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-060 discuss | in the document all mentions on GitHub record | |
| PC-0065✎ edit📣 feedback | received | editorial | No human |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.68 l.Table 3.5 |
Linkage as exemplified by SNOMED CT-LOINC mappingsLinkage as exemplified by SNOMED CT-LOINC mappings Suggested revision: This is symptomatic of standards lock in. Linakge should sit outside the DPI-H where it is necessitated by duplication in two co-existing standards. This type of linkage is an operational necessity not a ideal system component Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | |
| PC-0066✎ edit📣 feedback | received | technical | No human |
3.6.2 Data and health content standards §3.6.2 p.73 l.793…. |
There are emerging challenges about long term archiving, reference and review of digital health records (all components…There are emerging challenges about long term archiving, reference and review of digital health records (all components but for the sake of this comment principally the individual direct clinical records) Suggested revision: Documents versus machine readable data and applications to present primary data with the necessary supporting registry of systems/versions, archived digital applications etc etc are all needed. Non-standard approach would be to treat documents and the data separately but require both: one as static, validated images of a "transaction" the other as the persistent logical representation of an individual (events, trajectory etc). This is not data embedded documents but loosely analogous to double entry book keeping Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-071 discuss | in the document all mentions on GitHub record | |
| PC-0067✎ edit📣 feedback | received | editorial | No human |
3.6.2 Data and health content standards §3.6.2 p.73 l.811 anchor: medium |
I would challenge a prior assumption that anything should be protected from re-invention including existing standardsI would challenge a prior assumption that anything should be protected from re-invention including existing standards Suggested revision: While referring to existing established, dominant even good standards, it works against the general intentions of DPI to explicitly name anything but a proven ideal standard. The later description does mitigate somewhat but I would recommend mimising the implication that something is "approved" The final paragraph describes adaptors but I would suggest making this explicit as an operational delivery compromise rather than the answer to the boundary/replacement challenges for an true interoperability All this is particularly important where alternatives to structure are entertained as in comment #19 Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-286 discuss | in the document all mentions on GitHub record | |
| PC-0068✎ edit📣 feedback | received | technical | No human |
4.1.1 No Country Starts from Zero §4.1.1 p.88 l.13 anchor: medium |
I both completely agree that this is true and disagree that this should be accepted as a ground truth. Sometimes a blan…I both completely agree that this is true and disagree that this should be accepted as a ground truth. Sometimes a blank slate is necessary to achieve a step change, sometimes simply to allow free thinking so the installed base can be evolved in ways that would not otherwise have been possible. Suggested revision: I would either explore this contention or remove the implied position that a blank slate approach is "wrong" I would refer again to parallel development (operational and theoretical) and would also invite the theoretical to be undertaken from the premise (if not the reality) of a blank slate and to do so with the only truly universal patient population who are (from a data perspective) essentially blank slates! REDDHI is too pragmatic if a better position the continuing any status quo Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | |
| PC-0069✎ edit📣 feedback | received | technical | No human |
4.3.1 Design Data Structures and Data Models First §4.3 p.95 l.274-281 |
No comment on chronology. Archiving and retrospective review of digital records require data/metadata that describe no …No comment on chronology. Archiving and retrospective review of digital records require data/metadata that describe no only any evolution in attributes over time but also applicability where a property may be transient for example. Suggested revision: Include temporal/chronology component as foundational for all the core registry DPI-H components Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | |
| PC-0070✎ edit📣 feedback | received | editorial | No human |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.306 |
I understand why FHIR is being recommended but I would advise no existing specific standard for actual implementation b…I understand why FHIR is being recommended but I would advise no existing specific standard for actual implementation be recommended and if it is it should be recommended as a "right now" or pragmatic recommendation Suggested revision: Modify wording if not remove an explicit recommendation entirely as it is out of step with the principles of DPI-H Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | |
| PC-0071✎ edit📣 feedback | received | editorial | No human |
5.1 Emerging technologies and the foundations they depend on §5 p.104…. l.104…. |
A section on future proofing the architecture is pertinent on the one hand but could be seen as somewhat redundant on t…A section on future proofing the architecture is pertinent on the one hand but could be seen as somewhat redundant on the other. The inclusion of specific section AI is both understandable but also potentially unnecessary for the reasons described in this section....namely that future technologies (especially data based technologies such as AI) are dependent on data foundations which DPI supports. Suggested revision: Comment on future technologies with less emphasis on AI With reference to AI I would highlight as with other data at scale technologies that precision is prioritised over accuracy which in addition to risk of bias are critical weaknesses. Basil Bekdash, UK NHS, United Kingdom (England) |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | |
| PC-0072✎ edit📣 feedback | received | general | Editorial ai |
DPI-H Reference Architecture Framework §2 (chapter introduction) p.24 l.19–27 anchor: low |
We support this methodological choice. Using TOGAF as the foundation and expressing the architecture in ArchiMate (3.1,…We support this methodological choice. Using TOGAF as the foundation and expressing the architecture in ArchiMate (3.1, p.42, lines 34–36) creates a clear link between a health goal and the components and specifications that support it. Ministries and ICT units in small states will find this one of the guidance's most useful features. It makes the architecture practical for assessing investment proposals and drafting procurement requirements, rather than leaving it as a design reference only. Suggested revision: Retain this section as drafted, and highlight the bidirectional traceability point (lines 24–26) in the executive summary. It is a strong reason for countries to use the architecture as a planning and procurement tool, not just as a technical reference. Utica Alves, CARICOM Secretariat, Caribbean Community (CARICOM) — Guyana |
none | not yet | CS-002 discuss | in the document all mentions on GitHub record | |
| PC-0073✎ edit📣 feedback | received | general | Editorial ai |
2.1.3 Relationship to foundational DPI §2.1.3 p.26 l.87–97 |
This is especially important for Member States where foundational DPI is still limited or does not yet exist. Health sy…This is especially important for Member States where foundational DPI is still limited or does not yet exist. Health systems should be able to move ahead now and connect to digital identity, payments and data-exchange infrastructure as these become available, rather than waiting for foundational DPI to mature. In our region, waiting for that wider infrastructure is a common reason digital health investment stalls. The point is easy to miss at the end of the sub-section. Suggested revision: Give this point more prominence by including it in the executive summary and repeating it in 1.1.4 ('Who can benefit from this guidance?', p.12). Suggested wording: 'The absence of mature foundational DPI is not a reason to defer DPI-H investment. Health-sector components can be established first and integrated with foundational DPI as it becomes available.' Utica Alves, CARICOM Secretariat, Caribbean Community (CARICOM) — Guyana |
none | not yet | CS-011 discuss | in the document all mentions on GitHub record | |
| PC-0074✎ edit📣 feedback | received | general | Core architects ai |
1.5 The Seven Priority Health Sector Goals §1.5 p.21–23 l.423–437 |
The seven priority health sector goals fit well with Caribbean priorities. They are also broadly consistent with the ON…The seven priority health sector goals fit well with Caribbean priorities. They are also broadly consistent with the ONE Caribbean Digital Health Roadmap agreed by seven CARICOM Member States (2026) and the IDB/PAHO Pan-American Highway for Digital Health (PH4H). However, some regions already have their own agreed goal frameworks. The guidance should explain how countries can map the seven goals to an existing regional or national framework, rather than appearing to replace it. Suggested revision: Add a short paragraph at the end of 1.5 noting that countries and regional bodies may already have agreed digital health goal frameworks. Clarify that the seven goals should be mapped to those frameworks, not replace them. A brief worked example would also be helpful. Utica Alves, CARICOM Secretariat, Caribbean Community (CARICOM) — Guyana |
none | not yet | CS-023 discuss | in the document all mentions on GitHub record | |
| PC-0075✎ edit📣 feedback | received | technical | Core architects ai |
3.4.6 Regional governance considerations §3.4.6 p.62–63 l.495–516 |
The regional governance section and its layered model are helpful. However, it assumes that each country operates its o…The regional governance section and its layered model are helpful. However, it assumes that each country operates its own components while a regional body governs the shared arrangements. Small states often find another model more practical: operating a component once at regional level and providing it as a service to several countries. A single country will frequently lack the scale and specialist staff to run it alone. Terminology services, conformance and testing infrastructure, and the logical information model repository are strong candidates for this approach. Suggested revision: Add a paragraph to 3.4.6 that treats shared regional operation as a separate deployment model. Distinguish between (a) components governed regionally but operated nationally and (b) components operated regionally and used by participating countries. The second model needs service levels, data residency and sovereignty, exit and continuity arrangements, and cost-sharing set out. Utica Alves, CARICOM Secretariat, Caribbean Community (CARICOM) — Guyana |
none | not yet | CS-053 discuss | in the document all mentions on GitHub record | |
| PC-0076✎ edit📣 feedback | received | technical | Core architects ai |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 p.100–101 l.500–524 |
The nine specialist roles give a realistic picture of the skills the architecture requires, and it is helpful that line…The nine specialist roles give a realistic picture of the skills the architecture requires, and it is helpful that lines 521–524 note that each role does not need a separate post. States with populations under one million face a different problem. Skills such as FHIR modelling, terminology curation, conformance testing and security architecture often do not exist in the national labour market and are seldom sustainable as full-time national posts. The guidance does not yet offer a practical route for these settings beyond building capacity over time. Suggested revision: Add a short sub-section on shared and regional capacity. It should cover regional pools of specialist skills, jointly procured or operated terminology and conformance services, and regional bodies serving as the institutional home for skills that cannot be sustained nationally. It should also identify which roles remain national, such as architecture ownership, data governance and security accountability, and which can be shared. Utica Alves, CARICOM Secretariat, Caribbean Community (CARICOM) — Guyana |
none | not yet | CS-107 discuss | in the document all mentions on GitHub record | |
| PC-0077✎ edit📣 feedback | received | general | Editorial ai |
Lifelong Health Record §Appendix D (D.2 and D.3) p.229–235 l.91–219 |
The implementation examples do not include a small island developing state or a CARICOM example. The thirteen country e…The implementation examples do not include a small island developing state or a CARICOM example. The thirteen country examples come from large or high-income systems, and the European Union is the only regional example. This makes it harder for readers in small states to see how the guidance applies at their scale. Relevant Caribbean experience is available. ONE Caribbean Connect (Port of Spain, 2026) brought together The Bahamas, Barbados, Belize, Guyana, Jamaica, Suriname and Trinidad and Tobago. It produced the ONE Caribbean Digital Health Roadmap Commitment on governance, legal and policy frameworks, and interoperability under the IDB/PAHO Pan-American Highway for Digital Health (PH4H). Suggested revision: Add at least one small-state example to D.2 and one small-state regional grouping to D.3. D.3 could be based on ONE Caribbean Connect and the ONE Caribbean Digital Health Roadmap, showing regional coordination on interoperability and cross-border health data exchange among small states. Utica Alves, CARICOM Secretariat, Caribbean Community (CARICOM) — Guyana |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0078✎ edit📣 feedback | received | general | Core architects ai |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.89–90 l.63–101 |
The four entry points are a useful diagnostic, but small states often fall under entry points 1 and 2 at the same time:…The four entry points are a useful diagnostic, but small states often fall under entry points 1 and 2 at the same time: limited national governance and foundational DPI, alongside several donor-funded, programme-specific systems already in operation. The text presents the entry points as alternatives and does not explain how to sequence the work when more than one applies. Suggested revision: Add a sentence noting that a country can fall under more than one entry point at the same time. Explain how to sequence the work in that case; for example, establishing architectural standards and governance under entry point 1 before starting the integration work described under entry point 2. Utica Alves, CARICOM Secretariat, Caribbean Community (CARICOM) — Guyana |
none | not yet | CS-092 discuss | in the document all mentions on GitHub record | |
| PC-0079✎ edit📣 feedback | received | general | Editorial ai |
Executive Summary §Executive Summary p.Global l.Executive Summary anchor: medium |
The guidance provides a strong strategic rationale for Digital Public Infrastructure for Health (DPI-H) and effectively…The guidance provides a strong strategic rationale for Digital Public Infrastructure for Health (DPI-H) and effectively links health outcomes with digital architecture. However, the overall document length and technical depth may limit accessibility for senior decision-makers. Suggested revision: Develop a concise executive companion document summarizing key messages, governance requirements, implementation priorities, expected benefits and investment implications. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-0080✎ edit📣 feedback | received | general | Editorial ai |
How to use this guidance §Audience and Scope p.Global l.Audience Definition anchor: medium |
The intended audience is broad and diverse. Stakeholder-specific needs could be more clearly differentiated.The intended audience is broad and diverse. Stakeholder-specific needs could be more clearly differentiated. Suggested revision: Provide role-based reading pathways and stakeholder-specific guidance. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-004 #21 | in the document all mentions on GitHub record | |
| PC-0081✎ edit📣 feedback | received | technical | Core architects ai |
1.2 Why health needs more than foundational DPI §DPI-F and DPI-H Distinction p.Relevant Section l.Relevant Lines anchor: medium |
The distinction is useful and well reasoned but would benefit from practical examples.The distinction is useful and well reasoned but would benefit from practical examples. Suggested revision: Add country examples illustrating health-specific requirements such as consent, longitudinal records and surveillance. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-011 discuss | in the document all mentions on GitHub record | |
| PC-0082✎ edit📣 feedback | received | technical | Core architects ai |
2.2 Resilient Essential Data and Digital Health Infrastructure (REDDHI) §REDDHI Framework p.Relevant Section l.Relevant Lines |
REDDHI is a strong organizing concept but may appear ambitious for some LMICs.REDDHI is a strong organizing concept but may appear ambitious for some LMICs. Suggested revision: Introduce foundational, intermediate and advanced maturity levels. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | |
| PC-0083✎ edit📣 feedback | received | technical | Core architects ai |
3.5.3 How the components are organised §Architecture Layers p.Relevant Section l.Figure/Diagram anchor: low |
Relationships between foundational registries and business services are not immediately apparent to non-specialists.Relationships between foundational registries and business services are not immediately apparent to non-specialists. Suggested revision: Include simplified workflow diagrams. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-004 #21 | in the document all mentions on GitHub record | |
| PC-0084✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §Semantic Governance Infrastructure p.Relevant Section l.Relevant Lines anchor: low |
SGI addresses a critical interoperability challenge but implementation arrangements need clarification.SGI addresses a critical interoperability challenge but implementation arrangements need clarification. Suggested revision: Provide governance models, institutional responsibilities and implementation examples. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | |
| PC-0085✎ edit📣 feedback | received | technical | Metadata registries ai |
Metadata registries and foundational components §Terminology Services and LIMR p.Relevant Section l.Relevant Lines anchor: low |
Additional operational guidance is needed.Additional operational guidance is needed. Suggested revision: Include governance structures, workforce requirements, costs and sustainability guidance. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-0086✎ edit📣 feedback | received | technical | Core architects ai |
3.6 Interoperability Architecture within DPI-H §Interoperability p.Relevant Section l.Relevant Lines anchor: medium |
A strong cross-cutting approach but procurement risks remain.A strong cross-cutting approach but procurement risks remain. Suggested revision: Add procurement guidance and implementation anti-patterns. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-260 discuss | in the document all mentions on GitHub record | |
| PC-0087✎ edit📣 feedback | received | technical | Core architects ai |
3.7 Conformance and Testing across Architecture and Components §Conformance and Testing p.Relevant Section l.Relevant Lines anchor: medium |
LMIC implementation capacity may be limited.LMIC implementation capacity may be limited. Suggested revision: Introduce staged conformance levels and regional test services. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-246 discuss | in the document all mentions on GitHub record | |
| PC-0088✎ edit📣 feedback | received | general | Core architects ai |
4.3.4 Interoperability Implementation Pathways §Implementation Pathways p.Relevant Section l.Relevant Lines anchor: medium |
Further practical detail is required for fragmented ecosystems.Further practical detail is required for fragmented ecosystems. Suggested revision: Include migration strategies and implementation playbooks. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-099 discuss | in the document all mentions on GitHub record | |
| PC-0089✎ edit📣 feedback | received | general | Financial systems ai |
4.6.1 The Investment Case §Financing and Sustainability p.Relevant Section l.Relevant Lines anchor: medium |
Investment case would benefit from further evidence.Investment case would benefit from further evidence. Suggested revision: Provide business cases and indicative costing models. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0090✎ edit📣 feedback | received | general | Core architects ai |
4.5 Roles, Skills, and Capacity §Workforce Capacity p.Relevant Section l.Relevant Lines anchor: medium |
Specialist skills are scarce in many countries.Specialist skills are scarce in many countries. Suggested revision: Include competency frameworks and regional support models. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-107 discuss | in the document all mentions on GitHub record | |
| PC-0091✎ edit📣 feedback | received | general | Core architects ai |
unplaced §Applicability and Equity p.Relevant Section l.Relevant Lines |
Guidance for fragile settings could be expanded.Guidance for fragile settings could be expanded. Suggested revision: Add considerations for low-connectivity and humanitarian settings. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-239 discuss | all mentions on GitHub record | |
| PC-0092✎ edit📣 feedback | received | general | Editorial ai |
D.3 Regional and multi-country examples §Country Examples p.Relevant Section l.Relevant Lines anchor: medium |
More LMIC examples would improve relevance.More LMIC examples would improve relevance. Suggested revision: Include examples from Pakistan, Bangladesh, Ethiopia and Sierra Leone. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0093✎ edit📣 feedback | received | editorial | Editorial ai |
unplaced §Language and Accessibility p.Relevant Section l.Relevant Lines |
Technical language may be difficult for non-specialists.Technical language may be difficult for non-specialists. Suggested revision: Add plain-language summaries and glossaries. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-284 discuss | all mentions on GitHub record | |
| PC-0094✎ edit📣 feedback | received | technical | Core architects ai |
Future proofing the Architecture §Emerging Technologies and AI p.Relevant Section l.Relevant Lines |
AI enablement pathways require further elaboration.AI enablement pathways require further elaboration. Suggested revision: Add an AI and Epidemiological Intelligence Readiness Framework linked to REDDHI, LIMR, SGI, HMIS and PHSP. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | |
| PC-0095✎ edit📣 feedback | received | technical | Metadata registries ai |
5.2 Why data foundations determine what AI can deliver §LIMR and AI Maturity p.Relevant Section l.Relevant Lines anchor: medium |
LIMR as a prerequisite for trustworthy AI is underemphasized.LIMR as a prerequisite for trustworthy AI is underemphasized. Suggested revision: Position LIMR as the structural foundation for AI readiness and scalability. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-119 discuss | in the document all mentions on GitHub record | |
| PC-0096✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §SGI and Clinical AI Governance p.Relevant Section l.Relevant Lines anchor: low |
The relationship between SGI and clinical AI is not fully explained.The relationship between SGI and clinical AI is not fully explained. Suggested revision: Include governance schematics linking SGI, LIMR, CDSE and AI systems. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | |
| PC-0097✎ edit📣 feedback | received | technical | Core architects ai |
unplaced §Epidemiological Intelligence Maturity p.Relevant Section l.Relevant Lines |
Countries need guidance on sequencing epidemiological intelligence investments.Countries need guidance on sequencing epidemiological intelligence investments. Suggested revision: Add maturity stages from surveillance to predictive epidemiology and learning health systems. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-246 discuss | all mentions on GitHub record | |
| PC-0098✎ edit📣 feedback | received | general | Core architects ai |
5.4.1 What AI readiness means §Country AI and Public Health Readiness p.Relevant Section l.Relevant Lines anchor: medium |
AI investments should follow digital health maturity.AI investments should follow digital health maturity. Suggested revision: Provide a country-level AI maturity roadmap. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | |
| PC-0099✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §Human-Centred AI Governance p.Relevant Section l.Relevant Lines anchor: medium |
Human oversight principles are insufficiently articulated.Human oversight principles are insufficiently articulated. Suggested revision: Introduce Human-in-the-Loop governance ensuring AI augments rather than replaces decision makers. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0100✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §Trustworthy and Ethical AI p.Relevant Section l.Relevant Lines |
Operational responsible AI guidance is limited.Operational responsible AI guidance is limited. Suggested revision: Add a responsible AI framework covering fairness, safety, transparency and accountability. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0101✎ edit📣 feedback | received | technical | Core architects ai |
5.4.3 Equity and safety §AI Equity and Bias Surveillance p.Relevant Section l.Relevant Lines anchor: medium |
Algorithmic bias risks are not sufficiently addressed.Algorithmic bias risks are not sufficiently addressed. Suggested revision: Require representative datasets, fairness audits, subgroup performance monitoring and bias surveillance. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-124 discuss | in the document all mentions on GitHub record | |
| PC-0102✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §Explainability and AI Lifecycle Governance p.Relevant Section l.Relevant Lines anchor: medium |
Explainability and lifecycle governance require stronger treatment.Explainability and lifecycle governance require stronger treatment. Suggested revision: Require rationale, confidence levels, evidence references, audit trails and SGI-supported model governance. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0103✎ edit📣 feedback | received | general | Core architects ai |
unplaced §Integrated Maturity Framework p.Relevant Section l.Relevant Lines |
Multiple maturity concepts are presented but not integrated.Multiple maturity concepts are presented but not integrated. Suggested revision: Develop a consolidated framework linking REDDHI, interoperability, SGI, SMART Guidelines, epidemiological intelligence and AI maturity. Dr. Yahya Gulzar, WHO, Pakistan |
none | not yet | CS-246 discuss | all mentions on GitHub record | |
| PC-0104✎ edit📣 feedback | received | general | Core architects ai |
3.7.5 Validating goals and adoption §3.7.5 Validating goals and adoption p.85 l.1195-1231 |
Core mechanism terms (realisation relationship, Application Component level, Association, Specialisation) are used with…Core mechanism terms (realisation relationship, Application Component level, Association, Specialisation) are used without definition and assume familiarity with a specific EA modelling notation Suggested revision: Give worked example ties any of this to an actual health-system component. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | |
| PC-0105✎ edit📣 feedback | received | editorial | Editorial ai |
3.7.5 Validating goals and adoption §3.7.5 Validating goals and adoption p.85 l.1196–1231 |
"Adoption" is used both as the overarching concept being measured (subsection heading; line 1225 "Adoption is thereby q…"Adoption" is used both as the overarching concept being measured (subsection heading; line 1225 "Adoption is thereby quantifiable") and as one of the three specific alignment pathways (line 1204), creating ambiguity as to which sense applies where. Suggested revision: Add a one-sentence inline definition of "realisation relationship" on first use, and a page cross-reference for "Conformance at the Application Component level." Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | |
| PC-0106✎ edit📣 feedback | received | technical | Core architects ai |
3.7.5 Validating goals and adoption §3.7.5 Validating goals and adoption p.85 l.1196–1231 |
No worked example illustrates the difference between adoption, adaptation, and mapping using an actual health-system co…No worked example illustrates the difference between adoption, adaptation, and mapping using an actual health-system component, making the distinctions hard to apply in practice. A Ministry of Health official reading this will not know what action to take Suggested revision: Add a short worked example, e.g. contrasting a national patient registry that realises the reference "Patient Identity Resolution" component under each of the three pathways. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | |
| PC-0107✎ edit📣 feedback | received | technical | Core architects ai |
3.7.5 Validating goals and adoption §3.7.5 Validating goals and adoption p.85 l.1196–1231 |
The phrase "fall out mechanically" is misleading and overconfident. In practice, determining whether a country element …The phrase "fall out mechanically" is misleading and overconfident. In practice, determining whether a country element "realises" a reference element requires expert judgment, not mechanical computation. The bullet list describes an idealized process but provides no guidance on who performs the assessment, what tools they use, or how disputes are resolved when a vendor claims conformance but the MOH disagrees. The inheritance of "Requirements, Constraints, and conformance expectations" is also unexplained — where do these inherited criteria come from? How are they documented? How does a country test them if they lack testing infrastructure? Suggested revision: Add Appendix X: Architecture Mapping Template Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | |
| PC-0108✎ edit📣 feedback | received | technical | Core architects ai |
3.3 The reference architecture in practice §3.3 The reference architecture in practice p.50-52 l.172-192, Figure 3.3-3.5 |
Figure 3.3-3.5 uses ArchiMate colours to layer the sub-goal and outcome, capabilities and services, and metadata compon…Figure 3.3-3.5 uses ArchiMate colours to layer the sub-goal and outcome, capabilities and services, and metadata components for the "Establish Trusted Personal Health Records" sub-goal, but the colour coding does not visually distinguish DPI-F, DPI-H, and functional application elements from one another elsewhere in the document these three are referred to by different names/labels, so the same or similar colours mapping to inconsistently-named categories makes the layering hard to interpret correctly. Suggested revision: Assign DPI-F, DPI-H, and functional applications distinct, consistently-applied colours in Figure, with a legend that cross-references the terminology used for each category elsewhere in the document, so the colour-to-term mapping is unambiguous throughout. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | |
| PC-0109✎ edit📣 feedback | received | editorial | Editorial ai |
3.3 The reference architecture in practice §3.3 The reference architecture in practice p.50 l.172, Figure 3.3 |
"PKI" and "Trust Architecture" are used inconsistently, with what appears to be duplicate labelling for the same elemen…"PKI" and "Trust Architecture" are used inconsistently, with what appears to be duplicate labelling for the same element; PKI is also treated as synonymous with trust architecture, though PKI is only one possible implementation and does not represent every trust architecture a country may use. Suggested revision: Standardise on a single term throughout either use "PKI" specifically where PKI is meant, or use the broader "Trust Architecture" where the concept is generic and remove the duplicate labelling in Figure 3.3. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | |
| PC-0110✎ edit📣 feedback | received | editorial | Editorial ai |
3.3 The reference architecture in practice §3.3 The reference architecture in practice p.50-52 l.172-192, Figure 3.3-3.5 |
"Terminology service" and "terminology server" are used inconsistently, apparently referring to the same element, simil…"Terminology service" and "terminology server" are used inconsistently, apparently referring to the same element, similar to the PKI/Trust Architecture issue above. Suggested revision: Standardise on a single term throughout "service" if referring to the functional/architectural role, or "server" if referring to the specific technical implementation and apply consistently across all figures and text. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | |
| PC-0111✎ edit📣 feedback | received | technical | Core architects ai |
3.4.3 Strategic governance §3.4 Governance of Digital Health Architectures and DPI-H p.55-60 l.290-451 |
The document never explicitly resolves where the Semantic Governance Infrastructure (SGI) sits in the governance hierar…The document never explicitly resolves where the Semantic Governance Infrastructure (SGI) sits in the governance hierarchy. Section 3.4.3 says strategic governance "does not manage operations; it creates the mandate" (lines 293–294). Section 3.4.4 says operational governance includes "interoperability and semantic governance… through the Semantic Governance Infrastructure described in 3.4.5" (lines 355–358), which places SGI under operational governance. But Section 3.4.5 then describes SGI as "cross-cutting" and "not a component of any single registry" (lines 414–416) whose scope spans "global, national and local content" (lines 412–413) — work that sounds strategic (national standards alignment, clinical reality reflection). The reader is left uncertain: Is SGI an operational function executing strategic policy? A strategic function with operational mechanics? Or a third layer between the two? Suggested revision: State explicitly in 3.4.5 whether SGI decisions route through operational governance alone, strategic governance alone, or both depending on decision type, and adjust the 3.4.4 bullet to reflect that SGI is not solely an operational output. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | |
| PC-0112✎ edit📣 feedback | received | technical | Core architects ai |
3.4.3 Strategic governance §3.4 Governance of Digital Health Architectures and DPI-H p.55-60 l.290-451 |
Line 293 states strategic governance "does not manage operations," but the "Securing financial continuity" and "Managin…Line 293 states strategic governance "does not manage operations," but the "Securing financial continuity" and "Managing demand on shared capacity" subsections assign it operational-sounding actions (monitor utilisation against capacity, adjust fee structures, monitoring and reporting of utilisation patterns), contradicting the stated separation. Suggested revision: Reframe these actions as strategic-level authority exercised on operationally-supplied data or explicitly note that strategic bodies set the parameters that operational governance then applies. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-044 discuss | in the document all mentions on GitHub record | |
| PC-0113✎ edit📣 feedback | received | technical | Core architects ai |
3.4.3 Strategic governance §3.4 Governance of Digital Health Architectures and DPI-H p.55-60 l.290-451 |
The governance/runtime/content three-layer model introduced here is not cross-referenced to the strategic/operational g…The governance/runtime/content three-layer model introduced here is not cross-referenced to the strategic/operational governance split from 3.4.3–3.4.4, nor to the escalation pathway defined in 3.4.4 (363–372), leaving unclear which body decides major semantic changes versus routine terminology curation. Suggested revision: Add a sentence mapping the "governance layer" to strategic and/or operational governance (e.g. "routine content review sits within operational governance; changes that expand SGI's scope or affect multiple registries escalate to strategic governance per 3.4.4"). Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | |
| PC-0114✎ edit📣 feedback | received | editorial | Core architects ai |
3.4.3 Strategic governance §3.4 Governance of Digital Health Architectures and DPI-H p.55-60 l.290-451 |
The three-layer model (governance layer, runtime layer, content/application layer) introduced in lines 419–431 is edito…The three-layer model (governance layer, runtime layer, content/application layer) introduced in lines 419–431 is editorially confusing because it does not map to the document's overall architecture framework. Earlier sections presumably describe the architecture using a component model (client registry, terminology service, etc.) or a layered model (business, data, application, technology — per TOGAF or OpenHIE). Now a new "three layers" model appears without explaining how it relates to those existing layers. Is the governance layer part of the business architecture? Is the runtime layer the technology architecture? Is SGI an application component or a cross-cutting concern? Suggested revision: Add an explicit mapping paragraph after line 431: "These three layers can be understood in relation to the architecture framework used throughout this document as follows: The governance layer corresponds to the business architecture processes and the governance structures defined in Sections 3.4.3 and 3.4.4. The runtime layer corresponds to the application and technology architecture components — specifically the Terminology Service, Logical Information Model Repository, and their underlying infrastructure (Section [X.X]). The content and application layer corresponds to the business use cases and the consuming applications that implement them. SGI spans the governance and runtime layers: it is a business process (governance) that operates on application components (runtime) and is triggered by content layer feedback." Then add a figure showing the three SGI layers mapped to the document's primary architecture framework. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | |
| PC-0115✎ edit📣 feedback | received | editorial | Editorial ai |
3.4.6 Regional governance considerations §3.4.6 Regional governance considerations p.62-63 l.495-516 |
The term "layered" is reused here for regional-vs-national governance ("Layered governance," 511) after 3.4.5 already e…The term "layered" is reused here for regional-vs-national governance ("Layered governance," 511) after 3.4.5 already established "layers" to mean governance/runtime/content (419–431). The same word now denotes two unrelated structures within a few pages of each other. Suggested revision: Use a distinct term for the regional/national split (e.g. "tiered governance" or "governance scope split") to avoid conflating it with the governance/runtime/content layering in 3.4.5. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | |
| PC-0116✎ edit📣 feedback | received | technical | Core architects ai |
3.4.6 Regional governance considerations §3.4.6 Regional governance considerations p.62-63 l.495-516 |
The section defines a regional strategic governance body but does not address whether a regional operational governance…The section defines a regional strategic governance body but does not address whether a regional operational governance function exists or is expected for shared components (e.g. who performs release management or service-level monitoring for infrastructure shared across countries). This mirrors the operational/strategic split established in 3.4.3–3.4.4 for the national level but leaves the regional level only half-specified. Suggested revision: Either state explicitly that regional operational governance is out of scope and remains nationally delegated per component, or add a short subsection defining a regional operational governance function analogous to 3.4.4. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-053 discuss | in the document all mentions on GitHub record | |
| PC-0117✎ edit📣 feedback | received | technical | Core architects ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 The foundational shared data layer p.67 l.638-667 |
The four registries are each defined as "the authoritative [index / list / record / source] of/for..." with a different…The four registries are each defined as "the authoritative [index / list / record / source] of/for..." with a different noun for each, and the document never states whether this variation reflects a deliberate architectural distinction (e.g. pointer-based index vs. full attribute record) or is incidental word choice. Suggested revision: Either (a) standardise on one term (e.g. "authoritative source of record") across all four registries if no distinction is intended, or (b) if the distinction is deliberate, add a sentence stating so explicitly and briefly defining what "index" vs "list" vs "record" vs "source" imply for that registry's data model. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-051 discuss | in the document all mentions on GitHub record | |
| PC-0118✎ edit📣 feedback | received | editorial | Editorial ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 The foundational shared data layer p.67 l.638-667 |
The Lifelong Health Record entry breaks the "authoritative [noun] of/for" pattern used by the preceding four registries…The Lifelong Health Record entry breaks the "authoritative [noun] of/for" pattern used by the preceding four registries, instead describing itself as a "governed, person-centred capability" — plausibly intentional given its centralised/federated/hybrid flexibility (649–650), but this rationale is not stated. The clause also contains an apparent text artifact ("...central store. person-centred that") that reads as duplicated/incomplete. Suggested revision: Add a brief clause explaining why the Lifelong Health Record is defined differently from the other four (e.g. "unlike the registries above, it is defined as a capability rather than a single store, because implementation may be centralised, federated, or hybrid"); remove or complete the stray "person-centred that" fragment. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | |
| PC-0119✎ edit📣 feedback | received | editorial | Editorial ai |
4.2.1 Different Entry Points toward REDDHI §4.2.1 Different Entry Points toward REDDHI p.89-90 l.71-80 |
"The REDDHI minimum viable layer" is introduced without definition or a cross-reference to where it is specified, leavi…"The REDDHI minimum viable layer" is introduced without definition or a cross-reference to where it is specified, leaving a reader at Entry Point 1 unable to determine what this layer comprises. Suggested revision: Add a cross-reference to the section defining the minimum viable layer, or a one-clause description on first use. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-246 discuss | in the document all mentions on GitHub record | |
| PC-0120✎ edit📣 feedback | received | general | Financial systems ai |
4.6.3 Approaches to Financing §4.6 Financing and Partnerships p.92-93 l.547-600 anchor: medium |
4.6.3 addresses financing sources only and contains no underlying cost structure. DIIG in costing section warning — tha…4.6.3 addresses financing sources only and contains no underlying cost structure. DIIG in costing section warning — that budgets "frequently underestimated" because they focus on demonstration/deployment costs and omit long-term O&M — is exactly the risk a "Sustain and evolve" / recurrent-financing section should be guarding against, but 4.6.3 never uses the concept or term, and never warns against front-loaded budgeting. Suggested revision: Add a short introductory paragraph whether this part complement WHO Digital Implementation Investment Guide, which part may be referred to that guide, and which is not part of the DPI-H Reference Architecture Guidance Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0121✎ edit📣 feedback | received | general | WHO ai |
Executive Summary §1. Executive summary p.1 l.39-55 |
Beyond the single introductory claim about the DHP Handbook and one reference to WHO DIIG (4.2.2, line 124–125), the do…Beyond the single introductory claim about the DHP Handbook and one reference to WHO DIIG (4.2.2, line 124–125), the document does not reference other relevant WHO digital health guidance — the Global Digital Health Monitor (GDHM), WHO SMART Guidelines — at any point reviewed, despite these being directly relevant comparator or complementary frameworks (GDHM in particular was already found to differ from REDDHI in indicator wording, making an explicit comparison valuable rather than optional). Suggested revision: Add a short "Related WHO guidance" cross-reference at the start of major sections (or a consolidated subsection early in the document) mapping REDDHI/DPI-H concepts to GDHM indicators, SMART Guidelines components, DIIG costing stages, and DHP Handbook concepts, with specific section numbers in each case. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-002 discuss | in the document all mentions on GitHub record | |
| PC-0122✎ edit📣 feedback | received | general | Clinical ai |
4.1.2 Assessing Where You Are §4.1.2 Assessing Where You Are p.89 l.49-54 |
Sections describing clinical content, service delivery, or point-of-care guidance do not reference WHO SMART Guidelines…Sections describing clinical content, service delivery, or point-of-care guidance do not reference WHO SMART Guidelines, despite SMART Guidelines being the mechanism for computable clinical guidance and a natural point of alignment with REDDHI's business services layer. Suggested revision: Add explicit cross-references to WHO SMART Guidelines wherever REDDHI's business services layer (clinical decision support, etc.) or Services and Applications domain is discussed, specifying how SMART Guidelines content is intended to be consumed within the DPI-H architecture. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | |
| PC-0123✎ edit📣 feedback | received | technical | Core architects ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 What REDDHI is and its foundational core p.28 l.141, Table 2.2. |
The "Foundational capability" table title implies comprehensive coverage of REDDHI's foundation, but every row and comp…The "Foundational capability" table title implies comprehensive coverage of REDDHI's foundation, but every row and component listed is technical infrastructure. The ongoing REDDHI readiness index by HQ/MIS treats financing/sustainability and data analytics (including workforce and institutional capacity) as equally foundational, with neither represented in this table. Suggested revision: Not sure, maybe retitle the table to specify its technical scope, and add a cross-reference noting that financing and institutional/workforce readiness are addressed separately (e.g. via the readiness index. Or align with HQ/MIS on REDDHI Readiness Index. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | |
| PC-0124✎ edit📣 feedback | received | editorial | Editorial ai |
3.4.3 Strategic governance §3.4 Governance of Digital Health Architectures and DPI-H p.55-60 l.290-451 |
Governance (3.4), particularly 3.4.5 Semantic Governance Infrastructure, discusses governing the Terminology Service an…Governance (3.4), particularly 3.4.5 Semantic Governance Infrastructure, discusses governing the Terminology Service and LIMR before these components are formally introduced in 3.5.3.1 (p.67), forcing forward references throughout 3.4. Suggested revision: Reorder Chapter 3 so DPI-H Application Components (3.5) and Interoperability Architecture (3.6) precede Governance (3.4); alternatively, add explicit forward-reference notes in 3.4.5 pointing to 3.5.3.1. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-052 discuss | in the document all mentions on GitHub record | |
| PC-0125✎ edit📣 feedback | received | editorial | Editorial ai |
4.2.4 The Role of the National Digital Architect §4.2.4 The Role of the National Digital Architect p.93 l.226 anchor: medium |
"The Role of the National Digital Architect" (4.2.4) is separated by two sections (4.3, 4.4) from "Roles, Skills, and C…"The Role of the National Digital Architect" (4.2.4) is separated by two sections (4.3, 4.4) from "Roles, Skills, and Capacity" (4.5), which covers closely related content ("Roles and Skills Needed to Build and Govern the Architecture," 4.5.2). Suggested revision: Consolidate role-related content into 4.5, or add explicit cross-references between 4.2.4 and 4.5.2. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | |
| PC-0126✎ edit📣 feedback | received | editorial | Editorial ai |
3.6.5 Conformance §3.7 Conformance and Testing across Architecture 963 and Components p.78 l.964 anchor: medium |
3.7 subsections (in particular 3.7.3 Alignment with IHE profiles and 3.7.5 Validating goals and adoption) depend on con…3.7 subsections (in particular 3.7.3 Alignment with IHE profiles and 3.7.5 Validating goals and adoption) depend on concepts introduced both in Chapter 2.4 (methodology, ~40 pages earlier) and in 3.5–3.6 (components/interoperability, just prior), requiring the reader to hold references across widely separated parts of the document within a single section. Suggested revision: Add a short recap paragraph at the start of 3.7 restating the key 2.4 and 3.5/3.6 concepts it depends on, so the section is more self-contained on a linear read. Diana Wijayanti, WHO, HQ / Indonesia |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | |
| PC-0127✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.no page l.3-4 anchor: medium |
Should add some details to represent healthcareShould add some details to represent healthcare Suggested revision: Instead, they should build shared data and digital capabilities that support multiple health programmes, multiple diseases at multiple levels of care Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0128✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.no page l.9-12 anchor: medium |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: Different from the fundamental digital public infrastructure, including identity, payments and data interchange, which the health sector can build upon, the DPI-H refers to digital resources created as a shared means for carrying out various health agency functions. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0129✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.no page l.17 anchor: medium |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: Interoperability as a cross-cutting architectural feature Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0130✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.no page l.18 anchor: medium |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: The establishment of common standards/grounds for health digital public infrastructure (DPI-H) Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0131✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.no page l.19 anchor: medium |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: These, in turn, serve as crucial pillars for "AI-ready data" and "AI for health". Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0132✎ edit📣 feedback | received | technical | Editorial ai |
Executive Summary §Executive summary p.1 l.53-55 |
to relate on the cost of investmentto relate on the cost of investment Suggested revision: With both references, countries can move from strategic decision making to technical implementation with confidence that their architectural choices support long-term health sector goals leveraging their investments. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0133✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.1 l.56-57 |
correcting the context of sentencescorrecting the context of sentences Suggested revision: Figure 1: The Reference Architecture for planning and implementing a digital health enterprise Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-003 discuss | in the document all mentions on GitHub record | |
| PC-0134✎ edit📣 feedback | received | technical | Editorial ai |
Executive Summary §Executive summary p.1 l.58 anchor: medium |
correcting the context of sentences for phase 1 stepscorrecting the context of sentences for phase 1 steps Suggested revision: Conduct an inventory of existing or previously used software applications, ICT systems and other infrastructures to better understand the requirements for reuse and interoperability. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-003 discuss | in the document all mentions on GitHub record | |
| PC-0135✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.2 l.60-65 |
correcting the context of sentencescorrecting the context of sentences Suggested revision: It explains how an intentional governance infrastructure maintains the shared meaning of data over time, how interoperabilitty is realised as a cross-cutting feature of the architecture rather than a single component, how nations can approach compliance, coverage and progress, the roles and skills needed and the financing and partnership arrangements that make DPI-H sustainable. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0136✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.2 l.65-67 |
correcting the context of sentencescorrecting the context of sentences Suggested revision: Artificial intelligence is positioned as a cross-cutting factor that relies on and points out the significance of the reliable, well-governed data foundations the system creates when emergent technologies are specifically incorporated. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0137✎ edit📣 feedback | received | technical | Editorial ai |
Executive Summary §Executive summary p.2 l.78 |
Did not define DPI-F in previous paragraphsDid not define DPI-F in previous paragraphs Suggested revision: define F Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0138✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.2 l.81 |
The sentence is incompleteThe sentence is incomplete Suggested revision: Outlining the precise health needs that fundamental DPI would have to meet Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0139✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.2 l.97-99 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: A testable architecture that allows adherence to the reference to be verified against public profiles rather than only described. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0140✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary p.3 l.100-102 anchor: medium |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: When combined, these contributions provide nations with an organised framework and a common terminology that they can use and modify to fit their particular situation. Regardless of where they begin, they may move from strategic purpose to cohesive, standards-based technical execution. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0141✎ edit📣 feedback | received | editorial | Editorial ai |
How to use this guidance §How to use the guidance p.4 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: This guidance is organised in a manner that allows individual readers to avoid reading through the entire document. The cards below outline the primary benefits for each user group and provide an approximate page count for that essential pathway. The subsequent matrix delineates, by section, what is fundamental, beneficial or flexible for you. Locate your column and trace it downward through the table. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-004 #21 | in the document all mentions on GitHub record | |
| PC-0142✎ edit📣 feedback | received | editorial | Editorial ai |
1.1 About the Reference Architecture for health Digital Public Infrastructure (DPI-H) Guidance §1.1 p.8 l.4-11 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: The majority of countries are not beginning from scratch : by 2025, 129 countries had established national digital health strategies in accordance with universal health coverage and the Sustainable Development Goals. However, the execution frequently stays scattered, as nations lack a methodical approach to transition from broad health objectives to solid infrasructure choices. The WHO's Global Startegy on Digital Health 2020-2027 urges Member States to establish digital health frameworks employing enterprise architecture methodologies, however, detailed guidance tailored to individual needs of countries has been mostly absent until recently. This directive addresses the gap. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0143✎ edit📣 feedback | received | editorial | Editorial ai |
1.1 About the Reference Architecture for health Digital Public Infrastructure (DPI-H) Guidance §1.1 p.8 l.2-3 anchor: medium |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: Adressing the Referance Architecture for Health Digital Public Infrastructure (DPI-H) Guidance Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0144✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.1 What is a reference architecture, and why does it matter for the health sector? §1.1.1 p.8 l.12-13 anchor: medium |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: What is referance architecture and why is it important in health sector? Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0145✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.1 What is a reference architecture, and why does it matter for the health sector? §1.1.1 p.8 l.14-25 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: A referance architecture serves as a technology-independent framework that delineates the fundamental components, interconnections and design principles of technical ecosystem, enabling organisations to avoid beginning from scratch. Utilising recognised enterprise architectural methodologies, it acts as a definitive referance that directs the creation of more tailored architectures and solutions, while providing an organised framework of reusable components. Its significance resides in providing various stakeholders with a unified framework - a collective terminology and organisational structure that harmonises decisions, minimises redundancy and facilitates the integration and sustainability of application components. In the context of health, where services are provided through numerous programs, institutions and tiers of care, this holds particular significance. A reference architecture offers nations a unified method to convert broad health policy objectives into digital frameworks taht are interoperable, manageable, and tailored to their specific circumstances. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0146✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §1.1.2 p.9 l.42-55 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: The G20 characterised DPI as a collection of collaborative digital infrastructures that must be secure and interoperable, constructed on open standards and specifications to ensure equitable access to public and/or private services at a societal level, governed by relevant legal frameworks and enabling regulations to promote development, inclusion, innovation, trust and competition, while upholding human rights and fundamental freedoms. Collectively, these criteria delineate essential attributes of DPI: it functions as a communal infrastructure at a society level, and its value arises not from an individual system but from its open, interoperable basis that enables both public and private entities to innovate. The G20 acknowledges that Digital Public Infrastructure (DPI) is a dynamic notion, not confined to systems with particular features, and may be customised to fit the unique situations of many nations, often referred to by diverse terminology. This establishes the foundation for expressing a health-centric interpretation of DPI, tailored to the requirements of the health sector while aligning with the broad agreement. This health-specific digital public infrastructure is derived from a comprehensive cross-sectoral understanding. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0147✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §1.1.2 p.10 l.62-71 |
The first aspect is focused on collective resources. DPI-H is not a compilation of specialised tools or service-specifi…The first aspect is focused on collective resources. DPI-H is not a compilation of specialised tools or service-specific apps; rather, it is an infrastructure that is communal, reusable and accessible to all stakeholders in the health system, eliminating the need for each to develop comparable capablilities independently. The second pertains to the connection between DPI-H and fundamental DPI. DPI-H does not aim to duplicate the offerings of foundational DPI; instead, it enhances and supplements them with the specialised funstionalities necessary for the health sector that general-purpose DPI cannot fulfil. Where basic DPI is present and available, DPI-H expands upon it. In instances where it falls short, DPI-H delivers the crucial functionalities required for the health system to operate, while maintaining an architechturally flexible framework for integration as the larger digital ecosystem evolves. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0148✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.10 l.87-90 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: The reference architecture guidance is geared to the evolution of national digital ecosystems, emphasising that health is a sector utilising shared Digital Public Infrastructure (DPI) instead of developing separate systems solely for health, thereby enhancing the understanding of the integration of health-specific DPI (DPI-H) with wider DPI. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0149✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.10 l.92-93 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: While the DHP Handbook and OpenHIE Architecture do not explicitly mention the DPI idea, the core issues these materials aimed to tackle persist unchanged. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0150✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.10 l.98 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: Requirement for reusable elements and communal infrastructure. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0151✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.10 l.99 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: Significance of bypassing vendor lock-in Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0152✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.10 l.100-101 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: Concerns regarding sustainability arise with vertical strategies - independent systems designed for a specific program or disease domain, which replicate efforts and incur high maintenance costs. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0153✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.11 l.102 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: DPI has shown influence in nations and stimulated ecosystem innovation across various sectors. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0154✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.11 l.103-106 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: Fundamental Digital Public Infrastructure for identification, data interchange and electronic transactions are illustrated by India's Aadhaar digital identity system, Brazil's Pix instant payment platform and Estonia's X-Road data exchange framework, has demonstrated significant value as a communal resource that can be utilised across several industries. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0155✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.11 l.115-120 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: The health sector however, although not being unique in its ability to leverage fundamental DPI, exhibits some unique requirements that have not yet been stated to enable it to properly apply these foundational components. This guidance articulates the precise health-sector standards that foundational DPIs would need to satisfy in order to contribute to health sector goals. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0156✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.3 Building on existing foundations §1.1.3 p.12 l.130-135 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: This guidance results from a comprehensive collaborative effort that incorcoprates the experiences, knowledge and insights of a varied international group of professionals. It encapsulates input from digital health designers, clinical informatics professionals, health financing authorities, supply chain specialists, national implementers and development collaborators from low, middle and high-income nations across various regions - guaranteeing that the framework it delineates is rooted in practical implementation rather than theoretical concepts. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0157✎ edit📣 feedback | received | editorial | Editorial ai |
1.1.4 Who can benefit from this guidance? §1.1.4 p.12 l.161-163 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: The referance architecture delineates standard specifications and compliance criteria that facilitate transparent procurement, vendor fairness and informed assessment of solutions. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | |
| PC-0158✎ edit📣 feedback | received | editorial | Editorial ai |
1.2.1 Identity DPI and Identification in Healthcare §1.2 p.13 l.176-1781 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: This is excellent guidance where basic DPIs exist, are thrustworthy and are accessible and the health industry should build on them wherever it can. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-010 discuss | in the document all mentions on GitHub record | |
| PC-0159✎ edit📣 feedback | received | editorial | Editorial ai |
1.2.1 Identity DPI and Identification in Healthcare §1.2.1 p.13 l.197-199 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: A national ID system identifies who a person is, but health demands knowing what a person is entitled for, what treatments they are receiving, what prescriptions have been prescribed and whether they have consented to share certain data with specified parties. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-010 discuss | in the document all mentions on GitHub record | |
| PC-0160✎ edit📣 feedback | received | editorial | Editorial ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27 l.120-123 |
rephrasing to make the statement easy to understandrephrasing to make the statement easy to understand Suggested revision: These registries are mutually reliant : a longitudinal record lacks value without the capability to determine the origin and author of each entry, thus the facility and health workforce registries enable the verification of record suthenticity, while the client registry ensures accurate attribution to the correct individual. Dhaniah binti Abd Salam, Hospital Sungai Buloh, Malaysia |
none | not yet | CS-027 discuss | in the document all mentions on GitHub record | |
| PC-0161✎ edit📣 feedback | received | general | Core architects ai |
unplaced §Whole document p.— l.General comment (no specific lines) |
This joint submission synthesises two critical reviews written independently and without sight of each other (a semanti…This joint submission synthesises two critical reviews written independently and without sight of each other (a semantics-and-standards review and an integrated-care review; their convergence is documented in a separate comparison). Both commend the same strengths: the Semantic Governance Infrastructure (meaning as a permanently governed asset — institutions first, tools second); the outcome-defined Lifelong Health Record; the draft's realism (no country starts from zero; conformance as a graded model); and Chapter 5's sober treatment of AI. Both also identify the same missing piece: the draft's own definition of interoperability ends with 'use the exchanged information to execute functions effectively', yet nowhere is that effective use designed, supported or measured. Conformance verifies systems and transactions, never whether the receiving human understood the information and acted appropriately (the 'last mile'). Likewise 'capture once, use many times' silently assumes reuse is free, while in practice information must be transformed to each receiver's role and context ('informational metamorphosis') — a transformation that is neither designed nor governed. Comments 2–15 below make this actionable; that two unconnected critiques converge on the same point is itself evidence the gap is real. Suggested revision: Extend the draft's own logic — govern meaning, define by outcome, verify by testing — to the point of action, per the specific proposals in comments 2–15. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-263 discuss | all mentions on GitHub record | |
| PC-0162✎ edit📣 feedback | received | technical | Core architects ai |
4.4 Measuring Progress and Impact §4.4 p.98 l.Whole section; also §1.5 (p. 21), §3.7.5 (p. 85) anchor: medium |
Success is validated through conformance, adoption and coverage metrics. No goal or metric addresses whether the receiv…Success is validated through conformance, adoption and coverage metrics. No goal or metric addresses whether the receiving actor acts appropriately on exchanged information. A message can arrive complete, coded and conformant, and still leave the receiver unable to decide what to do. Moreover, 'capture once, use many times' assumes reuse is free; in practice information must be transformed to fit each receiver's role and context (informational metamorphosis), and this transformation is neither designed nor governed. Suggested revision: Add to §4.4 (and reference from §3.7.5) an explicit pragmatic outcome measure: periodic, scenario-based assessment of whether receiving actors (clinicians, community health workers, administrators, clients) take the appropriate next action on the basis of exchanged records. Additionally, design and govern receiver-appropriate views of shared records (role- and context-specific transformations). Position appropriateness-of-action as the ultimate validation criterion of the seven goals. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | |
| PC-0163✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.Whole section; also §2.2.2 (p. 28), Appendix F (p. 241) anchor: medium |
The draft rightly notes SNOMED CT licensing, and SGI covers release management. However, it nowhere states as a require…The draft rightly notes SNOMED CT licensing, and SGI covers release management. However, it nowhere states as a requirement that all participating systems must operate on the same versions of the same code systems and value sets. Divergent versions allow one code to carry a changed or deprecated meaning across systems — undermining precisely the semantic consistency the architecture exists to provide. Suggested revision: State explicitly (in §2.2.2 and in the SGI capability categories) that version alignment of terminologies and value sets across all consuming systems is a conformance requirement, with coordinated national release windows, deprecation notice periods, and migration testing as SGI-governed processes. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | |
| PC-0164✎ edit📣 feedback | received | technical | Metadata registries ai |
3.7.1 Purpose §3.7 p.78 l.Whole section; also §§4.3.1–4.3.3 (pp. 94–96), Appendix C — LIMR (p. 172) anchor: medium |
The LIMR governs logical models, and FHIR is recommended for exchange. Experience with national clinical information mo…The LIMR governs logical models, and FHIR is recommended for exchange. Experience with national clinical information models (e.g. the Netherlands' zibs, per ISO 13972) shows the translation from logical model to technical artefact (FHIR profile, storage model) is not inherently one-to-one; meaning can shift or be lost in that step even when systems are technically conformant. Suggested revision: Add to §3.7 a requirement for semantic fidelity testing across the translation step: round-trip verification that data instantiated from a logical model, exchanged via its technical representation, and re-interpreted at the receiving end preserves the governed meaning — not only structural/technical conformance. Reference ISO 13972 for clinical information model quality requirements. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | |
| PC-0165✎ edit📣 feedback | received | general | Clinical ai |
3.6 Interoperability Architecture within DPI-H §3.6 p.71 l.Whole section; also §1.2.2 (p. 15), Glossary (front matter, PDF pp. 8–10) anchor: medium |
The draft implicitly treats non-structured information as text awaiting structuring ('machine-processable rather than l…The draft implicitly treats non-structured information as text awaiting structuring ('machine-processable rather than locked in free text'). Clinical information also exists in interpretive and tacit/narrative states that resist faithful coding; forcing them into structure distorts rather than captures them. These states carry a large share of real clinical decision-making. Suggested revision: Acknowledge in §1.2.2 and §3.6 the limits of structuring: name the interpretive and narrative states of clinical information as first-class concerns, state that the architecture supports (rather than replaces) their human carriers — the conversation, the handover, the narrative note — and caution against measuring digitisation progress by the elimination of free text. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-257 discuss | in the document all mentions on GitHub record | |
| PC-0166✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §Appendix C p.155 l.Lifelong Health Record component; also Goal 4 in §1.5 (p. 21) anchor: medium |
The individual appears primarily as a rights-holder and, 'where applicable', a data source. The person is also a knowle…The individual appears primarily as a rights-holder and, 'where applicable', a data source. The person is also a knowledge source: the holder of context, corrections, and narrative that no provider system records — often decisive for safe care (allergies, adherence, home circumstances). Suggested revision: Extend the LHR component requirements with a governed citizen-contribution channel: the ability for individuals (and, where authorised, informal carers) to add structured and narrative contributions and corrections to their record, with provenance and review workflow, so the record reflects lived reality as well as institutional data. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | |
| PC-0167✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.Capability categories; also §5.2 (p. 105), Appendix F (p. 241) anchor: medium |
SGI's feedback loop runs from consuming applications back into the governance cycle. It does not yet include feedback f…SGI's feedback loop runs from consuming applications back into the governance cycle. It does not yet include feedback from care outcomes and receiver comprehension — e.g. terms or models that are systematically misread at the point of care. Suggested revision: Add to the SGI capability categories (and Appendix F) a capability for pragmatic feedback: structured intake of evidence that governed content is misinterpreted or fails to support appropriate action in practice, feeding the authoring/publication cycle. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | |
| PC-0168✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.Whole subsection anchor: medium |
We strongly endorse Chapter 5's framing. One principle deserves to be stated explicitly: an AI model must not be the te…We strongly endorse Chapter 5's framing. One principle deserves to be stated explicitly: an AI model must not be the terminal interpreter of clinical information. Its outputs become trustworthy data only when a human author has checked, integrated and signed them. Suggested revision: Add a sentence to §5.4.2 stating that AI outputs affecting care, eligibility or resources require a human author of record who verifies and signs the resulting data before it enters the Lifelong Health Record or downstream decision processes — consistent with the chapter's auditability principle. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0169✎ edit📣 feedback | received | technical | Core architects ai |
Glossary §Glossary p.PDF 8–10 l.Definition of interoperability; also §3.6.5 (p. 78); terms marked '[Under review]' anchor: medium |
Several glossary terms are under review and 'Health Information Exchange' is still to be included. Since the pragmatic …Several glossary terms are under review and 'Health Information Exchange' is still to be included. Since the pragmatic level (see comments 2, 5 and 7) is currently absent from the definitions, the revision of the glossary is the natural place to anchor it. Suggested revision: When finalising the glossary, define pragmatic interoperability (shared use of exchanged information for appropriate action) alongside the existing definition of interoperability, and align the conformance chapter's vocabulary with it. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | |
| PC-0170✎ edit📣 feedback | received | general | Metadata registries ai |
4.5 Roles, Skills, and Capacity §4.5–4.6 p.100–103 l.Whole sections anchor: medium |
SGI presupposes sustained institutional capacity (committees, curation, release management) that is scarcest in the LMI…SGI presupposes sustained institutional capacity (committees, curation, release management) that is scarcest in the LMICs this guidance most aims to serve. The financing and capacity sections are thin relative to what the governance model demands. Suggested revision: Expand §§4.5–4.6 with a minimal viable SGI staffing/costing model and options for regional pooling of semantic governance (shared curation across countries, as §3.4.6 hints), so the governance burden matches realistic capacity. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | |
| PC-0171✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.Whole section; also §4.3.1 (p. 94), Appendix C — LIMR (p. 172) anchor: medium |
The architecture governs the stewardship of information models (SGI, LIMR) but does not standardise how models are made…The architecture governs the stewardship of information models (SGI, LIMR) but does not standardise how models are made. Current artefact standards allow too many degrees of freedom: the same clinical concept can be modelled in many valid but incompatible ways, so two fully conformant implementations may still diverge semantically. A related, unnamed risk is the boundary problem: qualifiers, modifiers and localisations can be expressed in either the terminology or the information model, and this overlap breeds divergence. Suggested revision: Require (in §3.4.5 and Appendix C) that artefacts in the LIMR be produced with a declared, uniform modelling method — one generic semantic pattern from which artefacts are derived by specialisation, with mandatory context (what, where, when, who, how, why) at capture — and test that meaning survives its application. The emerging CEN/ISO 13606 part 3 (SIAMM) work is one standards-track candidate; the requirement itself should remain method-neutral. Explicitly name — and assign governance responsibility for — the boundary problem between coding systems and information models. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | |
| PC-0172✎ edit📣 feedback | received | technical | Clinical ai |
3.5 DPI-H Application Components §3.5 p.63 l.Component catalogue; also Appendix C (p. 114 ff.) anchor: medium |
Among the proposed components there is no component for the shared, multi-professional care plan — the living object st…Among the proposed components there is no component for the shared, multi-professional care plan — the living object stating who does what, when, and towards which goals for a specific person. 'Care plan' appears only in passing inside other components, never as an architectural object with its own repository, governance and exchange rules. Of the three recognised kinds of continuity of care — informational, management, relational — the draft covers essentially only the first and equates it with the whole. Suggested revision: Add a Shared Care Plan component to the catalogue: a governed repository and exchange rules for multi-professional, cross-organisational, long-term plans (building on existing patterns such as FHIR CarePlan and the International Patient Summary), as the architectural carrier of management continuity. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-069 discuss | in the document all mentions on GitHub record | |
| PC-0173✎ edit📣 feedback | received | general | Clinical ai |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §Ch. 1 p.9–23 l.Framing and examples; actor definitions throughout the document anchor: medium |
The draft's implicit care model is episodic and programme-centric (HIV, TB, immunisation examples). Across 254 pages, '…The draft's implicit care model is episodic and programme-centric (HIV, TB, immunisation examples). Across 254 pages, 'integrated care', 'social care' and 'long-term care' do not appear; 'caregiver' appears once; 'chronic' four times. The person with multiple chronic conditions whose care spans health and social services over years — precisely the population that most needs shared infrastructure — is absent as a design case. Suggested revision: Include integrated, long-term and social care explicitly in the framing and priority use cases; add social-care professionals and informal caregivers to the recognised actors; and include a worked example of a multimorbid person supported by a multi-professional, cross-organisational team over time. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-255 discuss | in the document all mentions on GitHub record | |
| PC-0174✎ edit📣 feedback | received | general | Core architects ai |
3.6.4 Cross-border health data flows §3.6.4 p.77 l.Cross-border health data flows; also Appendix D.3 (p. 234) anchor: medium |
The European Health Data Space (EHDS) — the largest legal and infrastructural implementation of exactly these ideas, es…The European Health Data Space (EHDS) — the largest legal and infrastructural implementation of exactly these ideas, establishing citizen rights, mandated exchange formats and cross-border channels for primary and secondary use — is never mentioned, although EU examples are cited. Suggested revision: Add an EHDS alignment section mapping DPI-H components to EHDS obligations and formats (e.g. the European exchange format and patient summary), so European implementers can position themselves and other regions can learn from the largest live implementation. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-261 discuss | in the document all mentions on GitHub record | |
| PC-0175✎ edit📣 feedback | received | general | Core architects ai |
2.2.1 What REDDHI is and its foundational core §2.2 p.26–30 l.REDDHI (§§2.2.1–2.2.2); also §4.4 (p. 98) anchor: medium |
REDDHI is rightly defined as a condition of maturity to be approached gradually and verified through observable signs —…REDDHI is rightly defined as a condition of maturity to be approached gradually and verified through observable signs — but the draft offers no structured self-assessment instrument with which a country can locate itself and plan progression. Suggested revision: Connect REDDHI to the existing tradition of maturity models — for example SCIROCCO, the European twelve-dimension self-assessment for integrated-care readiness, used for planning rather than grading — or provide a REDDHI maturity instrument with dimensions and observable indicators. Gerard Freriks and Angelo Rossi-Mori, Gerard Freriks is Affilated with CEN and ISO, Netherlands / Europe |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | |
| PC-0176✎ edit📣 feedback | received | technical | Core architects human |
3.7.1 Purpose §3.7.1 p.79 l.976–989 |
The distinction between system conformance, architecture conformance and outcome monitoring is helpful. The guidance ma…The distinction between system conformance, architecture conformance and outcome monitoring is helpful. The guidance may also benefit from clarifying that these forms of assessment do not necessarily establish whether the evidence supporting a particular consequential operational decision satisfies the substantive policy, programme, financing or regulatory requirements applicable to that decision. Suggested revision: Consider adding after the discussion of the three forms of assessment: “Conformance of systems and architectures establishes whether required technical capabilities, services, standards and architectural relationships are correctly implemented. Where information is subsequently used to support a consequential operational, financing, regulatory or programme decision, countries may additionally need governed processes to determine whether the available evidence satisfies the applicable requirements for that specific use. Such assurance is distinct from technical conformance and should be defined according to national policy, law and programme governance.” Yetunde Yusuf, HCOS Technologies, Inc., United States |
none | not yet | CS-082 discuss | in the document all mentions on GitHub record | |
| PC-0177✎ edit📣 feedback | received | technical | No human |
3.4.2 Governance principles §3.4.2 p.55 l.250–288 |
The governance principles appropriately address decision authority, escalation, transparency and accountability. The Cl…The governance principles appropriately address decision authority, escalation, transparency and accountability. The Clinical Decision Support Engine later provides a useful concrete pattern in which consequential decision logic is tied to authoritative content, transparency, accountability and documented override. Consider whether the general governance principles should identify an analogous cross-cutting traceability principle for other rules-based DPI-H decisions that materially affect individuals, providers, programmes or institutions. Suggested revision: Consider adding a cross-cutting governance principle that, where automated or rules-based processing materially affects an individual, provider, programme or institution, implementations should preserve sufficient traceability to reconstruct, as applicable, the authoritative requirement or rule version used, relevant evidence or data considered, resulting determination, responsible actor or system, timestamp, and any authorised exception or override. Yetunde Yusuf, HCOS Technologies, Inc., United States |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0178✎ edit📣 feedback | received | technical | Financial systems human |
Benefits Package Registry §Appendix C — Benefits Package Registry p.199–200 l.15–20; 41–50 |
The Benefits Package Registry appropriately separates authoritative benefit definitions from operational claims and pay…The Benefits Package Registry appropriately separates authoritative benefit definitions from operational claims and payment functions. It may be useful to make explicit that confirmation of coverage, eligibility, provider status and technical validity of a transaction does not necessarily establish that sufficient evidence exists to support a consequential claim or payment decision. Suggested revision: Consider clarifying that, where claims or other financing decisions depend on evidence of service delivery or fulfilment of programme conditions, countries should define where responsibility for assessing the sufficiency and provenance of that evidence resides within the financing architecture. Confirmation of coverage, eligibility or technical validity should not, by itself, be interpreted as establishing that all substantive requirements for payment or other consequential action have been satisfied. Yetunde Yusuf, HCOS Technologies, Inc., United States |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | |
| PC-0179✎ edit📣 feedback | received | technical | Core architects human |
C Appendix C: DPI-H Application Component Descriptions §Appendix C — Public Health Surveillance Platform; see also Computable Decision Support Engine p.228; 188 l.PHSP 214–220; CDSE 138–140 anchor: medium |
The draft already recognises governed verification before formal action in public-health surveillance and override/acco…The draft already recognises governed verification before formal action in public-health surveillance and override/accountability mechanisms in clinical decision support. Consider articulating a broader principle for consequential automated or rules-based determinations where underlying evidence is incomplete, conflicting, ambiguous or otherwise falls outside normal decision conditions. Suggested revision: Consider adding: “Where automated or rules-based determinations carry material consequences, countries should define proportionate exception and review mechanisms for situations in which evidence is incomplete, conflicting, ambiguous or otherwise falls outside normal decision conditions. Such mechanisms may include authorised review, reason capture, escalation and auditability, according to national law, policy and risk.” Yetunde Yusuf, HCOS Technologies, Inc., United States |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0180✎ edit📣 feedback | received | general | No human |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.68 l.Exact line numbers to be confirmed from full-review-version PDF anchor: medium |
This draft provides a comprehensive and valuable global reference architecture for digital public infrastructure for he…This draft provides a comprehensive and valuable global reference architecture for digital public infrastructure for health (DPI-H). However, overlapping content can be observed between the governance module and the data governance module in the current text. Without clear guidance on streamlining duplicated content, implementing practitioners may face confusion and reduced operational efficiency during national-level localization and deployment. Adding targeted reminders for content simplification will significantly improve the practical usability of the guidance for global implementers. Suggested revision: Add the following text to the implementation guidance section: “During national localization and deployment, implementers are encouraged to identify and streamline overlapping content between the governance module and the data governance module, to reduce redundant work and improve operational efficiency.” Li Jianping, Research Office of Guoxue Studies, Heluo Culture Research Institute, Harbin Normal University, China |
none | not yet | CS-052 discuss | in the document all mentions on GitHub record | |
| PC-0181✎ edit📣 feedback | received | general | No human |
4.2.1 Different Entry Points toward REDDHI §4.2.1 & 3.6.1 p.83 l.Exact line numbers to be confirmed from full-review-version PDF anchor: medium |
The guidance elaborates a sound framework for interoperability and semantic governance of health data. However, it larg…The guidance elaborates a sound framework for interoperability and semantic governance of health data. However, it largely assumes that participating countries have a relatively complete existing digital health foundation. Many low- and middle-income countries face fragmented legacy systems, limited technical capacity, and weak data infrastructure, which makes the ideal full interoperability framework difficult to implement in one step. The guidance lacks a practical gradient implementation path for countries with weak foundational conditions, which may lead to the framework being shelved due to mismatched local conditions. Suggested revision: Add the following text to the interoperability and implementation sections: “For countries with weak digital health foundations and fragmented legacy systems, a phased implementation path is recommended: first achieve basic data interoperability within core public health institutions, then gradually expand to cross-system and cross-regional full interoperability, to ensure the framework is adaptable to local technical and capacity conditions.” Li Jianping, Research Office of Guoxue Studies, Heluo Culture Research Institute, Harbin Normal University, China |
none | not yet | CS-246 discuss | in the document all mentions on GitHub record | |
| PC-0182✎ edit📣 feedback | received | general | No human |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 & 3.5.3 p.74 l.Exact line numbers to be confirmed from full-review-version PDF anchor: medium |
The current draft provides comprehensive guidance on the components of DPI-H, but does not clearly distinguish between …The current draft provides comprehensive guidance on the components of DPI-H, but does not clearly distinguish between baseline essential components and advanced optional components for country implementation. As a global reference framework, it faces the risk of being either over-implemented by low-income countries beyond their fiscal and technical capacity, or selectively implemented with key core components omitted by some countries. Clear differentiation of implementation priorities will help countries at different development levels to adopt the framework in a more targeted and feasible way. Suggested revision: Add the following text to the architecture and component guidance section: “The DPI-H components are divided into two categories: baseline essential components that all countries are encouraged to prioritize and implement first, and advanced optional components that can be deployed according to national fiscal, technical and health system conditions. This classification helps countries to formulate feasible implementation roadmaps that match their own development level.” Li Jianping, Research Office of Guoxue Studies, Heluo Culture Research Institute, Harbin Normal University, China |
none | not yet | CS-026 discuss | in the document all mentions on GitHub record | |
| PC-0183✎ edit📣 feedback | received | general | Financial systems ai |
4.6 Financing and Partnerships §4.6 & 4.5 p.111 l.Exact line numbers to be confirmed from full-review-version PDF anchor: medium |
The guidance mentions partnership and financing arrangements for DPI-H implementation, but lacks targeted guidance on t…The guidance mentions partnership and financing arrangements for DPI-H implementation, but lacks targeted guidance on two core practical challenges faced by most countries: first, the necessity of engaging local frontline experts in the localization adaptation of the framework; second, the matching of long-term operation and maintenance funds with the data interoperability implementation. Many countries have complete construction plans, but fail to land them due to the lack of local expert adaptation and insufficient long-term budget guarantee, resulting in the framework remaining on paper only. Suggested revision: Add the following two paragraphs to the implementation and financing sections: 1. “During the early stage of DPI-H localization and implementation, countries are recommended to establish a local adaptation working group composed of frontline medical and digital architecture experts, to adjust the framework to match local health system conditions and reduce the risk of mismatched implementation.” 2. “The implementation of data interoperability and semantic governance must be matched with a guaranteed long-term recurring budget for system operation, maintenance and iteration. Countries should incorporate the relevant funding needs into their medium and long-term fiscal planning, to ensure the sustainable operation of the digital infrastructure.” Li Jianping, Research Office of Guoxue Studies, Heluo Culture Research Institute, Harbin Normal University, China |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0184✎ edit📣 feedback | received | technical | Core architects ai |
Future proofing the Architecture §5.2, 5.4.1 p.104 - 107 l.24 - 70, 142 - 153 anchor: medium |
The document correctly asserts that AI depends on foundational data infrastructure but doesn’t define a structured mul…The document correctly asserts that AI depends on foundational data infrastructure but doesn’t define a structured multi-layered framework or roadmap to guide its adoption. Countries would benefit from a blueprint of sorts for them to understand the critical investments (e.g., compute infrastructure, data governance, applications, etc) and how to go about setting them up. A defined/custom AI capability stack guide in understanding how DPI-H relate to AI infrastructure Suggested revision: Consider adding a new sub-section in Chapter 5 that defines an AI capabilty framework with layers: (1) Data foundations (DPI-H components like registries, LHR, LIMR, TS) that provide governed, structured data (2) Interoperability and access (exchange layer that allows data to flow to models) (3) Model development and inference (infrastructure for training, testing, and deploying models) (4) Governance and oversight (policies and processes for trustworthy AI) (5) AI-enabled applications (point-of-care and analytical tools that consume AI outputs). Also include an indicative implementation sequence: countries should establish layers 1–2 before meaningful AI adoption. MICHAEL ODAL, UGANDA |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | |
| PC-0185✎ edit📣 feedback | received | technical | Core architects ai |
5.4.1 What AI readiness means §5.4.1 p.107 l.142 - 153 |
The term 'AI readiness' is discussed qualitatively but lacks a practical framework to guide assessment. A structured to…The term 'AI readiness' is discussed qualitatively but lacks a practical framework to guide assessment. A structured tool would support countries to self-evaluate across several dimensions and identify priority gaps Suggested revision: 1) Add an AI readiness assessment framework with concrete indicators across each dimension, including data governance maturity, availability of structured data for priority use cases, legal framework for algorithmic accountability, institutional capacity for model evaluation and monitoring, and workforce skills. 2) Present the framework as a self-assessment matrix that countries can complete during architecture planning MICHAEL ODAL, UGANDA |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | |
| PC-0186✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.107 l.155 - 169 |
This section correctly identifies the need for evluation. It however doesn't offer further practical guides nor provide…This section correctly identifies the need for evluation. It however doesn't offer further practical guides nor provide a draft framework to countries on how to assess systems before deployment. This framework is a critical step that will guide procurement teams in evaluating vendor claims and provide a basis for approving in-country AI tools for clinical decision support Suggested revision: 1) Add a sub-section on AI evaluation and assurance, including: a tiered approach to evaluation commensurate with risk (higher scrutiny for autonomous vs assistive systems); guidance on establishing test datasets representative of local populations; requirements for performance disaggregation across population subgroups; and a protocol for ongoing monitoring of model drift. 2) Reference existing frameworks such as WHO AI evaluation guidance and the EU AI Act conformity assessment approach. MICHAEL ODAL, UGANDA |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | |
| PC-0187✎ edit📣 feedback | received | general | Core architects ai |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.108 l.170 - 183 |
The document acknowledges AI cost and sustainability challenges but provides no practical guidance on financing models.…The document acknowledges AI cost and sustainability challenges but provides no practical guidance on financing models. Countries need to understand how to fund AI adoption sustainably, including through shared infrastructure models, public-private partnerships, and integration with existing DPI-H investments. Suggested revision: 1) Add a sub-section on AI financing and procurement, including: options for public-private partnerships; shared AI infrastructure models where costs are pooled across programmes; guidance on managing vendor lock-in (including through open-weight and open-source models); and criteria for evaluating whether to build sovereign AI capacity or rely on commercial offerings. 2) Include a risk assessment for data sovereignty/ownership and security when using commercial API-based models. MICHAEL ODAL, UGANDA |
none | not yet | CS-126 discuss | in the document all mentions on GitHub record | |
| PC-0188✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.107 l.155 - 169 |
The guidance notes the importance of human oversight but does not address documented risks such as automation bias (cli…The guidance notes the importance of human oversight but does not address documented risks such as automation bias (clinicians over-relying on AI recommendations) or AI-fuelled misdiagnosis, particularly in low-resource settings where validation data may be limited. Suggested revision: 1) Add specific guidance on mitigating cognitive and clinical risks associated with AI deployment, including: mandatory training on AI limitations and appropriate human override 2) Design requirements for explainability and transparency at the point of care (the importance of user-centred design that supports rather than supplants clinical reasoning) and the need for formal clinical validation of AI outputs before deployment, with ongoing monitoring of safety events. MICHAEL ODAL, UGANDA |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0189✎ edit📣 feedback | received | general | Core architects ai |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2, 5.4.1 p.101. 107 l.500 - 517 142 - 153 |
The roles and skills section does not include roles for AI governance and data science capacity, yet thes skills are in…The roles and skills section does not include roles for AI governance and data science capacity, yet thes skills are increasingly becoming essential as AI adoption grows. Without these, countries lack the institutional capacity to evaluate, procure, and oversee AI systems safely. Suggested revision: 1) Consider adding AI-specific roles and capacities to the roles and skills section, including: AI ethics and governance specialists; model evaluators and auditors; data scientists with health domain expertise; clinical informaticians with AI literacy; and MLOps engineers for model deployment and maintenance. 2) Include guidance on building these capacities through training programmes, partnerships with academic institutions, and regional centres of excellence. MICHAEL ODAL, UGANDA |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | |
| PC-0190✎ edit📣 feedback | received | technical | Core architects ai |
5.4.3 Equity and safety §5.4.3 p.108 l.1790 - 183 anchor: medium |
The draft document flags equity risks but doesn't address the documented risk of AI models performing poorly for unders…The draft document flags equity risks but doesn't address the documented risk of AI models performing poorly for underserved populations when trained on unrepresentative data. This is a known challenge (particular for LMICs) that requires explicit mitigation strategies, particularly in contexts where training data comes mainly from well-resourced urban settings. Suggested revision: Consider adding specific equity and inclusion requirements for AI systems, including: representativeness of training data (with explicit attention to rural populations, women, and marginalized communities); bias detection and mitigation protocols; the requirement that evaluation includes disaggregated performance reporting across population subgroups; and community engagement in AI governance to ensure diverse perspectives inform deployment decisions. MICHAEL ODAL, UGANDA |
none | not yet | CS-124 discuss | in the document all mentions on GitHub record | |
| PC-0191✎ edit📣 feedback | received | general | Financial systems ai |
4.6 Financing and Partnerships §4.6, 4.6.2 p.102 l.461 - 473 anchor: medium |
The document correctly identifies the need for an investment case and sustainability but does not provide a specific st…The document correctly identifies the need for an investment case and sustainability but does not provide a specific strategy for transitioning from donor-funded (project-based) models to domestically financed, service-oriented models. This transition is a critical challenge for LMICs. Suggested revision: Add a dedicated sub-section on transition planning, including: a phased roadmap for increasing domestic financing share over time, with clear milestones; guidance on engaging Ministries of Finance as strategic partners in the design and resourcing of shared infrastructure, framed around fiscal benefits rather than technology; practical advice on designing cost-recovery and shared-benefit mechanisms; and provide examples from countries that have successfully made this transition. MICHAEL ODAL, UGANDA |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | |
| PC-0192✎ edit📣 feedback | received | general | Core architects ai |
1.3.1 The Cost of Fragmentation §1.3.1, 1.3.3 p.18 - 19 l.294 - 306, 319 - 327 |
The document correctly identifies the political economy challenge of vertical, programme-driven fragmentation but provi…The document correctly identifies the political economy challenge of vertical, programme-driven fragmentation but provides limited guidance on how to build coalitions, manage resistance, and create accountability frameworks that reward contributions to shared infrastructure. The case for investment also lacks a tailored value proposition for Ministries of Finance. Suggested revision: 1) Consider adding a sub-section on navigating political economy, including: strategies for aligning donor funding with national architecture (rather than allowing parallel systems); guidance on creating accountability frameworks that reward contributions to shared infrastructure; and advice on sequencing investments to build momentum and demonstrate early value. 2) Expand the value proposition for Ministries of Finance with metrics that resonate: reduced fraud and leakage, verifiable health expenditure, budget execution tracking, and the ability to link spending to outcomes. MICHAEL ODAL, UGANDA |
none | not yet | CS-013 discuss | in the document all mentions on GitHub record | |
| PC-0193✎ edit📣 feedback | received | general | Financial systems ai |
4.6.3 Approaches to Financing §4.6.3 p.103 l.475 - 486 anchor: medium |
The document lists financing approaches but could provide more detailed guidance on how DPI-H components integrate with…The document lists financing approaches but could provide more detailed guidance on how DPI-H components integrate with national health insurance (NHI) and public financial management (PFM) systems. This is essential for countries implementing health financing reforms. Suggested revision: 1) Consider adding a sub-section on integration with National Health Insurance (NHI) and Public Finance Management (PFM) systems, detailing: how the Benefits Package Registry and claims management systems interface with existing government financial systems; specific integration patterns for revenue collection, member management, and provider payment; and reference to established frameworks (e.g., WHO health financing guidance, World Bank PFM frameworks). 2) Include a worked example of a claims flow from eligibility to payment. MICHAEL ODAL, UGANDA |
none | not yet | CS-115 discuss | in the document all mentions on GitHub record | |
| PC-0194✎ edit📣 feedback | received | general | Core architects ai |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4, 5.5 p.108 - 109 l.170 - 218 anchor: medium |
The document mentions sovereign models and openness but does not provide guidance on how countries should decide betwee…The document mentions sovereign models and openness but does not provide guidance on how countries should decide between building their own AI capabilities, relying on commercial offerings, or using open-weight models. This decision has significant implications for cost, sovereignty, and sustainability. Suggested revision: Add guidance on the AI procurement landscape, including: criteria for evaluating commercial AI offerings (performance, cost, data sovereignty, security); consideration of open-weight and open-source models as alternatives to proprietary models; procurement clauses that protect national data assets and ensure portability; and the conditions under which sovereign AI infrastructure (national or regional) may be worth the investment. MICHAEL ODAL, UGANDA |
none | not yet | CS-126 discuss | in the document all mentions on GitHub record | |
| PC-0195✎ edit📣 feedback | received | editorial | Financial systems ai |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2 p.36 l.503 - 525 |
The worked example for health financing is helpful but could be expanded to include a practical scenario showing how th…The worked example for health financing is helpful but could be expanded to include a practical scenario showing how the Benefits Package Registry interfaces with a national health insurance scheme's operational systems (claims, enrolment, payment). This would make the architectural concepts more tangible. Suggested revision: Consider expanding the worked example to include a concrete scenario(s): - how a person's coverage is determined by querying the Benefits Package Registry - how a claim is validated against the registry at the point of service - how payment is triggered to a provider - how the registry feeds into financial accountability. This would bridge the gap between architecture and operational reality for non-technical readers in health financing roles. MICHAEL ODAL, UGANDA |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | |
| PC-0196✎ edit📣 feedback | received | technical | No human |
C Appendix C: DPI-H Application Component Descriptions §Appendix C-Terminology anchor: medium |
The Required/Recommended framework for code system, value set, and concept map management in Appendix C maps cleanly on…The Required/Recommended framework for code system, value set, and concept map management in Appendix C maps cleanly onto how LOINC is actually maintained and consumed by implementers, and we support it without reservation. Suggested revision: No change requested. Noted as a strength worth preserving in future revisions. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-0197✎ edit📣 feedback | received | technical | Metadata registries ai |
unplaced §Whole Document |
Where the document names SNOMED International and WHO-FIC as governance or federation partners, it should name Regenstr…Where the document names SNOMED International and WHO-FIC as governance or federation partners, it should name Regenstrief Institute alongside them wherever LOINC is the terminology under discussion, rather than referencing LOINC only as a code system without its governing organization. Suggested revision: Revise to include reference to Regenstrief Institute where governing entities are mentioned Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | CS-277 discuss | all mentions on GitHub record | |
| PC-0198✎ edit📣 feedback | received | technical | No human |
Terminology Service §Whole document; Appendix C Terminology Service p.164-171 anchor: medium |
The draft correctly identifies LOINC as one of the core internationally recognized terminologies a national Terminology…The draft correctly identifies LOINC as one of the core internationally recognized terminologies a national Terminology Service (TS) must host and manage, alongside ICD-11 and SNOMED CT/GPS, and the glossary definition accurately reflects LOINC's full scope (measurements, observations, survey instruments and documents — not laboratory results alone). Suggested revision: No change requested. Noted as a strength worth preserving in future revisions. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-0199✎ edit📣 feedback | received | technical | Metadata registries ai |
Terminology Service §Appendix C – “Federation and alignment with international sources” (p. 166) and Governance item (5), “International coordination” (p. 171) p.166 171 anchor: medium |
Regenstrief Institute, LOINC's steward, is named alongside SNOMED International, SNOMED CT’s steward and WHO-FIC as an …Regenstrief Institute, LOINC's steward, is named alongside SNOMED International, SNOMED CT’s steward and WHO-FIC as an anchor body for federation and international coordination — the only place LOINC's governing organization is identified. This requirement is classed “Recommended,” not “Required,” and the text does not describe how synchronization with LOINC releases, or submission of national term requests to Regenstrief, would work in practice. Suggested revision: Elevate federation/synchronization for the three core terminologies (ICD-11, SNOMED CT, LOINC) from Recommended to Required, consistent with how code system and value set versioning were elevated elsewhere in the same appendix. Add a short explanatory note describing LOINC's release cadence and Regenstrief's process for receiving national/local term submissions. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | |
| PC-0200✎ edit📣 feedback | received | technical | Metadata registries ai |
C Appendix C: DPI-H Application Component Descriptions §p. 29 footnote (standards licensing); Appendix C – “Licensing management” and Governance item (4), “Licensing obligations” (pp. 166–171) p.29 166-171 anchor: medium |
The document devotes a footnote and two governance provisions to SNOMED CT's licensing model and national member-fee ob…The document devotes a footnote and two governance provisions to SNOMED CT's licensing model and national member-fee obligations but never notes that LOINC is freely available worldwide at no cost, with no membership requirement. This asymmetry could leave national planners with the impression that all three core terminologies carry licensing costs. Suggested revision: Add a parallel footnote or sentence clarifying that LOINC is released under an open license with no license fee, so that licensing/budget implications are distinguished clearly across the three core terminologies. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | |
| PC-0201✎ edit📣 feedback | received | technical | Metadata registries ai |
3.5.3.2 The business services layer §§3.5.3.2, LIMR/TS comparison table – blood-pressure worked example (pp. 68–70) p.68-70 anchor: medium |
The document's only detailed worked example involving LOINC treats it purely as the downstream target of a concept map …The document's only detailed worked example involving LOINC treats it purely as the downstream target of a concept map from a SNOMED CT concept (271649006 → LOINC 8480-6), rather than as a primary code system with its own structure (panels, question/answer conventions, document and observation typing). This may understate LOINC's role as a first-class terminology. Suggested revision: Add a second worked example in which LOINC is the primary code system — e.g., a laboratory order/result or clinical document use case — to balance the SNOMED-CT-first framing of the existing example. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | |
| PC-0202✎ edit📣 feedback | received | technical | Metadata registries ai |
C Appendix C: DPI-H Application Component Descriptions §§3.5.3.2 concept-map example (pp. 68–70); Appendix C – “Concept map management” (p. 165) p.68-70 165 anchor: medium |
The SNOMED CT–to–LOINC concept-map example effectively re-derives a mapping relationship without reference to the exist…The SNOMED CT–to–LOINC concept-map example effectively re-derives a mapping relationship without reference to the existing, LOINC Ontology: LOINC-SNOMED CT Interoperability Solution already published by Regenstrief and SNOMED International Suggested revision: Add a citation/footnote pointing implementers to the existing LOINC Ontology: LOINC-SNOMED CT Interoperability Solution so national teams build on established work rather than re-mapping independently. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | |
| PC-0203✎ edit📣 feedback | received | technical | Metadata registries ai |
unplaced §Document-wide – footnotes and citations |
The document footnotes URLs for WHO SMART Guidelines, the SNOMED CT licensing note, the OpenHIE Terminology Service spe…The document footnotes URLs for WHO SMART Guidelines, the SNOMED CT licensing note, the OpenHIE Terminology Service specification, and the IHE SVCM specification, but includes no citation or link to LOINC (loinc.org) or to Regenstrief Institute. Suggested revision: Add a footnote citing loinc.org (and Regenstrief Institute's role as steward) at first mention of LOINC, consistent with the citation treatment given to the other named standards and specifications. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | CS-277 discuss | all mentions on GitHub record | |
| PC-0204✎ edit📣 feedback | received | technical | Metadata registries ai |
Terminology Service §Appendix C – “Value set management” and “Core attributes” (pp. 165, 167–168) p.165 167-168 anchor: medium |
LOINC's own conventions for panels and standardized answer lists (LOINC Answer List / LL codes) are not mentioned, even…LOINC's own conventions for panels and standardized answer lists (LOINC Answer List / LL codes) are not mentioned, even though the Value Set Management requirements (intensional/extensional value sets) apply directly to how LOINC panels and answer lists are represented and consumed in practice. Suggested revision: Add a brief note under “Value set management” citing LOINC panels and standardized answer lists as a concrete example, alongside the existing SNOMED CT/ICD examples. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | |
| PC-0205✎ edit📣 feedback | received | technical | Editorial ai |
3.5.3.1 The foundational shared data layer §General – ordering convention throughout the document anchor: medium |
In every list pairing the three core terminologies, LOINC consistently appears last (“SNOMED CT, ICD-11, LOINC” or “ICD…In every list pairing the three core terminologies, LOINC consistently appears last (“SNOMED CT, ICD-11, LOINC” or “ICD-11, SNOMED CT, LOINC”). Combined with the LOINC-as-downstream-example pattern noted in Comment 4, this may cumulatively read as treating LOINC as secondary. Suggested revision: No substantive change needed; noted for awareness. Varying the ordering in a future revision or stating explicitly that no priority is implied by list order, would remove any ambiguity. Marjorie Rallins, DPM, MS, Executive Director, Health Data Standards, Regenstrief Institute, Health Data Standards, LOINC/UCUM, Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-0206✎ edit📣 feedback | received | general | Core architects ai |
1.1.4 Who can benefit from this guidance? §1.1.4 p.12 l.136–165 |
The intended audiences are clearly described, but civil-society organisations, community health representatives and aca…The intended audiences are clearly described, but civil-society organisations, community health representatives and academic institutions are not listed, although they are important to implementation, accountability, trust, capacity-building and community engagement in countries such as Mozambique. Suggested revision: Add an audience category for civil society, community representatives and academic institutions, explaining their roles in inclusive governance, implementation research, workforce development, public accountability and the translation of community needs into national digital-health priorities. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-004 #21 | in the document all mentions on GitHub record | |
| PC-0207✎ edit📣 feedback | received | technical | Core architects ai |
1.2.1 Identity DPI and Identification in Healthcare §1.2.1 p.13 l.195–207; Box 1.2 |
The distinction between foundational identity and health-sector identification is highly relevant. The guidance should …The distinction between foundational identity and health-sector identification is highly relevant. The guidance should state more explicitly that assignment of a health identifier and access to essential care must not depend on possession of a civil or national identity document. Suggested revision: Add: “A person shall be able to receive a health identifier and access essential health services without possessing a civil or national identity document. The Client Registry should support temporary identifiers, probabilistic matching, deduplication and subsequent linkage to civil identity when available.” Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-009 discuss | in the document all mentions on GitHub record | |
| PC-0208✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.32 l.240–255 |
The draft recognises that continuous central connectivity cannot be assumed, but intermittent connectivity and unreliab…The draft recognises that continuous central connectivity cannot be assumed, but intermittent connectivity and unreliable electricity should be treated as core architectural conditions in low-resource and rural settings, not only as considerations supporting federated exchange. Suggested revision: Add minimum offline-first requirements covering local data capture, encrypted storage, delayed synchronisation, conflict resolution, audit continuity, identity matching after reconnection, safe device recovery, alternative power arrangements and continuity of essential services during extended outages. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | |
| PC-0209✎ edit📣 feedback | received | general | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.33 l.304–322 |
The principle of local capacity is strong, but it would be more actionable if linked to a structured national capacity-…The principle of local capacity is strong, but it would be more actionable if linked to a structured national capacity-development approach. Short project-based training is insufficient to build and retain architecture, FHIR, terminology, security and governance capability. Suggested revision: Recommend national programmes combining competency assessment, practical training, mentoring, certification pathways, communities of practice and retention measures. Encourage partnerships among governments, universities, civil society, professional associations and regional networks, with progressive transfer of responsibilities from external consultants to national teams. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-242 discuss | in the document all mentions on GitHub record | |
| PC-0210✎ edit📣 feedback | received | general | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.34 l.325–343 |
Equity and inclusion should address linguistic accessibility, disability and low digital literacy more explicitly. In m…Equity and inclusion should address linguistic accessibility, disability and low digital literacy more explicitly. In multilingual settings such as Mozambique, meaningful participation and consent cannot depend on fluency in the official language, written forms or individual smartphone ownership. Suggested revision: Expand the equity principle to require accessible and multilingual interfaces and processes, including local languages, assisted or oral consent where legally permitted, formats for persons with disabilities, and service pathways for people without personal digital devices or sufficient digital literacy. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | |
| PC-0211✎ edit📣 feedback | received | general | Core architects ai |
3.4.2 Governance principles §3.4.2 p.54 l.249–272 |
The requirement for inclusive representation is welcome. However, the guidance could better explain how civil society a…The requirement for inclusive representation is welcome. However, the guidance could better explain how civil society and affected communities obtain genuine influence rather than nominal participation, particularly where technical governance structures are highly specialised. Suggested revision: Recommend defined voting or decision rights where appropriate, transparent selection of community representatives, accessible disclosure of decisions, feedback and grievance mechanisms, resourcing for effective participation, and periodic assessment of whether rural populations, women, displaced persons and underserved groups influence strategic decisions. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-048 discuss | in the document all mentions on GitHub record | |
| PC-0212✎ edit📣 feedback | received | general | Core architects ai |
4.2.2 A Phased Implementation Approach §4.2.2 p.90–91 l.113–165 |
The phased implementation approach is useful, but countries with limited technical and institutional capacity may still…The phased implementation approach is useful, but countries with limited technical and institutional capacity may still struggle to identify a minimum viable starting package and the concrete outputs expected from each phase. Suggested revision: Provide a low-resource implementation annex specifying minimum governance arrangements, baseline assessment, priority registries, interoperability capability, FHIR implementation guides, security controls, testing environment, capacity plan, financing plan, responsible institutions, indicative costs and measurable milestones for each phase. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-246 discuss | in the document all mentions on GitHub record | |
| PC-0213✎ edit📣 feedback | received | technical | Core architects ai |
4.3.5 Minimum Conformance and Testing §4.3.5 p.98 l.398–408 |
Conformance testing is correctly linked to procurement, but the draft would be more useful if it provided model require…Conformance testing is correctly linked to procurement, but the draft would be more useful if it provided model requirements that ministries and development partners could insert into tenders and acceptance procedures. Suggested revision: Include adaptable procurement clauses requiring published national FHIR profiles and APIs, testing in an approved environment, secure data export and migration, full documentation, disclosed recurrent costs, security and audit compliance, offline capability where relevant, knowledge transfer, and retesting after major system updates. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-260 discuss | in the document all mentions on GitHub record | |
| PC-0214✎ edit📣 feedback | received | general | Core architects ai |
4.5.3 Building and Sustaining National Capacity §4.5.3 p.101 l.526–539 |
The section recognises that capacity is institutional rather than a series of individual hires. It should additionally …The section recognises that capacity is institutional rather than a series of individual hires. It should additionally emphasise multidisciplinary capacity, structured retention and practical application, especially for countries that depend heavily on short-term external technical assistance. Suggested revision: Add a recommended national capacity framework covering enterprise architecture, HL7 FHIR modelling, terminology, interoperability, cybersecurity, privacy, data stewardship, clinical informatics, conformance testing and change management, supported by practical assignments, mentoring, institutional career paths and periodic competency assessment. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-107 discuss | in the document all mentions on GitHub record | |
| PC-0215✎ edit📣 feedback | received | general | Financial systems ai |
4.6.2 Sustainability by Design §4.6.2 p.102 l.566–577 |
The five sustainability dimensions are appropriate, but they are not accompanied by measurable indicators. This may mak…The five sustainability dimensions are appropriate, but they are not accompanied by measurable indicators. This may make it difficult for countries, ministries of finance and development partners to determine whether transition from project funding to a sustainable national capability is occurring. Suggested revision: Add indicators such as the proportion of recurrent costs financed domestically, total cost of ownership, retention of qualified national staff, dependence on individual suppliers or consultants, service availability, rural and population coverage, upgrade and maintenance costs, and continuity during funding or connectivity disruptions. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-111 discuss | in the document all mentions on GitHub record | |
| PC-0216✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §5.4.2–5.4.3 p.108 l.154–175 |
The discussion of representative data and trustworthy AI is important. Greater attention is needed to African populatio…The discussion of representative data and trustworthy AI is important. Greater attention is needed to African populations and local languages that are underrepresented in global datasets, since systems trained and evaluated elsewhere may perform inequitably in Mozambique and other multilingual settings. Suggested revision: Require evaluation against locally representative clinical cases, population groups and languages before deployment. Encourage governed development of local-language datasets, terminology resources and benchmarks, with community participation, appropriate consent, documented human oversight and clear accountability for harmful or incorrect outputs. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-124 discuss | in the document all mentions on GitHub record | |
| PC-0217✎ edit📣 feedback | received | general | Core architects ai |
Public Health Surveillance Platform §Appendix D.2 p.231–234 l.Country examples anchor: medium |
The African examples are valuable, but no Lusophone African country is included. Greater linguistic and regional divers…The African examples are valuable, but no Lusophone African country is included. Greater linguistic and regional diversity would strengthen the global applicability of the guidance and provide lessons from countries at earlier stages of architecture maturity. Suggested revision: Include or actively solicit emerging examples from Mozambique, Angola, Guinea-Bissau, Cabo Verde and São Tomé and Príncipe. Establish a mechanism for countries to submit implementation profiles and lessons for future versions. Mozambique could contribute experience on a Unique Patient Identifier, FHIR capacity-building and integration with existing systems. Eden Elão Manhique, SEMEAR, Mozambique |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0218✎ edit📣 feedback | received | technical | Metadata registries ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.26 l.148–169 |
The REDDHI open standards list (line 148) and surrounding text reference SNOMED CT, ICD-11, and LOINC as a group withou…The REDDHI open standards list (line 148) and surrounding text reference SNOMED CT, ICD-11, and LOINC as a group without articulating that these are complementary, not interchangeable, standards. Each occupies a distinct clinical domain: SNOMED CT covers clinical concepts and findings; ICD-11-MMS supports morbidity/mortality classification and reimbursement; LOINC standardises laboratory and clinical observation identifiers. A country implementing only one of these three would produce a functionally incomplete Terminology Service. The current grouping may lead national programmes to conclude that any single standard satisfies the architectural requirement. Suggested revision: Add a clarifying sentence following the open standards list: "These standards are complementary rather than interchangeable: SNOMED CT provides clinical concept and procedural coverage; ICD-11 MMS supports mortality and morbidity classification; LOINC provides universal identifiers for laboratory tests and clinical observations. A complete national Terminology Service typically requires all three, operating together." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | |
| PC-0219✎ edit📣 feedback | received | technical | Metadata registries ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 (Footnote 14) p.26 l.Footnote 14 anchor: medium |
The footnote describing SNOMED CT licensing correctly states the membership model and mentions the SNOMED International…The footnote describing SNOMED CT licensing correctly states the membership model and mentions the SNOMED International Global Patient Set (GPS), but does not clearly communicate that the GPS is freely available to all countries, including non-Members, at no charge, with no application or registration barrier. For LMIC audiences, this ambiguity risks perpetuating the perception that SNOMED CT is a commercial product and not a global terminology standard, that it is inaccessible without membership fees, which is not the case for the GPS. This is a material equity concern given that DPI-H is designed to serve all country income levels. Suggested revision: Suggestion to expand the footnote: "SNOMED CT requires a licence: the license is available at no charge within SNOMED International Member countries; others license it directly. For non-member countries, the SNOMED International Global Patient Set (GPS) is an open-access product including all of SNOMED CT concenpts freely available at no charge to any country without membership requirements, providing an immediate zero-cost entry pathway for LMIC implementations. Countries should confirm their licensing position before adoption. See snomedct.org/gps." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | |
| PC-0220✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.373–433 |
The Semantic Governance Infrastructure (SGI) is described as a purely national governance function. The section does no…The Semantic Governance Infrastructure (SGI) is described as a purely national governance function. The section does not address the formal relationship between national SGI bodies and the international standards development organisations (SDOs) that develop, publish, and maintain the underlying terminologies such as SNOMED International for SNOMED CT, Regenstrief Institute for LOINC, WHO for ICD-11 and ICD-11 MMS. Without a defined international dimension, national SGI processes are likely to diverge over time, producing semantic fragmentation that undermines the cross-border interoperability DPI-H is designed to achieve. Countries establishing SGI bodies will have no normative reference for how to engage SDOs for requests for change, receive versioned releases, validate localised content, or escalate governance issues internationally. Suggested revision: Suggestion to add a paragraph: "National SGI bodies should maintain formal alignment with the international SDOs that develop the terminologies they govern. SNOMED International's National Release Centre (NRC) programme provides a tested model for this relationship, including governance templates, release pipeline tooling, and a global NRC peer network. WHO and ITU are invited to establish a formal Technical Advisory Group, comprising SNOMED International and fellow SDOs such as Regenstrief Institute for LOINC, HL7 International, and WHO, to develop SGI implementation guidance for national programmes." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | |
| PC-0221✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.61 l.482 |
Line 482 cites SNOMED International's National Release Centre (NRC) model as a consensus-based authoring and release fr…Line 482 cites SNOMED International's National Release Centre (NRC) model as a consensus-based authoring and release framework, and is the only named, tested framework for terminology governance referenced in the document. However, the citation is brief and provides no actionable guidance to countries on how to engage SNOMED International to implement an NRC-aligned SGI. Countries reading this section have no indication that tooling, governance templates, or a formal engagement pathway exist. Suggested revision: Following the NRC model citation at line 482, we suggest to add: "Countries wishing to establish an NRC-aligned SGI body can engage SNOMED International through the NRC onboarding programme (snomedct.org/nrc). SNOMED International provides governance templates, access to Snowstorm, an open-source HL7 FHIR Terminology Server, the SNOMED CT Browser, and connection to the global NRC peer community, at no additional cost to Member countries. Non-member countries can access GPS and NRC guidance materials as a starting point." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | |
| PC-0222✎ edit📣 feedback | received | technical | Metadata registries ai |
3.5.3.1 The foundational shared data layer §3.4.5 / Table 3.5 p.82 l.814 / Table 3.5 |
Line 814 and Table 3.5 enumerate SNOMED CT (and SNOMED GPS), ICD-11, and LOINC as required terminology standards. The d…Line 814 and Table 3.5 enumerate SNOMED CT (and SNOMED GPS), ICD-11, and LOINC as required terminology standards. The document is silent on cross-maps between these standards, specifically the SNOMED CT to ICD-11 MMS map and the SNOMED CT-LOINC alignment. These cross-maps are operationally essential: a country using SNOMED CT for clinical data capture must map to ICD-11 MMS for administrative and statistical reporting. Without authoritative cross-maps, countries will build their own divergent, unmaintained mappings or fail to meet both requirements simultaneously. Historically, SNOMED International and WHO have collaborated on an official SNOMED CT-ICD 10 map; SNOMED International and Regenstrief collaborate on SNOMED CT-LOINC alignment via the LOINC Ontology. These resources are precisely what implementing countries will need. Suggested revision: We suggest the authors add to section 3.4.5 or Table 3.5: "Cross-maps between SNOMED CT, ICD-11 MMS, and LOINC are a required component of a functional national Terminology Service, not an optional enhancement. WHO and ITU should commission a joint Mapping Governance White Paper, co-authored with SNOMED International, WHO's ICD-11 programme, and Regenstrief Institute, providing countries with authoritative guidance on deploying and maintaining cross-terminology maps within their national SGI. Official SNOMED CT-ICD 10 maps are available from SNOMED International; and the LOINC Ontology from Regenstrief and SNOMED International jointly." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | |
| PC-0223✎ edit📣 feedback | received | technical | Metadata registries ai |
3.5.3.1 The foundational shared data layer §3.7 / 3.7.2 p.78 l.962–1000 |
Section 3.7 describes a machine-testable conformance framework. The Terminology Service is a named DPI-H component (Sec…Section 3.7 describes a machine-testable conformance framework. The Terminology Service is a named DPI-H component (Section 3.4.5, Table 3.5) within scope of the Section 3.7 conformance model. However, the section does not reference the HL7 FHIR Terminology Service specification, which is the most widely deployed, mature, and machine-testable conformance model available for Terminology Service implementations. The FHIR Terminology Service defines testable operations ($lookup, $expand, $validate-code, $translate, $subsumes) that map directly to the Terminology Service capabilities described in Section 3.4.5 and Table 3.5. SNOMED International's open-source Snowstorm server and Regenstrief's LOINC FHIR API both implement this specification and are available as reference implementations. Suggested revision: We suggest to add to Section 3.7.2 or 3.7.3: "For Terminology Service components, the HL7 FHIR Terminology Service specification (R4/R5, http://hl7.org/fhir/terminology-service.html) provides a ready-made, machine-testable conformance baseline. National Terminology Service implementations are encouraged to conform to the FHIR Terminology Service specification as part of their Section 3.7 conformance profile. Open-source reference implementations, including SNOMED International's Snowstorm server are currently available for countries to deploy and use as benchmarks." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-067 discuss | in the document all mentions on GitHub record | |
| PC-0224✎ edit📣 feedback | received | general | Metadata registries ai |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F p.241 l.Table, Appendix F anchor: medium |
Appendix F provides useful capability details for the Semantic Governance Infrastructure but does not reference the too…Appendix F provides useful capability details for the Semantic Governance Infrastructure but does not reference the tools, programmes, or SDO engagement pathways available to countries to operationalise those capabilities. Countries reading Appendix F will understand what capabilities are required but receive no guidance on how to implement them or where to seek technical support which is a significant implementation gap given the technical complexity of building an SGI from scratch. Suggested revision: We suggest to add a column to the Appendix F capability table: "Available tools and SDO resources." Suggested entries: Concept lookup and value set management → Snowstorm (SNOMED International open-source FHIR Terminology Server); Laboratory observation management → LOINC FHIR API (Regenstrief); Terminology governance and release pipeline → SNOMED International NRC programme; FHIR conformance profiling → HL7 International Implementation Guides; Clinical-to-administrative coding maps → SNOMED International-WHO ICD cross-map programme. Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-227 discuss | in the document all mentions on GitHub record | |
| PC-0225✎ edit📣 feedback | received | general | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.373–500 |
The SGI section addresses terminology governance within a country but does not address the international release cycle …The SGI section addresses terminology governance within a country but does not address the international release cycle dimension: national SGI bodies must receive, validate, localise, and distribute versioned terminology releases from international SDOs on defined schedules (SNOMED CT: monthly; LOINC: biannual; ICD-11: annual). The governance of this international-to-national terminology flow (requests for change, maintenance, version management, localisation authority, and release validation), is entirely absent from the current text. Without this, countries will develop ad-hoc processes that diverge from authoritative international releases. Suggested revision: Add paragraph: "National SGI bodies are responsible for receiving, validating, and distributing versioned releases from international terminology organisations on their published schedules. Countries should establish formal version management processes aligned to the release cycles of each terminology. SNOMED International's NRC Release Pipeline provides a reference model for national SNOMED CT release management. Countries are encouraged to participate in SDO governance processes to receive advance notice of content changes and contribute to international content development." Additionally, we encourage the WHO/ITU to work directly with SNOMED Interantional, and to establish a formal Technical Advisory Group, comprising SNOMED International and fellow SDOs such as Regenstrief Institute for LOINC, HL7 International, and WHO, to develop SGI implementation guidance for national programmes. The SNOMED International NRC model is highlighted throughout the document as a tried and true model, having our organization in the partnership will help to faciliate this framework beyond theory and into working practice. Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | |
| PC-0226✎ edit📣 feedback | received | general | Metadata registries ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 / 3.4.5 p.26 / 57 l.148 / 482 |
The document does not reference the existing historical formal collaboration between SNOMED International and WHO on IC…The document does not reference the existing historical formal collaboration between SNOMED International and WHO on ICD-10/SNOMED CT cross-mapping, a collaboration that produced the authoritative map between the classification and terminology standard. required by DPI-H and that is directly relevant to the cross-terminology governance challenge identified in this document. Similarly, the Regenstrief-SNOMED International LOINC Ontology collaboration is unacknowledged. Suggested revision: Add footnote or information box: "Historically SNOMED International and WHO collaborate on the production of authoritative cross-maps between SNOMED CT and ICD-10. These maps are available freely and are essential for a national Terminology Service supporting both clinical data capture (SNOMED CT) and administrative/statistical reporting (ICD-10). SNOMED International and Regenstrief additionally collaborate on SNOMED CT-LOINC concept-level alignment and collaboratively produce the LOINC Ontology. Countries implementing DPI-H should plan to incorporate these cross-maps into their Terminology Service rather than building custom mappings." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | |
| PC-0227✎ edit📣 feedback | received | general | WHO ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 / Overall p.57 l.373+ |
SNOMED International formally offers to serve as an International SGI Reference Partner for WHO and ITU in the implemen…SNOMED International formally offers to serve as an International SGI Reference Partner for WHO and ITU in the implementation of the DPI-H framework. As the steward of SNOMED CT, explicitly named in Section 3.4.5 and the REDDHI Open Standards list as foundational to the DPI-H Terminology Service, SNOMED International has a direct organisational interest in, and responsibility for, the success of national SGI implementations. SNOMED International's NRC programme, Snowstorm server, SNOMED CT Browser, and global member network constitute the resources countries will need to implement SGI at scale. SNOMED International would welcome the establishment of a formal SDO Technical Advisory Group to develop SGI implementation guidance alongside WHO and ITU. Suggested revision: Add to Section 3.4.5: "WHO and ITU are invited to formally recognise SNOMED International as an International SGI Reference Partner for the DPI-H framework. A formal Technical Advisory Group, comprising SNOMED International, Regenstrief, HL7 International, and WHO, is proposed to develop SGI implementation guidance, standard operating procedures for NRC-aligned national bodies, and a DPI-H Terminology Service Conformance Profile for use in national procurement." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | |
| PC-0228✎ edit📣 feedback | received | technical | Metadata registries ai |
Glossary §Glossary p.9 anchor: medium |
SNOMED CT definition is too narrow. The DPI-H Glossary defines SNOMED CT as "a structured clinical terminology standard…SNOMED CT definition is too narrow. The DPI-H Glossary defines SNOMED CT as "a structured clinical terminology standard for use in electronic health records." This is materially incomplete. SNOMED CT is used for clinical decision support, population health analytics, disease surveillance, research and registry data, AI/ML model training, and interoperability across virtually every digital health domain, not only EHRs. Defining it as an EHR tool understates its architectural relevance to the very components DPI-H describes: the CDSE, HMIS, PHSP, and Terminology Service all depend on SNOMED CT in ways that go beyond EHR coding. Suggested revision: We suggest a change to the following definition: "SNOMED CT: a comprehensive, multilingual clinical terminology providing a structured, hierarchical representation of clinical concepts including clinical findings, procedures, body structures, and observable entities, used for data capture, clinical decision support, population health analytics, disease surveillance, and research across digital health systems." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | |
| PC-0229✎ edit📣 feedback | received | technical | Metadata registries ai |
Glossary §Glossary p.9 anchor: medium |
SNOMED CT Global Patient Set (GPS) definition ("a list of basic clinical terms") is inaccurate in two respects. First, …SNOMED CT Global Patient Set (GPS) definition ("a list of basic clinical terms") is inaccurate in two respects. First, "basic" is wrong: the GPS is a curated, clinically meaningful subset of the SNOMED CT International Edition, providing broad coverage of the most clinically relevant concepts across findings, procedures, medications, and other domains. Second, the word "basic" may actively deter adoption by implying inadequacy for serious clinical use, which is the opposite of the document's intent. The definition also omits the GPS's most important policy feature: it is freely available to all countries without any SNOMED International membership requirement or fee. This is the primary access pathway for LMIC implementations and should be stated plainly in the Glossary. Suggested revision: We suggest the following change: "SNOMED CT Global Patient Set (GPS): a curated subset of the SNOMED CT International Edition, providing broad coverage of clinically essential concepts across findings, procedures, and related domains. The GPS is freely available to all countries at no charge, with no membership requirement, providing an immediate zero-cost access pathway for national terminology services in any country." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | |
| PC-0230✎ edit📣 feedback | received | technical | Metadata registries ai |
3.6.4 Cross-border health data flows §3.6.4 p.87–88 l.line 942 and Appendix C Terminology Service, §1 |
Section 3.6.4 recommends the International Patient Summary (IPS) as the cross-border exchange standard for the minimum …Section 3.6.4 recommends the International Patient Summary (IPS) as the cross-border exchange standard for the minimum health data set. The IPS is named without noting that SNOMED CT is the primary clinical terminology binding in the IPS specification. The HL7 FHIR IPS Implementation Guide binds clinical findings, procedures, and allergies to SNOMED CT value sets. Countries implementing IPS conformance will therefore require SNOMED CT (or GPS) for clinical coding regardless of whether the Terminology Service section makes that explicit. This is a direct, normative dependency that should be stated. Omitting it allows a country to read §3.6.4 and the Terminology Service component description independently, without understanding that IPS conformance effectively mandates SNOMED CT. Suggested revision: Suggested addition to §3.6.4: "The IPS HL7 FHIR Implementation Guide binds key clinical elements, including problems, allergies, and procedure, to SNOMED CT value sets. Countries implementing IPS-conformant data exchange should plan for SNOMED CT (or SNOMED CT GPS for non-member countries) as the clinical terminology underpinning their IPS profiles." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | |
| PC-0231✎ edit📣 feedback | received | general | Metadata registries ai |
3.5.3.1 The foundational shared data layer §5.2 & 5.3 p.115–116 and 117 |
Chapter 5 correctly identifies governed terminology as essential infrastructure for AI-ready health data (p. 115: "term…Chapter 5 correctly identifies governed terminology as essential infrastructure for AI-ready health data (p. 115: "terminology services, which provide the semantic consistency that allows an algorithm to operate on data that means the same thing across the systems that produced it"). However, SNOMED CT is ommitted, despite SNOMED CT named in §3.4.5, and Table 3.5, as the required clinical terminology throughout the rest of the document. Additionally, p. 116 introduces the concept of AI models calling authoritative services through shared interfaces (explicitly mentioning the Model Context Protocol), describing exactly the kind of deterministic, governed reference services that SNOMED International's Snowstorm FHIR Terminology Server and SNOMED CT FHIR API provide. These are not mentioned. SNOMED CT's hierarchical, computable structure (including ability for post-coordinated expressions, direct attribute relationships, and transitive closure), makes it uniquely suited for ML training, NLP named entity recognition, and AI reasoning. Suggested revision: Suggested addition to §5.2: "For clinical data, the governed terminology standard that delivers semantic consistency across AI training and inference is SNOMED CT, the same terminology required for the Terminology Service component described in Section 3.4.5. Its hierarchical and computable structure, which captures relationships between clinical concepts, allows AI models to generalise across equivalent clinical expressions rather than treating each code as an isolated label. The SNOMED CT GPS provides this foundation to non-member countries without cost. SNOMED International's open-source Snowstorm server implements the HL7 FHIR Terminology Service specification and is available as an authoritative, machine-callable service for AI and analytical applications." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-119 discuss | in the document all mentions on GitHub record | |
| PC-0232✎ edit📣 feedback | received | technical | Metadata registries ai |
Terminology Service §Appendix C, Functional Requirements, Requirement 23 p.180 anchor: medium |
Issue: Requirement 23 ("Federation with international sources") which covers synchronisation with content published by …Issue: Requirement 23 ("Federation with international sources") which covers synchronisation with content published by international terminology authorities including SNOMED International, WHO-FIC, and Regenstrief, is classified as Recommended, not Required. This means a national Terminology Service can achieve full DPI-H conformance without establishing any formal connection to international SDOs for terminology updates. This is a serious structural deficiency. SNOMED CT, ICD-11, and LOINC all publish versioned releases on defined cycles (SNOMED CT: monthly; ICD-11: annual; LOINC: biannual). A national Terminology Service that does not federate with these sources will progressively diverge from authoritative international content, producing the exact semantic fragmentation that the SGI concept is designed to prevent. The classification as Recommended effectively makes international alignment optional which contradicts the document's stated purpose and the intent of §3.4.5. Elevating this requirement to Required would be consistent with: (a) the document's own statement that the TS must manage the "lifecycle of terminologies from international adoption through national extension to local use" (p. 174); (b) the SGI governance notes in §3.4.5; and (c) the international release cycle governance comment already submitted in the formal matrix (Comment #8). Suggested revision: Suggested revision: Elevate Requirement 23 from Recommended to Required. Add: "Without active federation with international terminology authorities, national Terminology Services will diverge from authoritative content releases, undermining the semantic comparability DPI-H is designed to achieve. Federation with SNOMED International (for SNOMED CT/GPS), WHO-FIC (for ICD-11), and Regenstrief (for LOINC) is therefore a conformance requirement, not an optional enhancement." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | |
| PC-0233✎ edit📣 feedback | received | general | Metadata registries ai |
Lifelong Health Record §Appendix D p.241–244 anchor: medium |
Issue: The country implementation examples contain two omissions relevant to SNOMED CT:Issue: The country implementation examples contain two omissions relevant to SNOMED CT: Australia (p. 241–242): Described as illustrating "Terminology Service" but the text does not mention that Australia is a SNOMED International Member country with a national SNOMED CT release (the Australian Clinical Terminology, maintained by the Australian Digital Health Agency). The example focuses on Ontoserver (correctly cited in footnote 85) but omits the national SNOMED CT governance programme that makes Ontoserver useful. For a document designed to encourage other countries to adopt national terminology services, the failure to explicitly name SNOMED CT as what Australia's national TS hosts is remissed. Denmark (p. 242): Denmark's example focuses only on sundhed.dk (the patient health portal) and is categorised as illustrating only "LHR." Denmark is one of the founding Members of SNOMED International with an active national SNOMED CT governance programme (NRC) and a national extension, none of which is mentioned. Denmark is frequently cited as an advanced example of national SNOMED CT governance and would strengthen the document's case for the SGI model. Suggested revision: Suggested addition to Australia example: "Australia operates a national SNOMED CT programme, producing and maintaining the National Clinical Terminology Service (NCTS), run by the Australian Digital Health Agency. This is a national extension of the SNOMED CT International Edition governed by the Australian Digital Health Agency, which is hosted in Ontoserver and distributed to point-of-care systems across the country." Suggested addition to Denmark: Add Terminology Service to Denmark's illustrated components and note: "Denmark operates a national SNOMED CT governance programme as a SNOMED International Member, providing a national extension of SNOMED CT that supports coded data capture across the Danish health system." Don Sweete, SNOMED International, Global (international not-for-profit SDO) |
none | not yet | CS-204 discuss | in the document all mentions on GitHub record | |
| PC-0234✎ edit📣 feedback | received | general | Clinical ai |
3.4.2 Governance principles §3.4.2 p.54 l.250–264 |
The governance principles give necessary weight to underserved communities, but they do not explicitly require frontlin…The governance principles give necessary weight to underserved communities, but they do not explicitly require frontline clinical, clinical-informatics or patient-safety expertise in decisions that can affect care delivery. A deployment could therefore meet the stated representation principle while clinically consequential architecture decisions are made without those who understand workflow hazards, service constraints and patient-safety consequences. Suggested revision: Add a governance principle on clinical and service accountability: governance bodies should include frontline clinical, clinical-informatics, patient-safety and service-user expertise, with defined decision rights for safety-relevant architecture, data and workflow decisions. Representation should be proportionate to the clinical consequences of the decision, not merely advisory. Dr. Samer Al-Diri, Independent, United Arab Emirates |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | |
| PC-0235✎ edit📣 feedback | received | general | Clinical ai |
3.4.3 Strategic governance §3.4.3 p.55 l.290–304 |
The strategic-governance responsibilities address equity, sustainability and dependency risks. Patient safety, clinical…The strategic-governance responsibilities address equity, sustainability and dependency risks. Patient safety, clinical effectiveness and accountable clinical authority are not named. As a result, the relationship between national architecture decisions and their consequences in care settings may remain unclear. Suggested revision: Add responsibilities to: designate an accountable clinical-governance or patient-safety authority; define clinical-risk appetite and safety/outcome thresholds for DPI-H-enabled services; and require strategic approval of changes with material clinical or patient-safety consequences. Include patient safety and clinically significant service degradation among the systemic risks monitored. Dr. Samer Al-Diri, Independent, United Arab Emirates |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | |
| PC-0236✎ edit📣 feedback | received | technical | Clinical ai |
3.4.4 Operational governance §3.4.4 p.56–57 l.334–362 |
Operational governance is accountable for infrastructure integrity, safe change and evaluation in use, but the monitori…Operational governance is accountable for infrastructure integrity, safe change and evaluation in use, but the monitoring scope is not explicit at the architecture-to-care interface. Availability, data quality and standards conformance alone may miss unsafe workarounds, delayed or missed care, documentation burden, near misses, inequitable access and deterioration in clinically meaningful outcomes. Suggested revision: Expand operational monitoring to include point-of-care consequences: downtime and degraded-service effects; workarounds and override patterns; delayed or missed care; near misses and adverse events; clinical workload and usability burden; equity of access; and clinically meaningful outcome drift. Require feedback from frontline clinicians and service users, with findings feeding operational correction and strategic review. Dr. Samer Al-Diri, Independent, United Arab Emirates |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | |
| PC-0237✎ edit📣 feedback | received | technical | Clinical ai |
3.4.4 Operational governance §3.4.4 p.57 l.363–372 |
The escalation examples cover scope, capacity, stakeholder conflict, security and continuity. Clinically consequential …The escalation examples cover scope, capacity, stakeholder conflict, security and continuity. Clinically consequential events are not named. A serious identity, terminology, interoperability or workflow defect could therefore continue to be handled as an operational technology incident when it also requires patient-safety review. Suggested revision: Add explicit escalation triggers for actual or suspected patient-safety events; clinically significant performance degradation; unsafe identity, data, terminology or decision-support behaviour; and change-induced workflow hazards. Define time-bound escalation to the relevant clinical-governance or patient-safety authority, including regulatory reporting where required, and criteria for service restriction, rollback or suspension. Dr. Samer Al-Diri, Independent, United Arab Emirates |
none | not yet | CS-046 discuss | in the document all mentions on GitHub record | |
| PC-0238✎ edit📣 feedback | received | general | Clinical ai |
4.2.2 A Phased Implementation Approach §4.2.2 p.91 l.131–145 |
Phase 1 establishes the architecture governance body, stakeholders and evaluation plan, but does not explicitly establi…Phase 1 establishes the architecture governance body, stakeholders and evaluation plan, but does not explicitly establish clinical-safety governance before implementation. Deferring this function risks treating clinical assurance as a late implementation check rather than a design constraint carried through procurement, configuration, testing and deployment. Suggested revision: Add a Phase 1 deliverable to establish the clinical-governance and patient-safety workstream, including a named accountable lead, a DPI-H hazard/risk log, clinical acceptance criteria, escalation and incident routes, and requirements for frontline clinical and service-user participation. Carry these controls through procurement, testing, go-live and post-deployment evaluation. Dr. Samer Al-Diri, Independent, United Arab Emirates |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | |
| PC-0239✎ edit📣 feedback | received | general | Clinical ai |
4.2.4 The Role of the National Digital Architect §4.2.4 p.94 l.226–240 |
The national digital architect is appropriately accountable for architectural coherence, but describing this role as th…The national digital architect is appropriately accountable for architectural coherence, but describing this role as the accountable designer of the health system's digital infrastructure could be read as concentrating accountability for clinically consequential effects in an architectural function. Architecture authority and clinical accountability require distinct expertise and should be coupled rather than conflated. Suggested revision: Clarify that the national digital architect is accountable for architectural coherence and conformance, while a named clinical-governance or patient-safety authority is accountable for assessing effects on care delivery. Require joint review and documented approval for safety-critical designs and changes, with clear routes for disagreement and escalation. Dr. Samer Al-Diri, Independent, United Arab Emirates |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | |
| PC-0240✎ edit📣 feedback | received | general | Clinical ai |
4.6.4 Partnerships §4.6.4 p.103 l.601–610 |
The partnerships section explains how relationships are coordinated but does not define accountability at the boundarie…The partnerships section explains how relationships are coordinated but does not define accountability at the boundaries between government, donors, suppliers, implementers and care providers. Ambiguity at these boundaries can delay ownership of validation, operational readiness, incident response, corrective action and safe exit when a shared component affects clinical services. Suggested revision: Recommend a documented responsibility matrix and contractual allocation covering design assurance, clinical and technical validation, deployment readiness, data stewardship, service monitoring, incident response, change control, rollback, supplier exit and data portability. State that, consistent with applicable national law, regulatory responsibilities and governance arrangements, public authorities should retain appropriate stewardship and decision authority for clinically consequential risks even where delivery functions are outsourced. Dr. Samer Al-Diri, Independent, United Arab Emirates |
none | not yet | CS-113 discuss | in the document all mentions on GitHub record | |
| PC-0241✎ edit📣 feedback | received | technical | Clinical ai |
5.4.1 What AI readiness means §5.4.1–5.4.2 p.108 l.142–168 |
The AI-readiness and trustworthy-AI sections cover evidence, human oversight, accountability and periodic evaluation. W…The AI-readiness and trustworthy-AI sections cover evidence, human oversight, accountability and periodic evaluation. What is less clear is how a deployed AI capability should connect to routine clinical governance, incident reporting and service management. Making that connection explicit would help ensure that model monitoring is considered alongside care outcomes and frontline signals. Suggested revision: Add lifecycle requirements for locally representative clinical validation; a named clinical owner; workflow and human-factors assessment; logging and traceability; subgroup performance and drift monitoring; accessible clinician override and incident-reporting routes; and predefined criteria for restriction, rollback or suspension. Require these signals to feed existing clinical-governance and patient-safety systems, not a parallel AI-only process. Dr. Samer Al-Diri, Independent, United Arab Emirates |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | |
| PC-0242✎ edit📣 feedback | received | general | Core architects ai |
1.4 DPI-H Principles §1.4 DPI-H Principles — Autonomy and Sovereignty p.21 l.412-416 |
The principle states that countries 'should not be dependent on actors outside their jurisdiction for the continued ope…The principle states that countries 'should not be dependent on actors outside their jurisdiction for the continued operation or evolution of their core digital health infrastructure'. Artificial intelligence introduces a form of cross-jurisdictional dependency that the guidance does not name. A country may own every registry, exchange layer and record described in this architecture and still have every clinical decision-support inference executed on a model hosted in another jurisdiction, under that jurisdiction's export controls, and subject to a supplier's unilateral pricing and deprecation decisions. That is the dependency this principle forbids, arriving through a door the architecture leaves undescribed. The distinction that matters architecturally is not whether AI is used but whether the model can be executed within the country's own infrastructure. Suggested revision: Extend the Autonomy and Sovereignty principle with a sentence to the effect: 'Where artificial intelligence forms part of a health capability, the architecture should preserve the option of in-jurisdiction inference — that is, models whose weights can be hosted and operated on national infrastructure. Dependence on a remotely hosted model that cannot be substituted or relocated is a sovereignty risk of the same class as dependence on a foreign-operated registry, and should be assessed as such.' The Blue Capital Studio, Cyprus |
none | not yet | CS-127 discuss | in the document all mentions on GitHub record | |
| PC-0243✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 Design Principles — VI. Local Capacity p.33-34 l.304-322 |
The principle already favours 'widely supported, well-documented technologies over specialised or closed technologies w…The principle already favours 'widely supported, well-documented technologies over specialised or closed technologies whose inner workings are not visible to the teams expected to run them', and states that an architecture a country cannot understand, operate and evolve with its own people is not genuinely owned by it. A model available only as a remote API is precisely a closed technology whose inner workings are not visible to the team expected to run it. The guidance makes the argument for software but does not extend it to models, which is where the argument is now most consequential. Suggested revision: Add to Principle VI a clause noting that the same test applies to model artefacts: where an AI capability is adopted, preference should be given to models that in-country teams can host, inspect, evaluate and substitute, rather than models accessible only as an external service. The Blue Capital Studio, Cyprus |
none | not yet | CS-127 discuss | in the document all mentions on GitHub record | |
| PC-0244✎ edit📣 feedback | received | technical | Core architects ai |
2.2.1 What REDDHI is and its foundational core §2.2 REDDHI — Table 2.2, 'Longitudinal health records, with provenance and attribution' p.28 l.141 (Table 2.2) |
Provenance is currently defined by the Client, Health Facility and Health Workforce registries — that is, by which pers…Provenance is currently defined by the Client, Health Facility and Health Workforce registries — that is, by which person, which place and which worker. Once AI-drafted clinical content can enter a record, a third dimension is required: whether an entry was machine-generated or machine-drafted, by which system and version, and which human clinician reviewed and attested it. Without this, a Lifelong Health Record silently mixes human-authored and machine-drafted content and no subsequent audit, liability determination, quality review or model evaluation can separate them. This cannot be retrofitted: if the record structure does not carry the distinction from the outset, the historical record is permanently ambiguous. Because it concerns the foundational shared data layer rather than any point-of-service application, it belongs in this architecture and not in procurement guidance. Suggested revision: Add to the provenance row of Table 2.2, and to the Lifelong Health Record component description, a requirement that record entries carry machine-generated content indicators: the authoring system and version, whether the content was machine-drafted, and the identity of the human clinician who reviewed and attested it. HL7 FHIR Provenance already supports the necessary structure, so this is a conformance expectation rather than a new component. The Blue Capital Studio, Cyprus |
none | not yet | CS-247 discuss | in the document all mentions on GitHub record | |
| PC-0245✎ edit📣 feedback | received | general | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 Design Principles — VII. Equity and Inclusion p.34 l.325-343 |
The equity principle addresses connectivity, infrastructure and institutional capacity, and requires that the architect…The equity principle addresses connectivity, infrastructure and institutional capacity, and requires that the architecture 'degrade gracefully rather than exclude'. Language is absent from it. In a substantial share of the settings this guidance addresses — refugee and displacement contexts, migrant populations, multilingual states, and rural populations served by clinicians trained in a national or colonial language — the patient and the clinician do not share a fluent language. This is not a user-interface localisation matter. History taken across a language barrier is systematically less complete and less accurate, and that deficit propagates directly into the registries and longitudinal records this architecture exists to make trustworthy. Language is therefore a data-quality property of the architecture, not a presentation-layer concern. Suggested revision: Add language to the equity design decisions, along the lines of: 'The architecture should not assume that the person and the health worker share a language. Where they do not, the capability to capture history in the person's own language and render it into the clinical record in the working language of the health system is a data-quality requirement, not a presentation concern, and should be treated as such in conformance expectations for systems that write to the shared record.' The Blue Capital Studio, Cyprus |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | |
| PC-0246✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 Design Principles — IV. Sustainability p.33-34 l.266-283 |
Sustainability is assessed against 'whole-of-life cost and viability — to build, operate, maintain, and evolve'. Where …Sustainability is assessed against 'whole-of-life cost and viability — to build, operate, maintain, and evolve'. Where a capability depends on external model inference, a material part of that whole-of-life cost is a per-unit price set by a third party, revisable unilaterally, and denominated in a foreign currency — a cost structure that scales with clinical volume rather than with the country's budget cycle, and that has no analogue among the other components described. Model deprecation carries the same character: a capability can be withdrawn or materially altered on a supplier's schedule. Suggested revision: Note under Principle IV that capabilities dependent on externally hosted models carry a volume-linked, externally set recurring cost and a supplier-controlled deprecation risk, and that whole-of-life assessment should make both explicit. The Blue Capital Studio, Cyprus |
none | not yet | CS-127 discuss | in the document all mentions on GitHub record | |
| PC-0247✎ edit📣 feedback | received | editorial | Core architects ai |
Glossary §Glossary — 'Point-of-service applications' [Under review] p.2 (glossary) l.glossary entry anchor: medium |
The definition is marked [Under review]. As drafted it groups all end-user applications together, but the obligations t…The definition is marked [Under review]. As drafted it groups all end-user applications together, but the obligations that follow differ sharply depending on whether an application writes to the shared record or only reads from it. A system that writes into the Lifelong Health Record inherits conformance, provenance and data-quality duties that a read-only viewer does not. Suggested revision: Revise to distinguish point-of-service applications that write to shared infrastructure from those that only consume it, and state that the former carry conformance and provenance obligations defined by the architecture. The Blue Capital Studio, Cyprus |
none | not yet | CS-025 discuss | in the document all mentions on GitHub record | |
| PC-0248✎ edit📣 feedback | received | general | Core architects ai |
1.5.1 The Health Sector Goals §1.5.1 Health Sector Goals — first goal, 'domestic AI development' p.23 l.468-469 |
Goal 1 refers to a single high-quality data capture supporting clinical care, facility management, population analytics…Goal 1 refers to a single high-quality data capture supporting clinical care, facility management, population analytics, public health monitoring 'and domestic AI development simultaneously'. Throughout Chapters 1 and 2, AI appears only as a consumer of data. The reciprocal question — where the resulting AI capability is executed, and under whose control — is not posed, although Chapter 5 may address it (not reviewed here). If the ambition is domestic AI development, then domestic AI operation is the corresponding architectural requirement, and the two should be stated together. Suggested revision: Where 'domestic AI development' is referenced, pair it with domestic operability: the ability to run the resulting capability on national infrastructure, not only to contribute the data from which it is built. The Blue Capital Studio, Cyprus |
none | not yet | CS-127 discuss | in the document all mentions on GitHub record | |
| PC-0249✎ edit📣 feedback | received | general | Core architects ai |
1.2.1 Identity DPI and Identification in Healthcare §1.2.1 Identity / Box 1.2 — coverage gaps p.14-15 l.197-209 anchor: medium |
Box 1.2 correctly identifies newborns before civil registration, refugees, undocumented migrants and marginalised commu…Box 1.2 correctly identifies newborns before civil registration, refugees, undocumented migrants and marginalised communities as populations foundational identity does not reach. These are substantially the same populations least likely to share a language with the clinician treating them. The guidance treats the identification gap structurally and thoroughly; the communication gap affecting the same people is not treated at all. Linking them would strengthen both the identity discussion and the equity principle. Suggested revision: Add a cross-reference between the coverage gaps in Box 1.2 and the equity principle in Section 2.3, noting that the populations least reliably identified are frequently also those least reliably understood at the point of care. The Blue Capital Studio, Cyprus |
none | not yet | CS-009 discuss | in the document all mentions on GitHub record | |
| PC-0250✎ edit📣 feedback | received | No human |
unplaced §NOTE ON SCOPE OF THIS REVIEW p.— l.— |
This submission is based on a full reading of Chapter 1 and Chapter 2 only. Chapters 3, 4 and 5, and the appendices, we…This submission is based on a full reading of Chapter 1 and Chapter 2 only. Chapters 3, 4 and 5, and the appendices, were not reviewed. Comments 1, 2, 5 and 7 concern artificial intelligence and may overlap with Chapter 5 (Future-proofing the Architecture), which the reviewer has not read; where they duplicate material already present there, they should be disregarded. Suggested revision: — The Blue Capital Studio, Cyprus |
none | not yet | none | all mentions on GitHub record | ||
| PC-0251✎ edit📣 feedback | received | editorial | Core architects ai |
2.2.1 What REDDHI is and its foundational core §Glossary; 2.2.1; 4.3.1 p.2; 27–28; 94–95 l.Registry definition; 118–137; 248–273 anchor: medium |
The draft uses “minimum”, “core”, “foundational core”, “shared”, “minimum viable foundation”, “canonical minimum data s…The draft uses “minimum”, “core”, “foundational core”, “shared”, “minimum viable foundation”, “canonical minimum data set” and “minimum conformance” for different kinds of concepts. These can refer to implementation feasibility, architectural centrality, shared reuse, mandatory data content or semantic necessity, but the distinctions are not defined. This may lead countries to interpret a minimum technical baseline as sufficient even where essential meaning or safety is lost. Suggested revision: Add a short terminology box distinguishing: (a) minimum implementation baseline; (b) core capability or component; (c) shared core intended for reuse across programmes or systems; (d) minimum semantic core- the least meaning and relationships that must not be lost; (e) bounded core with inclusion, exclusion and governance rules; and (f) extensible framework allowing controlled national, professional and local extensions. Clarify that data minimisation asks what need not be collected, whereas a minimum semantic core asks what meaning must not be lost. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-027 discuss | in the document all mentions on GitHub record | |
| PC-0252✎ edit📣 feedback | received | technical | Metadata registries ai |
2.2.1 What REDDHI is and its foundational core §2.2.1; 4.3.1 p.27–28; 94–95 l.131–137; Table 2.2; 256–273 |
Table 2.2 treats consistent data structure through the Logical Information Model Repository (LIMR) as an enabler that c…Table 2.2 treats consistent data structure through the Logical Information Model Repository (LIMR) as an enabler that can be built as maturity grows rather than part of the minimum foundation. However, section 4.3.1 later states that countries should define and govern minimum data models before implementation. Without at least a minimum governed information-model capability, structural assumptions remain implicit and semantic fragmentation can be embedded from the start. Suggested revision: Retain progressive implementation of LIMR tooling, but require every REDDHI starting point to establish a minimum governed information-model capability. This could initially be a published national data dictionary, approved model catalogue or lightweight repository covering priority components, with clear ownership, versioning and extension rules, before evolving into a fuller LIMR. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-029 discuss | in the document all mentions on GitHub record | |
| PC-0253✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5; 4.3.1 p.57–59; 94–96 l.373–442; 256–284 |
The Semantic Governance Infrastructure appropriately governs terminologies, value sets and information models, but it d…The Semantic Governance Infrastructure appropriately governs terminologies, value sets and information models, but it does not explicitly distinguish between validating individual clinical models and determining the minimum professional meaning and relationships that must remain present across an end-to-end care process. Correct isolated models can still produce an incomplete professional record if relationships among evidence, judgement, plan, intervention, evaluation, provenance and accountability are omitted. Suggested revision: Add a capability for professionally governed minimum semantic cores. Each professional domain should be able to define, through evidence-informed and multi-stakeholder governance, the bounded and extensible minimum concepts, relationships, context, provenance and accountability required for safe interpretation across documentation, exchange, transformation and reuse. Terminology coverage alone does not determine which professional meanings and relationships must be preserved; the guidance should therefore support explicit inclusion and exclusion criteria, clinical and technical validation, versioning, national adaptation and conformance testing for these domain-specific semantic cores. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | |
| PC-0254✎ edit📣 feedback | received | general | Core architects ai |
3.4.2 Governance principles §3.4.2–3.4.4 p.54–56 l.239–352 |
The governance chapter supports inclusive representation, subsidiarity, strategic governance and operational governance…The governance chapter supports inclusive representation, subsidiarity, strategic governance and operational governance, but leaves composition and decision procedures largely to national implementation. Participation alone may not balance the authority of organisations that fund, procure or operate infrastructure with the authority needed to protect public legitimacy, professional meaning and technical integrity. Suggested revision: Add a non-prescriptive tripartite governance pattern that countries may adapt across strategic, operational and semantic governance: (1) public authorities and multilateral institutions; (2) health professionals, patients, communities and civil society; and (3) standards organisations, technical experts, academia and implementers. Distinguish who decides public purpose and rights, clinical/professional validity, and technical conformance; identify matters requiring joint approval; and define conflict-resolution and escalation routes between global, regional, national and local levels. This would be consistent with the wider inclusive, multi-stakeholder direction of the UN Global Digital Compact, while remaining adaptable to country context. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-048 discuss | in the document all mentions on GitHub record | |
| PC-0255✎ edit📣 feedback | received | general | Core architects ai |
How to use this guidance §How to use this guidance; 1.1.4; 3.4.5 p.4–7; 12; 57–58 l.Reading paths table; 136–169; 387–399 anchor: medium |
The intended audiences and reading paths emphasise ministries, DPI authorities, architects, development partners and pr…The intended audiences and reading paths emphasise ministries, DPI authorities, architects, development partners and procurement teams. Clinical professionals, professional bodies, patients, communities and civil society are essential to the semantic and public-interest governance described later, but are not presented as an explicit audience or governance constituency. Nurses, midwives and allied health professionals are not named in the draft, despite being major generators and users of health data. Suggested revision: Add an explicit reading path and stakeholder category for clinical/professional and public-interest communities. Name nurses and nursing informaticians, midwives, allied health professionals, community health workers, physicians, pharmacists, public-health professionals, patients and community representatives as co-governors of domain meaning and acceptable use- not only as consultees or end users. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-004 #21 | in the document all mentions on GitHub record | |
| PC-0256✎ edit📣 feedback | received | technical | Core architects ai |
4.3.1 Design Data Structures and Data Models First §4.3.1–4.3.3; 3.7.4 p.94–96; 84 l.248–330; 1132–1168 |
The draft explains the progression from data models to actors, FHIR profiles and testing, but it does not require expli…The draft explains the progression from data models to actors, FHIR profiles and testing, but it does not require explicit end-to-end traceability from an approved professional or clinical semantic requirement into the implemented model, terminology binding, storage, exchange, analytics/AI use and conformance test. Without traceability, an implementation can be syntactically conformant while progressively losing the rationale and meaning that the original content governance approved. Suggested revision: Require a traceability chain for priority clinical content: governed requirement to logical information model, to terminology/value-set binding and to implementation profile, to persistence/provenance requirements and to exchange transaction, to analytics/AI use and to conformance and regression tests. Material deviations and local extensions should be documented with rationale and clinical approval. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | |
| PC-0257✎ edit📣 feedback | received | technical | Core architects ai |
3.7.4 Planning testing from the architecture §3.7.4; 4.3.3 p.84; 96 l.1132–1168; 307–330 |
The conformance model is strong for component services, roles, transactions and standards coverage, but it does not cle…The conformance model is strong for component services, roles, transactions and standards coverage, but it does not clearly require tests that clinically significant meaning survives an end-to-end transformation. FHIR validity and transaction success do not by themselves detect lossy mappings, altered status or certainty, missing provenance, or broken relationships between clinical concepts. Suggested revision: Extend semantic conformance testing to include preservation of provenance and authorship; status, certainty and negation; mandatory terminology bindings; units and reference systems; relationships among clinical concepts; absent/unknown/not-applicable distinctions; detection of lossy mappings; and professional review of clinically significant transformations. Include these checks in reusable reference test data and regression test packs where feasible. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | |
| PC-0258✎ edit📣 feedback | received | technical | Clinical ai |
3.4.4 Operational governance §3.4.4; 3.7.4; 5.4.2 p.56–57; 84; 108 l.334–362; 1132–1152; 154–169 |
Safe change management, testing and AI evaluation are discussed, but the guidance does not present an architecture-wide…Safe change management, testing and AI evaluation are discussed, but the guidance does not present an architecture-wide clinical digital safety lifecycle for safety-critical components, interfaces and data transformations. Technical conformance can be achieved while clinically hazardous behaviour remains unrecognised, especially where changes affect downstream systems or professional workflows. Suggested revision: Add a proportionate clinical digital safety lifecycle for safety-critical DPI-H capabilities and interfaces which are hazard identification, named clinical safety accountability, safety requirements and acceptance criteria, documented risk controls, pre-deployment testing, release approval, incident response, rollback, post-implementation monitoring and reassessment triggers when data sources, models, algorithms, interfaces, intended use or deployment context materially change. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | |
| PC-0259✎ edit📣 feedback | received | technical | Core architects ai |
5.2 Why data foundations determine what AI can deliver §5.2; 5.4.2 p.106; 108 l.71–84; 154–169 |
The draft correctly warns that an authoritative-looking answer may be difficult to distinguish from an unfounded one. T…The draft correctly warns that an authoritative-looking answer may be difficult to distinguish from an unfounded one. This is a factuality-versus-fluency problem, a clear, coherent and confident output is not evidence that it is accurate, complete or supported. The architecture does not yet specify how the epistemic status of generated or inferred information should be represented and preserved. Suggested revision: Require systems to distinguish visibly between a directly observed/measured data; professionally asserted or verified information; deterministically calculated information; probabilistically inferred information; and AI-generated narrative or synthesis. For outputs affecting care, eligibility, financing or public-health action, preserve source evidence, provenance, generating model and version, intended use, limitations, uncertainty where meaningful, validation/review status, and correction or withdrawal mechanisms. Do not treat fluency or a confidence score alone as proof of factuality. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-247 discuss | in the document all mentions on GitHub record | |
| PC-0260✎ edit📣 feedback | received | technical | Core architects ai |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.85–102 |
The distinction between authoritative deterministic services and model inference is valuable but currently presented as…The distinction between authoritative deterministic services and model inference is valuable but currently presented as an emerging AI pattern rather than an architecture-wide safety principle. Exact, governed rules and probabilistic inference have different assurance needs and should not be blended invisibly. Suggested revision: Elevate the principle, where a health-system function has an authoritative, exact or rule-bound answer- such as identity status, consent, units, eligibility, indicator definitions, reference calculations or authorisation- AI should invoke a governed deterministic service rather than recreate the result through inference. Reserve probabilistic methods for genuine uncertainty, preserve uncertainty explicitly, and keep inferred outputs distinguishable from authoritative facts and rules. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | |
| PC-0261✎ edit📣 feedback | received | technical | Core architects ai |
5.3 Where artificial intelligence can support the health system §5.3–5.4.2 p.107–108 l.109–169 |
The draft favours assistive AI and meaningful human oversight, but does not define non-delegable professional responsib…The draft favours assistive AI and meaningful human oversight, but does not define non-delegable professional responsibilities or controlled write-back rules. Generated summaries, recommendations and inferred data may become indistinguishable from source facts if written back without explicit status, review and accountability. Suggested revision: State that probabilistic or generated content must not silently overwrite authoritative source information or become indistinguishable from professionally verified facts. Require output provenance, model/version, timestamp, intended user and action, uncertainty, validation status, reviewing professional, audit history, override/correction and supersession. Identify non-delegable responsibilities proportionate to risk, including professional judgement, ethical reasoning, contextual interpretation, escalation, final authorisation where required, and accountability for material clinical-record changes. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-247 discuss | in the document all mentions on GitHub record | |
| PC-0262✎ edit📣 feedback | received | general | Core architects ai |
3.4.2 Governance principles §3.4.2–3.4.3; 5.4.3 p.54–56; 109 l.258–265; 299–327; 170–176 |
The draft addresses underserved populations, representation and unrepresentative AI data, but largely treats equity thr…The draft addresses underserved populations, representation and unrepresentative AI data, but largely treats equity through separate demographic or geographic categories. Systems may appear equitable in aggregate while performing poorly for people experiencing overlapping disadvantages, and some vulnerable populations may be missing from formal datasets altogether. Suggested revision: Operationalise intersectional equity across representation, access, performance and outcomes. Where lawful, proportionate and ethically justified, assess combinations of relevant characteristics and contexts- such as poverty, disability, language, geography, migration status, gender and digital exclusion- rather than only single-group averages. Require attention to missing populations, missing contextual meaning, cultural and linguistic fit, and community-defined priorities, while avoiding unnecessary collection of sensitive data. Distinguish measurable health inequalities from avoidable and unjust health inequities. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | |
| PC-0263✎ edit📣 feedback | received | technical | Core architects ai |
5.2 Why data foundations determine what AI can deliver §5.2; Appendix C- LHR; Appendix C- HMIS p.105–106; 161; 212–213 l.42–83; LHR requirement 16; 97–104; 159–167 anchor: low |
The architecture promotes capture-once/reuse-many-times and supports secondary use, but it does not provide a single as…The architecture promotes capture-once/reuse-many-times and supports secondary use, but it does not provide a single assurance pattern for the quality of source data or the governance of controlled analysis and outputs. Registries, routine reporting, dashboards and administrative datasets may otherwise be treated as ground truth without sufficient evidence of coverage, denominator quality, timeliness or validation. Suggested revision: Add data-source assurance requirements covering owner, provenance and lineage, reporting pathway, denominator, coverage, completeness, timeliness, representativeness, validation method, audit history and known limitations. For secondary use, require purpose approval, public-benefit assessment, proportionate de-identification, secure processing/access controls, complete audit trails, output checking, transparency, and governance of commercial and cross-border use. Clarify whether data reflect policy intent, system availability, actual use or verified implementation. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-252 discuss | in the document all mentions on GitHub record | |
| PC-0264✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3; 5.4.4; Appendix C- LIMR p.35; 109; 179 l.381–389; 177–194; LIMR governance items 3–7 anchor: medium |
The draft addresses open standards, model substitutability, national control and vendor lock-in. Whole-life assurance w…The draft addresses open standards, model substitutability, national control and vendor lock-in. Whole-life assurance would be stronger if it explicitly covered not only technical data portability but semantic portability, continuity of governed content, supplier exit and decommissioning. A country may possess its data but still be unable to interpret or safely migrate it if models, bindings, transformation logic or audit history are proprietary or incomplete. Suggested revision: Add procurement and lifecycle requirements for open/documented interfaces; export of data together with metadata, terminology versions and logical-model identifiers; portability of audit and provenance records; supplier performance and renewal checkpoints; cybersecurity patching; source-code escrow where proportionate; migration and decommissioning plans; continuity during supplier failure; and reassessment when contracts, models or intended uses materially change. Require semantic as well as technical portability. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | |
| PC-0265✎ edit📣 feedback | received | general | Core architects ai |
1.4 DPI-H Principles §1.4; 3.4.2–3.4.3 p.20; 54–56 l.394–410; 258–265; 279–289; 321–327 |
Public governance, privacy and inclusion are necessary foundations, but trust should not be presented as an automatic r…Public governance, privacy and inclusion are necessary foundations, but trust should not be presented as an automatic result of technical architecture or formal representation. Trust depends on clear and bounded purpose, understandable data use, visible safeguards, independent scrutiny, consistency between commitments and practice, and meaningful routes for people to question, correct or contextualise information. Health information should support two-way, context-aware communication rather than only top-down message delivery. Suggested revision: Add a trust and public-legitimacy principle stating that secure architecture enables but does not manufacture trust. Require transparent purpose and limits, plain-language and multilingual explanations of data flows and automated uses, health-literacy and accessibility considerations, published decision and access rules, feedback and redress mechanisms, community participation with real influence, communication of uncertainty, and the ability of patients, families, health workers and communities to question, correct or contextualise information. Periodically evaluate public and workforce experience. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-016 discuss | in the document all mentions on GitHub record | |
| PC-0266✎ edit📣 feedback | received | technical | Core architects ai |
3.4.4 Operational governance §3.4.4; 5.4.1–5.5 p.56–57; 108–110 l.359–362; 142–169; 209–223 |
The draft includes operational learning, AI evaluation and continuing stewardship, but the monitoring requirements are …The draft includes operational learning, AI evaluation and continuing stewardship, but the monitoring requirements are dispersed. Safety, bias and representational quality can degrade after deployment through data drift, model drift, workflow change, terminology updates, local adaptation and unintended use. Suggested revision: Define a continuous learning-and-monitoring capability across safety-critical DPI-H components, not only AI, post-deployment performance and bias surveillance, data/model drift detection, incident reporting, clinician and patient feedback, outcome monitoring, version control, change impact assessment, regression testing and governed system improvement. Learning should improve implementation without weakening the protected identity, provenance, semantic, authorisation and accountability requirements. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | |
| PC-0267✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5; Appendix F p.57–59; 241–250 l.373–442; Appendix F capability tables anchor: medium |
The Semantic Governance Infrastructure describes intake, review, publication, distribution and lifecycle management, bu…The Semantic Governance Infrastructure describes intake, review, publication, distribution and lifecycle management, but it does not provide a clear maturity pathway for creating new professional clinical content. There is a risk that a technically convened group could publish content before adequate evidence synthesis, professional/public consensus, clinical validation and implementation testing. Suggested revision: Add a non-prescriptive content-development pathway for new national or professional semantic assets which are evidence mapping; candidate definitions and inclusion/exclusion rules; multi-stakeholder consensus; clinical, public and technical validation; controlled pilot; publication and standards alignment; conformance testing; versioning; and long-term maintenance. The pathway should be proportionate to risk and should not imply that an individual author, vendor or technical team can declare a professional semantic standard unilaterally. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | |
| PC-0268✎ edit📣 feedback | received | technical | Core architects ai |
1.4 DPI-H Principles §1.4; 2.3; 3.6–3.7 p.20–21; 31–36; 71–86 l.368–421; architecture principles; interoperability and testing sections |
Identity, consent, time, authentication, provenance, audit, authorisation and accountability are addressed across the d…Identity, consent, time, authentication, provenance, audit, authorisation and accountability are addressed across the draft, but they are dispersed across principles and component requirements rather than declared as architecture-wide protected invariants. During mapping, transformation, aggregation, exchange or AI reuse, these properties may be weakened or stripped even when the transaction remains technically valid. Suggested revision: Define a small set of protected architecture-wide invariants that every DPI-H component, interface and transformation must preserve or explicitly and lawfully supersede which are identity and identity-resolution status; consent/permission; event time; source and authorship; provenance and lineage; authorisation/verification status; audit history; and accountable ownership. Require conformance and regression tests to detect alteration, loss or ambiguity of these invariants. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-017 discuss | in the document all mentions on GitHub record | |
| PC-0269✎ edit📣 feedback | received | general | Core architects ai |
3.4.7 Governance maturity considerations §3.4.7; 4.4.1–4.4.2 p.63; 98–100 l.Governance maturity considerations; progress and impact dimensions anchor: medium |
The maturity and progress sections focus appropriately on architecture coverage, conformance, governance capability and…The maturity and progress sections focus appropriately on architecture coverage, conformance, governance capability and outcomes. However, progress in infrastructure maturity- connectivity, exchange, security, access and platform coverage- may be mistaken for equivalent progress in how faithfully clinical and professional reality is represented. A system can exchange more data while still carrying incomplete or shallow meaning. Suggested revision: Measure infrastructure maturity and representational maturity as related but distinct dimensions. In addition to component coverage and technical conformance, assess whether priority clinical content is complete, professionally validated, semantically faithful, linked across the care process, usable at the point of care, and preserved during secondary use. Avoid treating the existence of a platform, profile or data flow as evidence that the underlying professional meaning is adequate. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | |
| PC-0270✎ edit📣 feedback | received | technical | Core architects ai |
C Appendix C: DPI-H Application Component Descriptions §3.5.2; 3.7; Appendix C p.65; 78–86; 114–228 l.Component-description template; conformance model; component functional requirements anchor: medium |
The draft specifies inputs, data objects, transactions and many component-specific outputs, and the CDSE has strong str…The draft specifies inputs, data objects, transactions and many component-specific outputs, and the CDSE has strong structured-output requirements. There is not yet a common output-specification pattern applied across all DPI-H components. Alerts, risk scores, summaries, dashboards, indicators, eligibility results, surveillance signals and patient messages may be technically generated but unsafe or unusable if the recipient, intended action, status, uncertainty and correction pathway are unclear. Suggested revision: Add a reusable output-contract requirement for components that generate information or recommendations. Each material output should specify its intended user and purpose; expected action; data structure, coding and status; source inputs and provenance; uncertainty/limitations where relevant; timeliness; downstream write-back rules; auditability; correction, override and withdrawal processes; and accountability for acting or not acting on the output. Include output-contract checks in conformance testing. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-063 discuss | in the document all mentions on GitHub record | |
| PC-0271✎ edit📣 feedback | received | general | Core architects ai |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2–4.5.3; 3.4.4–3.4.5 p.100–101; 56–59 l.Core roles and skills list; operational and semantic governance anchor: medium |
The draft correctly states that implementation fails for want of people and identifies specialist capabilities. The rol…The draft correctly states that implementation fails for want of people and identifies specialist capabilities. The role model would be stronger if it more explicitly connected architectural accountability with clinical/professional semantic stewardship, clinical digital safety, information governance, cybersecurity, public engagement and AI oversight. Without named ownership, these functions may be treated as temporary project input rather than sustained national capability. Suggested revision: Within the non-prescriptive role model, explicitly require accountable capability for national architecture; clinical/professional leadership; nursing and other domain semantic stewardship; data standards and terminology management; clinical digital safety; privacy/data protection; cybersecurity and resilience; AI/algorithm governance; public and community engagement; procurement/lifecycle assurance; and evaluation. Countries may combine roles, but decision rights, deputies, escalation routes and RACI-style (responsible, accountable, consulted, informed) responsibilities should be documented. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | |
| PC-0272✎ edit📣 feedback | received | general | Core architects ai |
1.3.3 Value Across Stakeholders §1.3.3; 1.5; 4.4; 4.5 p.19; 21–23; 98–101 l.329–366; 440–448; progress measures; capacity sections |
Reduced administrative burden and improved workforce capability are stated benefits, but workforce burden and socio-tec…Reduced administrative burden and improved workforce capability are stated benefits, but workforce burden and socio-technical fit are not consistently framed as required evidence of architecture success. Shared infrastructure can still introduce duplicate entry, new reconciliation work, alert fatigue, training burden, workflow disruption or dependence on scarce specialist staff, especially for nurses, midwives and community health workers. Suggested revision: Include workforce and implementation-burden measures in baselines and impact evaluation which are duplicate data-entry and reporting time; cognitive and alert burden; workflow fit; training and supervision needs; competence and deskilling risks; downtime/manual fallback capability; availability of local support; staff acceptability; and whether benefits are sustained after donor or project funding ends. Require co-design and validation with frontline users across different resource and service settings. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-014 discuss | in the document all mentions on GitHub record | |
| PC-0273✎ edit📣 feedback | received | technical | Clinical ai |
C Appendix C: DPI-H Application Component Descriptions §3.6.4; 4.3.1; Appendix C- LHR p.77; 94–95; 155–163 l.International Patient Summary discussion; minimum data models; LHR data requirements anchor: medium |
The use of the International Patient Summary as a meaningful minimum for cross-border exchange is valuable. However, a …The use of the International Patient Summary as a meaningful minimum for cross-border exchange is valuable. However, a generic patient summary may not contain the profession-specific or contextual meaning needed for continuity in every pathway. A minimum summary can become a ceiling if countries and implementers do not have governed extension rules and tests for preserving additional clinically essential content. Suggested revision: Clarify that IPS is a bounded shared minimum rather than a complete representation of care. Require governed national and professional extensions where necessary, without breaking the common core; document inclusion/exclusion rules and terminology bindings; and test that clinically significant content outside the base IPS- such as care needs, functional status, communication requirements, professional judgements, interventions and follow-up plans- can be preserved and exchanged when relevant. Robylin Tweetie Diya, RN, MSc Health Informatics (cand.), Independent reviewer; UK Registered Nurse; Health Informatics Specialist; Senior Systems Specialist (personal/professional capacity), United Kingdom |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | |
| PC-0274✎ edit📣 feedback | received | general | Core architects ai |
3.4.1 Purpose and framing §3.4 p.53-60 l.(Governance of Digital Health Architectures and DPI-H) anchor: medium |
The governance section establishes governance for digital health architectures but does not explicitly address governan…The governance section establishes governance for digital health architectures but does not explicitly address governance considerations for distributed AI operating across multiple institutions and jurisdictions. Suggested revision: As AI-enabled health systems increasingly operate across multiple organizations and jurisdictions, governance frameworks should address distributed intelligence environments in which data, models and decision-support capabilities may be developed, validated or updated collaboratively while remaining under decentralized institutional control. Governance arrangements should define accountability, oversight, transparency and lifecycle management across participating organizations. Chirag Tyagi, Vectorise Global Private Limited - DiagNXT, Bangalore, India |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0275✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.162 |
Insert new paragraph after L162 (Sec. 5.4.2)Insert new paragraph after L162 (Sec. 5.4.2) Suggested revision: “Where distributed intelligence approaches (for example, federated learning) are adopted, governance should extend beyond individual institutions to include mechanisms for model provenance, version control, auditability, validation across participating organizations, and clearly defined accountability for model performance, updates and retirement throughout the AI lifecycle.” Chirag Tyagi, Vectorise Global Private Limited - DiagNXT, Bangalore, India |
none | not yet | CS-125 discuss | in the document all mentions on GitHub record | |
| PC-0276✎ edit📣 feedback | received | technical | Core architects ai |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.183 |
The section discusses sovereign AI models but does not acknowledge privacy-preserving distributed learning approaches t…The section discusses sovereign AI models but does not acknowledge privacy-preserving distributed learning approaches that support collaborative model improvement while maintaining institutional data sovereignty. Suggested revision: In addition to nationally hosted AI models, consideration may also be given to privacy-preserving distributed learning approaches, such as federated learning, where appropriate. Such approaches enable collaborative model improvement across multiple organizations while allowing sensitive health data to remain within institutional or jurisdictional boundaries, supporting AI sovereignty, data protection and cross-institutional collaboration. Chirag Tyagi, Vectorise Global Private Limited - DiagNXT, Bangalore, India |
none | not yet | CS-125 discuss | in the document all mentions on GitHub record | |
| PC-0277✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §Lifelong Health Records p.157 l.3. (Core Attributes) |
The guidance supports structured clinical documentation but does not explicitly reference standardized HL7 FHIR resourc…The guidance supports structured clinical documentation but does not explicitly reference standardized HL7 FHIR resources for capturing computable clinical data at the point of documentation. Suggested revision: Add: “...including standardized HL7 FHIR resources (for example, Encounter and Observation), where appropriate.” Chirag Tyagi, Vectorise Global Private Limited - DiagNXT, Bangalore, India |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | |
| PC-0278✎ edit📣 feedback | received | technical | Core architects ai |
3.5.3 How the components are organised §3.5.3 (Figure 3.5) p.66 l.622-631; also Appendix C p. 118 line 179, Principle III (p. 32, lines 245-255) and Principle IX (p. 36, lines 415-418) |
The architecture is federated at the data layer: Principle III warns that centralised mediators create single points of…The architecture is federated at the data layer: Principle III warns that centralised mediators create single points of failure and concentrations of control. Trust is then assigned wholesale to the layer beneath. Figure 3.5 places National Trust Services, itemised as PKI, digital signatures, verifiable credentials, CA and GDHCN, in the foundational DPI layer, and Appendix C states the position plainly: the Client Registry may consume PKI services, 'but PKI is a foundational DPI component that sits outside the health sector'. The result is an asymmetry of specification. Each of the twelve components in Appendix C receives functional requirements carrying a SHALL, SHOULD or MAY status. The trust services on which all twelve depend receive one box in a figure and no requirements whatever. A ministry adopting this guidance can test whether its Health Workforce Registry conforms, but has nothing against which to test the national trust service that the registry's credentials rest on, and no statement of what to require if it must procure, inherit or build one. Suggested revision: State the properties a foundational trust service must exhibit to carry health-sector use, expressed as requirements on the interface between DPI-H and DPI-F, even though the implementation sits outside the health sector. At minimum: containment of compromise as Principle IX already requires; a defined key lifecycle that includes recovery and not only revocation; verifiability where connectivity is intermittent; delegation below national-authority level, so that an institution or a practitioner can be authenticated and not only an authority; and algorithm agility. Where an inherited national PKI cannot exhibit these properties, architectures built on self-certifying identifiers with verifiable key event logs (the Trust over IP KERI specification family, used as the basis of GLEIF's verifiable LEI and codified by ISO in ISO 17442-3:2024) satisfy several of them structurally and are worth naming as an admissible route. Their open questions belong in the same sentence: governance of witness infrastructure at national scale is unsettled, and no deployment exists at the scale of a national population of natural persons. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-076 discuss | in the document all mentions on GitHub record | |
| PC-0279✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 (Principle IX) p.35-36 l.392-427 |
Principle IX requires that compromise of any single component is contained rather than able to cascade (lines 407-408),…Principle IX requires that compromise of any single component is contained rather than able to cascade (lines 407-408), and directs the health sector to build on national trust infrastructure where it exists (lines 415-418). Neither the principle nor any other part of the document says what that infrastructure must do about keys. Generation, custody, rotation, revocation, recovery and algorithm agility are unaddressed throughout, and there is no trust-anchor-failure model, so the containment requirement cannot be tested against any candidate service. The gap is substantive rather than editorial, and the vocabulary of the mechanism the guidance points at shows why. RFC 5280 section 5.3.1 enumerates ten revocation reason codes and distinguishes superseded (4) from keyCompromise (1), but none of them expresses recovery from compromise. The single reversible state is certificateHold (6), lifted by removeFromCRL (8), which RFC 5280 scopes to a certificate that 'expired or was removed from hold' rather than to a keyCompromise revocation being undone. A practitioner or institution whose key is compromised and who then regains control can be represented only as permanently revoked. DigiNotar remains the reference case for what an uncontained trust-anchor failure costs a country. Suggested revision: State minimum key-lifecycle requirements and a trust-anchor-failure model, so that the containment requirement in Principle IX becomes testable rather than aspirational. Name the lifecycle states a national trust service must be able to represent, and include recovery from compromise among them and not revocation alone. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | |
| PC-0280✎ edit📣 feedback | received | technical | Core architects ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57-62 l.373-414; also Figure 3.5 (p. 66) |
Section 3.4.5 makes an argument that the guidance does not then apply to itself. Terminology services, it observes, can…Section 3.4.5 makes an argument that the guidance does not then apply to itself. Terminology services, it observes, cannot be relied on as runtime infrastructure unless the content they serve is governed, and the response is a full Semantic Governance Infrastructure with named roles, lifecycle and stewardship. The identical argument holds for trust: certificate and credential services cannot be relied on as runtime infrastructure unless the keys and credentials they serve are governed. Where semantics received a governance infrastructure, trust received an entry in Figure 3.5 and a referral out of the health sector. The asymmetry is a choice the draft makes rather than one it argues for, and a reader cannot tell from the text why semantic governance is health-specific while trust governance is inheritable. Suggested revision: Apply the reasoning of 3.4.5 to trust. Either describe a trust-governance function at comparable depth, covering identity issuance and verification for institutions and systems, key and credential lifecycle, revocation and recovery, audit-log integrity, and the roles that steward them; or state explicitly why trust governance, unlike semantic governance, can safely be inherited from outside the health sector, so that the reader can weigh that judgement instead of inferring it. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-076 discuss | in the document all mentions on GitHub record | |
| PC-0281✎ edit📣 feedback | received | technical | Clinical ai |
2.2.1 What REDDHI is and its foundational core §2.3 (Principle VIII) p.35 l.355-379; also Table 2.2 (p. 28) and Appendix C, Lifelong Health Record requirement 14 (p. 161) |
Consent is well grounded in the principles: Table 2.2 names a health-sector consent service with consent enforced at th…Consent is well grounded in the principles: Table 2.2 names a health-sector consent service with consent enforced at the point of data exchange; Principle VIII explains why the architecture does not set consent rules and anticipates a health-sector consent capability; the Lifelong Health Record is Required to integrate with consent management services (Appendix C, requirement 14). But the consent service named in Chapter 2 has no component specification. It is not among the twelve components of the Appendix C catalogue, so it has no functional requirements, no minimum data model and no conformance requirements, although every other load-bearing capability receives all three. The standards Chapter 2 points to, the IHE privacy and consent profiles and the HL7 FHIR Consent resource, are correspondingly absent from the component specifications. Suggested revision: Give the consent service a component specification, or assign the capability explicitly to a named component and cite the applicable standards in Appendix C. Address withdrawal semantics directly, including what becomes of authorisations already granted when consent is withdrawn after data has crossed an institutional boundary, and state whether that case is in scope for DPI-H at all. EHDS Article 71 (Regulation (EU) 2025/327) is instructive here: it gives natural persons a right to opt out of secondary use at any time, applicable from 26 March 2029 under the phased timetable in Article 105, and Article 71(3) expressly preserves data permits and health data requests issued or approved before the opt-out was exercised. Even the most developed consent regulation on the books therefore stops at the institutional boundary, which is precisely why a component specification should say how consent rules are versioned, distributed and made auditable between organisations that share no common operator, so that the question of which rules governed a given exchange remains answerable afterwards. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-235 discuss | in the document all mentions on GitHub record | |
| PC-0282✎ edit📣 feedback | received | technical | Core architects ai |
3.6.4 Cross-border health data flows §3.6.4 p.77-78 l.926-951 |
Section 3.6.4 contains the document's strongest normative trust statement: a cross-jurisdiction trust framework, with m…Section 3.6.4 contains the document's strongest normative trust statement: a cross-jurisdiction trust framework, with mutual recognition of identities, credentials and digital signatures underpinned by appropriate public-key infrastructure, shall establish that participants and the data they exchange can be trusted (lines 945-947). 'Appropriate' is undefined, and the GDHCN pattern cited immediately above verifies document provenance between national authorities; it does not authenticate live exchange participants, nor anything below authority level, such as a hospital verifying a foreign hospital or a clinician's role verified across a border. Suggested revision: Specify what 'appropriate' must include: mutual recognition below the national-authority level via verifiable delegation from authority to institution to practitioner, key lifecycle and revocation, offline verifiability, algorithm agility, and no single point of control. Delegated verifiable identifiers extend the authority-level trust the GDHCN already establishes down to institutions and practitioners under the same framework, without creating a supranational authority. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-076 discuss | in the document all mentions on GitHub record | |
| PC-0283✎ edit📣 feedback | received | technical | Core architects ai |
Health Facility Registry §Appendix C (Health Workforce Registry) p.138-141 l.Requirements 8 and 22; also Principle VII (p. 34, lines 336-340) and Chapter 5 lines 8-9 |
Workforce licence verification is specified as a synchronous online query against a central registry, invoked at the po…Workforce licence verification is specified as a synchronous online query against a central registry, invoked at the point of care and therefore availability-critical (Health Workforce Registry requirements 8 and 22). The same guidance recommends offline operation for the Lifelong Health Record, HMIS and surveillance components, and Principle VII requires that the absence of continuous connectivity reduce what is available rather than lock users out. These requirements conflict in exactly the low-connectivity settings the guidance prioritises. Chapter 5 names verifiable digital credentials as an emerging technology (lines 8-9) but never connects them to the workforce credentialing APIs in section 4.3.4, their most direct application. Suggested revision: Make the connection normative: a worker presents a cryptographically verifiable credential that verifies against cached trust state with no registry round-trip, with the registry acting as issuer and revocation anchor rather than as a synchronous verification dependency. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | |
| PC-0284✎ edit📣 feedback | received | technical | Core architects ai |
5.1 Emerging technologies and the foundations they depend on §Chapter 5 p.104-110 l.1-223 |
Chapter 5, Future proofing the Architecture, discusses AI, genomics, wearables and edge computing, but the document con…Chapter 5, Future proofing the Architecture, discusses AI, genomics, wearables and edge computing, but the document contains no mention of post-quantum cryptography or cryptographic agility anywhere in its 254 pages. NIST finalised its first post-quantum standards in August 2024 (FIPS 203, 204 and 205), and lifelong health records are a prime harvest-now-decrypt-later target: data exchanged today must remain confidential for the lifetime of the patient. The term is also used loosely in the field. Programmes that describe a key-rotation mechanism as post-quantum readiness are describing something materially different from migration to the standardised post-quantum algorithms, and joint WHO and ITU guidance is well placed to hold that distinction for countries evaluating vendor claims. Suggested revision: Add cryptographic agility as a design requirement for trust and exchange infrastructure: every participant must be able to migrate keys and algorithms without changing identifiers, breaking existing trust relationships, or coordinating a simultaneous global migration. Identifiers that commit to key digests rather than to a named algorithm allow the signing algorithm to change without re-establishing identity, which is what makes an unsynchronised national migration feasible at all. Ask countries to distinguish that architectural property from algorithm migration itself, and to require both. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | |
| PC-0285✎ edit📣 feedback | received | technical | Core architects ai |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.85-102; also 4.3.2 (p. 95, lines 289-291) and 5.4.2 (p. 108, lines 156-158) |
Section 5.2 helpfully anticipates AI agents invoking governed services, including via Model Context Protocol servers. I…Section 5.2 helpfully anticipates AI agents invoking governed services, including via Model Context Protocol servers. It specifies no model for how an agent authenticates to a service, how its authority is scoped and delegated from an accountable human or institution, or how its actions are attributed. Section 4.3.2 requires that actions recorded in a shared record be attributed to an identifiable actor, and section 5.4.2 requires accountability to identifiable people. Suggested revision: Require that agents carry verifiable, delegated identities whose authority chains to the responsible legal entity, so that cross-boundary agent actions remain attributable and revocable. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-120 discuss | in the document all mentions on GitHub record | |
| PC-0286✎ edit📣 feedback | received | technical | Core architects ai |
3.7.3 Alignment with IHE profiles §3.7.3 p.83-84 l.1118-1131; also 3.6.5 (p. 78, lines 955-959) |
The conformance model defers to IHE for interoperability testing, but names only the exchange profiles. The IHE securit…The conformance model defers to IHE for interoperability testing, but names only the exchange profiles. The IHE security and privacy profile family is not cited anywhere in the document: ATNA, IUA and XUA appear zero times against thirty-one occurrences of IHE. Section 3.6.5 wants vendor security claims testable before and during procurement, and the deferral mechanism of 3.7.3 is the natural place to make them so. Suggested revision: Name the IHE security and privacy profile family in the deferral mechanism of 3.7.3 alongside the exchange profiles. Audit Trail and Node Authentication (ATNA) and Cross-Enterprise User Assertion (XUA) are Final Text; Internet User Authorization (IUA) is still a Trial Implementation supplement, which is itself worth noting where a normative document defers to it; and the current successors in the same family are Basic Audit Log Patterns (BALP) and Privacy Consent on FHIR (PCF), the latter directly relevant to the consent gap raised elsewhere in this matrix. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-083 discuss | in the document all mentions on GitHub record | |
| PC-0287✎ edit📣 feedback | received | general | Core architects ai |
4.6.1 The Investment Case §4.6 p.102-103 l.547-600 |
Section 4.6 frames DPI-H as capital infrastructure with recurrent budget lines, but never itemises trust operations amo…Section 4.6 frames DPI-H as capital infrastructure with recurrent budget lines, but never itemises trust operations among them: identity issuance and verification, credential lifecycle, audit infrastructure, security operations. This is the cost class whose underfunding stays invisible until a breach, and the one that project-based donor funding historically drops first. Its absence is more consequential here than elsewhere, because the guidance also places trust services outside the health sector, so no budget holder in the sector is told to plan for them. Suggested revision: Name trust operations explicitly among the sustainability dimensions in 4.6.2 and the financing approaches in 4.6.3. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0288✎ edit📣 feedback | received | general | Core architects ai |
3.6.4 Cross-border health data flows §3.6.4 p.77-78 l.926-951; also Figure 3.5 (p. 66) and section 1.1.3 (pp. 10-12) |
WHO's Global Digital Health Certification Network appears twice: as an entry in the National Trust Services box of Figu…WHO's Global Digital Health Certification Network appears twice: as an entry in the National Trust Services box of Figure 3.5, and in the cross-border discussion of section 3.6.4. Neither states the relationship a country should expect between its own DPI-H trust services and GDHCN participation, and the distinction that matters most is left implicit. The GDHCN pattern establishes provenance for documents exchanged between national authorities. It does not authenticate live exchange participants, and it does not reach below authority level, so it does not address how a hospital verifies a foreign hospital, or how a clinician's role is verified across a border. A reader planning national trust infrastructure could reasonably take the Figure 3.5 entry to mean that GDHCN participation covers cross-border trust in general. Suggested revision: State in 3.6.4, and in 1.1.3 where the guidance discusses the foundations it builds on, what GDHCN participation does and does not provide, and how national DPI-H trust services are expected to relate to it. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-076 discuss | in the document all mentions on GitHub record | |
| PC-0289✎ edit📣 feedback | received | general | Core architects ai |
1.1.3 Building on existing foundations §1.1.3 p.11 l.102-113; also Figure 3.5 (p. 66) |
The section cites India's Aadhaar and CoWIN, alongside Estonia's X-Road, as evidence that health capabilities can be de…The section cites India's Aadhaar and CoWIN, alongside Estonia's X-Road, as evidence that health capabilities can be delivered at population scale by building on foundational DPI. The examples are apt for identity and service delivery. Research whose corresponding author is at the WHO South-East Asia Regional Office has since added a second and more cautionary chapter to the same case, and the guidance would be stronger for carrying it. An assessment of FHIR implementation in India (Jain et al., Preprints.org, 24 June 2026, DOI 10.20944/preprints202606.1791.v1) records that although the Ayushman Bharat Digital Mission is built on FHIR R4, it carries consent through a structured national construct, the MeitY Consent Artefact, 'instead of FHIR Consent' and rather than relying solely on SMART-on-FHIR patterns. The same paper records the omission of FHIR AuditEvent and Provenance resources and of OAuth2/OIDC scopes in patient-facing applications, and finds that ABDM certification 'primarily verifies connectivity (API availability, token flow) rather than data semantics'. This bears on the guidance directly, because OpenID and OAuth2 are the only identity-and-access standards Figure 3.5 names: the largest national programme built on that stack found it did not carry cross-institutional consent and engineered around it. The companion Sri Lanka baseline (Irfaan et al., DOI 10.20944/preprints202606.1768.v1) records that uncertainty over implementation of the Personal Data Protection Act 'creates hesitation among implementers regarding health data exchange, consent management, and legal liability'. Suggested revision: Cite both assessments where the guidance discusses existing foundations, and let the India case carry its full lesson: foundational identity infrastructure transferred well into health, while cross-institutional consent required a construct built outside the standards stack the same programme had adopted. Three cautions belong with the citation. Both papers are posted as preprints and are explicitly marked not peer-reviewed. Their author teams are largely Indian and Sri Lankan institutions with a WHO South-East Asia Regional Office corresponding author, so they are regional research rather than WHO position papers. And the MeitY artefact is itself gateway-mediated and operator-anchored, so the case evidences how hard it is to carry consent across institutional boundaries rather than validating any particular remedy. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-006 discuss | in the document all mentions on GitHub record | |
| PC-0290✎ edit📣 feedback | received | general | Core architects ai |
3.5.2 How each component is described §3.5.2 p.65-66 l.608-620; also pp. 80-81 lines 1036-1044 and Appendix C, Lifelong Health Record (p. 161) |
The guidance states that each component's requirements carry a status on a tiered model (SHALL, SHOULD, MAY) and that t…The guidance states that each component's requirements carry a status on a tiered model (SHALL, SHOULD, MAY) and that the component descriptions are intended for use in planning, procurement and conformance (lines 609-610 and 618). It never defines what those keywords oblige. There is no reference to RFC 2119, RFC 8174 or any equivalent conformance-language convention; the string 'RFC' does not occur in the document, and 'normative' occurs once, in a note on ArchiMate modelling. Two further vocabularies then run alongside the first. Appendix C uses 'Required' and 'Recommended' (the Lifelong Health Record specification on page 161 alone carries nine instances of 'shall', six of 'Required' and one of 'Recommended'), and lines 1036-1044 introduce 'mandatory' and 'optional' as a support qualifier mapped to the IHE required/optional designation. That passage carefully reserves 'required' for one sense and 'mandatory' for another, which shows the drafters were alert to exactly this ambiguity in one place while leaving it open in two others. For the ministries, DPI authorities and procurement teams named as the intended audience, whether 'Required' in Appendix C is advisory or contractual once a country adopts the guidance is a first-order question. Suggested revision: State the document's normative status explicitly in the front matter, and add a short conformance-language key that defines SHALL, SHOULD and MAY (RFC 2119 as updated by RFC 8174 is the usual reference) and reconciles all three vocabularies: the SHALL/SHOULD/MAY tiers, the Required/Recommended labels in Appendix C, and the mandatory/optional support qualifier. Say plainly whether the requirement tiers are advisory to countries, binding on implementations that claim conformance, or intended as procurement language that countries may adopt by reference. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | |
| PC-0291✎ edit📣 feedback | received | editorial | Editorial ai |
References §References p.111 l.n/a anchor: medium |
The references section is a placeholder: 'Reference list to be included before publication'. Substantive claims that ci…The references section is a placeholder: 'Reference list to be included before publication'. Substantive claims that cite the numbered reference list rather than inline footnotes cannot be checked without it. Suggested revision: Include the complete reference list in the next review round, not only in the final publication. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | |
| PC-0292✎ edit📣 feedback | received | editorial | Editorial ai |
Glossary §Glossary p.1-2 (front matter) l.n/a anchor: medium |
Several glossary entries are placeholders: 'Health Information Exchange' is marked to be included before publication, '…Several glossary entries are placeholders: 'Health Information Exchange' is marked to be included before publication, 'Repository' is empty, and several entries are marked under review. Suggested revision: Complete the glossary entries before publication; the Health Information Exchange definition matters because the main text deliberately avoids a central HIE component. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | |
| PC-0293✎ edit📣 feedback | received | editorial | Editorial ai |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4 p.96-97 l.339 and 369 |
Two consecutive sections are both numbered 4.3.4 (Integration Interfaces with Foundational DPI, and Interoperability Im…Two consecutive sections are both numbered 4.3.4 (Integration Interfaces with Foundational DPI, and Interoperability Implementation Pathways), which shifts the numbering of the following sections. Suggested revision: Renumber the second 4.3.4 and cascade the correction through 4.3.5 and the table of contents. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-097 discuss | in the document all mentions on GitHub record | |
| PC-0294✎ edit📣 feedback | received | editorial | Editorial ai |
1.2.1 Identity DPI and Identification in Healthcare §1.2 p.13-16 l.206, 223, 259 |
The body text refers to Box 2, Box 3 and Box 4, while the boxes themselves are labelled Box 1.2, Box 1.3 and Box 1.4.The body text refers to Box 2, Box 3 and Box 4, while the boxes themselves are labelled Box 1.2, Box 1.3 and Box 1.4. Suggested revision: Align the in-text references with the box labels. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-254 discuss | in the document all mentions on GitHub record | |
| PC-0295✎ edit📣 feedback | received | editorial | Editorial ai |
E Appendix E: Health Goals to DPI Mapping §Appendix E p.237-240 l.274 and 307 |
The goal-to-DPI mapping spreadsheets are referenced as placeholder tokens, for example [HG2_Health_Workforce_Mapping] a…The goal-to-DPI mapping spreadsheets are referenced as placeholder tokens, for example [HG2_Health_Workforce_Mapping] at line 274 and [HG3_Quality_Continuity_Care_Mapping] at line 307, and are not included in the review draft. They are the one artefact that would show which foundational-DPI trust and identity services each health goal depends on, which bears on several comments above. Suggested revision: Include the mapping spreadsheets, or a link to them, in the consultation materials so they can be reviewed. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-220 discuss | in the document all mentions on GitHub record | |
| PC-0296✎ edit📣 feedback | received | editorial | Editorial ai |
Supplier Registry §Appendix C (Supplier Registry) p.192 l.35-50 |
The passage on fragmentation appears twice in near-identical form, once as a prose paragraph and once as a bullet list,…The passage on fragmentation appears twice in near-identical form, once as a prose paragraph and once as a bullet list, both opening with 'This fragmentation has direct supply chain consequences'. Suggested revision: Remove the duplicate. Georg Greve, Vereign AG, Switzerland |
none | not yet | CS-194 discuss | in the document all mentions on GitHub record | |
| PC-0297✎ edit📣 feedback | received | general | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.388-392 |
The distinction between semantic governance and runtime services is well drawn, and the text correctly states that both…The distinction between semantic governance and runtime services is well drawn, and the text correctly states that both are mutually necessary. What remains less explicit is how an approved semantic-governance decision becomes a machine-checkable constraint on data instances at the point of use. Making that handoff explicit would strengthen the connection between governance and operational conformance. Suggested revision: Add a cross-reference stating that approved semantic constraints published through the SGI should be expressible in computable form and enforceable through runtime validation of data instances against the governed model. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-058 discuss | in the document all mentions on GitHub record | |
| PC-0298✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.58 l.406-408 |
The text observes that "governance without runtime services produces decisions that cannot be operationalised." The arc…The text observes that "governance without runtime services produces decisions that cannot be operationalised." The architecture would be strengthened by making explicit the mechanism by which approved governance decisions become enforceable on data instances: constraints made available in machine-checkable form and evaluated at runtime against the governed model. Suggested revision: After line 408, add: "Governance decisions become operational when the constraints they express are available in machine-checkable form and can be enforced through deterministic validation of data instances against the governed information model, so that conformance can be verified rather than assumed." Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-058 discuss | in the document all mentions on GitHub record | |
| PC-0299✎ edit📣 feedback | received | technical | Metadata registries ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 / Appendix C (LIMR) p.68 / 176 l.Table 3.5 (LIMR cell) / LIMR Req 10 |
Table 3.5 states LIMR definitions are "precise and unambiguous, leaving no room for reinterpretation by consuming syste…Table 3.5 states LIMR definitions are "precise and unambiguous, leaving no room for reinterpretation by consuming systems," yet the requirement that would guarantee this, LIMR Req 10 "model-driven validation of data instances," is marked Recommended. As drafted, the no-reinterpretation claim is an aspiration, not an enforced property. This is the single mechanism that turns the LIMR from a specification catalogue into an enforcement point. Suggested revision: Elevate LIMR Req 10 ("Conformance and validation support" / model-driven validation of data instances) from Recommended to Required. Align Table 3.5's "no room for reinterpretation" language to the enforced requirement. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | |
| PC-0300✎ edit📣 feedback | received | technical | Core architects ai |
3.7.2 The model §3.7 p.80 / 85 l.1011-1012 / 1188-1191 |
Conformance is claimed to be machine-checkable, but the verdict is "left implicit for now" and "not modelled as a disti…Conformance is claimed to be machine-checkable, but the verdict is "left implicit for now" and "not modelled as a distinct element." Because conformance claims, including those used in procurement, may drive consequential decisions, the result should be an explicit, persistent assessment that can be reviewed or re-verified after the fact. Suggested revision: Model the conformance verdict as an explicit, persistent assessment result together with sufficient provenance to identify the actor or test mechanism, specification and version tested, inputs, result, and timestamp. Where appropriate, established provenance standards such as W3C PROV may be used so that the assessment can be independently reviewed or re-verified. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | |
| PC-0301✎ edit📣 feedback | received | technical | Core architects ai |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 / Appendix C p.75 / 170,177 l.867-869 / TS Req 25, LIMR Req 16 anchor: low |
The architecture already requires strong auditability in several places, including a tamper-evident Lifelong Health Rec…The architecture already requires strong auditability in several places, including a tamper-evident Lifelong Health Record audit log that records the data affected by an event. However, audit evidence is generally retained as a property of the originating service or repository. In federated exchange, a downstream consumer may also need portable evidence of the governance or conformance decision that materially affected a particular data instance. Suggested revision: Consider a requirement for portable provenance or conformance evidence that identifies the relevant data instance or digest, decision, governing model or policy and version, actor or service, and timestamp, and that can be verified independently of the originating platform. Existing system audit logs would remain complementary. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-077 discuss | in the document all mentions on GitHub record | |
| PC-0302✎ edit📣 feedback | received | technical | Core architects ai |
3.6.4 Cross-border health data flows §3.6.4 / 3.5.3.1 / 4.3.4 p.78 / 67 / 98 l.911-912 / 638-640 / 385-388 |
The federated exchange model is anchored on shared standards and common identifiers from the core registries, while the…The federated exchange model is anchored on shared standards and common identifiers from the core registries, while the guidance also supports intermittent-connectivity and store-and-forward operation. In such settings, identifier use should not depend on uninterrupted access to a central registry, and locally assigned identifiers must be reconcilable without creating collisions or ambiguous identity links. Suggested revision: Add a requirement that identifier schemes used in federated or intermittently connected deployments support collision-resistant local assignment where needed, offline persistence of identifiers already issued, and deterministic reconciliation when connectivity is restored, without requiring uninterrupted access to a central registry. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | |
| PC-0303✎ edit📣 feedback | received | technical | Core architects ai |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.85-91, 99-102, 103-106 |
The section makes an important distinction between probabilistic inference and functions for which identical inputs sho…The section makes an important distinction between probabilistic inference and functions for which identical inputs should yield identical outputs. It also identifies machine-readable specifications and metadata as a developing readiness practice. This distinction could be strengthened without implying that all AI outputs should be deterministic. Suggested revision: State as a recommended AI-readiness practice that deterministic subtasks should, where feasible, be delegated to governed authoritative services, while machine-readable specifications and metadata should support automated discovery and interpretation of those services. Reserve probabilistic model inference for tasks that genuinely benefit from it. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | |
| PC-0304✎ edit📣 feedback | received | technical | Core architects ai |
3.6.2 Data and health content standards §3.6.2 / 4.3.3 p.74 / 96 l.822-827 / 318-322 |
The guidance already makes the important point that conformance to the same exchange standard does not guarantee semant…The guidance already makes the important point that conformance to the same exchange standard does not guarantee semantic interoperability when implementations extend it differently, and it recommends nationally governed minimum data models. The mechanism behind that observation is worth stating: conformance to an extensible base standard does not by itself guarantee conformance to the same governed semantic model, so where implementations use divergent profiles or extensions, or where exchanged instances are not validated against a shared governed profile at the exchange boundary, two systems may both be conformant to the base standard while remaining semantically incompatible. This principle could be strengthened by requiring machine-checkable conformance to that governed minimum at exchange boundaries, including assurance that local extensions do not alter or contradict the shared semantics required for national interoperability. As one openly documented implementation example of this broader pattern, the Semantic Data Charter (Axius SDC) combines standards-based structural constraints, provenance and deterministic validation; it is cited here as an implementation example, not as a proposed dependency of DPI-H. Suggested revision: Add a design principle to §3.6.2: "Local extensions may add context required by national or local use cases, but exchanged data should remain conformant to the nationally governed minimum model, and conformance should be machine-checkable at the exchange boundary so that local extensions do not alter or contradict the shared semantics required for interoperability." Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-070 discuss | in the document all mentions on GitHub record | |
| PC-0305✎ edit📣 feedback | received | technical | Metadata registries ai |
F Appendix F: Semantic Governance Infrastructure: capability details §3.4.5 / Appendix F p.62 / 242 l.492-494 / Table F (Authoring/publication) anchor: medium |
Appendix F's "Business Rule Enforcement" capability validates that authoring and publication actions conform to governa…Appendix F's "Business Rule Enforcement" capability validates that authoring and publication actions conform to governance policy. The detailed SGI capability set does not explicitly include runtime enforcement of governed constraints on data instances. That distinction matters because governance of an artefact does not by itself ensure that data produced or exchanged against that artefact conforms to it. Suggested revision: Add a capability under a suitable SGI category (e.g. Consumption or Monitoring): "Runtime constraint enforcement — machine-checkable validation of data instances against the applicable governed model at the point of use, distinct from authoring and publication governance." Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-232 discuss | in the document all mentions on GitHub record | |
| PC-0306✎ edit📣 feedback | received | general | Metadata registries ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 / Appendix C (LIMR) p.69 / 179 l.Table 3.5 / GOVERNANCE (3) |
The architecture already provides strong model and terminology versioning, lifecycle states, version-specific bindings …The architecture already provides strong model and terminology versioning, lifecycle states, version-specific bindings and backwards-compatibility policies. One additional permanence property could be stated explicitly: historical data should remain independently interpretable and validatable against the exact model and terminology versions that governed it when created. This is especially important for longitudinal records such as the Lifelong Health Record. Suggested revision: Add a principle: "Data validated against the version of a model and terminology binding in force at its creation remains independently interpretable and validatable against those versions thereafter; model evolution must not retroactively invalidate conformant historical data." Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | |
| PC-0307✎ edit📣 feedback | received | general | Core architects ai |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.94-95 l.257-273 |
This section ("the most consequential implementation decision … is … what data to capture and how to structure it") is …This section ("the most consequential implementation decision … is … what data to capture and how to structure it") is a strong, correct anchor and aligns the whole implementation chapter with a data-models-first approach. Recommend surfacing it earlier (it is the practical core of the guidance) and cross-referencing it from §3.4.5 and §3.6.1 so the architecture and implementation halves reinforce the same principle. Suggested revision: Add a forward reference from §3.4.5 and §3.6.1 to §4.3.1, and consider elevating the "data models first" principle into the Chapter 3 architecture narrative, not only the implementation chapter. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | |
| PC-0308✎ edit📣 feedback | received | editorial | Editorial ai |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4 p.96 / 97 l.339 / 369 |
Two distinct subsections are both numbered 4.3.4 ("Integration Interfaces with Foundational DPI" on p.96 and "Interoper…Two distinct subsections are both numbered 4.3.4 ("Integration Interfaces with Foundational DPI" on p.96 and "Interoperability Implementation Pathways" on p.97). Suggested revision: Renumber the second to 4.3.5 and cascade subsequent numbers (current 4.3.5 "Minimum Conformance and Testing" becomes 4.3.6). Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-097 discuss | in the document all mentions on GitHub record | |
| PC-0309✎ edit📣 feedback | received | editorial | Editorial ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.650-651 |
Sentence ends in a dangling, incomplete fragment: "…rather than implying a single central store. person-centred that" (…Sentence ends in a dangling, incomplete fragment: "…rather than implying a single central store. person-centred that" (line 651 blank). Suggested revision: Complete or delete the trailing fragment. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-060 discuss | in the document all mentions on GitHub record | |
| PC-0310✎ edit📣 feedback | received | editorial | Editorial ai |
References §References p.111 l.(page body) anchor: medium |
The References page contains only "[Reference list to be included before publication]." Flagging for completeness; seve…The References page contains only "[Reference list to be included before publication]." Flagging for completeness; several normative claims (e.g. standards selections, OpenHIE alignment) will need citation before publication. Suggested revision: Populate the reference list before publication; ensure standards and prior-art claims (HL7 UTG, OpenHIE, SNOMED NRC, IHE) are cited. Timothy W. Cook; Luciana Cavalini, MD, PhD (co-author), Axius SDC, Inc., United States (Cook); Brazil (Cavalini) |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | |
| PC-0311✎ edit📣 feedback | received | general | Clinical ai |
1.2.2 Data exchange DPI and Interoperability in the health sector §1.3 p.8 l.Lines 210–220 anchor: medium |
As currently framed, the guidance prioritizes technical data transmission capability without explicitly linking exchang…As currently framed, the guidance prioritizes technical data transmission capability without explicitly linking exchange to clinical-economic workflow resolution. Data exchange is clinically and economically neutral without clinical transaction resolution. In both high- and low-resource settings, the highest leverage lies in managing treatment adherence and preventing chronic disease progression (e.g., managing hypertension and early-stage kidney disease to avoid stroke or end-stage renal disease). Unclosed care loops create administrative noise, increase clinical burden, and result in a net-negative return on public infrastructure investment. Suggested revision: Insert under Section 1.3 (Design Principles): “As a core design principle, DPI-H should prioritize the clinical-economic resolution of workflows alongside technical data exchange. The architecture should be designed to deliver system-level clinical outcomes and prevent chronic disease progression (such as tracking medication adherence to prevent stroke, managing early-stage chronic kidney disease to avoid end-stage renal disease, and supporting hypertension treatment control) rather than optimizing for technical transmission capability alone.” Karim Keshavjee, Institute for Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada |
none | not yet | CS-256 discuss | in the document all mentions on GitHub record | |
| PC-0312✎ edit📣 feedback | received | technical | Clinical ai |
3.7 Conformance and Testing across Architecture and Components §Chapter 3 l.Conformance & Testing anchor: medium |
Maturity models and compliance checklists that evaluate technical exchange capability alone create a structural blind s…Maturity models and compliance checklists that evaluate technical exchange capability alone create a structural blind spot. A health system can achieve high technical standards conformance (e.g., FHIR profile compliance) while front-line care coordination remains stagnant or decays. Without an operationalized metric for transaction resolution, national architectures cannot verify whether clinical value is being generated. Suggested revision: Add to conformance and performance metrics guidance: “The performance evaluation framework for DPI-H should recommend Loop-Closure Rates as the primary success metric for national digital infrastructure. A transaction (such as a referral, prescription, or diagnostic order) is only considered successful when it closes securely at both endpoints of the clinical workflow, with transactional visibility provided to the patient.” Karim Keshavjee, Institute for Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada |
none | not yet | CS-256 discuss | in the document all mentions on GitHub record | |
| PC-0313✎ edit📣 feedback | received | general | Core architects ai |
4.6 Financing and Partnerships §Chapter 5 l.Operational Financing anchor: low |
Health systems chronically overspend on initial builds and underspend on ongoing operations. Without dedicated, recurri…Health systems chronically overspend on initial builds and underspend on ongoing operations. Without dedicated, recurring operational funding to manage software version alignment, continuous semantic normalization, local code mapping, and compliance auditing, shared national infrastructure inevitably degrades back into fragmented, non-comparable silos once short-term capital grants run out. Suggested revision: Add to guidance on financing: “Guidance on financing must explicitly distinguish between Initiation (Capital Build) and Maintenance (Ongoing Run-Rate) phases. Guidelines should advise member states that any capital investment in DPI-H components should be tethered to a secured, recurring operational maintenance budget to prevent system divergence and technological decay.” Karim Keshavjee, Institute for Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0314✎ edit📣 feedback | received | general | Core architects ai |
4.6.1 The Investment Case §Chapter 5 l.Sustainability & Business Case anchor: low |
Sustaining a high-performing digital public infrastructure requires continuous, long-term operational funding to preven…Sustaining a high-performing digital public infrastructure requires continuous, long-term operational funding to prevent system drift. This funding is only politically and economically defensible if it is mathematically justified by the avoidance of high-cost clinical complications. Treating operational maintenance as an isolated IT cost center makes infrastructure vulnerable to budget cuts that trigger technical decay. Suggested revision: Add to investment case guidance: “Guidelines should instruct member states to explicitly link recurring operational IT maintenance budgets to the clinical-economic savings realized through coordinated chronic disease management. Rather than treating maintenance as an isolated IT expense, the operational business case should demonstrate how closed clinical loops prevent high-cost disease endpoints—such as avoiding costly dialysis regimens through early-stage glycemic and blood pressure control.” Karim Keshavjee, Institute for Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada |
none | not yet | CS-116 discuss | in the document all mentions on GitHub record | |
| PC-0315✎ edit📣 feedback | received | technical | Clinical ai |
The Reference Architecture for DPI-H §Chapter 3 / Chapter 5 l.Adoption Layer anchor: low |
Relying solely on clinician workflows to drive adoption and ensure treatment adherence is often insufficient. Without t…Relying solely on clinician workflows to drive adoption and ensure treatment adherence is often insufficient. Without transactional visibility, patients remain passive subjects rather than active drivers of their own care loops. In chronic disease management (such as hypertension or diabetes), activating the patient as an active participant introduces a vital layer of systemic accountability and catches errors before they cause irreversible harm. Suggested revision: Add to adoption layer guidance: “The DPI-H framework should recommend patient-visible loop closure and real-time transaction receipts as a core component of the adoption layer. Rather than treating patient portals as optional, passive viewing panes, the guidelines should encourage architectures that automatically send active transactional notifications to patients—such as alerts when a chronic disease prescription is filled or missed, or confirmations when a critical referral loop has closed.” Karim Keshavjee, Institute for Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada |
none | not yet | CS-256 discuss | in the document all mentions on GitHub record | |
| PC-0316✎ edit📣 feedback | received | editorial | Editorial ai |
unplaced §Whole of document |
I found this highly technical. I suggest summarising the key points for each chapter and leaving technical details and …I found this highly technical. I suggest summarising the key points for each chapter and leaving technical details and worked examples to Annexes Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-284 discuss | all mentions on GitHub record | |
| PC-0317✎ edit📣 feedback | received | editorial | Editorial ai |
unplaced §Whole of document |
For readability I suggest limiting paragraphs to 3-4 sentences. Make a point and use next paragraph to provide a contex…For readability I suggest limiting paragraphs to 3-4 sentences. Make a point and use next paragraph to provide a context or example Suggested revision: Example of one instance (blank lines have been left here to demonstrate the point but not expecting blank lines in the final document) Line 102 DPI has demonstrated impact in countries and catalysed ecosystem innovation across sectors. Foundational DPI for identity, data exchange and digital payments — exemplified by India's Aadhaar digital identity, Brazil's Pix instant payments, and Estonia's X-Road data exchange layer — have shown tremendous value as shared infrastructure that can be leveraged by multiple sectors. The health sector has been a direct beneficiary in some countries; for example, in India, the COVID-19 vaccination platform CoWIN was built on the existing Aadhaar identity infrastructure for beneficiary verification, helping deliver over one billion vaccine doses within nine months and reaching more than 940 million registered users. In Estonia, the national health information system — which since 2008 has maintained a longitudinal electronic health record for every resident — runs on the same X-Road data exchange layer used across all public services, while citizens access their records through the national digital identity (IDcard or Mobile-ID) rather than a health-specific credential . Together these cases show how health-specific capabilities can be delivered at population scale by leveraging foundational DPI, rather than building parallel identity, data-exchange or payment systems for health alone. The health sector however, while not being unique in its ability to leverage foundational DPI, possesses some unique requirements that have not yet been articulated to enable it to effectively leverage these foundational components. This guidance articulates the explicit health-sector requirements that foundational DPIs would need to satisfy in order to contribute to health sector goals. Additionally, this reference architecture recognises that the health sector possesses some components that can be shared and reused across different programmes in the health sector, components that can be described as health DPIs (DPI-H). It also articulates the explicit requirements that the “health DPIs” would need to satisfy in order to contribute to health sector goals. Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-284 discuss | all mentions on GitHub record | |
| PC-0318✎ edit📣 feedback | received | general | Metadata registries ai |
unplaced §Whole of document |
Why is WHO not recommending all three of their own Family of International Classifications as core data standards? ICD-…Why is WHO not recommending all three of their own Family of International Classifications as core data standards? ICD-11, ICHI and ICF. All three classifications now also have a terminological common foundation. I would also recommend including ICD-O as well. Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-278 #17 | all mentions on GitHub record | |
| PC-0319✎ edit📣 feedback | received | general | WHO ai |
unplaced §Whole of document |
Why were the WHO committees for classifications and terminologies not consulted in the development of this document esp…Why were the WHO committees for classifications and terminologies not consulted in the development of this document especially the Informatics and Terminologies Committee of the WHO-FIC Network? Before this architecture document is finalised further consultation must be undertaken with relevant committees and reference groups to garner subject matter expert input. Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | none | all mentions on GitHub record | |
| PC-0320✎ edit📣 feedback | received | technical | Metadata registries ai |
unplaced §Whole of document |
The document speaks of open standards – but SNOMED and LOINC both require licensing agreements to be in place. This see…The document speaks of open standards – but SNOMED and LOINC both require licensing agreements to be in place. This seems contradictory Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-277 discuss | all mentions on GitHub record | |
| PC-0321✎ edit📣 feedback | received | editorial | Editorial ai |
Acronyms §Acronyms and Glossary anchor: low |
The WHO-FIC classifications ICD, ICHI and ICF are not in the acronym list nor the glossary and should beThe WHO-FIC classifications ICD, ICHI and ICF are not in the acronym list nor the glossary and should be Suggested revision: Descriptions of these classifications are on the WHO website Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-131 discuss | in the document all mentions on GitHub record | |
| PC-0322✎ edit📣 feedback | received | editorial | Editorial ai |
Acronyms §Acronyms and Glossary anchor: low |
API is not in the acronym list nor the glossaryAPI is not in the acronym list nor the glossary Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-131 discuss | in the document all mentions on GitHub record | |
| PC-0323✎ edit📣 feedback | received | editorial | Metadata registries ai |
Glossary §Acronyms and Glossary |
The glossary should also explain what a health classification and a health terminology is (and the difference between t…The glossary should also explain what a health classification and a health terminology is (and the difference between them) Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | |
| PC-0324✎ edit📣 feedback | received | editorial | Editorial ai |
Glossary §Acronyms and Glossary |
The glossary has no definition for “Repository”The glossary has no definition for “Repository” Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | |
| PC-0325✎ edit📣 feedback | received | editorial | Editorial ai |
Acronyms §Acronyms and Glossary anchor: low |
The document refers to TOGAF and Archimate but no glossary information as to what they are and the acronym TOGAF is not…The document refers to TOGAF and Archimate but no glossary information as to what they are and the acronym TOGAF is not in list, nor expanded until quite a way into the document (page 10), Archi is explained in a footnote on page 42. Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-131 discuss | in the document all mentions on GitHub record | |
| PC-0326✎ edit📣 feedback | received | editorial | Metadata registries ai |
unplaced §Whole of document |
I find it interesting that the document refers to the WHO Digital Adaptation Kits as an example of centralised metadata…I find it interesting that the document refers to the WHO Digital Adaptation Kits as an example of centralised metadata – but these are developed in silos and have no communal metadata repository or even standard definitions of common data elements (I work on these directly so am aware of several of their content and design). I would even suggest that WHO consider to engage the AIHW to build and maintain their DAK metadata in our metadata repository METEOR (it would need to be a funded project of course) METEOR can be found at www.https://meteor.aihw.gov.au Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-282 discuss | all mentions on GitHub record | |
| PC-0327✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary l.2 anchor: medium |
Countries are unlikely to achieve their health goals through investing in isolated or siloed health 3 systems. Instead,…Countries are unlikely to achieve their health goals through investing in isolated or siloed health 3 systems. Instead, they should build shared data and digital capabilities that support multiple 4 programmes, multiple diseases and multiple levels of care.” They should also multiple locations of care Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0328✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §Executive summary l.31 anchor: medium |
Line 31 – first use of TOGAF and Archimate – with no information as to what they areLine 31 – first use of TOGAF and Archimate – with no information as to what they are Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-001 discuss | in the document all mentions on GitHub record | |
| PC-0329✎ edit📣 feedback | received | editorial | Core architects ai |
1.2.1 Identity DPI and Identification in Healthcare §Chapter 1 p.14 l.209 anchor: medium |
coverage gaps (pg 14 line 209). Newborns are managed in Australia in the HIS as “baby of” before formal civil registrat…coverage gaps (pg 14 line 209). Newborns are managed in Australia in the HIS as “baby of” before formal civil registration, there are mechanism for identifying individuals before formal registration or identification ie “Jane Doe” and “John Doe” which may not grammatically be applicable in all countries but a mechanism is possible Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-009 discuss | in the document all mentions on GitHub record | |
| PC-0330✎ edit📣 feedback | received | editorial | Core architects ai |
1.2.2 Data exchange DPI and Interoperability in the health sector §Chapter 1 l.Section 1.2.2 anchor: low |
actors need to also include clinical coders and data analystsactors need to also include clinical coders and data analysts Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | |
| PC-0331✎ edit📣 feedback | received | editorial | Core architects ai |
1.2.3 Payments DPI and financial transactions in the health sector §Chapter 1 anchor: low |
there seems to be a big focus on data for funding (ie section 1.2.3) and worked example 2.4.2, but this is a secondary…there seems to be a big focus on data for funding (ie section 1.2.3) and worked example 2.4.2, but this is a secondary use case for health data. First use case should be population health statistical outputs. Suggested revision: For example they could reference the ICD-11 reference guide and use something similar to “Health data systems need to be designed to address the needs of a broad range of use cases, such as: causes of death, morbidity, epidemiology, casemix (Diagnosis-Related Groups (DRG)), quality and patient safety, primary care, functioning assessment, research, prevention, substance (medication) or device safety, specific surveillance like antimicrobial resistance (AMR), cancer registration, injury research, as well as ensuring semantic interoperability for clinical documentation, decision support and guidelines or recommendations.” Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-012 discuss | in the document all mentions on GitHub record | |
| PC-0332✎ edit📣 feedback | received | editorial | Clinical ai |
1.3.3 Value Across Stakeholders §Chapter 1 p.329 l.Section 1.3.3 anchor: medium |
we would like to have included some content around data to measure patient outcomes not just condition treated and serv…we would like to have included some content around data to measure patient outcomes not just condition treated and service provided Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-014 discuss | in the document all mentions on GitHub record | |
| PC-0333✎ edit📣 feedback | received | editorial | Editorial ai |
1.5.1 The Health Sector Goals §Chapter 1 p.508 |
The outcomes these goals describe are not automatic. The extent to which they are realised depends on the quality of im…The outcomes these goals describe are not automatic. The extent to which they are realised depends on the quality of implementation and the context in which it takes place; evidence to date shows that benefits anticipated in design are not always borne out in practice.” It also depends on the extent of implementation Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | |
| PC-0334✎ edit📣 feedback | received | editorial | Core architects ai |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §Chapter 2 anchor: medium |
Would prefer a word example showing health service management and accountabilityWould prefer a word example showing health service management and accountability Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-287 discuss | in the document all mentions on GitHub record | |
| PC-0335✎ edit📣 feedback | received | editorial | Metadata registries ai |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §Chapter 4 p.505 l.Section 4.5.2 anchor: medium |
“Terminology and semantic specialists, who curate value sets, code systems, and mappings (for example to SNOMED CT/GPS,…“Terminology and semantic specialists, who curate value sets, code systems, and mappings (for example to SNOMED CT/GPS, ICD-11, and LOINC) and operate the semantic governance processes”. They also need to maintain the value sets and mappings as the classifications and terminologies evolve. Metadata is not a “set and forget” process. Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | |
| PC-0336✎ edit📣 feedback | received | No human |
Future proofing the Architecture §Chapter 5 |
AI use – we would like a broader discussion across our national agencies before commenting on this chapterAI use – we would like a broader discussion across our national agencies before commenting on this chapter Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0337✎ edit📣 feedback | received | technical | Metadata registries ai |
D Appendix D: Country and Regional Implementation Examples §Appendix D l.Australian note anchor: medium |
Ontoserver is not the only national terminology service in Australia – it has a specific use case and owner. Perhaps ad…Ontoserver is not the only national terminology service in Australia – it has a specific use case and owner. Perhaps add more detail as to the scope of use for Ontoserver for transparency. Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-204 discuss | in the document all mentions on GitHub record | |
| PC-0338✎ edit📣 feedback | received | technical | Metadata registries ai |
D Appendix D: Country and Regional Implementation Examples §Appendix D l.Australian note anchor: medium |
The description in the document of the Australian system In Appendix D is lacking many components and seems to be SNOME…The description in the document of the Australian system In Appendix D is lacking many components and seems to be SNOMED focused only. The NCTS predominantly focuses on SNOMED CT AU, other health classifications are managed by other agencies (eg IHACPA for ICD-10-AM, ACHI and other ABF classifications). Suggested revision: • We agree that centralised metadata repositories are the best practice – ie METEOR at the AIHW • We agree that information regarding a patient should be accessible across multiple service providers – ie My Health Record • We agree that silo’d systems are problematic – ie why the AIHW created NHDH • We agree that when transition all existing systems need to be reviewed and possibility updated to ensure consistent metadata use and development - this is why we have the Australian ICD-11 Task Force with all agencies, states and jurisdictions involved • We agree that metadata should be based in internationally developed classification and terminology standards - ADHA maintain a reference library of digital standards including health classifications and terminologies • We agree that a classifications / terminology service should have the governance over the content used for metadata – ie AIHW have the NHDISC, CSIRO has the NCTS and IHACPA have their committees and technical groups • We agree that governance should be appropriate to the service ie in Australia the ABS has legislated governance for mortality, IHACPA has legislated governance for activity based funding, CSIRO has governance for SNOMED CT AU (CSIRO), and the ACC is the central agency for contributions to the WHO-FIC classifications, and ADHA / DHDA look at whole of government coordination Filippa Pretty, Australian Collaborating Centre for WHO-FIC, Australia |
none | not yet | CS-204 discuss | in the document all mentions on GitHub record | |
| PC-0339✎ edit📣 feedback | received | general | Core architects ai |
unplaced §Whole document |
The guidance needs to have a clear articulation of what an Enterprise Architecture (EA) is and how this guidance is int…The guidance needs to have a clear articulation of what an Enterprise Architecture (EA) is and how this guidance is intended to fit or complement that. Given many countries are newly developing Digital Health strategies and an Enterprise Architecture is a key component, muddling DPI-H, Enterprise Architecture, and Registries in this document will be very confusing. In places this document reads as an approach to developing an Enterprise Architecture, in other places it frames DPI-H as a registry-specific layer within the EA. Suggested revision: Agree on a clear position and framing for how this guidance fits into or complements an Enterprise Architecture, as otherwise we are adding to existing confusion regarding registry layers within EA by throwing a new "DPI-H" concept at Ministries of Health who have largely been socialized and encouraged to develop EAs and master facility lists most recently. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-042 discuss | all mentions on GitHub record | |
| PC-0340✎ edit📣 feedback | received | general | Editorial ai |
unplaced §Whole document (esp. Chapters 1, 2, 4, 5) p.n/a l.n/a |
ArchiMate/TOGAF terms like "capability" and "application component" are used from page 8 onward, but the notation isn't…ArchiMate/TOGAF terms like "capability" and "application component" are used from page 8 onward, but the notation isn't actually explained until page 42 (Section 3.1). Chapters 1, 2, and 4 are meant for non-technical readers too (ministries, donors, procurement), so this makes the early chapters harder to follow than they need to be. Suggested revision: Move a short version of the Section 3.1 notation table earlier, right after the glossary, or use plainer language in Chapters 1, 2, and 4 and save the formal terminology for Chapter 3 and the Appendix C component descriptions. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-039 discuss | all mentions on GitHub record | |
| PC-0341✎ edit📣 feedback | received | Core architects ai |
unplaced §Whole document |
This is an incredibly long and difficult to digest document. I assume some of this will come as the document will be fi…This is an incredibly long and difficult to digest document. I assume some of this will come as the document will be finalized, but please consider: - an executive summary - a simpler reference architecture diagram - either instead of or in addition to the full diagram 3.2. There are many aspects there that are not critical to implementing DPI-H - a simpler enterprise architecture diagram that guides chapter 4 (as a subset of the full DPI-H reference architecture) - reducing the background, introductory, explanatory text throughout - some of these feel like "filler" content and could be shorter Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-284 discuss | all mentions on GitHub record | ||
| PC-0342✎ edit📣 feedback | received | technical | Core architects ai |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §1.2 (and other sections) p.10 l.66-70 anchor: low |
The proposed relationship between foundational DPIs and DPI-Hs is unclear. The para talks about "extending" "complement…The proposed relationship between foundational DPIs and DPI-Hs is unclear. The para talks about "extending" "complementing" "building upon" and "integration with". Could the recommended approach for this relationship be clarified - here and throughout the document. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-007 discuss | in the document all mentions on GitHub record | |
| PC-0343✎ edit📣 feedback | received | general | Core architects ai |
1.3.1 The Cost of Fragmentation §1.3.1 p.17 l.265 onwards anchor: medium |
Is it possible to quantify the cost of fragmentation? we have some data on the extent of fragmentation in a few countri…Is it possible to quantify the cost of fragmentation? we have some data on the extent of fragmentation in a few countries (# overlapping systems, #systems per health area, etc.) that we assessed with MOHs in few countries that we would be happy to share for this (with MOH permission) if helpful Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-013 discuss | in the document all mentions on GitHub record | |
| PC-0344✎ edit📣 feedback | received | technical | Core architects ai |
2.2.2 The enabling conditions for REDDHI §2.2 p.29 l.160-161 |
The 'full-STAC' framework, which defines REDDHI's enabling conditions, is grounded in a single cited peer-reviewed pape…The 'full-STAC' framework, which defines REDDHI's enabling conditions, is grounded in a single cited peer-reviewed paper rather than a broadly ratified standard or multi-source consensus term. Suggested revision: Either cite additional corroborating sources for full-STAC, or clarify that it is a proposed framework from this specific paper rather than an established cross-body consensus term. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | |
| PC-0345✎ edit📣 feedback | received | general | Core architects ai |
2.2.1 What REDDHI is and its foundational core §2.2. (and other sections) p.27 anchor: medium |
What is the difference between REDDHI and DPI-H? Could we just stick to one terminology (ideally DPI-H, given how commo…What is the difference between REDDHI and DPI-H? Could we just stick to one terminology (ideally DPI-H, given how commonplace the understanding and use of the term DPI is) even if we don't think it encompasses everything? Suggested revision: Use DPI-H consistently throughout the document, and remove references to REDDHI. OR clarify how they relate or are different from each other Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | |
| PC-0346✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.32 l.240–249 |
The principle's caution against 'a single centralised mediator' is a substantive architectural position, but no country…The principle's caution against 'a single centralised mediator' is a substantive architectural position, but no country implementation example is cited to demonstrate it in practice, and the trade-offs relative to well-run centralised HIE/mediator models (in use in many current national health information exchanges) are not discussed. Suggested revision: Cross-reference a relevant Appendix D country example illustrating distributed/federated mediation working in practice, or acknowledge the governance-coordination trade-offs of decentralisation more explicitly. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | |
| PC-0347✎ edit📣 feedback | received | technical | Financial systems ai |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2 (table 2.4) p.39 l.507-520 |
The financing capability list covers coverage, provider credentialing, benefit rules, pricing and payment movement. It …The financing capability list covers coverage, provider credentialing, benefit rules, pricing and payment movement. It leaves out the budget cycle: planning and formulating health budgets, executing them, and tracking expenditure against them. In a number of LMICs health is financed through budget appropriations/allocations rather than claims, so the budget cycle is where the bottleneck often lies. Suggested revision: Add rows to Table 2.4 for budget planning and allocation, budget execution, and expenditure tracking, and what potential supports could be for each. If the mapping is deliberately scoped to purchasing and coverage, state that at line 502 and flag budget-cycle capabilities as out of scope for this version. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | |
| PC-0348✎ edit📣 feedback | received | general | Core architects ai |
3.3 The reference architecture in practice §Section 3.3 p.48-52 l.lines 133-218 |
Public health campaigns are not illustrastred as an end -to-end use case. Campaigns are a major mechanism through which…Public health campaigns are not illustrastred as an end -to-end use case. Campaigns are a major mechanism through which countries operationalize population-level health goals and typically involves planning, readiness, execution, monitoring and response. An integrated campaign example could demostrate how the sharard DPI-H components are reused across programmes Suggested revision: Consider adding an integrated public health campaign as a layered view example.The example could follow a campaign from planning and population enumeration through readiness, implementation and monitoring, showing how shared DPI-H components such as the Client Registry, Health Facility Registry, Health Workforce Registry, Product Registry, geospatial/reference data, terminology services and interoperability capabilities support the campaign. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | |
| PC-0349✎ edit📣 feedback | received | technical | Core architects ai |
3.3 The reference architecture in practice §Section 3.3 p.48-52 l.152-193 |
The examples are useful for explaining the architecture, but they largely demonstrate the architecture through health-s…The examples are useful for explaining the architecture, but they largely demonstrate the architecture through health-system/clinical goals. A more operational example could help bridge the gap between the reference model and implementation. Suggested revision: Consider adding one or more example based on an operational public health intervention, alongside the existing examples, to demonstrate how the architecture supports time-bound, population-level activities. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | |
| PC-0350✎ edit📣 feedback | received | technical | Core architects ai |
3.5 DPI-H Application Components §Section 3.5 p.63 onward anchor: medium |
The concept of a DPI-H application component is central to understanding the reference architecture, particularly the d…The concept of a DPI-H application component is central to understanding the reference architecture, particularly the distinction between shared infrastructure and functional applications. This distinction could be surfaced more prominently before the detailed component catalogue begins Suggested revision: Consider adding a short "What is and is not a DPI-H component?" summary at the beginning of §3.5, with examples of shared registries/components versus functional programme or point-of-care applications. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-025 discuss | in the document all mentions on GitHub record | |
| PC-0351✎ edit📣 feedback | received | technical | Metadata registries ai |
3.5.3.1 The foundational shared data layer §Section 3.5.3.1 p.67 l.Lines 663-667 |
Many countries implementing DPI-H operate in multilingual contexts, and health workers may use languages at the point o…Many countries implementing DPI-H operate in multilingual contexts, and health workers may use languages at the point of service that differ from those used to author national terminology, value sets and data-collection forms. Localisation therefore extends beyond language to include conventions for dates, numbers and currencies in shared content. Suggested revision: Consider expanding the Terminology Service articulation in §3.5.3.1 and Appendix C to explicitly address multilingual and localisation requirements, including the ability to associate multiple language designations with concepts and provide translated display terms for value sets Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | |
| PC-0352✎ edit📣 feedback | received | technical | Core architects ai |
3.6.3 Interoperability between DPI-H and foundational DPI §section 3.6.3 p.75 l.889-895 |
Intermittent connectivity is acknowledged in 2.3 VII and 3.6.3, but is not translated into explicit architectural requi…Intermittent connectivity is acknowledged in 2.3 VII and 3.6.3, but is not translated into explicit architectural requirements. The draft should address key offline-first considerations, including local caching, offline client matching and reconciliation, conflict/duplicate handling, and provenance for records created while disconnected. Box 1.2 identifies probabilistic matching but does not address the more challenging offline scenario. Suggested revision: Add a short subsection (e.g., 3.6.6, “Operating with Intermittent Connectivity”) outlining the requirements for shared components: value-set caching and versioning in the Terminology Service, deferred matching and reconciliation in the Client Registry, and deferred writes and conflict resolution in the Lifelong Health Record. Cross-reference this subsection from the equity and inclusion principle Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | |
| PC-0353✎ edit📣 feedback | received | general | Core architects ai |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.29-62 |
The inventory framework does not cover a funding/financing section - which can be crucial for decision making purposes.…The inventory framework does not cover a funding/financing section - which can be crucial for decision making purposes. Whether a system is funded domestically, externally and more importantly when does the funding end. And where feasible we could have a slot to also capture run cost per year. This helps with rationalisation decision Suggested revision: Adding in of a cost component Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0354✎ edit📣 feedback | received | general | Core architects ai |
4.4.2 Tracking progress over time §4.4.2 p.99 l.447-460 |
The four components are well articulated and listed out for tracking progress and making a case. However looking at it …The four components are well articulated and listed out for tracking progress and making a case. However looking at it from a sustainable financing perpespective - it would be great to have a measure on finance. The hypotheses is that with a DPI approach there would be cost efficiencies - unit cost falls as components are shared. This is particularly compelling as we make a case to a Ministry of Finance (MoF) to argue for investment in this approach Suggested revision: Add a fifth dimension covering cost and financing: annual running cost of shared components, the share funded from the domestic recurrent budget, and the number of systems retired or consolidated. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | |
| PC-0355✎ edit📣 feedback | received | general | Core architects ai |
4.6.1 The Investment Case §4.6.1 p.102 l.547-564 |
The investment case and rationale is well articulated and how it should be pitched to MoF. Would be useful to have/refe…The investment case and rationale is well articulated and how it should be pitched to MoF. Would be useful to have/refer to a costing method or approach. In particular it can be hard to answer the TCO of a registry, data exchange or a payment rail - and leaving this at an impasse when MoH and MoF speake with each other. Suggested revision: Add in reference to costing guidance or an external link to frameworks developed to do this. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0356✎ edit📣 feedback | received | general | Core architects ai |
A Appendix A §Appendix A p.112 l.Table A anchor: medium |
Table A does not include a distinct stakeholder category for private-sector commercial actors (technology vendors, supp…Table A does not include a distinct stakeholder category for private-sector commercial actors (technology vendors, suppliers of digital health products), despite Section 1.3.3 explicitly discussing 'the commercial sector' as a DPI-H value beneficiary. Suggested revision: Add a 'Private Sector / Technology and Solution Providers' category to Table A for completeness and internal consistency with Section 1.3.3. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | |
| PC-0357✎ edit📣 feedback | received | general | Core architects ai |
Client Registry §Appendix C p.115 l.45 |
Suggest also referencing how health can strengthen/create foundational DPIsSuggest also referencing how health can strengthen/create foundational DPIs Suggested revision: "Where one does not, the Client Registry provides the health sector's own identity resolution capability, and can serve as the foundational ID system that is adopted by other sectors" Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | |
| PC-0358✎ edit📣 feedback | received | general | Supply chain ai |
Product Registry §Appendix C p.145 l.380 anchor: medium |
Suggest defining product upfront, since product can mean so many things, especially in a tech contextSuggest defining product upfront, since product can mean so many things, especially in a tech context Suggested revision: The Product Registry is a foundational DPI-H component holding standardised, and cross-sectorally reusable master data for core health products - medicines, vaccines, medical devices, diagnostics, and health commodities. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | |
| PC-0359✎ edit📣 feedback | received | Supply chain ai |
Product Registry §Appendix C p.145 l.384 |
The scope lists "medicines, vaccines, medical devices, diagnostics, and health commodities" but does not mention medica…The scope lists "medicines, vaccines, medical devices, diagnostics, and health commodities" but does not mention medical equipment. Important to distinguish for many reasons, e.g., "diagnostics" covers both test kits and equipment. Equipment needs different attributes that don't necessarily fit the model. Suggested revision: Clarify whether medical equipment should sit inside or outside of this registry; if not within the registry, state where it should be included. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-0360✎ edit📣 feedback | received | Supply chain ai |
Product Registry §Appendix C p.150 anchor: medium |
The registry should hold only the "minimum sufficient set to unambiguously identify a product", but the data element ta…The registry should hold only the "minimum sufficient set to unambiguously identify a product", but the data element table makes attributes like volumetrics, storage requirements, and shelf life mandatory, though they aren't necessary to identify a product (e.g., volumetrics is even stated to be for transport and storage capacity planning.) Suggested revision: State the criteria for what counts as foundational data, and re-check each data element against it. Elements for supply chain management only should not be in a cross-sectoral registry. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-0361✎ edit📣 feedback | received | general | Clinical ai |
Lifelong Health Record §Appendix C p.155 l.1 anchor: medium |
Why are we choosing the term Lifelong Health Record vs. Shared Health Record, which is more commonly used and understoo…Why are we choosing the term Lifelong Health Record vs. Shared Health Record, which is more commonly used and understood already? Suggested revision: Change references to Lifelong Health Record to Shared Health Record Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | |
| PC-0362✎ edit📣 feedback | received | Supply chain ai |
Product Registry §Appendix C p.145-154; 190-198 anchor: medium |
Both the Product Registry and Supplier Registry reference being cross-sectoral, but the discussion is largely around he…Both the Product Registry and Supplier Registry reference being cross-sectoral, but the discussion is largely around health supply chain systems. Suggested revision: Add at least one cross-sectoral use case for each to better emphasize the foundational element of these two registries. Lakshmi Balachandran, Obaroene Ogidiagba, Boluwatito Adeyemi, Sameen Babur, Srikant Mohan, Lauren Theis, Clinton Health Access Initiative |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-0363✎ edit📣 feedback | received | general | Core architects ai |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §1.1.2 p.9 l.55–61 |
The definition is useful and simple but remains health-agency and asset centred. A DPI should be judged not only by reu…The definition is useful and simple but remains health-agency and asset centred. A DPI should be judged not only by reuse across agency functions, but by whether it creates public value across a health ecosystem that includes people, communities, public and private providers, and subnational actors. The definition also omits the complementarity of assisted and non-digital routes, which are important where digital identity, literacy, connectivity or devices are uneven. This is consistent with the Universal DPI Safeguards Framework: https://www.dpi-safeguards.org/framework Suggested revision: Revise the definition to describe DPI-H as an evolving, publicly governed socio-technical infrastructure that enables multiple health and public-health functions across societal actors. DPI-H is complementary to equitable assisted/non-digital access functions. DPI-H should create public value across the network of health stakeholders. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-007 discuss | in the document all mentions on GitHub record | |
| PC-0364✎ edit📣 feedback | received | general | Core architects ai |
1.1.3 Building on existing foundations §1.1.2 p.11 l.102–124 anchor: low |
The examples of Aadhaar, CoWIN and Estonia are presented mainly as demonstrations of scale and reuse. Because these cas…The examples of Aadhaar, CoWIN and Estonia are presented mainly as demonstrations of scale and reuse. Because these cases have also generated concerns about exclusion, privacy, purpose expansion and dependency on digital access, a public-health guidance document should avoid a success-only narrative for these examples. Otherwise ‘scale’ may be read as sufficient evidence of public value or safety. Suggested revision: For each illustrative case, add a short, balanced note on context, documented benefits, known limitations and safeguards. Explicitly state that scale does not itself establish all DPI-H design princples have been met; equity, rights protection, health impact or transferability to another country. This may be a difficult ask, politically, for a WHO document. However, you could also consider an example that has not yet scaled nationally, but has taken into strong consideration DPI-H design principles around e.g. data ownership, trust and security. How di system designers address pushback, incidents, or inflexion points? Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-006 discuss | in the document all mentions on GitHub record | |
| PC-0365✎ edit📣 feedback | received | general | Core architects ai |
1.4 DPI-H Principles §1.4 p.20 l.368–421 |
The principles emphasize technical and institutional properties, but omit several principles central to HISP’s socio-te…The principles emphasize technical and institutional properties, but omit several principles central to HISP’s socio-technical approach: participatory co-design, use of information for action, incremental learning, local ownership and accessible grievance/redress. HISP describes action research, local–global feedback and long-term capacity building as core to sustainable systems: https://dhis2.org/hisp-approach These principles also align with the principles of digital developmen, e.g. "design with people, share reuse and improve" Suggested revision: Add a principle titled ‘Participation, learning and local ownership’. Require meaningful involvement of health workers, managers, communities and subnational authorities throughout the lifecycle; iterative learning from use; feedback to data producers; locally accountable stewardship; and accessible mechanisms to correct data and challenge harmful decisions. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-048 discuss | in the document all mentions on GitHub record | |
| PC-0366✎ edit📣 feedback | received | technical | Core architects ai |
1.5 The Seven Priority Health Sector Goals §1.5 p.21 l.429–459 |
‘Capture once, governed well, made available’ is a helpful antidote to duplicate reporting, but it can imply that all d…‘Capture once, governed well, made available’ is a helpful antidote to duplicate reporting, but it can imply that all data should be captured at the finest level and reused indefinitely. In health, data are contextual: purpose, granularity, timeliness, provenance and lawful basis affect fitness for reuse. We are wary as this phrase may unintentionally encourage excessive collection and function creep. Suggested revision: Replace with: ‘Collect minumum needed; govern transparently; and reuse only where lawful, necessary, and fit for the new purpose.’ Add that aggregate-first collection may be appropriate and that secondary use requires purpose-specific governance and disclosure controls. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-100 discuss | in the document all mentions on GitHub record | |
| PC-0367✎ edit📣 feedback | received | editorial | Editorial ai |
2.1 The Reference Architecture Scope §2.1 p.24 l.29–61; Figure 2.1 |
Figures and tables in this section start at 2.2; figure 2.1 does not exist. Numbering should follow the number of the …Figures and tables in this section start at 2.2; figure 2.1 does not exist. Numbering should follow the number of the main section (see Tables 3.1, 3.2, 3.3 under section 3.1) and then order of figures/tables Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-254 discuss | in the document all mentions on GitHub record | |
| PC-0368✎ edit📣 feedback | received | general | Core architects ai |
2.1 The Reference Architecture Scope §2.1 p.24 l.29–61; Figure 2.1 |
We see the HMIS as having inherent properties of digital infrastructure, and thus this section has a major architectura…We see the HMIS as having inherent properties of digital infrastructure, and thus this section has a major architectural omission: the two-layer model has no category for a shared public-health information and analytics platform. Foundational resources are restricted mainly to registries/LHR/terminology, while HMIS is placed downstream as a business application (data consumer). This misses infrastructure capabilities visible in mature DHIS2 deployments: an organisational hierarchy, metadata and indicator management, health workforce registries and user management, collection and triangulation of aggregate/event/Tracker data sets, analytics and GIS, data-quality and approval workflows, offline syncing, user notifications/messaging, and APIs. These core functions or registries may be derived, in some settings, from other registries (e.g. health facility registry), but in practice, these are often are built within and coalesce around the HMIS. Suggested revision: Add a cross-cutting ‘Public Health Information and Analytics Platform’ capability, or recognise that a nationally shared HMIS/RHIS can itself provide infrastructural capabilities. Show that it can host reusable metadata, harmonise aggregate and event/person data, support multiple programmes, provide decentralised analytics and expose governed APIs. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | |
| PC-0369✎ edit📣 feedback | received | technical | Core architects ai |
2.2.1 What REDDHI is and its foundational core §2.2 p.26–28 l.109–173; Table 2.2 |
REDDHI makes registries and a Lifelong Health Record the common minimum, but excludes the national RHIS/HMIS platform t…REDDHI makes registries and a Lifelong Health Record the common minimum, but excludes the national RHIS/HMIS platform that already constitutes the most mature digital health infrastructure in many LMICs. A DHIS2-based national RHIS often supplies shared organisational units, indicator metadata, aggregate data, surveillance, dashboards, APIs and a trained support ecosystem. Building new person-level foundations before strengthening this asset could delay value and fragment governance. Suggested revision: Define the REDDHI minimum through country priorities and installed capabilities. Add ‘shared RHIS/public-health information platform’ as an eligible core starting component in Table 2.2. Permit aggregate-first, surveillance-first and mixed-modality pathways, with registries/LHR added when priority use cases, lawful basis, coverage and operating capacity justify them. Our point here is twofold. First, REDDHI "components" described in Tbl2.2 are all "foundational DPI"; yet registries alone cannot capture all essential facility-level aggregate, logistics, or surveillance data (many of which are cross-cutting!). Second, business service layers already capture, combine, analyze, and extend those data along with the core registries. Thus, building on, learning from, or drawing on an installed base RHIS in the "business service layer" for development of foundational DPI, should be considred a key pathway for development towards REDDHI. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | |
| PC-0370✎ edit📣 feedback | received | general | Core architects ai |
2.2.2 The enabling conditions for REDDHI §2.2 p.28 l.164–173 |
‘Full-STAC’ omits two assets central to the DHIS2/HISP model: configurable metadata/content and an open implementation …‘Full-STAC’ omits two assets central to the DHIS2/HISP model: configurable metadata/content and an open implementation community. Content can be covered by open content and open architectures, although SMART guidelines are presented as the only option, rather than a country-owned terminology system. We also would argue the community and ecosystem of successful DPI implementations should be acknowledged as a key enabling condition which promotes national DPI-H sustainability. Suggested revision: Extend STAC to ‘STACC’: standards, technology, architecture, content/configuration and community/capacity. Or, one line on community as an enabling condition ataround line 165 Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | |
| PC-0371✎ edit📣 feedback | received | general | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.33 l.304–322 |
The local-capacity principle, because it focuses on design choises, is too narrow for platforms that become national in…The local-capacity principle, because it focuses on design choises, is too narrow for platforms that become national infrastructure. DHIS2 sustainability depends not only on documented technology but on a distributed HISP ecosystem: permanent ministry teams, local HISP groups, universities, academies, implementers, help desks, peer networks and country-to-country learning. These relationships retain knowledge, support upgrades and turn local requirements into reusable platform improvements. Suggested revision: Require a costed national capacity and support architecture: designated public-sector ownership; national and subnational core teams; local implementation/support organisations (HISP model as an example); university partnerships; academies, apprenticeship and mentoring; communities of practice; help-desk and escalation arrangements; succession; and recurrent budgets. Evaluate capacity as infrastructure, to be developed and maintained over time--not as a one-off training deliverable. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-242 discuss | in the document all mentions on GitHub record | |
| PC-0372✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.34–35 l.346–379 |
The text states that consent is the primary mechanism by which individuals exercise control over their health data. Thi…The text states that consent is the primary mechanism by which individuals exercise control over their health data. This conflates consent, legal basis, authorization and data rights. Public-health surveillance and many care operations may rely on statutory or public-interest bases; consent may not be freely given or operationally appropriate. Conversely, a lawful basis does not remove duties of transparency, minimization, security, correction and redress. WHO’s data principles similarly distinguish ethical data governance from blanket openness or consent: https://www.who.int/data/principles/ Suggested revision: Distinguish: (1) lawful basis for processing; (2) authorization and role-based access; (3) consent where consent is appropriate; and (4) enforceable individual/community rights. Require purpose limitation, minimization, access logs, correction, appeal/redress, independent oversight and special safeguards for surveillance and vulnerable populations. If limited by space, acknowledge that consent policies vary not only at the level of "systems that hold and exchange the data" but also within a system itself (e.g. public health surveillance may have different consent policies depending on type of disease or population). Consent resouces should contain at a minimum lawful basis, consent tupe, authorization and acces. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | |
| PC-0373✎ edit📣 feedback | received | technical | Core architects ai |
2.4 Methodology: Mapping Health Goals to DPI-H §2.4 p.38 l.467–486 |
The methodology presents a Client Registry as recurrent and required. A client registry may be valuable for longitudina…The methodology presents a Client Registry as recurrent and required. A client registry may be valuable for longitudinal care, but it is not universally required for a DPI-H entry point. Aggregate HMIS, event-based surveillance or services that must operate for unknown or undocumented persons. Labeling it required may drive premature identity-centric architecture and unnecessary linkage risk. Suggested revision: Change ‘required’ to ‘frequently useful where the priority use cases require person matching’. Require a necessity and proportionality test, identity-optional workflows, temporary/pseudonymous identifiers and a documented alternative for contexts without universal or trusted identification. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-026 discuss | in the document all mentions on GitHub record | |
| PC-0374✎ edit📣 feedback | received | general | Core architects ai |
3.4.1 Purpose and framing §3.4 p.53–56 l.219–372 |
The governance treatment is very strong. But we see here that participation is concentrated in national strategic and t…The governance treatment is very strong. But we see here that participation is concentrated in national strategic and technical bodies. There is insufficient assurance that district/facility managers, frontline workers, community representatives, civil society and marginalized groups can influence priorities, metadata, access rules, performance review and remediation. Representation in formal committees alone may not surface harms or operational realities. Suggested revision: Add examples of blended governance committees at national and subnational levels. Advocate for specific means to ensure equirable participation, such as transparent decision records, recurring user/community forums, conflict-of-interest rules, feedback channels and accessible grievance/redress. Require evidence that feedback changed design or operations—not only that consultation occurred. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-048 discuss | in the document all mentions on GitHub record | |
| PC-0375✎ edit📣 feedback | received | technical | Core architects ai |
3.5.1 What Distinguishes a DPI-H Application Component §3.5 p.64 l.550–572; Box 3.1 |
The criterion that a component be reusable ‘without modification to core design’ is too rigid for health information in…The criterion that a component be reusable ‘without modification to core design’ is too rigid for health information infrastructure, or it may be easily misinterpreted. For example, is "modifying" a HIV registry for TB patients modifying its "core design"? They may have similar workflows, and both link to the shared client registry, but the content will be substantively different. What about updating an existing registry within new data elements, constraints, or reporting stages? Suggested revision: Add "data content definitions may be reused or altered, but the software serving these content definitions remains stable and content-neutral". Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | |
| PC-0376✎ edit📣 feedback | received | technical | Core architects ai |
3.5.1 What Distinguishes a DPI-H Application Component §3.5 p.64 l.566–569; Box 3.1 |
‘Non-transactional’ is not a defensible defining property of shared infrastructure. Registries, benefits registries, su…‘Non-transactional’ is not a defensible defining property of shared infrastructure. Registries, benefits registries, supply services and surveillance platforms perform transactions and state-changing workflows, even at clinical level. The criterion also conflicts with the document’s own business-service components and could cause inconsistent conformance decisions. Suggested revision: Delete the ‘non-transactional’ criterion. If the intended concern is excessive coupling to one application, say: ‘not tightly coupled to a single programme or point-of-service workflow, and usable through stable interfaces by multiple authorized services’. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | |
| PC-0377✎ edit📣 feedback | received | technical | Core architects ai |
3.5.1 What Distinguishes a DPI-H Application Component §3.5 p.64 l.550–572; Box 3.1 |
The component criteria can be interpreted as a one-component/one-product procurement blueprint. This misrepresents plat…The component criteria can be interpreted as a one-component/one-product procurement blueprint. This misrepresents platform architectures. A single DHIS2 deployment can co-realise aggregate HMIS, case/event surveillance, registries, facility profiles, campaigns, community information, analytics and feedback; conversely, one logical capability may be distributed across systems. Mandatory product separation would recreate silos and duplicate metadata, hosting, support and user workflows. Suggested revision: State prominently that components are logical capabilities, not mandatory software, procurement or deployment boundaries. Permit one governed platform to implement several components and one component to be distributed across services. Conformance should test capabilities, interfaces, safeguards and outcomes rather than count products or boxes. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | |
| PC-0378✎ edit📣 feedback | received | technical | Core architects ai |
3.7.3 Alignment with IHE profiles §3.7 p.83–84 l.1132–1152 |
The statement that standard components ‘arrive tested’ overstates what standards and shared test artifacts can guarante…The statement that standard components ‘arrive tested’ overstates what standards and shared test artifacts can guarantee. A product may pass a conformance suite while its configuration, deployment, security, performance, accessibility, data quality and fit with local work remain untested. This could encourage procurement teams to equate certification with implementation readiness. Suggested revision: Say that reusable specifications and test suites reduce—but do not replace—local verification. Require product conformance testing plus configuration, integration, security/privacy, performance, usability/accessibility, workflow, data-quality, failover and user-acceptance testing in the intended setting. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | |
| PC-0379✎ edit📣 feedback | received | technical | Core architects ai |
3.7.5 Validating goals and adoption §3.7 p.85 l.1195–1231 |
The separation of adoption, adaptation, and mapping is very useful. But quantifying adoption "coverage" as the proporti…The separation of adoption, adaptation, and mapping is very useful. But quantifying adoption "coverage" as the proportion of reference elements realized turns an adaptive reference architecture into a completeness checklist. It penalizes context-appropriate omission and may create incentives to buy components that do not solve a priority health problem. Architectural coverage is an input, not an outcome or a sufficient indicator of maturity. Suggested revision: Less emphasis on component-coverage scoring, with more on goal- and capability-based fitness. Allow justified ‘not applicable/not yet’ decisions. Countries should also assess whether priority use cases work safely and equitably, whether data are used for action, and whether the architecture can evolve sustainably; report component coverage only as descriptive context. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | |
| PC-0380✎ edit📣 feedback | received | general | Core architects ai |
4.1.1 No Country Starts from Zero §4.1 p.88 l.12–61 |
This is a good set of 4 assessment questions. But the current-state assessment should go beyond applications, infrastru…This is a good set of 4 assessment questions. But the current-state assessment should go beyond applications, infrastructure, standards and governance documents (i.e. desk review). A socio-technical baseline must examine actual work: informal workarounds, reporting burden, incentives, decision forums, support practices, data trust, power relationships, user capability and who is excluded. These factors often explain why technically functional systems are not used. Suggested revision: Add participatory work-practice and institutional assessment methods: observation/interviews, workflow and burden mapping, information-use assessment, stakeholder/power analysis, support-capacity mapping, equity and accessibility assessment, and identification of locally valued use cases and functioning installed-base elements to preserve. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | |
| PC-0381✎ edit📣 feedback | received | general | Core architects ai |
4.2.1 Different Entry Points toward REDDHI §4.2 p.89–92 l.63–197 |
Although described as adaptable, the phases remain infrastructure-first and largely waterfall. The DHIS2/HISP experienc…Although described as adaptable, the phases remain infrastructure-first and largely waterfall. The DHIS2/HISP experience demonstrates a different pathway: start from an immediate information-use problem; configure a minimum solution on a generic platform; implement in real work; learn through action research; and progressively generalise metadata, workflows and software. This is our experience how a platform grows from a useful local system into national infrastructure. It could be argued that DPI-H evolution is different than RHIS, in that there is not a specific high-priority health data use case to target, but rather foundational functionalities with cross-cutting purposes. However, the "phased implementation" piecemeal approach could still be problem-oriented -- what have been the thorniest health problems to date, what would be quick wins, are there small foundational DPI-H investments that could show short-term results? This would reinforce the coalition of supporters over 2+ years to Phase 4, and also ties in with the "priority health goals" identified in 4.1 Suggested revision: Recast phases as iterative platform-building cycles: priority decision/use case → participatory configuration → minimum usable deployment → routine use and support → mixed-method evaluation → metadata/software adaptation → capacity transfer → scale or stop decision. In EP2 and EP3, explicitly allow existing platforms to be extended with new programmes and capabilities in each cycle. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-245 discuss | in the document all mentions on GitHub record | |
| PC-0382✎ edit📣 feedback | received | technical | Core architects ai |
4.2.2 A Phased Implementation Approach §4.2.2–4.2.3 p.91–92 l.155–184 |
Placing HMIS only in Phase 3—after registries and LHR—marginalises the principal national digital health platform in ma…Placing HMIS only in Phase 3—after registries and LHR—marginalises the principal national digital health platform in many LMICs. DHIS2 is used by more than 80 LMICs as a government-wide health data system and supports routine reporting, surveillance, programme monitoring and other shared functions. Treating this installed base as a late business service creates a greenfield bias and may channel investment away from operational national infrastructure. Later in the document, HMIS core attributes include "Data collection and ingestion. Reception of health data through multiple channels, including direct facility-based and community-based reporting..." - yet its not part of the data layer. Source: https://dhis2.org/about-2/ Suggested revision: Allow an ‘RHIS/platform-first’ pathway. In Phase 1–2, strengthen an existing national HMIS/DHIS2 platform as shared infrastructure: harmonise organisational units and metadata, improve data quality/use, establish governance and support, expose APIs, and add aggregate/event/Tracker use cases iteratively. Develop LHR and registry services in parallel where justified. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-245 discuss | in the document all mentions on GitHub record | |
| PC-0383✎ edit📣 feedback | received | general | Core architects ai |
4.2.4 The Role of the National Digital Architect §4.2.4 p.93–94 l.226–245 |
Assigning the architecture to ‘an individual or small team’ with a single authority risks a heroic-architect model, con…Assigning the architecture to ‘an individual or small team’ with a single authority risks a heroic-architect model, concentration of power, bottlenecks to timelines, and turnover leading to loss of continuity. DPI-H decisions span public health, clinical care, law, privacy, enterprise architecture, implementation, gender/equity and subnational operations; no single professional can legitimately represent all of these. Suggested revision: Specify a multidisciplinary, institutionally anchored architecture function with shared decision rights, documented accountability, subnational and user representation, conflict-of-interest safeguards, succession and knowledge management. A named lead may coordinate, lead with strategic direction, and even have "final word" on decisions if necessary, but should not substitute for collective governance and independent review. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | |
| PC-0384✎ edit📣 feedback | received | general | Core architects ai |
4.3.1 Design Data Structures and Data Models First §4.3 p.94 l.256–284 |
Calling data models the starting point, as a top-down approach, overlooks the public-health information cycle and how h…Calling data models the starting point, as a top-down approach, overlooks the public-health information cycle and how health data is refined into health intelligence. In DHIS2, collection forms are not the analytical model (‘data input ≠ data output’); reusable data elements, dimensions, indicators, organisational units and workflows are configured from decision and reporting needs and evolve with use. A data model-first approach may simply digitise reporting forms and increase reporting burden. Evidence: https://docs.dhis2.org/en/implement/implementing-dhis2/conceptual-design-principles.html Suggested revision: Foundational facility and health workforce registries require minimal administrative datasets and may be the best place to start defining requirements. Client registries: minimal dataset for capturing essential demographic details, both digital identifiers optional elements. Here we have found a logical model to be very useful, and a good place to start buildign logical models. For terminology services, which will define the health data content of DPI-H, a longer and more thorough M&E review process is justified, going program by program and across administrative divisions. A level below that, EMRs will feed M&E systems and also inform clinical decisions; divergence of interests is greater across programs and regions. To consolidate health program requirements, we recommend starting with priority decisions, users, workflows, existing reporting obligations and action pathways. Then define minimum reusable metadata—data elements, dimensions, organisational units, indicators, validation and workflow rules—separating collection interfaces from analytical outputs. Require participatory testing and iterative metadata governance rather than a one-off model-first exercise. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | |
| PC-0385✎ edit📣 feedback | received | technical | Core architects ai |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.95–96 l.306–338 |
FHIR is an important exchange framework, but the text may be read as making it the universal semantic and exchange solu…FHIR is an important exchange framework, but the text may be read as making it the universal semantic and exchange solution. Aggregate reporting, imaging, laboratory, logistics and geospatial/public-health data may require other standards. FHIR versions and resources also differ in normative maturity; HL7 describes R5 as an STU while R4 combines normative and STU content: https://fhir.hl7.org/fhir/versions.html Suggested revision: Describe FHIR as one (highly recommended) standards family within a governed standards portfolio. Require stated versions, national profiles/implementation guides, terminology bindings, validation and migration policy. Recognize complementary standards and non-FHIR aggregate interfaces. National standards frameworks depend on use case and maturity rather than by blanket preference. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | |
| PC-0386✎ edit📣 feedback | received | technical | Core architects ai |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4 Integration Interfaces p.96 l.339–367 |
The foundational identity API example assumes retrieval of a verified national identifier. This can increase exclusion,…The foundational identity API example assumes retrieval of a verified national identifier. This can increase exclusion, surveillance and cross-domain linkage risk, and couples health services to an identity system whose coverage or trust may be incomplete. Health services and public-health reporting must be able to proceed when identity is absent, contested or unsafe to disclose. Suggested revision: Require sector-specific or pseudonymous tokens where suitable, data minimization, purpose-bound matching, separation of identifiers, audit and redress. Define temporary/unknown-person workflows and state explicitly that essential care or reporting must not be denied or delayed because a foundational identifier cannot be verified. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | |
| PC-0387✎ edit📣 feedback | received | editorial | Editorial ai |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4 p.96–97 l.Section headings anchor: medium |
Two consecutive subsections are numbered 4.3.4 (‘Integration Interfaces’ and ‘Interoperability Implementation Pathways’…Two consecutive subsections are numbered 4.3.4 (‘Integration Interfaces’ and ‘Interoperability Implementation Pathways’). This creates ambiguous cross-references. Suggested revision: Renumber ‘Interoperability Implementation Pathways’ as 4.3.5 and update all subsequent references and the table of contents. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-097 discuss | in the document all mentions on GitHub record | |
| PC-0388✎ edit📣 feedback | received | technical | Core architects ai |
4.4.1 Assessing impact: Are goals being achieved? §4.4.2 p.99 l.427–443 anchor: low |
The claim that a baseline-endline allows later change to be ‘attributed with confidence’ is too strong. A before/after …The claim that a baseline-endline allows later change to be ‘attributed with confidence’ is too strong. A before/after baseline alone cannot distinguish DPI-H effects from policy changes, outbreaks, financing shifts, workforce changes or secular trends . A "process evaluation" does not cover these externalities. Suggested revision: Replace ‘attributed’ with ‘assessed’ or ‘contribution examined’. Support research and evidence for national investments, including an explicit theory of change (how DPI-H investments will lead to outcomes observed), repeated measures across implementation, qualitative process evidence and, where feasible, comparison groups or quasi-experimental methods. Report uncertainty and alternative explanations for outcomes. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-104 discuss | in the document all mentions on GitHub record | |
| PC-0389✎ edit📣 feedback | received | general | Core architects ai |
4.4.2 Tracking progress over time §4.4.2 p.99 l.445–463 |
The monitoring framework under-measures whether a shared platform becomes institutionalised and used. HISP has assessed…The monitoring framework under-measures whether a shared platform becomes institutionalised and used. HISP has assessed country maturity of DHIS2 as an MIS platform across health and non-health domains. Relevant RHIS/DHIS2 measures include coexistence/triangulation of aggregate, event and Tracker data; end users have access to analytic dashboards; active use at subnational level; API integrations; local configuration/support capability; upgrade sustainability; and retirement of duplicative reporting systems. Suggested revision: We recommend measures for "routine system use" to catpure DPI-H institutionalization. Are data review meetings routine? How frequently are outages reported for civil registry systems? Are all facility and clients registered across the country -- and if not, does it prevent use of the system? Are data exchanged from other systems visible to healthcare providers, or do they inform critical M&E indicators? Have previous reporting systems been retired, or are they still add-on? See for example PRISM Framework https://www.measureevaluation.org/resources/prism.html Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | |
| PC-0390✎ edit📣 feedback | received | general | Core architects ai |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5 p.100–101 l.493–539 |
The workforce model is specialist-heavy and does not capture the roles we see as needed to sustain a configurable natio…The workforce model is specialist-heavy and does not capture the roles we see as needed to sustain a configurable national platform: M&E specialists, platform administrators/configurators, district information officers, trainers, help-desk/support staff, implementation researchers, local app/integration developers and user-community facilitators. In the DHIS2 context, these roles often sit across ministries, HISP groups and universities. Suggested revision: Add a platform operations and learning workforce stream. Define national and subnational teams for metadata governance, configuration, analytics and data use, user support, training, integration/app development, security and performance, action research and community facilitation. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | |
| PC-0391✎ edit📣 feedback | received | general | Core architects ai |
4.6.1 The Investment Case §4.6 p.102–103 l.541–610 |
Sustainability is discussed, but the cost model should more explicitly cover the recurrent work hidden behind ‘shared’ …Sustainability is discussed, but the cost model should more explicitly cover the recurrent work hidden behind ‘shared’ infrastructure: metadata and terminology maintenance, hosting, connectivity/power, devices, cybersecurity, upgrades, integration regression testing, user support, supervision, data-quality work, community engagement and safe decommissioning. Capital funding without these functions creates brittle infrastructure. Suggested revision: Require a 5–10 year total-cost-of-ownership and transition plan covering central and subnational recurrent costs, like local support ecosystems, refresh/upgrade cycles, security and incident response, training/supervision, accessibility, vendor exit, data migration and decommissioning. Link scale decisions to demonstrated financing and operational capacity. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0392✎ edit📣 feedback | received | general | No human |
C Appendix C: DPI-H Application Component Descriptions §Appendix C – CRVS anchor: medium |
Positive feedback -- good description of client registry and its relation to CRVS; we note that cause of death and infa…Positive feedback -- good description of client registry and its relation to CRVS; we note that cause of death and infant health records, particularly immunization registers, have a key function connecting to and strengthening CRVS systems where they are weak. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-0393✎ edit📣 feedback | received | technical | Editorial ai |
Health Management Information System §Appendix C – HMIS p.210 l.2–30 |
HMIS and RHIS terminology. We often define RHIS as all routine health-facility-based systems, which includes registers,…HMIS and RHIS terminology. We often define RHIS as all routine health-facility-based systems, which includes registers, HR, surveillance, lab and logistics systems. https://iris.who.int/server/api/core/bitstreams/20f53c27-babe-406b-8ffc-09cf96e4c08f/content HMIS is a subset of RHIS, used for reporting and analytics of aggregate/anonymized routine facility data on health services and outcomes. Suggested revision: Minor semantic point and can be omitted, as Official WHO definitions are already vague and conflicting on these distinctions. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | |
| PC-0394✎ edit📣 feedback | received | general | Core architects ai |
Health Management Information System §Appendix C – HMIS p.210 l.2–30 |
THis section presents a fairly accurate architectural description of what a mature DHIS2 national HMIS deployment alrea…THis section presents a fairly accurate architectural description of what a mature DHIS2 national HMIS deployment already does. But, HMIS/RHIS is reduced to a ‘shared application component’ and explicitly declared non-foundational, even within business service layer. This underestimates the infrastructural role of a national DHIS2 platform: it provides shared organisational hierarchies, metadata, aggregate and event/person data, indicators, analytics/GIS, data quality and approval workflows, offline collection, notifications, APIs, extensions and a user/support ecosystem across programmes. While these could come from other sources, in current landscape, HMIS are the source of truth for facility registries and indicator construction. Public-health informatics treats RHIS as the people–process–information–technology system through which routine decisions are made—not merely an application consuming LHR data. Suggested revision: Redefine HMIS/RHIS as a governed socio-technical public-health information infrastructure. Distinguish its software platform from the wider RHIS, but recognise that the platform may supply shared foundational capabilities. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | |
| PC-0395✎ edit📣 feedback | received | technical | Core architects ai |
Health Management Information System §Appendix C – HMIS p.212 l.114–124 |
The LHR is described as the primary source for HMIS aggregates, which contradicts real RHIS architecture and also the f…The LHR is described as the primary source for HMIS aggregates, which contradicts real RHIS architecture and also the first HMIS "core attribute". DHIS2 supports direct aggregate reporting, event data and registered Tracker data concurrently; it can analyse them together or transform Tracker indicators into aggregate values. This mixed-modality model preserves continuity while facilities and programmes transition at different speeds. Furthermore, HMIS covers a variety of inputs and outputs that are not based on shared patient records (CHW services, health facility assessments, health education services/outreach, stock availability, to name a few) Source: https://docs.dhis2.org/en/implement/maintenance-and-use/tracker-and-aggregate-data-integration.html Suggested revision: Describe HMIS as a multi-source, mixed-granularity platform. Make direct aggregate, event, Tracker/registry, laboratory, logistics, workforce, finance, CRVS, survey and imported data first-class. Allow coexistence and triangulation across modalities, with explicit provenance, completeness, source-of-truth and transition rules. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | |
| PC-0396✎ edit📣 feedback | received | technical | Core architects ai |
Health Management Information System §Appendix C – HMIS p.212 l.114–124 |
The Client Registry is presented as supporting accurate denominators. A registry of service users is not a population d…The Client Registry is presented as supporting accurate denominators. A registry of service users is not a population denominator and may systematically omit people who do not access care, migrants, mobile populations and marginalized groups. Using it as a denominator can bias coverage estimates and intensify identity linkage without analytical benefit. Suggested revision: Instead use "accurate calculation of denominators for healthcare utilization indicators" Use census and population projections, CRVS, surveys, catchment estimates and other validated population sources for denominators, with uncertainty documented. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | |
| PC-0397✎ edit📣 feedback | received | general | Core architects ai |
Health Management Information System §Appendix C – HMIS p.211 l.64–108 |
The core attributes focus mainly at access, dashboards and dissemination. DHIS2/HISP evidence treats information use as…The core attributes focus mainly at access, dashboards and dissemination. DHIS2/HISP evidence treats information use as a decentralised cycle linking data quality, interpretation, feedback, action and renewed demand. Platform features specifically desgined to support data use include user-specific dashboards, maps, interpretations/discussion, internal messages, alerts and action tracking. These features enrich decision-point convenings such as data review meetings, healthworker supervision and policy dialogues. In essence, HMIS should promote translation of data into information, and track actions taken by HMIS actors. Evidence: https://docs.dhis2.org/en/implement/health/chis-community-health-information-system/implementation/data-quality-and-use.html Suggested revision: Add ‘decentralised information-to-action and feedback’ as a core capability. Require role-appropriate analytics at facility, district and national levels; interpretation/discussion; configurable alerts; action plans with owners and deadlines; follow-up and closure; supervisory feedback to data producers; and measurement of whether information changed decisions or services. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-183 discuss | in the document all mentions on GitHub record | |
| PC-0398✎ edit📣 feedback | received | technical | Core architects ai |
Public Health Surveillance Platform §Appendix C – PHSP p.218 l.4–24 |
The logical separation of PHSP (surveillance) and HMIS is defensible, but calling them distinct platforms is not. DHIS2…The logical separation of PHSP (surveillance) and HMIS is defensible, but calling them distinct platforms is not. DHIS2 supports indicator-based, event-based and case-based surveillance together with analytic dashboards, laboratory linkage, alert thresholds and emergency workflows. WHO-aligned DHIS2 surveillance toolkit deliberately triangulate case-based and weekly aggregate data. Such surveillance functions often overlap with and are sourced from HMIS; separate boundaries for HMIS and PHSP would duplicate metadata, users, hosting and support. Evidence: https://dhis2.org/disease-surveillance/ We see the primary distinction as one of governance, not business logic or functional requirements. For example, most countries have a designated agency responsible for infectious disease surveillance, within the MoH or an institute of public health. This institutional pattern is derived from two intertwined political mandates: to provide routine health services, and protect the public from epidemics. Often, the HMIS already captures monthly indicator-based surveillance datasets. So PHSP can use HMIS indicators as an early signal, in conjunction with its own case surveillance and contact tracing processes. We further note that many countries also have developed ""public health emergency operations centres"", as evidenced during Covid19, when some countries special units were created under executive branches for on-demand health statistics and crisis management. Emergencies focused health leaders on identifying best-available data from all sources, leading to collapsed institutional constraints. This demonstrated an acute need for merged HMIS/PHSP models, linkages with lab systems, and collaborating with other ministries such as MET agencies and veterinary services. Suggested revision: Describe HMIS and PHSP as distinct capability domains that may share a metadata-driven platform, organisational hierarchy, analytics and support ecosystem. Permit co-realisation in HMIS and PHSP where data segregation, privacy, access, performance and emergency requirements are satisfied. Acknowledge that HMIS and PHSP often share data sources, but serve different administrative structures. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | |
| PC-0399✎ edit📣 feedback | received | technical | Core architects ai |
Public Health Surveillance Platform §Appendix C – PHSP p.221, 225 l.162–168; Requirement 16 |
The LHR is described as the primary surveillance source and PHSP integration with LHR is mandatory, while the text also…The LHR is described as the primary surveillance source and PHSP integration with LHR is mandatory, while the text also invokes consent. Many surveillance systems must work before LHRs exist and receive notifications directly from laboratories, facilities, communities, borders or environmental sources. Public-health processing may rely on statutory authority rather than consent, subject to safeguards. Suggested revision: Make LHR integration conditional on the national architecture and priority use cases, not a universal SHALL. Require PHSP to operate with direct case/event/lab/community channels. Replace blanket consent wording with lawful-basis, necessity, proportionality, minimization, transparency, access-control and oversight requirements. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | |
| PC-0400✎ edit📣 feedback | received | technical | Core architects ai |
Public Health Surveillance Platform §Appendix C – PHSP p.220 l.113–120 |
Linking each case or contact to a verified Client Registry or foundational identity is unsafe as a universal expectatio…Linking each case or contact to a verified Client Registry or foundational identity is unsafe as a universal expectation. Surveillance must accommodate unknown persons, rapidly evolving outbreaks, migrants, undocumented people and sensitive conditions. Mandatory verification can delay notification, deter care and create unnecessary cross-sector linkage. Suggested revision: Require identity-optional case creation, temporary and pseudonymous identifiers, later reconciliation where necessary, strict separation of civil and health identifiers, and no denial or delay of care/reporting. Make Client Registry linkage a governed, risk-assessed option rather than a prerequisite. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | |
| PC-0401✎ edit📣 feedback | received | technical | Core architects ai |
Health Workforce Registry §Appendix C – PHSP requirements p.224 l.Requirement 11 anchor: medium |
The climate-related requirement is limited to ingesting sensor or data streams. Climate-informed public-health surveill…The climate-related requirement is limited to ingesting sensor or data streams. Climate-informed public-health surveillance also requires compatible geospatial/temporal units, joint indicators, uncertainty handling, thresholds, cross-sector governance and explicit action protocols. Data integration without a decision pathway may produce dashboards without preparedness. Suggested revision: Expand the requirement to include governed climate–health indicator definitions, geospatial/temporal alignment, provenance and forecast uncertainty, alert thresholds, cross-sector data-sharing agreements, responsible decision owners, response protocols and evaluation of false positives/negatives and unequal impacts. In other words, these integrations have functional requirements as well as governance models. In more technical detail: we should also address the temporal and spatial resolution mismatch between climate data (often gridded, continuous, sub-daily) and routine health surveillance data (facility-based, weekly/monthly, point-located), since this reconciliation — not just data receipt — is the actual technical challenge climate-health integration efforts like DHIS2's Chap Modeling Platform have had to solve. Distinguish between passively receiving environmental data streams for monitoring/analysis and the more demanding case of climate-driven predictive/forecasting models (e.g., climate-sensitive disease forecasting), since the latter requires defining model outputs and decision-support integration as a distinct capability rather than framed around communicable disease surveillance. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-183 discuss | in the document all mentions on GitHub record | |
| PC-0402✎ edit📣 feedback | received | technical | Core architects ai |
Health Management Information Service §Appendix D.1 p.230 l.57–65 |
Major omission/misclassification: DHIS2 is listed narrowly under HMIS and ‘DHIS2 Tracker’ separately under PHSP, as if …Major omission/misclassification: DHIS2 is listed narrowly under HMIS and ‘DHIS2 Tracker’ separately under PHSP, as if they were two products supporting two boxes. DHIS2 is a Digital Public Good and a configurable public-sector information platform. Core capabilities include aggregate, event and registered Tracker models; organisational hierarchies; reusable metadata/WHO packages; indicators and analytics/GIS; data quality/approval; alerts, messaging and workflows; offline Android; role-based sharing; APIs, data exchange and apps; and a global–local HISP implementation ecosystem. Sources: https://dhis2.org/about-2/ and https://dhis2.org/health-data-toolkit/ Suggested revision: Replace the two narrow listings with a platform-level DHIS2 entry. Map the single platform to the logical capabilities it can co-realise—HMIS/RHIS, PHSP/eIDSR, registries/cohort tracking, facility profiles, community information, campaigns, logistics-related reporting and cross-cutting analytics—while clarifying that capability, deployment and governance choices are country-specific. Add the HISP support/capacity model as part of the implementation evidence. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | |
| PC-0403✎ edit📣 feedback | received | editorial | Core architects ai |
Nigeria §Appendix D.2 – Uganda p.233 l.134-141 |
Nigeria mentions it combines routine aggregate reporting with dedicatedNigeria mentions it combines routine aggregate reporting with dedicated outbreak-investigation and contact-tracing tooling ". Only PHSP is listed, but routien aggregate reporting sounds like an HMIS function. Suggested revision: include HMIS Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-209 discuss | in the document all mentions on GitHub record | |
| PC-0404✎ edit📣 feedback | received | technical | Core architects ai |
Tanzania §Appendix D.2 – Uganda p.234 l.170–185 |
The Uganda example labels the components as HMIS and CDSE even though it describes national electronic IDSR. It therefo…The Uganda example labels the components as HMIS and CDSE even though it describes national electronic IDSR. It therefore misses PHSP/eIDSR and the broader DHIS2 platform pathway: extending an existing national HMIS installed base with surveillance workflows, local requirements work, training, phased scale-up and HISP Uganda support. The peer-reviewed study documents expansion to 100 of 146 districts and shows that institutional and capacity arrangements—not only software—enabled scale: https://doi.org/10.2196/59783 Suggested revision: Correct the mapping to PHSP, CDSE, plus the shared DHIS2 platform/HMIS installed base. Cite the implementation study and describe: reuse of national platform and organisational units; participatory requirements; aggregate/case surveillance capability; phased scale; training and support; HISP Uganda’s role; information use; outcomes and limitations. Present this as a socio-technical infrastructure trajectory. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-213 discuss | in the document all mentions on GitHub record | |
| PC-0405✎ edit📣 feedback | received | general | Core architects ai |
D Appendix D: Country and Regional Implementation Examples §Appendix D p.229–235 l.3–22 and country examples |
The examples do not adequately demonstrate the most consequential platform pattern for LMICs: a national DHIS2-based RH…The examples do not adequately demonstrate the most consequential platform pattern for LMICs: a national DHIS2-based RHIS growing incrementally into shared infrastructure across programmes and capabilities. Technology lists miss the common organisational hierarchy and metadata, aggregate/Tracker coexistence, cross-programme analytics, offline operation, local HISP support, long-term upgrades and governance that make the platform infrastructural. Suggested revision: Add one or more structured DHIS2 country trajectories using a common evidence template: installed base; shared metadata/organisational units; programmes and capabilities co-realised; aggregate/event/Tracker flows; APIs/interoperability; decentralised use; offline reach; HISP/local capacity; governance/financing; scale and duration; measured outcomes; safeguards and limitations. Uganda can be one case, with another mature national RHIS example. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0406✎ edit📣 feedback | received | general | Core architects ai |
Health Management Information System §Appendix C – HMIS placement p.210 l.2–30 |
Highest-priority issue for us at HISP: the categorical statement that HMIS ‘is not foundational’ is analytically unsoun…Highest-priority issue for us at HISP: the categorical statement that HMIS ‘is not foundational’ is analytically unsound across country contexts. A national RHIS platform can be both a business service and infrastructure when multiple programmes depend on its shared organisational hierarchy, metadata, aggregate repository, analytics, APIs, user management and support network. For many LMICs, the DHIS2-based HMIS is the most established national digital health infrastructure; classifying it only as downstream risks misdirecting investment toward new registries/LHR services while weakening what is already distributed, operational, and cost-effiicient. Suggested revision: Remove the categorical ‘not foundational’ statement. Use a functional/contextual test: an HMIS/RHIS platform may be foundational, shared-platform or business-service infrastructure depending on national reuse, dependency, governance and scale. In Figure 2.1 and Appendix C, show HMIS/RHIS spanning foundational and business-service layers where it supplies shared platform capabilities. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | |
| PC-0407✎ edit📣 feedback | received | technical | Core architects ai |
Health Workforce Registry §Appendix C – HMIS requirements p.213–216 l.Requirements 1–22 anchor: medium |
Major missing requirement: metadata-driven configuration and platform extensibility. The requirements specify indicator…Major missing requirement: metadata-driven configuration and platform extensibility. The requirements specify indicators, analytics, APIs and offline use but not the capability to configure datasets, forms, programmes, organisational units, roles, validation/workflow rules and dashboards without modifying core code; reuse governed metadata packages across programmes; support aggregate, event and registered person/cohort data in one platform; or extend the platform through open APIs/apps. These are central to DHIS2’s ability to serve as adaptable national infrastructure at subnational levels. Suggested revision: Add a Required ‘metadata-driven, multi-modal and extensible platform’ capability. The HMIS shall separate core software code from governed configuration; support reusable/versioned metadata packages and national localisation; manage aggregate, event and registered cohort data with explicit linkage/aggregation rules; expose complete documented APIs and an app-extension model; and preserve configuration through upgrades. Cite DHIS2 as an illustrative implementation. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-183 discuss | in the document all mentions on GitHub record | |
| PC-0408✎ edit📣 feedback | received | technical | Core architects ai |
3.5 DPI-H Application Components §3.5 p.52 l.Figure 3.5 anchor: medium |
Figure 3.5 places EMR in the same tier as core registries, contradicting its point-of-service classification elsewhere …Figure 3.5 places EMR in the same tier as core registries, contradicting its point-of-service classification elsewhere (p.52 vs. p.48). Suggested revision: Set EMR at the correct Tier Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | |
| PC-0409✎ edit📣 feedback | received | general | Core architects ai |
Lifelong Health Record §Appendix D p.230 l.HMIS anchor: medium |
Human-in-the-loop data quality is asserted as a goal frequently, but this process is specified nowhere. For example, da…Human-in-the-loop data quality is asserted as a goal frequently, but this process is specified nowhere. For example, data quality functionality is also listed as a core attribute of the HMIS though data quality assurance is only "recommended" functional requirement. This seems to derive from an assumption that all HMIS data would derive from digital registries, although mixed modes of paper, digital, aggregate and line lists are prevalent in many settings. Suggested revision: Recommend: (1) an explicit data-quality-assurance dimension added to the HMIS and PHSP component articulations, naming who reviews data at each administrative level and how corrections propagate through the pipeline; (2) reconsidering "structured quality feedback" for Required status; (3) a data-quality-assurance workstream added to the Chapter 4 phased roadmap; (4) referencing WHO's own established DQR toolkit rather than leaving this to be reinvented per country. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-243 discuss | in the document all mentions on GitHub record | |
| PC-0410✎ edit📣 feedback | received | general | Core architects ai |
3.5 DPI-H Application Components §3.5 p.63 l.Reference architecture (general) anchor: medium |
Gap in architecture: Laboratory information systems, Blood bank/ blood safety systems, biomedical and cold chain equipm…Gap in architecture: Laboratory information systems, Blood bank/ blood safety systems, biomedical and cold chain equipment, and One Health. In particular, DPI-H presents an opportunity to critically appraise national availability of data from outside the formal "health sector", such as animal and plant health, in a One Health framework. Suggested revision: Recommend references to national data soruces to the left. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-259 discuss | in the document all mentions on GitHub record | |
| PC-0411✎ edit📣 feedback | received | technical | Core architects ai |
4.3.4 Interoperability Implementation Pathways §4.4 p.97-98 l.376-384 |
The draft explicitly warns that centralized interoperability layers risk "concentration of control, single points of fa…The draft explicitly warns that centralized interoperability layers risk "concentration of control, single points of failure and procurement bottlenecks" (p.72) but gives no criteria for when a country should choose centralised vs. federated vs. hybrid. Based on our field experience, the decision factors (national IT capacity, existing platform landscape, donor funding structure, political economy) actually driving this choice are pragmatic. The architecture is rarely chosen in advance, but accrues over time via installed base, funding availability, and IT capacity at MoH to manage ETL middleware. Thus the guidance on interoperability layer to choose should be studied in more detail. Suggested revision: Acknowledge that the decision for centralized vs federated vs hybrid depends on pragmatic considerations for development and maintenance, not just architectural ideals. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | |
| PC-0412✎ edit📣 feedback | received | general | Core architects ai |
4.6 Financing and Partnerships §4.6 p.102-103 anchor: medium |
We fully support advocating for a recurrent line item in national health budget to signal government ownership of DPI-H…We fully support advocating for a recurrent line item in national health budget to signal government ownership of DPI-H. In addition to payment for recurrent domestic costs of running these systems, contributions to the technologies that underpin their DPI-H, particularly for digital public goods, would be strategic, cost-efficient, and risk free means for maintaining the technologies long-term. Contributions may take the form of DPG capacity building, feature suggestions, or in-kind support to the national innovation ecosystem around DPGs. One direct contribution model, now underway through DHIS2 Shared Services Fee, offers a novel global funding strategy to sustain the digital public goods of DPI-H. If a country contributes even marginally to a pooled fund, then it directly contributes to a stake in platform governance, security, and maintenance, which will have downstream benefits for their national DPI-H. We note tha without a durable funding stream for digital public goods, countries will either need to accept the long-term risk of product degradation, or turn to proprietary software vendors, which have been shown by evidence to be more costly on aggregate. Suggested revision: Describe community contributions and pooled funding models as means to sustain DPI-H tools and capacity in the country. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-115 discuss | in the document all mentions on GitHub record | |
| PC-0413✎ edit📣 feedback | received | general | Core architects ai |
4.6.3 Approaches to Financing §4.6 p.103 l.582-584 |
This is a suitable framing.We support continuing engagement with partners within and outside the government to align al…This is a suitable framing.We support continuing engagement with partners within and outside the government to align all contributions within the national architecture. However, we note that we have not yet seen a country trainsition from from primarily donor-to-domestic financing for their DPI-H. Such a dynamic limits full country ownership and, long-term, the sustainability of open source digital public goods which compose DPI-H. Suggested revision: Identify countries in examples section that are actively "weaning off" donor support for DPI-H, or have evidence of mature domestic funding models. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | |
| PC-0414✎ edit📣 feedback | received | technical | Supply chain ai |
Product Registry §Appendix C p.145 l.379-478 |
The national LMIS must build on the Product Registry and ensure complete alignment and compliance. In practice, DHIS2 w…The national LMIS must build on the Product Registry and ensure complete alignment and compliance. In practice, DHIS2 will only use an item code and item description which must be completely aligned with the upstream, national LMIS such as mSupply (which must be indirectly aligned with the Product Registry). I fully support this approach. Any LMIS system in a country must categorically align to any national regulations and registries, also to ensure interoperability. Codes and names in DHIS2 must always match names on products, packing lists and any national documents. Even small discrepancies will cause confusion and mistakes in ordering, stock management and use of healthcare goods. Having several different item codes and descriptions is common and a logistics night mare. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-165 discuss | in the document all mentions on GitHub record | |
| PC-0415✎ edit📣 feedback | received | technical | Supply chain ai |
Product Registry §Appendix C p.146 l.379-478 |
GTINs: fully endorsed but just noting that GTINs are assigned by national authorities and the same product may have dif…GTINs: fully endorsed but just noting that GTINs are assigned by national authorities and the same product may have different different GTINs in different countries. Therefore uniqueness is not insured when healthcare goods are imported from various countries. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | |
| PC-0416✎ edit📣 feedback | received | technical | Supply chain ai |
Product Registry §Appendix C p.147 l.379-478 |
UNSPSC: no objection but this is just a classifier and not a product identifier and useless for end-usersUNSPSC: no objection but this is just a classifier and not a product identifier and useless for end-users Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-167 discuss | in the document all mentions on GitHub record | |
| PC-0417✎ edit📣 feedback | received | technical | Supply chain ai |
Health Workforce Registry §Appendix C p.148 l.379-478 anchor: medium |
Base unit: must almost be the smallest, indivisible unit such as one table, one vial, one suture etc. with any number o…Base unit: must almost be the smallest, indivisible unit such as one table, one vial, one suture etc. with any number of additional packaging quantities Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | |
| PC-0418✎ edit📣 feedback | received | technical | Supply chain ai |
C Appendix C: DPI-H Application Component Descriptions §Appendix C p.149 l.379-478 anchor: medium |
GS1 coding: DHIS2 natively features parsing of GS1 DataMatrix codes. However, regardless of coding requirements in the …GS1 coding: DHIS2 natively features parsing of GS1 DataMatrix codes. However, regardless of coding requirements in the Product Catalogue, for stock management only the codes printed on products are relevant and those depend on (international) manufacturers. For the last mile, using manufacturer codes is not practical because not all products feature codes (especially non-sterile medical devices) and because two products from two different manufacturers can be therapeutically equivalent but need to be managed as the same stock entity. Therefore, it is much better to use QR-code labels on shelving which must of course be aligned with the national registry. Brian O'Donnell (on behalf of HISP-UiO), HISP Centre at University of Oslo, Norway |
none | not yet | CS-167 discuss | in the document all mentions on GitHub record | |
| PC-0419✎ edit📣 feedback | received | general | Core architects ai |
unplaced §Across the document p.- l.- |
It may be useful for the draft to give more explicit consideration to include emergency care and blood-bank services wi…It may be useful for the draft to give more explicit consideration to include emergency care and blood-bank services within the proposed digital health architecture. Blood bank and transfusion services, as well as emergency medical response, are important areas within digital health (As reflected in WHO's classification of digital health interventions ID: 9789240081949) and could be reflected more clearly across the relevant priority goals and components. For example, the Facility Registry could consider including blood banks and ambulance/EMS stations within its illustrative facility types and services. Similarly, the Public Health Surveillance Platform and Product Registry could consider whether there are relevant use cases for these domains. It may also be worth considering whether emergency response and blood-bank services would benefit from a more explicitly defined business process or component, given their close relationship with several of the capabilities already described in the architecture. Making these linkages more explicit could help ensure that the architecture is sufficiently comprehensive across essential health-service delivery domains. Suggested revision: Suggested addition to Sec 1.5 (under the relevant priority goal): 'Illustrative examples of essential health services supported by this goal include emergency medical response and blood/transfusion services.' Suggested addition to the Facility Registry's Facility type field (p.131): extend the illustrative list to read '...health centre, dispensary, pharmacy, laboratory, mobile clinic, blood bank, ambulance/EMS station.' Suggested addition to the Type of services offered field (p.132): extend to '...emergency care, ambulance/EMS coordination, blood and transfusion services, ANC, laboratory, HIV treatment, TB, surgery, pharmacy.' Mohd Hussain Shaik, Asian Development Bank, India |
none | not yet | CS-259 discuss | all mentions on GitHub record | |
| PC-0420✎ edit📣 feedback | received | technical | Core architects ai |
3.7.1 Purpose §3.7 p.78 l.964 anchor: medium |
It may be valuable to expand the conformance and testing approach in Sec 3.7 to include non-functional testing for high…It may be valuable to expand the conformance and testing approach in Sec 3.7 to include non-functional testing for high-demand and emergency scenarios. For example, a pandemic or other major public-health event could lead to simultaneous increases in patient registrations, laboratory results, surveillance data and supply requests across the country. Testing could therefore consider whether core registries and the Lifelong Health Record can maintain performance and availability under peak loads, as well as how they operate under degraded-connectivity conditions. Including peak-load simulation, resilience and degraded-connectivity testing as part of the testing framework could provide implementers with a practical way to assess pandemic readiness and system resilience. This would be very relevant from an outbreak/pandemic perspective. Suggested revision: Suggested new subsection, e.g. 3.7.7 Non-functional and resilience testing: "In addition to functional conformance, implementers should consider testing core registries and the Lifelong Health Record under peak-load conditions, for example, simulating a surge in registrations, laboratory results and supply requests consistent with a pandemic or other major public-health event and under degraded-connectivity conditions, to assess whether performance and availability are maintained and how the system degrades when they are not." Mohd Hussain Shaik, Asian Development Bank, India |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | |
| PC-0421✎ edit📣 feedback | received | general | Clinical ai |
C Appendix C: DPI-H Application Component Descriptions §Appendix C and relevant pages p.161 l.#16 (SHRF-8) anchor: medium |
It may be useful to give research and public-health analysis more explicit consideration in the design of the Lifelong …It may be useful to give research and public-health analysis more explicit consideration in the design of the Lifelong Health Record. The ability to use health data for appropriately governed secondary purposes will be an important benefit of shared digital health infrastructure. The draft allows countries to implement the Lifelong Health Record through fully federated or virtual models, which provides useful flexibility. In this context, it may be worth considering whether the secondary-use export capability described under SHRF-8 should be strengthened, particularly for federated or virtual implementations. A clearer requirement or minimum expectation for this capability could help ensure that appropriately governed health-data access for research and public-health analysis remains feasible regardless of the underlying LHR implementation model. Suggested revision: Suggested revision to SHRF-8: change status from Recommended to Required, at minimum for federated, hybrid and virtual-record implementations. Suggested wording: 'The LHR shall support the ability to export data for secondary use, including for HMIS, PHSP, research and analytics purposes, in agreed formats and through agreed access governance mechanisms, without requiring parallel or duplicative data collection from source systems. (Required for federated, hybrid and virtual-record implementations; Recommended otherwise.)' Mohd Hussain Shaik, Asian Development Bank, India |
none | not yet | CS-252 discuss | in the document all mentions on GitHub record | |
| PC-0422✎ edit📣 feedback | received | technical | Clinical ai |
C Appendix C: DPI-H Application Component Descriptions §Appendix C p.189 l.#21 anchor: medium |
It may be useful to complement the CDSE's existing technical safety features and functional testing with a more explici…It may be useful to complement the CDSE's existing technical safety features and functional testing with a more explicit clinical-safety risk-governance methodology. The existing provisions around safe failure, continuity, governance, knowledge review and liability provide a useful foundation. A further layer of structured clinical-risk management could include elements such as a hazard log covering potential failure modes, a defined approach for assessing the severity of identified risks, and a clearly assigned role or accountability for overall clinical safety. These elements would align the framework more closely with established approaches to clinical software risk management, including the structures reflected in ISO 14971 and the UK's DCB0129/0160 standards. Including such a methodology as an explicit governance expectation could strengthen the overall clinical-safety framework. Suggested revision: Suggested addition as an eighth governance consideration (p.189): '(8) Clinical risk management. Countries should maintain a structured clinical risk-management process for the CDSE, comprising: a hazard log recording identified failure modes and their potential clinical impact; a risk classification scheme for grading the likelihood and severity of harm; and a named, accountable clinical safety role responsible for the CDSE's overall risk posture. This should draw on established frameworks such as ISO 14971 and the UK's DCB0129/DCB0160 clinical risk management standards.' Mohd Hussain Shaik, Asian Development Bank, India |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | |
| PC-0423✎ edit📣 feedback | received | technical | Financial systems ai |
C Appendix C: DPI-H Application Component Descriptions §Appendix C p.206 l.156 anchor: medium |
It may be valuable to establish a minimum cross-scheme reconciliation requirement linking country-specific Contract and…It may be valuable to establish a minimum cross-scheme reconciliation requirement linking country-specific Contract and Benefits Management Systems (CBMS) with the shared Client Registry identity. The draft provides a useful description of the relationship between the Benefits Package Registry, Beneficiary Registry and CBMS, including the importance of reliable enrolment records for identifying duplicate enrolment and potential fraud. Given that CBMS implementations are country-specific, a minimum interoperability expectation could help ensure consistent safeguards across different health schemes. For example, a requirement for country-specific CBMS implementations to reconcile enrolments and claims against the shared Client Registry identity could provide a common baseline for detecting duplicate enrolment and supporting appropriate fraud-prevention processes. Suggested revision: Suggested addition (p.206-208, Distinguishing... section): 'Any country-specific Contract and Benefits Management System (CBMS) implementation should reconcile enrolment and claims records against the shared Client Registry identity, and should support a standard cross-scheme check for duplicate enrolment, to provide a common baseline for fraud-prevention and eligibility-verification processes across schemes.' Mohd Hussain Shaik, Asian Development Bank, India |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | |
| PC-0424✎ edit📣 feedback | received | general | Clinical ai |
5.1 Emerging technologies and the foundations they depend on §5.1 p.104 l.28 |
It may be useful for the architecture to consider citizens not only as users of digital health services, but also as po…It may be useful for the architecture to consider citizens not only as users of digital health services, but also as potential contributors of health data. This could help make the proposed infrastructure more future-ready as self-testing kits, home-monitoring devices and wearable technologies become increasingly common sources of health information. One option could be to provide an optional, appropriately governed pathway for patient-generated health data, including data from wearables and home-monitoring devices, to be incorporated into the Lifelong Health Record where appropriate. The future-proofing section could also give this area more dedicated consideration, building on the existing recognition of wearables and remote monitoring as an emerging trend. Providing a clear architectural direction for these data sources could help countries accommodate new forms of patient-generated data while retaining appropriate governance and safeguards. Suggested revision: Suggested addition to Sec 5.1: 'Where appropriate governance and consent mechanisms are in place, countries may wish to establish an optional pathway for patient-generated health data, including data from personal wearables and home-monitoring devices, to be incorporated into the Lifelong Health Record, subject to the same consent and data-quality safeguards that apply to other data sources.' Suggested expansion to the Chapter 5 introduction (p.104): develop the existing reference to 'remote monitoring, wearable sensors' into a short dedicated paragraph describing their implications for the shared health data foundation. Mohd Hussain Shaik, Asian Development Bank, India |
none | not yet | CS-271 discuss | in the document all mentions on GitHub record | |
| PC-0425✎ edit📣 feedback | received | general | Core architects ai |
4.6.1 The Investment Case §4.6 p.102 l.548 |
The case for engagement with Ministries of Finance could potentially be strengthened by including a small number of qua…The case for engagement with Ministries of Finance could potentially be strengthened by including a small number of quantified examples alongside the discussion of reduced leakage and efficiency gains. For this audience, concrete evidence on the scale of potential savings or improvements can help translate the broader value proposition into fiscal terms. Examples from countries that have documented benefits from government data-exchange and digital-service infrastructure could be particularly useful. Including an example, with appropriately sourced figures and a brief explanation of the context in which the benefits were achieved, could make the section more compelling while also helping readers understand the potential magnitude of the benefits. Suggested revision: Example addition to Sec 4.6.1: 'For example, Estonia's X-Road data-exchange infrastructure has been associated with documented reductions in administrative processing time and cost across government services (or) Singapore's APEX platform has been associated with a measurable reduction in the time required to complete government-service applications.' Mohd Hussain Shaik, Asian Development Bank, India |
none | not yet | CS-116 discuss | in the document all mentions on GitHub record | |
| PC-0426✎ edit📣 feedback | received | technical | Core architects ai |
3.6 Interoperability Architecture within DPI-H §3.6 p.71 anchor: medium |
It may be helpful for the draft to provide greater clarity on how and when consent is operationalised when health data …It may be helpful for the draft to provide greater clarity on how and when consent is operationalised when health data are exchanged. The principle that consent should travel with an individual's data provides an important foundation. The architecture could build on this by specifying, for each of the proposed data-sharing approaches, where the consent status is checked, when that check takes place, and how the result is communicated or enforced when systems exchange data directly rather than through a central hub. Providing this operational detail would help implementers translate the consent principle into consistent technical processes and would strengthen the connection between the principle described earlier in the document and its implementation in subsequent sections. Suggested revision: Suggested addition to Sec 3.6, for each exchange pattern (centralised, federated, hybrid): 'In a federated exchange, the requesting system should verify the individual's current consent status with the source system (or a designated consent service) at the time of each query, and the response should reflect that status before any data is returned.' (Adapt equivalent wording for the centralised and hybrid patterns.) Mohd Hussain Shaik, Asian Development Bank, India |
none | not yet | CS-235 discuss | in the document all mentions on GitHub record | |
| PC-0427✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §Lifelong Health Record p.155 l.7–29 |
The draft correctly supports federated and hybrid models. It should explicitly recognise research institutions, clinica…The draft correctly supports federated and hybrid models. It should explicitly recognise research institutions, clinical-research platforms, laboratories and biorepositories as authorised source applications that retain operational custody of their records. Suggested revision: Add clinical-research management systems, LIMS, biorepository information-management systems and research-data repositories as recognised functional applications and data contributors within a federated DPI-H ecosystem. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0428✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §Lifelong Health Record p.155 l.10–14 |
Laboratories should be expanded to include research laboratories and biobanks/biorepositories where applicable. Biospec…Laboratories should be expanded to include research laboratories and biobanks/biorepositories where applicable. Biospecimen information requires collection, processing, storage, quality, chain-of-custody, transfer and disposal records. Suggested revision: Amend the source-system list to include “laboratories, research laboratories, biobanks/biorepositories, pharmacies and authorised research systems.” Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0429✎ edit📣 feedback | received | general | Clinical ai |
Lifelong Health Record §Lifelong Health Record p.155 l.26–30 |
The statement that the LHR is not a central data lake should be strengthened for research, genomic and biospecimen data…The statement that the LHR is not a central data lake should be strengthened for research, genomic and biospecimen data. These data may be sensitive and governed by ethics approvals, participant choices and controlled-access requirements. Suggested revision: State that research, genomic and biospecimen data should normally remain in an authorised source system or controlled repository. The LHR may retain only minimum clinically relevant, consented information or metadata, with detailed data accessed through federated and governed mechanisms. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0430✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §LHR core attributes p.157 l.98–102 |
Longitudinal health data may arise from clinical research and specimen collection as well as routine care. The architec…Longitudinal health data may arise from clinical research and specimen collection as well as routine care. The architecture should recognise this without allowing research data to be reused for care or public-health purposes without an appropriate legal and ethical basis. Suggested revision: Include authorised clinical-research and biobank systems as possible sources, subject to ethics approval, participant consent choices, purpose limitation and applicable national law. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0431✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §LHR core attributes p.157 l.111–114 |
Consent for clinical care is not automatically consent for biospecimen storage, future research use, genetic or genomic…Consent for clinical care is not automatically consent for biospecimen storage, future research use, genetic or genomic analysis, data sharing, cross-border transfer, re-contact or commercial collaboration. Participants need meaningful choices about storage and use of samples and associated data. Suggested revision: Require interoperable consent management that separately records consent for collection; storage; current-study use; future use; genetic/genomic analysis where relevant; sharing; cross-border transfer where relevant; re-contact; and withdrawal. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0432✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §LHR core attributes p.157 l.111–121 |
Consent and provenance should not be reduced to a simple access flag. Research use may depend on the approved protocol,…Consent and provenance should not be reduced to a simple access flag. Research use may depend on the approved protocol, ethics committee conditions, data-access requirements and, where material is distributed, material-transfer obligations. Suggested revision: Ensure consent records retain consent version, date, study/protocol identifier, ethics approval reference, permitted purposes, review or expiry conditions, restrictions, withdrawal history and authorised decision-making body where applicable. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0433✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §LHR core attributes p.157 l.119–121 |
Data provenance should cover the full biospecimen lifecycle, not only the origin of clinical data. This supports partic…Data provenance should cover the full biospecimen lifecycle, not only the origin of clinical data. This supports participant protection, scientific validity and ISO 20387-aligned quality management. Suggested revision: Add biospecimen provenance requirements for collection, receipt, processing, parent–child and aliquot relationships, storage location, temperature excursions, quality assessment, retrieval, transfer, use, return and disposal; including actor, system, date/time and location. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0434✎ edit📣 feedback | received | technical | Metadata registries ai |
Terminology Service §Terminology Service p.164 l.7–15; 25–30 |
The Terminology Service should cover biospecimen and research-data terminology alongside clinical terminology, enabling…The Terminology Service should cover biospecimen and research-data terminology alongside clinical terminology, enabling laboratory and biobank data to be safely interpreted, reused and exchanged across studies and countries. Suggested revision: Include standardised concepts for sample type, collection method, parent/aliquot relationships, processing method, storage condition, quality indicators, consent category, access conditions and research-study metadata. Support mapping of local laboratory and biobank terms to recognised national and international terminologies. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0435✎ edit📣 feedback | received | technical | Metadata registries ai |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §FHIR p.96 l.Section 4.3.3 anchor: medium |
The interoperability guidance should include a minimum profile for clinical research, laboratories and biobanks. This i…The interoperability guidance should include a minimum profile for clinical research, laboratories and biobanks. This is relevant to institutions that link participant care, research, diagnostics and biospecimen repositories. Suggested revision: Recommend exchange using Patient, ResearchSubject, ResearchStudy, Consent, ServiceRequest, Specimen, Observation, DiagnosticReport, DocumentReference and Provenance, with national implementation guides and terminology bindings. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-098 discuss | in the document all mentions on GitHub record | |
| PC-0436✎ edit📣 feedback | received | technical | Core architects ai |
3.6.5 Conformance §Conformance and testing p.78–86 l.Section 3.6 anchor: medium |
Conformance should test more than data transmission. Laboratory and biobank systems need testing of identity matching, …Conformance should test more than data transmission. Laboratory and biobank systems need testing of identity matching, specimen traceability, consent enforcement, terminology validation, access control, audit trails and correction workflows. Suggested revision: Add test scenarios for participant-to-specimen linkage; parent–child specimen relationships; role-based access; consent withdrawal; provenance; offline capture and synchronisation; safe correction of records; and controlled exchange with authorised research systems. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | |
| PC-0437✎ edit📣 feedback | received | general | Core architects ai |
Metadata registries and foundational components §Appendix C — Component catalogue p.114–228 l.Component catalogue anchor: medium |
The component catalogue does not adequately represent the wider workflow of research institutions. MakBRC-type institut…The component catalogue does not adequately represent the wider workflow of research institutions. MakBRC-type institutions support grant and project management, clinical research, procurement, equipment management, ICT operations, LIMS, BIMS, research data management, analysis and reporting. Suggested revision: Recognise these as connected functional applications that may consume or contribute to DPI-H services while remaining outside the central foundational layer. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-171 discuss | in the document all mentions on GitHub record | |
| PC-0438✎ edit📣 feedback | received | general | Core architects ai |
4.1.1 No Country Starts from Zero §Chapter 4 — Implementation guidance p.88–103 l.Chapter 4 anchor: medium |
Implementation guidance should better address settings with intermittent connectivity, limited ICT staffing, laboratory…Implementation guidance should better address settings with intermittent connectivity, limited ICT staffing, laboratory equipment dependencies and the need to protect samples and data during outages. Suggested revision: Include offline-first workflows, barcode-based identification, local caching of terminology, queued synchronisation, secure backups, disaster recovery, cybersecurity controls, temperature-monitoring interfaces, equipment-maintenance integration and sustainable local technical capacity. Dafala Kezimbira, Makerere University Biomedical Research Centre, Uganda |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | |
| PC-0439✎ edit📣 feedback | received | technical | Metadata registries ai |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.315–321;and the subsequent discussion of FHIR-based implementation profiles on pp. 331–338 |
Lines 315–321 appropriately distinguish the authoritative, technology-independent logical model from its FHIR represent…Lines 315–321 appropriately distinguish the authoritative, technology-independent logical model from its FHIR representation. However, the subsequent recommendation to align underlying data models with FHIR resource structures may be interpreted as suggesting that the canonical semantic model should mirror the FHIR resource model. At national scale, this could create representation lock-in and make support for alternative exchange, analytical or persistence models more costly. Suggested revision: Retain FHIR as the recommended exchange framework, but clarify that FHIR readiness means preserving FHIR-mappable semantics and constraints, rather than requiring the canonical logical model to mirror FHIR resources. Define governed mappings or projections from the technology-independent model to FHIR profiles, with stable semantic identifiers, terminology bindings and mapping rules serving as the durable interoperability contract. This distinction between the canonical, technology-independent model and its FHIR representation also underlies the semantic-provenance requirement proposed for the Lifelong Health Record (see comment 3). Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | |
| PC-0440✎ edit📣 feedback | received | technical | Core architects ai |
4.3.5 Minimum Conformance and Testing §4.3.5; 4.4.2 p.98–99 l.399–408; 445–463 |
The draft provides useful lifecycle governance for semantic artefacts and recommends continuing national conformance mo…The draft provides useful lifecycle governance for semantic artefacts and recommends continuing national conformance monitoring. However, it does not yet make explicit how a product-level certification result remains interpretable as the normative baseline evolves. Without an explicit binding to the versions tested, a product may remain labelled “certified” even after relevant profiles, terminology resources, test suites or product releases have materially changed. Suggested revision: Make each conformance statement or certificate explicitly version-scoped. At minimum, record the tested actor role(s), profile or implementation-guide version, relevant logical-model and terminology/value-set versions, test-suite version and product release. Define expiry or reassessment triggers for material specification or product changes, together with a transition policy for overlapping versions and risk-based post-deployment surveillance. This would complement, rather than duplicate, the document’s existing artefact-lifecycle governance This is a distinct but related concern to the assurance operating model proposed in comment 5: this comment addresses what a conformance statement should record, while comment 5 addresses who should be authorised to issue it. Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | |
| PC-0441✎ edit📣 feedback | received | technical | Metadata registries ai |
Lifelong Health Record §Appendix C- Lifelong Health Record p.158 l.107–121 |
The LHR requirements appropriately address source provenance and record versioning, while the LIMR and Terminology Serv…The LHR requirements appropriately address source provenance and record versioning, while the LIMR and Terminology Service provide versioned management of semantic artefacts. However, the draft does not yet make explicit how an individual structured data item is linked to the model, profile, template or terminology context used to encode, validate, transform or migrate it. In a lifelong record spanning multiple generations of models and terminologies, this linkage is necessary to reconstruct the meaning that applied at the time of capture or transformation Suggested revision: Add a semantic-provenance requirement stating that, for structured contributions, the LHR should retain or be able to resolve the applicable model, profile or template identifier and version; the relevant terminology or value-set version, release or effective context; and any transformation or mapping lineage. This need not duplicate complete artefacts in the LHR. Persistent references to versioned content held in the LIMR or Terminology Service may be sufficient, provided that those references remain resolvable for the required retention period. This depends on the same canonical-model/FHIR-representation distinction raised in comment 1; the two points could be addressed together in a single semantic-governance response. Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | |
| PC-0442✎ edit📣 feedback | received | technical | Metadata registries ai |
4.2.2 A Phased Implementation Approach §4.2.2; 4.3.1 p.92; 94–95 l.120–123; 155–177; 257–273 |
The text appropriately states that governance begins in Phase 1 and continues throughout implementation. However, the p…The text appropriately states that governance begins in Phase 1 and continues throughout implementation. However, the phase-specific presentation may be read as placing establishment of the Semantic Governance Infrastructure in Phase 3, after Phase 2 has already introduced the LHR, basic terminology services and interoperability into production. Because Section 4.3.1 calls for data structures and models to be defined and governed before implementation, readers could interpret the sequencing as permitting production semantic dependencies before a minimum governance baseline is in place. Suggested revision: Clarify that Phase 2 requires a minimum semantic-governance baseline before the foundational shared data layer is scaled into production. This baseline need not include a fully developed LIMR. It could comprise named semantic stewards, canonical identifiers, a version and change-management policy, terminology-binding rules, an approval workflow, and a minimum catalogue of governed semantic assets. Phase 3 could then mature these arrangements into the full Semantic Governance Infrastructure and LIMR capabilities. Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | |
| PC-0443✎ edit📣 feedback | received | technical | Core architects ai |
1.4 DPI-H Principles §1.4; 4.2.4; 4.3.5; 4.5.1 p.20; 94; 98; 100 l.394–402; 228–241; 399–408; 473–486 |
The guidance assigns the national digital architect responsibility for architectural accountability, standards and conf…The guidance assigns the national digital architect responsibility for architectural accountability, standards and conformance evaluation, while also recognising reviewers and assessors. It does not yet clearly distinguish responsibility for setting the normative baseline from responsibility for executing high-volume conformity assessment. In a mature national market, concentrating both functions in a small government team could create capacity bottlenecks and perceived conflicts of interest, and could limit the scalability of assurance. The document's own "Public Governance" principle (1.4, lines 394–402) already establishes that components may be operated by public, private or non-governmental actors provided they remain accountable to public oversight - implying a distinction between the body that sets and safeguards the standard and the body that operates or is assessed against it. Section 4.2.4 does not carry this distinction through to the national digital architect role, which combines both functions. Suggested revision: Retain standards ownership, acceptance criteria and regulatory accountability with the national architecture or governance authority, while describing an assurance operating model in which testing may be performed by formally qualified independent laboratories, test centres or shared testing services against nationally governed test suites. Specify requirements for oversight, assessor competence, proficiency testing, quality assurance, transparent scope of authorisation, conflict-of-interest management and periodic requalification. Final conformity approval and regulatory accountability should remain with the competent national authority. This is a distinct but related concern to the version-scoping proposed in comment 2: that comment addresses what a conformance statement should record, this one addresses who should be authorised to issue it. This would extend the separation the document already establishes as a governance principle in 1.4 to the specific architectural role described in 4.2.4, rather than introducing a new requirement. Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-016 discuss | in the document all mentions on GitHub record | |
| PC-0444✎ edit📣 feedback | received | general | Financial systems ai |
4.6.1 The Investment Case §4.6.1–4.6.3 p.102–103 l.548–600 |
The financing chapter distinguishes how DPI-H is financed from what digital health financing can deliver. It could also…The financing chapter distinguishes how DPI-H is financed from what digital health financing can deliver. It could also consider routine financing workflows as one possible implementation lever for interoperability. In settings where claims, reimbursement or provider payment are central to routine operations, standards-conformant digital submission may create a recurring operational incentive for adoption. However, an immediate payment gate could shift effort toward syntactic compliance, exclude smaller providers or create risks of service disruption. Suggested revision: Add an optional, context-dependent implementation pattern in which claims, reimbursement or analogous routine financing workflows are used as a phased incentive for standards-conformant submission rather than as an immediate binary gate. Couple this approach with semantic and data-quality validation, transparent rejection feedback, grace periods, exception handling, appeals or remediation pathways, and technical support for smaller providers. The guidance should note that the choice and timing of such incentives must be aligned with national financing arrangements, legal requirements and equity safeguards. (For example, in Iran, hospitals are legally required to provide free inpatient care for accident-related injuries and subsequently submit claims to the Ministry of Health for reimbursement. Because nationwide compliance with electronic data submission was difficult to achieve immediately, the Ministry initially made reimbursement of these claims to inpatient hospital facilities contingent on submission of structured discharge data to the national electronic health record. In a second phase, basic public insurers similarly linked their hospital reimbursement to data submitted to the national EHR. This phased linkage between payment and EHR submission supported a transition to fully automated, EHR-based claims adjudication for inpatient services.) (A comparable international precedent is the United States' Medicare and Medicaid EHR Incentive Programs- commonly known as "Meaningful Use"- under which providers received payment incentives, and later payment adjustments, tied to demonstrated use of certified EHR technology and structured data submission. The programme achieved rapid national uptake of certified systems, but was also found to shift provider effort toward meeting reportable data-capture criteria rather than toward the underlying clinical objective, and increased documentation burden on clinicians. This reinforces the need, noted above, for semantic and data-quality validation rather than syntactic submission alone, and for monitoring unintended effects on clinical workflow and coding behaviour when payment is linked to data submission.) Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-115 discuss | in the document all mentions on GitHub record | |
| PC-0445✎ edit📣 feedback | received | technical | Metadata registries ai |
2.2.2 The enabling conditions for REDDHI §2.2.2; 3.6.2; Appendix C - Logical Information Model Repository p.28–29; 73–74; 172–188 l.148–151; 811–817; Appendix C- LIMR, architecture placement note (p. 172) anchor: low |
Section 2.2.2 (lines 148–151) and section 3.6.2 (lines 811–817) name HL7 FHIR, SNOMED CT (and SNOMED GPS), ICD-11, LOIN…Section 2.2.2 (lines 148–151) and section 3.6.2 (lines 811–817) name HL7 FHIR, SNOMED CT (and SNOMED GPS), ICD-11, LOINC, GS1/IDMP, DICOM, IHE profiles and the International Patient Summary as the referenced content standards. openEHR is acknowledged separately, as one of the standards the Logical Information Model Repository can anchor to (Appendix C, LIMR, architecture placement note). However, the wider ISO/TC 215 body of health informatics standards is not named in either list- including ISO 13606 (EHR communication), ISO 13940/ContSys (health informatics system of concepts) and ISO 18308 (EHR architecture requirements, cited once only as a footnote reference rather than as a standard the architecture supports). Countries that have already invested in ISO-based national EHR architectures are not given an explicit place in the reference architecture's standards list. Suggested revision: In 2.2.2 or 3.6.2, add ISO/TC 215 standards (ISO 13606, ISO 13940, ISO 18308, and related ISO/TC 215 standards) to the list of standards the architecture references, alongside HL7 FHIR and the openEHR reference already given in Appendix C. This would make explicit- rather than leave implicit- that countries with existing investments in ISO-based national architectures have a recognised path into the reference architecture, without weakening the recommendation of FHIR as the primary exchange framework. Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0446✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §Appendix C- Lifelong Health Record p.157; 161 l.126; 132–135; functional requirements table, row 19 ('Low-resource settings') |
The data-quality and reconciliation requirement (line 126) and the availability and resilience requirement (lines 132–1…The data-quality and reconciliation requirement (line 126) and the availability and resilience requirement (lines 132–135) both note that the record must remain usable under intermittent connectivity, with reconciliation of duplicate or conflicting records and support for offline operation and synchronisation. The functional requirements table (row 19, 'Low-resource settings') similarly requires 'reliable synchronisation... when connectivity is restored'. None of these specifies how a conflict is to be resolved when the same record is edited concurrently at two disconnected points- for example, two facilities updating the same encounter or medication list while both are offline. Given that the LHR explicitly supports federated and distributed deployment (row 18, 'Architecture flexibility'), concurrent offline edits are a routine rather than an edge-case scenario, and the resolution strategy chosen has direct clinical-safety implications. Suggested revision: Add an explicit conflict-resolution requirement for offline and federated synchronisation, specifying at minimum: how concurrent edits to the same record element are detected; whether resolution is automated, and by what rule (e.g. last-write-wins, source-priority, additive merge), or requires clinician review; and how the audit log (row 20) captures the original, conflicting and reconciled versions so that the resolution itself remains traceable. Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-175 discuss | in the document all mentions on GitHub record | |
| PC-0447✎ edit📣 feedback | received | technical | Core architects ai |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4; Appendix C- Lifelong Health Record p.96; 156 l.346–362; 111 |
Section 4.3.4 (lines 346–362) specifies the general and health-specific APIs connecting DPI-H to foundational DPI- ide…Section 4.3.4 (lines 346–362) specifies the general and health-specific APIs connecting DPI-H to foundational DPI- identity verification, civil registration, payment gateway and data exchange APIs- without addressing the consent or legal basis under which health data crosses this boundary into non-health foundational systems. The Lifelong Health Record's consent-governed access control (line 111) is described within the health domain; it is not stated whether, or how, that consent basis and its purpose limitation are carried across, or re-established, when data is exchanged through a foundational, cross-sector API such as a payment gateway or a whole-of-government data exchange. Suggested revision: Add a sentence in 4.3.4 stating that integration interfaces to foundational DPI must carry, or be able to resolve, the individual's consent basis and purpose limitation established in the health domain, and that countries should define- in national data-protection legislation or the interoperability governance arrangements described in 3.4- which cross-sector data flows require a legal basis beyond the health-sector consent already obtained. Somayeh Abedian, 1. Ludwig Boltzmann Institute for Digital Health and Prevention, Salzburg, Austria 2. Institute of Health Policy, Management and Evaluation, Dalla Lana School of Public Health, University of Toronto, Canada 3. Ministry of Health and Medical Education of Iran (Former deputy director at statistics and Information Technology Center- eHealth center/Unpaid leave for research), Austria |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | |
| PC-0448✎ edit📣 feedback | received | general | Core architects ai |
1.1.4 Who can benefit from this guidance? §1.1.4 p.12 l.136 anchor: medium |
The guidance states it serves low-, middle- and high-income settings, but the diagnosis is drawn almost entirely from L…The guidance states it serves low-, middle- and high-income settings, but the diagnosis is drawn almost entirely from LMIC experience: 'high-income' appears twice in the whole document and no high-income federated system is analysed. High-income readers will not find their problem described and may conclude the guidance is not addressed to them. Suggested revision: Distinguish two fragmentation mechanisms. Programme-vertical fragmentation is the pattern the draft describes. Organisation- and market-driven fragmentation is the high-income pattern: thousands of autonomous providers, entrenched vendors, a dominant financier, several statutory regimes. The Netherlands is a clear case of the second, with high digital maturity, twenty years of standardisation and persistent discontinuity of information between providers. State that the remedies differ: the first needs shared components, the second needs an ordering framework over components that largely already exist. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-013 discuss | in the document all mentions on GitHub record | |
| PC-0449✎ edit📣 feedback | received | technical | Core architects ai |
1.2.2 Data exchange DPI and Interoperability in the health sector §1.2.2 p.15 l.210 anchor: medium |
Data exchange DPI is treated as a national design matter. For 30 EU/EEA countries a binding supranational layer already…Data exchange DPI is treated as a national design matter. For 30 EU/EEA countries a binding supranational layer already exists in the European Health Data Space Regulation, which mandates specific services, bodies, rights and deadlines and removes national discretion in defined areas. The EHDS is not mentioned once in the document, which is the largest single applicability gap for high-income settings. Suggested revision: Add a subsection on operating within a binding regional legal framework, using the EHDS as the worked example: the mandated national access services and health data access bodies, MyHealth@EU as an operating cross-border implementation, and the primacy of the Regulation over national architecture choices. Say how to read the reference architecture where design space is constrained from above as well as from below, and treat comparable regional instruments elsewhere the same way. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-261 discuss | in the document all mentions on GitHub record | |
| PC-0450✎ edit📣 feedback | received | technical | Core architects ai |
3.6.4 Cross-border health data flows §3.6.4 p.77 l.905 anchor: medium |
The treatment of cross-border flows does not reference the most advanced operating implementation of this capability. M…The treatment of cross-border flows does not reference the most advanced operating implementation of this capability. MyHealth@EU has exchanged patient summaries and ePrescriptions between member states for several years, with a governed terminology layer and an established legal basis. Any region planning cross-border exchange would benefit from that evidence. Suggested revision: Cite MyHealth@EU and its central value-set governance as a worked example, including what it shows about semantic governance at scale and about legal prerequisites. Add the Dutch experience of connecting to it, where the binding constraint proved not to be the exchange specification but the absence of any national obligation on providers to make the data available in the first place. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-261 discuss | in the document all mentions on GitHub record | |
| PC-0451✎ edit📣 feedback | received | general | Core architects ai |
4.1.1 No Country Starts from Zero §4.1.1 p.88 l.13 anchor: medium |
The starting point is framed technically: inherited systems, legacy platforms, donor-funded tools. In institutionally p…The starting point is framed technically: inherited systems, legacy platforms, donor-funded tools. In institutionally plural systems the binding constraint is legally protected institutional autonomy rather than legacy technology. Providers cannot be required to participate, professional bodies hold normative authority, vendors hold contractual positions. A country can be technically advanced and structurally unable to act. Suggested revision: Extend the assessment of the starting point to institutional and legal preconditions alongside technical ones, with four questions: is there a party empowered to require participation; is there an enforceable norm; is there a durable funding basis; is there a route for resolving disputes. In the Netherlands all four are absent after two decades of investment, which explains persistent fragmentation better than any technical variable. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | |
| PC-0452✎ edit📣 feedback | received | technical | Core architects ai |
4.1.2 Assessing Where You Are §4.1.2 p.88 l.28 anchor: medium |
The maturity assessment measures capabilities and coverage but not the authority behind them. Two countries with identi…The maturity assessment measures capabilities and coverage but not the authority behind them. Two countries with identical component coverage have entirely different prospects if one can oblige participation and the other cannot, yet they would score the same. Suggested revision: Add an ordering-readiness dimension, scored separately from technical maturity: duty to connect; right to connect; enforceable norms with proportionate sanctions; statutory tariff or recurrent budget basis; accessible dispute resolution; designated holder per shared function. Countries can then see whether their gap is technical, institutional, or both, which determines what kind of intervention will help. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | |
| PC-0453✎ edit📣 feedback | received | general | Core architects ai |
4.6.2 Sustainability by Design §4.6.2 p.102 l.573 |
Sustainability by design names legislation as one of five reinforcing dimensions and states it deserves equal weight, b…Sustainability by design names legislation as one of five reinforcing dimensions and states it deserves equal weight, because the right to operate shared infrastructure, to share data across programmes and to require conformance all rest on it. The architecture chapters then offer no guidance on the legal instruments that deliver it. This is the largest gap between what the draft asserts and what it provides. Suggested revision: Add a subchapter on legal instruments for DPI-H, parallel to the governance subchapter, covering at minimum: a duty to connect; a corresponding right to connect on non-discriminatory terms; a statutory basis for processing that does not depend on case-by-case consent; a graduated and proportionate enforcement ladder; a tariff or cost-recovery basis; designated holdership per shared function; accessible dispute resolution; and a revision clause. The Dutch case shows the cost of omission: a national exchange infrastructure was technically completed while its enabling Bill was rejected by the Senate in 2011, after which it has operated on a private-law basis with voluntary participation for fifteen years. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | |
| PC-0454✎ edit📣 feedback | received | technical | Core architects ai |
1.4 DPI-H Principles §1.4 p.20 l.394 |
Public governance is rightly defined as accountable stewardship under public mandate rather than public ownership. But …Public governance is rightly defined as accountable stewardship under public mandate rather than public ownership. But the principle names no instrument that makes the accountability real, so 'accountable to public oversight' is a statement of intent that almost any arrangement can claim to satisfy. Suggested revision: List the minimum instruments that give the principle effect: formal designation of the operator with a defined mandate and term; an approved multi-year plan; performance published and measured by a party other than the operator; a proportionate sanction available to the overseeing authority; and a transfer regime if the operator fails or exits. In the Netherlands generic national functions are operated by private-law foundations funded predominantly by one payer with none of these instruments in place - an arrangement that satisfies the principle as currently worded. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-016 discuss | in the document all mentions on GitHub record | |
| PC-0455✎ edit📣 feedback | received | general | Core architects ai |
1.4 DPI-H Principles §1.4 p.21 l.412 |
There is no right of access for participants anywhere in the guidance. Public governance protects the infrastructure fr…There is no right of access for participants anywhere in the guidance. Public governance protects the infrastructure from capture by a single programme, donor or vendor, but nothing protects an individual participant - a provider, a regional collaborative, a small vendor - from being refused, delayed or charged differently by whoever operates the shared component. A duty to connect without a right to connect is an obligation to become dependent on a party that may refuse. Suggested revision: Add a right to connect as a DPI-H principle: any conformant participant may connect to a DPI-H component on published, non-discriminatory terms, within a defined lead time, with a route of appeal if refused or delayed. This mirrors third-party access in other regulated infrastructure and is, in Ostrom's terms, recognition of the right to organise. For small providers the right should be exercisable collectively, through a vendor or collaborative connecting on their behalf, with the cost carried in the tariff rather than in their own budget. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-018 discuss | in the document all mentions on GitHub record | |
| PC-0456✎ edit📣 feedback | received | technical | Core architects ai |
3.4.1 Purpose and framing §3.4 p.53 l.219–220 anchor: medium |
The governance chapter contains no dispute resolution. Transparency and accountability are required and escalation betw…The governance chapter contains no dispute resolution. Transparency and accountability are required and escalation between operational and strategic governance is described, but there is no route for a participant or citizen with a grievance: refused connection, refused correction of a record, disagreement over a shared object, or contested access. Governance without a grievance route relies on the goodwill of the party complained about. Suggested revision: Add dispute resolution as an operational governance function: low-threshold, accessible to providers, vendors and citizens, independent of the operator complained about, with published decisions so that precedent accumulates. Ostrom's design principles make locally accessible conflict resolution a condition for durable commons governance, and its absence is a good predictor of arrangements that erode. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-046 discuss | in the document all mentions on GitHub record | |
| PC-0457✎ edit📣 feedback | received | technical | Core architects ai |
3.4.2 Governance principles §3.4.2 p.54 l.273 |
This principle refers to enforcement mechanisms proportionate to scale and diversity of users, but the guidance nowhere…This principle refers to enforcement mechanisms proportionate to scale and diversity of users, but the guidance nowhere describes what enforcement consists of. Without a described ladder the only sanctions available in practice are withdrawal of funding, which punishes participants rather than abstainers, and exclusion from the infrastructure, which is unusable against a care provider. Suggested revision: Describe a graduated enforcement ladder and differentiate it by participant type. For vendors and component operators the top rung can be withdrawal of certification, which excludes a product and not care. For care providers it must remain administrative and financial - formal direction with a remedy period, penalty payments, consequences in the tariff - because disconnecting a provider creates a conflict with its statutory duty to deliver safe care. For holders of shared objects the proportionate top rung is transfer of holdership. This differentiation is absent from the draft and is where enforcement provisions usually fail in practice. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-046 discuss | in the document all mentions on GitHub record | |
| PC-0458✎ edit📣 feedback | received | technical | Core architects ai |
3.4.2 Governance principles §3.4.2 p.54 l.254 |
The principle separates strategy from operations, and elsewhere the draft requires that no single programme, donor or v…The principle separates strategy from operations, and elsewhere the draft requires that no single programme, donor or vendor control access or evolution. Neither addresses the combination of roles within one organisation: operating the shared infrastructure, holding the data that flows over it, and being its dominant funder. That combination makes improper influence possible even where none occurs, and no conduct rule fully remedies it. Suggested revision: Add a structural separation requirement: the infrastructure operator role, the data holder role and a dominant funding relationship should not coincide in one entity, irrespective of whether misuse is demonstrated. Ordering law elsewhere works this way - Dutch electricity legislation prohibits combining network operation, supply and ownership interest without requiring proof of abuse in each case. In Dutch health information the three roles are currently intertwined, which illustrates why a conduct rule is insufficient. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-045 discuss | in the document all mentions on GitHub record | |
| PC-0459✎ edit📣 feedback | received | technical | Core architects ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.633 anchor: medium |
The architecture assigns registries to national level but has no concept of a holder for shared objects that span organ…The architecture assigns registries to national level but has no concept of a holder for shared objects that span organisations: a care-network record, a shared medication overview, a regional care plan. These objects have no single source system, so no participant is responsible for the whole, and in practice nobody maintains them. Suggested revision: Introduce holdership as an explicit architectural property: for every shared object crossing organisational boundaries, name a designated holder accountable for its integrity, availability and lifecycle, distinct from the participants contributing to it. Dutch chain-care information systems document the consequence of omitting this - functionally infrastructural objects existed, no party held them, and maintenance failed without any single actor being at fault. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-038 discuss | in the document all mentions on GitHub record | |
| PC-0460✎ edit📣 feedback | received | general | Core architects ai |
4.2.2 A Phased Implementation Approach §4.2.2 p.90 l.113 anchor: medium |
The implementation guidance does not address what happens when a DPI-H component operator fails, withdraws or is discon…The implementation guidance does not address what happens when a DPI-H component operator fails, withdraws or is discontinued. For infrastructure on which a statutory right depends this is not a residual risk; it determines whether the right is real. Suggested revision: Add continuity of supply as an implementation requirement for every component classified as DPI-H: a designated fallback operator, a transfer dossier maintained in advance, source-code and data escrow, and a transfer plan that is exercised rather than only documented. The Dutch personal health environment programme is a documented case - a subsidised market of applications was created without any party obliged to secure the underlying function, and when the subsidy ended the statutory right of access became unexercisable through no single party's failure. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | |
| PC-0461✎ edit📣 feedback | received | technical | Core architects ai |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.63 l.544 |
The eight criteria describe design properties of a component. They do not answer the prior question a finance ministry …The eight criteria describe design properties of a component. They do not answer the prior question a finance ministry asks: is society dependent on this function such that public financing, supply-security obligations and holdership should attach? A component can satisfy all eight criteria and still be discretionary, and a function society cannot do without may satisfy none of them. Suggested revision: Add a dependency test applied first and cumulatively: (1) irreplaceability - does care delivery or a statutory right stop if this function fails, with no timely alternative route; (2) norm dependence - does its value depend on others using the same rules, so unilateral choices create externalities for third parties; (3) absence of exit - can a participant switch away within a reasonable period without loss of information or continuity. All three yes: infrastructure, warranting holdership, supply security and a tariff. Norm dependence only: standard-setting without a tariff. None: market. The eight design criteria then specify what such a component must look like. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | |
| PC-0462✎ edit📣 feedback | received | technical | Core architects ai |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.562–563 |
The non-transactional criterion is doing two different jobs and risks misclassification. It usefully excludes point-of-…The non-transactional criterion is doing two different jobs and risks misclassification. It usefully excludes point-of-care workflow engines, but read literally it would also exclude a consent or authorisation service, which processes very high real-time transaction volumes while being unambiguously infrastructural. The intended distinction appears to concern the nature of the function rather than the volume of calls. Suggested revision: Reword to separate clinical or administrative transaction processing from high-volume infrastructural operation. Suggested wording: 'not a processor of clinical or administrative transactions within a care or business workflow, though it may operate at high transaction volume in performing infrastructural functions such as identity resolution, authorisation or localisation'. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | |
| PC-0463✎ edit📣 feedback | received | technical | Core architects ai |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.65 l.582 |
The exclusion of point-of-care clinical systems from DPI-H is correct and important. It is also the classification most…The exclusion of point-of-care clinical systems from DPI-H is correct and important. It is also the classification most likely to be contested by ministries and vendors, because these systems consume the largest share of national digital health spending. The draft states the boundary but does not defend it. Suggested revision: Justify the exclusion using the dependency logic: a clinical record system has a working, if costly, exit - providers do replace them - so the public interest is secured by requirements on the product (conformance, exportability, ability to apply and honour access restrictions) rather than by public holdership of the function. Add that such systems remain a vital delivery layer on which conformance requirements should rest, so exclusion from DPI-H is not exclusion from regulation. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-025 discuss | in the document all mentions on GitHub record | |
| PC-0464✎ edit📣 feedback | received | technical | Core architects ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.647 |
The Lifelong Health Record is presented as a component. In federated systems it is not a component but a governed view …The Lifelong Health Record is presented as a component. In federated systems it is not a component but a governed view assembled on request from source systems that remain authoritative. Presenting it as a component invites the reading that a central longitudinal store is intended, which is precisely the reading that has defeated national programmes politically. Suggested revision: Describe the Lifelong Health Record at the two levels the draft already uses for registries: at governance level a single authoritative longitudinal view with defined provenance and attribution; at implementation level a store, a federated view, or a hybrid. State explicitly that a federated implementation satisfies the architecture. In the Netherlands this distinction is decisive: the 2011 Bill was rejected on the concern that data would be centralised, while the architecture in fact kept data at source. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | |
| PC-0465✎ edit📣 feedback | received | general | Core architects ai |
3.5.1 What Distinguishes a DPI-H Application Component §3.6.1 p.65 l.585 anchor: low |
Treating interoperability as a property of the whole rather than a component is one of the most useful clarifications i…Treating interoperability as a property of the whole rather than a component is one of the most useful clarifications in the draft, and it appears as a boundary note in the component chapter. In many countries, including the Netherlands, interoperability is organised as a succession of projects with start and end dates, which is the direct cause of capability that appears and then lapses. Suggested revision: Elevate this into the DPI-H principles in section 1.4 and state the practical consequence: because interoperability is a property and not a deliverable, it cannot be financed as a project and must be funded and governed as a standing capability. This gives countries a concrete test - if interoperability has a completion date in their plan, it is being treated as a component. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | |
| PC-0466✎ edit📣 feedback | received | technical | Core architects ai |
4.4.2 Tracking progress over time §4.4.2 p.99 l.445 anchor: medium |
The progress measures do not say who produces them. In practice the operator of a shared component is the only party ho…The progress measures do not say who produces them. In practice the operator of a shared component is the only party holding data about its own performance and also controls the definitions used. Where that is so, published progress cannot be verified, definitions can change between reporting periods without detection, and enforcement is impossible because the facts are not independently established. Suggested revision: Require that the performance of a DPI-H component be measured and published by a party other than its operator, with definitions fixed in advance and any change disclosed. Add a minimum measurable service-level set: availability and response time at the 95th percentile; transaction success rate against attempts; connection lead time after a complete request; incident resolution time; and conformance test throughput. This is also the precondition for any tariff regulation, since no regulator can set a price on figures supplied solely by the regulated party. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-104 discuss | in the document all mentions on GitHub record | |
| PC-0467✎ edit📣 feedback | received | technical | Core architects ai |
3.7.1 Purpose §3.7 p.78 l.962–963 anchor: medium |
The conformance model covers technical and semantic conformance thoroughly but does not test governance. A component ca…The conformance model covers technical and semantic conformance thoroughly but does not test governance. A component can pass every technical test while having no designated holder, no independently published performance, no transfer plan and no dispute route - which are the failure modes that actually end programmes. Suggested revision: Add governance conformance as a distinct test level with objectively checkable criteria: a designated operator with defined mandate and term; an approved multi-year plan; performance published by an independent party; a maintained transfer dossier and an exercised transfer plan; a functioning dispute route; and a stated revision moment. Countries could then report governance conformance alongside technical conformance, since it is governance conformance that determines whether a capability survives a change of political attention. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | |
| PC-0468✎ edit📣 feedback | received | technical | Core architects ai |
4.4.1 Assessing impact: Are goals being achieved? §4.4.1 p.99 l.427 anchor: medium |
Impact assessment is framed around goal achievement and omits continuity, the property that distinguishes infrastructur…Impact assessment is framed around goal achievement and omits continuity, the property that distinguishes infrastructure from a project. A country can meet every coverage and conformance target while each capability remains one funding decision away from disappearing. Suggested revision: Add continuity indicators: the proportion of essential functions with a designated holder; the proportion with a tested transfer plan; the proportion funded from a recurrent rather than project source; and the number of capabilities discontinued in the reporting period. The last is the most informative and the least often reported. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | |
| PC-0469✎ edit📣 feedback | received | technical | Core architects ai |
4.6.3 Approaches to Financing §4.6.3 p.103 l.578 |
The financing options are well chosen but the guidance does not say who sets the price, on what basis, or with what ove…The financing options are well chosen but the guidance does not say who sets the price, on what basis, or with what oversight. Cost recovery and use-based contributions both require a method for determining allowed cost; without one the arrangement is renegotiated annually, which reproduces the instability that recurrent financing is meant to remove. Suggested revision: Add guidance on tariff design for shared digital infrastructure: a statutory basis for the tariff; an independent body that sets it; cost orientation with an approved and capped investment envelope rather than a return on a regulated asset base, which suits physical networks but not fast-depreciating software; short regulatory periods of two to three years with an efficiency benchmark; and service levels attached to the tariff. Note that the cost-recovery model used for generic government digital services in several countries - billing affiliated organisations against an approved multi-year plan - is a closer precedent than utility regulation. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-114 discuss | in the document all mentions on GitHub record | |
| PC-0470✎ edit📣 feedback | received | technical | Core architects ai |
4.6.3 Approaches to Financing §4.6.3 p.103 l.585–586 |
Tying a contribution to use is sound in principle but creates a free-rider problem the draft does not name. Without a d…Tying a contribution to use is sound in principle but creates a free-rider problem the draft does not name. Without a duty to connect, a use-based contribution is paid by organisations that join and avoided by those that wait, so early adopters subsidise abstainers. This makes waiting individually rational and is a common reason voluntary shared infrastructure stalls at partial coverage. Suggested revision: State the interaction explicitly: use-based financing requires a duty to connect to be equitable, and a duty to connect requires a right to connect to be legitimate. Recommend deciding the three together rather than sequentially. The Netherlands illustrates the failure mode - successive subsidy schemes funded participation by the willing while national coverage remained partial, because nothing obliged the remainder to join. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | |
| PC-0471✎ edit📣 feedback | received | general | Core architects ai |
4.6.1 The Investment Case §4.6.1 p.102 l.547 |
The distinction drawn here between how DPI for health is financed and what DPI for health financing can deliver is amon…The distinction drawn here between how DPI for health is financed and what DPI for health financing can deliver is among the most practically useful points in the document, and it is made once and not carried forward. Conflating the two is the commonest reason investment cases fail with finance ministries. Suggested revision: Promote this distinction to a stated principle and apply it consistently in chapters 1 and 4. Add a third element finance ministries ask for and the draft omits: the cost of not investing, expressed in the same units as the investment. Recommend that countries publish a periodically updated estimate of the annual value of interoperability as a percentage of health expenditure, as a bandwidth rather than a point estimate, with the context conditions that determine where in the bandwidth a given setting falls. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-037 discuss | in the document all mentions on GitHub record | |
| PC-0472✎ edit📣 feedback | received | general | Core architects ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27 l.131 |
This passage explains that the foundational capabilities are interdependent - a longitudinal record has little weight w…This passage explains that the foundational capabilities are interdependent - a longitudinal record has little weight without the registries that establish provenance and attribution. The financing chapter does not draw the consequence: if value arises from interdependence, it cannot be measured component by component, so component-level appraisal will reliably under-invest in the foundation. Suggested revision: State explicitly that the value of DPI-H is emergent from the interdependence described here, and draw the financing consequence in 4.6.1: appraisal should be at the level of the shared foundation rather than the individual component, which is a further argument for recurrent budget lines over project appraisal. This also answers a question the draft leaves open - why health technology with demonstrated value often still fails to be financed. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-027 discuss | in the document all mentions on GitHub record | |
| PC-0473✎ edit📣 feedback | received | technical | Core architects ai |
4.6.2 Sustainability by Design §4.6.2 p.102 l.566 |
Sustainability covers creation and operation but not retirement. Standards, specifications and components are replaced,…Sustainability covers creation and operation but not retirement. Standards, specifications and components are replaced, and the draft does not say who carries the residual cost of what is withdrawn. In practice those costs land on parties that did not decide, which is a disincentive to adopt the next generation. Suggested revision: Add decommissioning to the sustainability dimensions: every new component carries a stated end-of-life review point and a funded decommissioning provision in its cost base, so the cost of withdrawal is budgeted before the cost of build is incurred. This also gives countries a defence against accumulating parallel generations of the same capability, a documented pattern in the Netherlands where successive national programmes were added without any being retired. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-111 discuss | in the document all mentions on GitHub record | |
| PC-0474✎ edit📣 feedback | received | general | Core architects ai |
3.4.2 Governance principles §3.4.2 p.54 l.258 |
This is the strongest statement on equity in the document and it stops one step short. It requires representation to be…This is the strongest statement on equity in the document and it stops one step short. It requires representation to be more than advisory and to carry genuine weight, and it acknowledges that translating nominal representation into real influence is a persistent challenge - but the mechanism offered in 3.4.3 remains representation rather than authority. Suggested revision: Name the mechanism that converts representation into influence: a formal vote on rule changes for the parties those rules bind, including a voting seat for citizen and patient representation, rather than consultative membership. Ostrom's third design principle makes participation in rule modification by those affected a condition for durable governance, and it is the feature most often omitted. Where a duty to participate is imposed, a vote on the rules is its proportionate counterpart. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-048 discuss | in the document all mentions on GitHub record | |
| PC-0475✎ edit📣 feedback | received | general | Core architects ai |
1.3.3 Value Across Stakeholders §1.3.3 p.19 l.329 |
The value analysis does not distinguish value that accrues regardless of an individual's capacity from value that requi…The value analysis does not distinguish value that accrues regardless of an individual's capacity from value that requires the individual to act. That distinction determines the distributional effect of the whole architecture: where value depends on citizen activation, it accrues disproportionately to those with the digital skills, language and health literacy to act, which correlates with income and education. Suggested revision: Separate two roles of the person in the architecture: as reference point, the axis along which information about one individual retains coherence, which requires nothing of them and benefits everyone equally; and as actor, which requires capacity that is unequally distributed. Recommend that the value case rest on the first. The capability approach of Sen and Nussbaum supplies the vocabulary - justify the architecture on the capability it creates, not on the extent to which people exercise it. Australia's national record illustrates the alternative: near-universal enrolment with persistently low activation. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | |
| PC-0476✎ edit📣 feedback | received | general | Core architects ai |
3.4.3 Strategic governance §3.4.3 p.55 l.299 |
Representation of individuals is addressed; representation of those who act on their behalf is not. For the people for …Representation of individuals is addressed; representation of those who act on their behalf is not. For the people for whom continuity of information matters most - those living with dementia, severe mental illness or intellectual disability, and children in care - the actor role is exercised by family carers or legal representatives. The architecture has no concept of delegated authority for information actions, which is distinct from consent. Suggested revision: Add delegated authority as an architectural concept: a recordable, revocable, time-bounded and system-visible mandate specifying who may view, add, correct or grant access on behalf of another, with a route for cases where representatives disagree or none exists. Most legal systems, including the Dutch, provide representation for care decisions and none for information actions; in practice the gap is filled with shared login credentials, which is neither lawful nor safe. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-044 discuss | in the document all mentions on GitHub record | |
| PC-0477✎ edit📣 feedback | received | technical | Core architects ai |
1.5.1 The Health Sector Goals §1.5.1 p.22 l.463 |
The seven goals are outcome-framed, which is right, but none names a non-digital route. In every country a proportion o…The seven goals are outcome-framed, which is right, but none names a non-digital route. In every country a proportion of the population cannot or will not use digital channels. If the architecture's goals are achievable only digitally, the goals themselves encode exclusion. Suggested revision: Add to the goals, or to the design principles, that every function on which a right or entitlement depends must have a non-digital route of equivalent standing, and make it a go/no-go condition for deployment rather than an aspiration. In the Netherlands roughly one in five adults has limited basic digital skills and roughly one in three has difficulty finding, understanding and appraising health information, while 94% of 65–75 year olds use the internet daily. These are three different measures and are routinely conflated. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | |
| PC-0478✎ edit📣 feedback | received | general | Core architects ai |
D.2 Country implementation examples §Appendix D p.231 l.91 |
The country examples are all cases of progress. Without cases where this approach was attempted and did not deliver, a …The country examples are all cases of progress. Without cases where this approach was attempted and did not deliver, a reader cannot calibrate risk and the guidance is open to the charge of selecting on outcome. The most instructive experiences in this field are the unsuccessful ones. Suggested revision: Add three documented negative or partial cases, each read against a specific design choice. The United States HITECH programme financed adoption of clinical record systems at scale without obligations to exchange, producing digitised but non-interoperable organisations until information-blocking rules were added a decade later - the strongest available evidence that funding without ordering does not produce interoperability. Germany's statutory electronic record and its implementing body show that a legal mandate without execution capacity and with deadlocked governance produces years of delay. Australia's national record shows that publicly secured availability does not by itself produce use. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-202 discuss | in the document all mentions on GitHub record | |
| PC-0479✎ edit📣 feedback | received | general | Core architects ai |
D.2 Country implementation examples §Appendix D p.229 l.23 |
No EU/EEA member state with a federated, market-based delivery system appears among the examples, and the Netherlands i…No EU/EEA member state with a federated, market-based delivery system appears among the examples, and the Netherlands is absent altogether. It is an unusually informative case because it separates technical maturity from ordering capacity: high digitisation, mature standards, twenty years of national programmes, and persistent discontinuity of information between providers. Suggested revision: Add the Netherlands with two documented episodes. First, a national exchange infrastructure technically completed while its enabling legislation was rejected by the Senate in 2011, after which it continued on a private-law basis with voluntary participation - a direct illustration of the legal dimension identified in 4.6.2 as deserving equal weight. Second, the personal health environment programme, in which a subsidised market of applications was created without any party made responsible for the underlying function, so that when the subsidy ended a statutory right of access became unexercisable. Both are matters of public record. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0480✎ edit📣 feedback | received | general | Core architects ai |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.198 anchor: medium |
The guidance on legacy systems is technical. The best-documented evidence on why technically sound deployments fail is …The guidance on legacy systems is technical. The best-documented evidence on why technically sound deployments fail is not about legacy interfaces: the United Kingdom's Whole System Demonstrator, a randomised trial with more than six thousand patients, found neither cost-effectiveness nor improvement in quality of life, attributed to implementation difficulty, inability to integrate into existing care practice, and the absence of a working business case. Suggested revision: Cite the Whole System Demonstrator and comparable evaluations, and draw the lesson: technical conformance and clinical plausibility do not predict adoption, so implementation capacity should be planned and financed as a distinct standing resource rather than assumed. Add that evaluations should deliberately include the populations that stand to benefit, which that trial did not, and which remains a common design fault. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-242 discuss | in the document all mentions on GitHub record | |
| PC-0481✎ edit📣 feedback | received | general | Core architects ai |
1.3.1 The Cost of Fragmentation §1.3.1 p.18 l.305–306 |
This sentence, and the analysis of structural incentives preceding it, is the most valuable passage in the document, an…This sentence, and the analysis of structural incentives preceding it, is the most valuable passage in the document, and it sits where a reader may treat it as background. If coordination is a political economy problem, then a reference architecture - a technical instrument - cannot on its own resolve it, and the guidance should say so plainly rather than leaving the inference to the reader. Suggested revision: Move this analysis into the introduction as a framing statement and draw the consequence explicitly: because the obstacle is an incentive structure, shared infrastructure will not emerge from voluntary alignment and requires instruments that change the incentives - obligation, enforcement, separation of roles, recurrent financing and dispute resolution. This supplies the rationale that the governance and financing chapters currently lack. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-013 discuss | in the document all mentions on GitHub record | |
| PC-0482✎ edit📣 feedback | received | technical | Core architects ai |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.71–72 |
This is the correct position and the chapter does not address the strategic risk it creates. Broad semantic harmonisati…This is the correct position and the chapter does not address the strategic risk it creates. Broad semantic harmonisation across all domains is both the most expensive element of a national programme and the element most exposed to automation: normalising free text, mapping between code systems and reconstructing context from surrounding documentation are precisely the tasks language models are improving at. Countries reading this chapter may commit to the costliest and least robust part of the agenda. Suggested revision: Distinguish what is robust under any AI trajectory from what is a bet on one. A small mandatory provenance set - source, method of measurement, time and status - is robust, because no model can reconstruct what was never recorded: whether a blood pressure was taken at home or in clinic, whether a diagnosis was a working hypothesis or a conclusion, whether a value was later revised. Broad semantic harmonisation is a bet. Recommend mandating the first, sequencing the second behind it, and setting an explicit review point. International estimates differ by more than an order of magnitude between countries that connect to existing standards and countries that model afresh, which makes this the largest single cost decision in a national programme. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | |
| PC-0483✎ edit📣 feedback | received | general | Core architects ai |
5.1 Emerging technologies and the foundations they depend on §5.1 p.104 l.26–27 anchor: medium |
Artificial intelligence is treated as a cross-cutting consideration. In practice it is becoming a distinct layer with i…Artificial intelligence is treated as a cross-cutting consideration. In practice it is becoming a distinct layer with its own components and governance requirements - model registries, provenance and audit of training data, monitoring of deployed models, allocation of liability - none of which map cleanly onto the present two-layer structure. Suggested revision: Consider describing AI as a distinct architectural layer resting on the shared data foundation, with its own governance requirements, rather than only as a cross-cutting consideration. Include the requirement that machine-generated content in a health record be labelled as such and remain distinguishable from human-authored content, which is a precondition both for clinical safety and for later training, and which aligns with transparency obligations in the EU AI Act. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | |
| PC-0484✎ edit📣 feedback | received | general | Core architects ai |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.177 anchor: medium |
The section addresses commercial pressure on countries but not the reciprocal question: what a country receives in retu…The section addresses commercial pressure on countries but not the reciprocal question: what a country receives in return when models are trained on health data its population produced collectively. Access regimes for secondary use are being established in several regions and the terms of that exchange are being set now. Suggested revision: Recommend attaching conditions to permits for secondary use of health data for model development, rather than asserting ownership of resulting models, for which no legal vehicle exists. Workable permit conditions include publication of the model card and performance characteristics, access for independent validation by a public body, and a usage right for the public health system. Under the EU Health Data Space this is enforceable through the access permit issued by the national health data access body. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-127 discuss | in the document all mentions on GitHub record | |
| PC-0485✎ edit📣 feedback | received | general | Core architects ai |
1.4 DPI-H Principles §1.4 p.20 l.404 |
The security principle addresses protection of the infrastructure but not the systemic risk that shared infrastructure …The security principle addresses protection of the infrastructure but not the systemic risk that shared infrastructure creates. Consolidating on one normative authority, one certification gate and a smaller set of conformant products reduces diversity, and reduced diversity means correlated vulnerability: one flaw in the certified implementation is a flaw across the system. Fragmented landscapes have the underappreciated property of failing in small pieces. Suggested revision: State the trade-off explicitly with its design consequences: do not mandate a single reference implementation, since that makes monoculture a requirement rather than an outcome; require degraded operating modes that keep care possible during outage, and require that they be exercised rather than only documented; and place national testing and validation capability under the same continuity regime as the components it certifies, so the conformance gate is not itself a single point of failure. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | |
| PC-0486✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.373 |
Semantic governance is described in institutional terms without addressing who staffs it. Standards and terminology com…Semantic governance is described in institutional terms without addressing who staffs it. Standards and terminology committees are resourced by organisations able to release expert time, predominantly established vendors and large providers. Whoever writes the standard determines who can meet it, so committee composition is a competition matter as well as a technical one. Suggested revision: Add a composition requirement for normative bodies: a stated balance between providers, professional bodies, smaller vendors, patient representation and public authorities; disclosure of participants and their affiliations; and publicly reasoned decisions. Without this, semantic governance reproduces the incumbent structure the guidance intends to open up, and does so with public authority behind it. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | |
| PC-0487✎ edit📣 feedback | received | technical | Core architects ai |
3.4.2 Governance principles §3.4.2 p.54 l.251 |
Subsidiarity is stated as a principle but the guidance does not say what happens where a subnational body already deliv…Subsidiarity is stated as a principle but the guidance does not say what happens where a subnational body already delivers the function well. As written, a national DPI-H programme can displace functioning regional arrangements without any test of whether it improves on them, which is the mechanism by which external rules crowd out effective self-organisation. Suggested revision: Add an equivalence provision: where an existing arrangement demonstrably delivers the required capability to the national standard, it satisfies the requirement and is recognised rather than replaced, on a comply-or-explain basis with periodic verification. This is Ostrom's seventh design principle - recognition by external authority of the right to self-organise - expressed as an implementation rule, and it materially reduces political resistance to national programmes. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-050 discuss | in the document all mentions on GitHub record | |
| PC-0488✎ edit📣 feedback | received | general | Core architects ai |
3.4.2 Governance principles §3.4.2 p.54 l.249 |
The eight governance principles correspond closely to Elinor Ostrom's design principles for durable common-pool resourc…The eight governance principles correspond closely to Elinor Ostrom's design principles for durable common-pool resource institutions, but the correspondence is not drawn, so the empirical basis is unavailable to the reader. Three of Ostrom's principles are absent from the list altogether. Suggested revision: Reference the design principles literature explicitly as the empirical foundation for this section, and add the three that are missing: clearly defined boundaries of who may participate and on what terms; accessible conflict resolution; and recognition by higher authorities of participants' right to devise their own rules. Note the correct reading for a DPI-H context: these are requirements on the rule system, not prescriptions about who sets the rules, so a framework law establishing who may make which rules by what procedure is consistent with them, while a law fixing their content is not. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-050 discuss | in the document all mentions on GitHub record | |
| PC-0489✎ edit📣 feedback | received | technical | Core architects ai |
3.4.7 Governance maturity considerations §3.4.7 p.63 l.517 |
Governance maturity is described developmentally but without a mechanism for revising the arrangement itself. The most …Governance maturity is described developmentally but without a mechanism for revising the arrangement itself. The most significant governance risk over the life of a health infrastructure is not immaturity but purpose expansion: capabilities built for care become available for research, oversight, enforcement or entitlement decisions, incrementally and by administrative decision. Suggested revision: Recommend that the legal instrument establishing DPI-H contain a revision clause requiring that any expansion of the purposes for which the infrastructure may be used be decided at the same level as its creation - legislative rather than administrative - with published justification. The most reliable protection against purpose creep is not technical control or supervision but the political cost of amending a law, and this is also the assurance that makes an objection-based model defensible to citizens who do not wish to participate. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | |
| PC-0490✎ edit📣 feedback | received | technical | Core architects ai |
3.4.4 Operational governance §3.4.4 p.56 l.334 anchor: medium |
Operational governance is described in terms of running the infrastructure but not the capacity required to do so. Acro…Operational governance is described in terms of running the infrastructure but not the capacity required to do so. Across the digital health literature the recurring cause of failure is not absent design but absent implementation capacity, and capacity is typically funded as a project deliverable rather than as a standing resource. Suggested revision: Add implementation and operating capacity as an explicit governance responsibility, budgeted as capacity rather than as project output, with a stated absorption limit: the volume of change the system can absorb in a given period, published, and used to sequence the roadmap. Guidance that states no absorption limit will be read as endorsing simultaneous delivery of everything it describes, which no country can do. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-242 discuss | in the document all mentions on GitHub record | |
| PC-0491✎ edit📣 feedback | received | editorial | Core architects ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27 l.109 |
REDDHI introduces a fifth term alongside DPI, foundational DPI, DPI-H and the reference architecture, for what the text…REDDHI introduces a fifth term alongside DPI, foundational DPI, DPI-H and the reference architecture, for what the text then describes as a condition of maturity rather than a thing. Readers are likely to treat it as a further category of system to procure, which the section explicitly says it is not. The acronym also does not translate well. Suggested revision: State in the first sentence that REDDHI names a state of the system and not a set of components, and give the relationship to DPI-H in one line - DPI-H is what is built, REDDHI is the condition its maturity produces. Alternatively dispense with the acronym and use a descriptive phrase. If retained, add it to the terminology table in the front matter with that distinction stated. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | |
| PC-0492✎ edit📣 feedback | received | editorial | Editorial ai |
4.3.4 Interoperability Implementation Pathways §4.3.4 p.96 l.339 |
Two different subsections are both numbered 4.3.4: 'Integration Interfaces with Foundational DPI' and 'Interoperability…Two different subsections are both numbered 4.3.4: 'Integration Interfaces with Foundational DPI' and 'Interoperability Implementation Pathways'. The duplication appears in both the table of contents and the body, and will make comment references and internal cross-references ambiguous. Suggested revision: Renumber the second as 4.3.5 and renumber the following 'Minimum Conformance and Testing' from 4.3.5 to 4.3.6, updating the table of contents accordingly. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-097 discuss | in the document all mentions on GitHub record | |
| PC-0493✎ edit📣 feedback | received | editorial | Editorial ai |
1.5 The Seven Priority Health Sector Goals §1.5 p.21 l.footnote to 1.5.1 anchor: medium |
An unresolved placeholder remains in the text: the mapping to WHO's six health system building blocks is said to be pro…An unresolved placeholder remains in the text: the mapping to WHO's six health system building blocks is said to be provided in 'Annex [X]'. No such annex appears, and Appendices A and B carry no titles in the table of contents or in the body. Suggested revision: Resolve the cross-reference to the actual annex, and give Appendices A and B titles in both the table of contents and the body. If the building-blocks mapping is not yet drafted, note it as forthcoming rather than referencing a placeholder, since officials will use that mapping to connect the guidance to existing national planning instruments. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-254 discuss | in the document all mentions on GitHub record | |
| PC-0494✎ edit📣 feedback | received | general | Core architects ai |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §1.1.2 p.10 l.62 |
The definition of DPI-H is sound and will be adopted into national policy documents, where it will meet existing nation…The definition of DPI-H is sound and will be adopted into national policy documents, where it will meet existing national vocabulary for the same concept. Without a mapping, countries will either invent a parallel vocabulary or conclude the guidance describes something other than what they already have. Suggested revision: Add a short mapping table inviting countries to place national terms against the DPI-H concepts, with two or three worked examples. For the Netherlands the equivalents are 'generieke functies' for the shared foundational components, 'landelijk dekkend netwerk' for the governed exchange capability, and 'databeschikbaarheid' for the shift from point-to-point exchange to governed availability. Naming such equivalences will materially increase uptake in countries that already have a national architecture. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-007 discuss | in the document all mentions on GitHub record | |
| PC-0495✎ edit📣 feedback | received | general | Core architects ai |
2.1 The Reference Architecture Scope §2.1 p.24 l.29 |
The scope statement describes what the architecture covers but not what it deliberately leaves to countries. Readers ne…The scope statement describes what the architecture covers but not what it deliberately leaves to countries. Readers need to know which choices are architectural and which are political, because presenting a political choice as an architectural one is how national programmes lose legitimacy. Suggested revision: Add a short statement of what the guidance does not decide: the legal basis for processing and the consent or objection model; whether participation is voluntary or obligatory; who operates each component; how it is financed; and the balance between national and subnational authority. Stating this protects the guidance from being read as prescribing a centralised model, which is the reading that has defeated national programmes politically in more than one high-income country. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-008 discuss | in the document all mentions on GitHub record | |
| PC-0496✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.31 l.179–180 anchor: medium |
The design principles are architectural properties and do not include a principle about the unit of obligation. The dif…The design principles are architectural properties and do not include a principle about the unit of obligation. The difference between obliging an exchange between two named parties and obliging a state of affairs - that a datum be findable and interpretable where there is a lawful basis - is architecturally consequential: the first requires a bilateral relationship per pair and scales quadratically, the second requires a shared capability and scales linearly. Suggested revision: Add a design principle on the unit of obligation: requirements should attach to the availability of information rather than to transfers between named parties. The consequences are that the number of relationships to be maintained changes from quadratic to linear, as section 1.3.1 already argues on cost grounds; the object of enforcement becomes a verifiable state rather than a message format; and responsibility for the whole becomes assignable to a holder. This is the core of the shift Dutch policy calls 'databeschikbaarheid'. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-015 discuss | in the document all mentions on GitHub record | |
| PC-0497✎ edit📣 feedback | received | editorial | Editorial ai |
1.3.1 The Cost of Fragmentation §1.3.1 p.17 l.284 |
The quadratic-cost argument is correct and central, and it is made in prose only. It is the argument most likely to per…The quadratic-cost argument is correct and central, and it is made in prose only. It is the argument most likely to persuade a finance ministry and the easiest of all to make visually. Suggested revision: Add a small figure contrasting point-to-point connections with connection through a shared capability, showing the number of relationships to be maintained at, say, 10, 100 and 1000 participants. Include the maintenance implication the text already notes - that every update to one system puts every connection to it at risk - since recurring maintenance rather than initial build is where the cost actually falls. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-013 discuss | in the document all mentions on GitHub record | |
| PC-0498✎ edit📣 feedback | received | technical | Core architects ai |
2.2.2 The enabling conditions for REDDHI §2.2.2 p.28 l.143 anchor: medium |
The enabling conditions are stated as capabilities to be built. Where foundational components already exist, the bindin…The enabling conditions are stated as capabilities to be built. Where foundational components already exist, the binding condition is not a further capability but the authority to require its use. Without that, the guidance offers no path from partial to comprehensive coverage other than continued persuasion. Suggested revision: Add authority to the enabling conditions alongside capability and capacity: an identifiable party empowered to require participation, an enforceable norm, a durable funding basis and a dispute route. Present these as conditions of the same standing as the technical ones, since a country can satisfy every technical condition and remain unable to progress - which is the Dutch position after two decades of investment. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | |
| PC-0499✎ edit📣 feedback | received | general | Core architects ai |
Executive Summary §Executive Summary p.1–3 l.1–102 |
The document runs to 254 pages and its most consequential content - the governance principles, the component boundary, …The document runs to 254 pages and its most consequential content - the governance principles, the component boundary, the financing guidance and the legal dimension - is distributed across chapters 3 and 4. Ministers and finance officials will not read it, and the officials who brief them need a version that can be acted on. Suggested revision: Add a decision document at the front of no more than four to six pages, setting out the decisions a country has to take rather than summarising the guidance: what to designate as DPI-H; who operates each component; whether participation is obligatory; how it is financed and by whom the price is set; who enforces and with what sanctions; and where disputes are resolved. Each with the instrument, the deciding body and an indicative sequence. The present executive summary describes the document; a decision document would describe the choices. Hans ter Brake, HCI - Health Cloud Initiative, Netherlands |
none | not yet | CS-002 discuss | in the document all mentions on GitHub record | |
| PC-0500✎ edit📣 feedback | received | general | Core architects ai |
3.3 The reference architecture in practice §3.3 p.48 l.Figure 3.2 anchor: medium |
Figure 3.2 is a high level diagram of the Reference Architecture. Having just reviewed Section 3.1 for guidance on adop…Figure 3.2 is a high level diagram of the Reference Architecture. Having just reviewed Section 3.1 for guidance on adoptiong ArchiMate for our own architectural documentation it was notable that this reference architecture takes a more aesthetic approach to it's own high-level concepts and does not use the ArchiMate approach. Suggested revision: Add guidance noting that high-level, landscape diagrams and schematics can – and where appropriate should – adopt more generally consumable approaches to diagramming, in doing so acknowledging the importance of capturing high-level, landscape design concepts.. Ideally, recommend an approach and tooling. Greg Farnan, Cirdan Imaging Limited, Portugal |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | |
| PC-0501✎ edit📣 feedback | received | technical | Core architects ai |
3.1 The architecture description approach §3.1 / 3.2 p.43-47 l.Table 3.1; Table 3.3 (pp. 45-46); lines 82-83 and 122-126 |
The published element palette traces goals and capabilities to application services, components and data objects, while…The published element palette traces goals and capabilities to application services, components and data objects, while Business Process and Business Role are absent. Section 3.2 appropriately places organisational practice and change management outside the present structural description, but that boundary leaves the model unable to show where operational work produces a required data object or which role performs that work. There is also a presentation inconsistency: Table 3.3 uses Application Function even though it is not listed in Table 3.1. Suggested revision: Clarify the distinction between the core DPI-H palette and extension elements. Add Business Process and Business Role to a defined extension palette, with relationships such as Business Process realises Capability, Business Role is assigned to Business Process, and Business Process accesses Data Object. Cross-reference this extension from section 3.2 for countries that need traceability from shared infrastructure to the operational settings that produce its data, and align Tables 3.1 and 3.3 so every element used is defined. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | |
| PC-0502✎ edit📣 feedback | received | technical | Core architects ai |
2.1.2 Business services layer §2.1 / 2.3 (Principle I) / 3.7.2 / 4.3.4 p.25, 31, 80 and 97 l.Lines 33-42, 205-215, 1009-1012 and 363-368 |
Point-of-service and operational applications are deliberately outside the DPI-H component boundary, and section 4.3.4 …Point-of-service and operational applications are deliberately outside the DPI-H component boundary, and section 4.3.4 correctly states that health should express requirements to foundational DPI rather than duplicate its functions. The guidance does not state the corresponding minimum obligations of the systems and settings that produce data for DPI-H. The current conformance model therefore tests component services and interfaces more clearly than the provenance and capture conditions of the data supplied to them. Suggested revision: Add a short boundary-contract subsection for data-producing and consuming systems. For each mandatory element, require alignment to the governed logical information model, attribution to an identifiable human or system actor, a defined capture or derivation point, and an accountable role. State that component conformance covers the exposed interface, while source-data conformance covers these defined producer obligations, without prescribing the internal application used by the setting. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-025 discuss | in the document all mentions on GitHub record | |
| PC-0503✎ edit📣 feedback | received | technical | Core architects ai |
4.3.1 Design Data Structures and Data Models First §4.3.1 / 4.3.2 p.94-95 l.Lines 256-304 |
Section 4.3.1 gives data structures priority over actors and workflows. Stable minimum data models are essential, espec…Section 4.3.1 gives data structures priority over actors and workflows. Stable minimum data models are essential, especially for authoritative registries, but data created through operational transactions also depends on who performs the work, at which workflow step, and for what purpose. The SMART Guidelines example in section 4.3.2 presents personas, workflows, data elements and decision logic together rather than as a data-only sequence. Suggested revision: Retitle section 4.3.1 as 'Design Data Models with Defined Actors and Workflows'. State that, where data is created through an operational transaction, the minimum data model should be designed and validated alongside the actors, workflow steps and decision logic that produce and use it. The sections may remain separate, but should be presented as a coordinated specification activity rather than a strict data-first sequence. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | |
| PC-0504✎ edit📣 feedback | received | technical | Core architects ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 / 4.3.2 / 5.2 / 5.4.2 p.67, 95, 106 and 108 l.Lines 643-656, 285-292, 92-96 and 156-165 |
The architecture requires actions to be attributed to an identifiable human or system actor and requires AI to be accou…The architecture requires actions to be attributed to an identifiable human or system actor and requires AI to be accountable to identifiable people. Attribution is therefore modelled, but the relationship between a non-human executing actor and the accountable human role is not. The Health Workforce Registry provides the authoritative source for human workers, while no corresponding governed catalogue identifies automated or AI actors, their permitted functions or deployed versions. Suggested revision: Add a governed register or catalogue for non-human executing actors, either as a companion to the Health Workforce Registry or as part of the component and service metadata. Record each actor's identity, permitted functions, deployed version and accountable human role. Require provenance and audit records to distinguish the executing actor from the accountable human whenever the executor is not a person. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-120 discuss | in the document all mentions on GitHub record | |
| PC-0505✎ edit📣 feedback | received | technical | Core architects ai |
5.3 Where artificial intelligence can support the health system §5.3 / 5.4.2 p.107-108 l.Lines 134-138 and 156-168 |
The draft appropriately favours assistive AI under meaningful human oversight, but oversight is described principally a…The draft appropriately favours assistive AI under meaningful human oversight, but oversight is described principally as a design characteristic. For outputs that require human review, oversight may become ineffective when output volume or complexity exceeds available review capacity, even though the system continues to be labelled assistive. Suggested revision: State that each deployment should define an operational oversight model proportionate to risk: which outputs require full review, sampling, exception review or escalation; the human capacity and competence required; and monitored thresholds indicating that oversight is no longer effective. A threshold breach should trigger re-evaluation of the deployment and its controls. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0506✎ edit📣 feedback | received | technical | Metadata registries ai |
4.2.2 A Phased Implementation Approach §4.2.2 (with 3.4.5 and 4.3.1) p.90, 92, 94 and 62 l.Lines 120-123, 176-177, 262-273 and 492-494 |
Section 3.4.5 states that Semantic Governance Infrastructure (SGI) is foundational, and section 4.3.1 requires national…Section 3.4.5 states that Semantic Governance Infrastructure (SGI) is foundational, and section 4.3.1 requires national data models to be governed before implementation begins. The phased plan nevertheless lists establishment of SGI in Phase 3, after Phase 2 has established components and basic terminology services. Although the introduction says governance threads begin earlier and are listed where most prominent, it does not identify the minimum semantic-governance functions that must operate while Phase 2 models and profiles are created. Suggested revision: Place a minimum SGI capability in Phase 2 alongside terminology services and information-model work. It should cover intake, authoring, approval, publication, versioning and release. Reserve Phase 3 for expanding this capability to broader multi-stakeholder curation, harmonisation and lifecycle maturity. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | |
| PC-0507✎ edit📣 feedback | received | general | Core architects ai |
1.1.4 Who can benefit from this guidance? §1.1.4 / 4.5.1 p.12 and 100 l.Lines 140-169 and 473-487 |
The named audiences and uses do not expressly include health-service delivery organisations such as hospital groups, pr…The named audiences and uses do not expressly include health-service delivery organisations such as hospital groups, provider networks and facility operators. These organisations may be intended to fall within 'implementers', but their responsibility at the national-to-facility boundary is not stated, even though they operate the settings in which much of the data used by DPI-H is produced. Suggested revision: Add health-service delivery organisations as a named audience, or clarify explicitly that they are included among implementers. Describe their use of the architecture as aligning local systems, actor definitions, capture points, terminology and information models with nationally governed specifications. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-004 #21 | in the document all mentions on GitHub record | |
| PC-0508✎ edit📣 feedback | received | technical | Core architects ai |
4.2.4 The Role of the National Digital Architect §4.2.4 / 3.4.4 p.93-94 and 57 l.Lines 226-245 and 363-372 |
The national digital architect is given authority to define standards, evaluate conformance, enforce coordination and s…The national digital architect is given authority to define standards, evaluate conformance, enforce coordination and say no or escalate. The guidance does not require countries to document which decisions the architect holds, where escalation runs, the criteria for an architectural objection, or what is recorded when an objection is overridden. Section 3.4.4 provides a useful model by requiring explicit triggers and documented, time-bound escalation for operational governance. Suggested revision: Require each country to publish a decision-rights statement for the national digital architect: decisions held outright, decisions on which the architect advises, escalation routes and trigger conditions, and the decision record required when an architectural objection is overridden. The institutional route may remain country-specific. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | |
| PC-0509✎ edit📣 feedback | received | technical | Metadata registries ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 / 4.3.1 / 4.3.3 p.28, 94 and 96 l.Table 2.2; lines 265-273 and 316-321 |
Table 2.2 identifies the Logical Information Model Repository (LIMR) as an enabler that may be built as maturity grows …Table 2.2 identifies the Logical Information Model Repository (LIMR) as an enabler that may be built as maturity grows rather than as part of the minimum foundation. Elsewhere, the LIMR is the designated home and governance mechanism for national data models, and the authoritative model from which FHIR profiles are derived and against which they are validated. This leaves unclear where required national models are governed before a LIMR exists. Suggested revision: Either include a minimum LIMR capability in the foundational set or specify the interim governed mechanism that holds national information models, the authority responsible for it, and the migration path when the full LIMR is established. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-029 discuss | in the document all mentions on GitHub record | |
| PC-0510✎ edit📣 feedback | received | technical | Core architects ai |
3.7.4 Planning testing from the architecture §3.7.4 / 4.4.2 / 5.2 p.84, 99 and 106 l.Lines 1154-1161, 447-460 and 69-70 |
The progress framework measures component coverage, standards conformance, governance maturity and outcome linkage, whi…The progress framework measures component coverage, standards conformance, governance maturity and outcome linkage, while section 5.2 notes that weaknesses in data quality cascade into analytical and AI reliability. None of the four progress dimensions directly measures the quality of data captured or derived at source, so a technically conformant architecture may still operate on incomplete, invalid, untimely or poorly attributed data. Suggested revision: Add a fifth progress dimension: source-data quality. Measure completeness, validity, timeliness, semantic conformance and provenance for mandatory elements in governed models, sampled at producing settings. Where factual accuracy cannot be tested automatically, specify a proportionate audit or validation method. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-243 discuss | in the document all mentions on GitHub record | |
| PC-0511✎ edit📣 feedback | received | general | Core architects ai |
1.3.1 The Cost of Fragmentation §1.3.1 / 4.2.2 p.18 and 91 l.Lines 294-314 and 146-169 |
Section 1.3.1 identifies structural incentives that reward programme-specific delivery over shared infrastructure. The …Section 1.3.1 identifies structural incentives that reward programme-specific delivery over shared infrastructure. The phased plan asks the first two or three programme systems to connect to the shared foundation, but does not address the first-mover problem: integration costs are borne immediately by the connecting programme while part of the value accrues later across other programmes and the wider health system. Suggested revision: Add guidance for the first implementation wave: select use cases in which the connecting programme is itself a principal beneficiary, fund common integration costs centrally or through a shared transformation budget, and make reuse benefits and cost allocation explicit in the business case. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-013 discuss | in the document all mentions on GitHub record | |
| PC-0512✎ edit📣 feedback | received | technical | Core architects ai |
5.4 Readiness, oversight, and responsible adoption §5.4 p.107-109 l.Lines 142-194 |
The section identifies important safeguards, including input and output controls, representative training data, drift m…The section identifies important safeguards, including input and output controls, representative training data, drift monitoring, evaluation, accountability and human oversight, and points to WHO's wider AI guidance. These requirements are dispersed across the narrative rather than consolidated into an operational baseline that procurement and implementation teams can test before deployment and during operation. Suggested revision: Add, or cross-reference, a concise minimum control checklist for AI operating on DPI-H data. Consolidate the safeguards already named and include validation, provenance, representativeness, drift monitoring, incident reporting, rollback or safe-disable procedures, evaluation intervals and a named accountable role. Link the checklist to a short risk/failure taxonomy across clinical, operational, financial and equity domains and to the relevant WHO AI guidance. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | |
| PC-0513✎ edit📣 feedback | received | technical | Core architects ai |
3.7.4 Planning testing from the architecture §3.7.4 / 5.2 p.84 and 106 l.Lines 1163-1168 and 103-106 |
Section 3.7 explains that a structured, machine-readable architecture can be assessed rather than merely described. Sec…Section 3.7 explains that a structured, machine-readable architecture can be assessed rather than merely described. Section 5.2 nevertheless treats publication of machine-readable specifications and metadata as a forward-looking practice that may later become a readiness criterion. This limits automation of discovery, assessment and conformance even where the architecture model itself is machine-readable. Suggested revision: Promote machine-readable publication of component specifications and metadata from a forward-looking observation to a SHOULD-level requirement, with appropriate maturity exceptions. Add the requirement to the component descriptions in Appendix C and cross-reference section 3.7. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | |
| PC-0514✎ edit📣 feedback | received | technical | Core architects ai |
4.2.2 A Phased Implementation Approach §4.2.2 p.90-92 l.Lines 113-172 |
The phases are described using indicative timeframes and are allowed to overlap and iterate. Phase 2 does contain a use…The phases are described using indicative timeframes and are allowed to overlap and iterate. Phase 2 does contain a useful outcome statement—a functioning, standards-conformant foundation used by real programmes—but this is not expressed as a measurable closure test, and comparable entry and exit conditions are not provided consistently for the other phases. Suggested revision: Convert the intended result of each phase into explicit entry conditions and closure criteria, while retaining timeframes as illustrations only. For example, formalise the Phase 2 outcome as defined components in production, conformance tested against published profiles, and used by the selected programme systems, with evidence recorded for each condition. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | |
| PC-0515✎ edit📣 feedback | received | technical | Core architects ai |
3.2 Reading and navigating the reference architecture §3.2 / 4.2.2 (Phase 4) / 4.2.4 p.46-47 and 92-94 l.Lines 94-103, 185-196 and 230-245 |
The navigable model is described as the authoritative source for element-level detail and Phase 4 requires continuous e…The navigable model is described as the authoritative source for element-level detail and Phase 4 requires continuous evolution of the architecture, but the guidance does not specify how the model is reconciled with the components and interfaces actually deployed. Without an explicit reconciliation process, coverage and conformance measures may be calculated against an increasingly outdated representation. Suggested revision: Require an as-built reconciliation and approval step for each material deployment or change, define the operational architecture repository as the source for progress measures, and assign an owner and review cadence. The national digital architect should be accountable for ensuring that discrepancies are resolved or formally recorded. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-253 discuss | in the document all mentions on GitHub record | |
| PC-0516✎ edit📣 feedback | received | general | Core architects ai |
4.1.1 No Country Starts from Zero §4.1.1 / 4.2.1 p.88-89 l.Lines 13-21 and 64-73 |
The four entry points are framed at country level. Within countries that already have mature shared infrastructure, new…The four entry points are framed at country level. Within countries that already have mature shared infrastructure, new facilities, service networks or cities may still be making foundational choices about processes, systems and capture points. Their local starting position can therefore differ materially from the national maturity category. Suggested revision: Add a short implementation note that entry-point assessment may also be applied to a major programme or delivery setting within the national architecture. Highlight commissioning and greenfield development as opportunities to align local actor definitions, data capture and system interfaces to national models before procurement and deployment. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-024 discuss | in the document all mentions on GitHub record | |
| PC-0517✎ edit📣 feedback | received | editorial | Editorial ai |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4 p.96-98 l.Lines 339 and 369; following subsection heading |
Two consecutive subsections are numbered 4.3.4: 'Integration Interfaces with Foundational DPI' and 'Interoperability Im…Two consecutive subsections are numbered 4.3.4: 'Integration Interfaces with Foundational DPI' and 'Interoperability Implementation Pathways'. The following subsection is numbered 4.3.5. Suggested revision: Renumber the subsections as 4.3.4 Integration Interfaces with Foundational DPI, 4.3.5 Interoperability Implementation Pathways, and 4.3.6 Minimum Conformance and Testing, and update cross-references. Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-097 discuss | in the document all mentions on GitHub record | |
| PC-0518✎ edit📣 feedback | received | editorial | Editorial ai |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Line 650 |
The Lifelong Health Record bullet ends with the fragment 'rather than implying a single central store. person-centred t…The Lifelong Health Record bullet ends with the fragment 'rather than implying a single central store. person-centred that', which appears to be an editing artefact. Suggested revision: Delete the trailing fragment so the bullet ends at 'rather than implying a single central store.' Brian de Francesca, Intelligent by Design (IBD), United Arab Emirates / MENA |
none | not yet | CS-060 discuss | in the document all mentions on GitHub record | |
| PC-0519✎ edit📣 feedback | received | technical | Core architects ai |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.155-168 |
Section 5.4.2 states that before a capability is relied upon "it should be evaluated against representative cases and e…Section 5.4.2 states that before a capability is relied upon "it should be evaluated against representative cases and explicit criteria" and asks "how it was evaluated." This framing does not address the condition where the evaluation environment itself was compromised or misconfigured — producing evaluation results that appeared valid but did not reflect the system's actual behavior in deployment. In July 2026, two frontier AI laboratories disclosed that their safety evaluation environments had failed without detection, producing passing artifacts from compromised conditions. For AI components integrated into DPI-H, this creates a governance gap: a country may accept an AI system's evaluation results as evidence of trustworthiness when the evaluation environment did not accurately represent the health system deployment environment. Suggested revision: After line 168, add: "Countries should require, as part of procurement and evaluation, that AI system providers attest that evaluation environments were isolated from production health systems and free from misconfiguration events during the evaluation period. Each AI system's disclosed evaluation results should identify whether findings are provider-attested only, or independently verified in a deployment-representative environment. This distinction is particularly important for AI systems deployed in clinical decision support and population health analytics roles." Dee Jared Johnson, Cognitive Fusion™, Salt Lake City, Utah, United States |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | |
| PC-0520✎ edit📣 feedback | received | general | Core architects ai |
5.4.3 Equity and safety §5.4.3 p.109 l.171-176 |
Section 5.4.3 addresses equity and safety concerns in AI deployment, focusing on training data representativeness. It d…Section 5.4.3 addresses equity and safety concerns in AI deployment, focusing on training data representativeness. It does not address a distinct equity dimension: the evaluation integrity gap is more consequential in LMIC settings precisely because independent verification capacity is most limited there. A health ministry in an LMIC deploying an AI-enabled DPI-H component based on a developer's evaluation documentation has fewer resources to conduct independent behavioral testing in its specific national health system environment. A country with limited AI oversight infrastructure has no mechanism to detect the gap between provider-attested evaluation results and actual system behavior in deployment. Suggested revision: Add after line 176: "Countries with limited independent AI evaluation capacity face a compounded equity risk: they are less able to verify that AI systems perform as evaluated for their specific population and health system context. The guidance should advise ministries and DPI authorities in these settings to: (a) require AI system providers to disclose whether evaluation results are provider-attested or independently verified; (b) prioritize independent behavioral verification for highest-consequence AI-enabled DPI-H components; and (c) request evaluation environment integrity attestation as part of procurement — confirming that the evaluation environment represented the intended deployment context." Dee Jared Johnson, Cognitive Fusion™, Salt Lake City, Utah, United States |
none | not yet | CS-124 discuss | in the document all mentions on GitHub record | |
| PC-0521✎ edit📣 feedback | received | technical | Core architects ai |
3.6.5 Conformance §3.6.5 p.78 l.964-961 anchor: medium |
Section 3.6.5 addresses conformance testing before and during procurement. It does not address behavioral drift in AI-e…Section 3.6.5 addresses conformance testing before and during procurement. It does not address behavioral drift in AI-enabled DPI-H components after deployment — the condition where an AI component that achieved conformance at procurement behaves differently after updates, changes to upstream data sources, or integration with new system components, without triggering re-conformance testing. For AI components used in clinical decision support or population health analytics, behavioral drift may represent a patient safety issue that the current conformance framework would not detect. Suggested revision: Add after line 961: "For AI-enabled DPI-H components, conformance testing should extend beyond point-in-time procurement validation to include: (a) defined thresholds at which behavioral drift from the conformance baseline requires re-testing; (b) post-deployment monitoring protocols that compare AI component behavior against its conformance baseline at defined intervals; and (c) a documented process for detecting and responding to retrospective evaluation integrity failures — cases where a conformance evaluation is later found to have been conducted in a misconfigured or unrepresentative environment. These requirements align with the NIST AI RMF MANAGE function (MANAGE 2.4), which addresses ongoing monitoring and retrospective evaluation integrity protocols." Dee Jared Johnson, Cognitive Fusion™, Salt Lake City, Utah, United States |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | |
| PC-0522✎ edit📣 feedback | received | technical | Clinical ai |
3.6.5 Conformance §3.6.5 / 3.7 / 4.3.5 p.78; 98 l.958; 401-406 |
Conformance certifies architectural roles (an Application Component realises Application Services), but no mechanism ce…Conformance certifies architectural roles (an Application Component realises Application Services), but no mechanism certifies that a conformant decision-support component executes published guideline content faithfully. A platform can pass every interaction test yet be unable to parse the L3 artifacts the architecture names as Required formats. Observed: an Aug 2026 scan of all 31 published WHO smart-* IG packages (4,052 resources) against a current FHIR-native platform found 259 resources - including every PlanDefinition and Measure in smart-immunizations - unparseable from a single model defect (ohs-foundation/kotlin-fhir#123). Role conformance would not have surfaced this; executing the published content did. Suggested revision: Add guideline-content execution as a conformance category: a conformant CDSE demonstrates it loads and executes published, unmodified L3 artifacts for the health areas it claims, with results matching reference-implementation output. In 4.3.5, list content-execution conformance alongside profile conformance in procurement guidance. Dan Heslinga, MD, Hopena Health, United States of America (Hawaii) |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | |
| PC-0523✎ edit📣 feedback | received | technical | Metadata registries ai |
Logical Information Model Repository §Appendix C (LIMR; CDSE) p.175; 181-190 l.Table (LIMR FR3/FR9); CDSE FRs anchor: medium |
The architecture separates knowledge governance (LIMR) from execution (CDSE) but nothing attests that content executed …The architecture separates knowledge governance (LIMR) from execution (CDSE) but nothing attests that content executed at runtime is byte-identical to content the LIMR governs. The WHO governance -> national LIMR -> CDSE trust chain is only as strong as this hand-off. Observed instance: a current knowledge-manager implementation indexes content by path reference with no copy and no checksum, so evaluation-time bytes are unattested against install-time content (reported on ohs-foundation/kotlin-fhir-knowledge PR #2, Aug 2026). Suggested revision: Add Required attributes: the LIMR publishes content with integrity metadata (version + hash); the CDSE verifies loaded logic against that metadata and records executed-content identity in decision audit records. This gives 'preserve fidelity' (glossary, p.2) a mechanical enforcement point. Dan Heslinga, MD, Hopena Health, United States of America (Hawaii) |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | |
| PC-0524✎ edit📣 feedback | received | technical | Clinical ai |
Computable Decision Support Engine §Appendix C (CDSE) p.181-190 l.158 (p.184) anchor: medium |
The CDSE is architected as a connected shared service: it holds no clinical data and queries the Lifelong Health Record…The CDSE is architected as a connected shared service: it holds no clinical data and queries the Lifelong Health Record at the moment of invocation, with point-of-care systems invoking it via CDS Hooks / SMART on FHIR. The community-health-worker settings WHO DAKs explicitly target are intermittently connected or offline-first; there the same L3 decision logic must execute on-device. This locus is technically demonstrated today (WHO CQL/PlanDefinition content running on offline-capable Kotlin Multiplatform ports of the HL7 CQL engine and FHIR Clinical Reasoning $apply) but is architecturally invisible in the draft. Suggested revision: Describe two deployment loci for the CDSE capability - shared service and on-device engine - consuming identical L3 artifacts from the same LIMR governance chain, with the same conformance expectations for both. Note offline content-version synchronization as an SGI distribution concern. Dan Heslinga, MD, Hopena Health, United States of America (Hawaii) |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | |
| PC-0525✎ edit📣 feedback | received | technical | Metadata registries ai |
Logical Information Model Repository §Appendix C (LIMR federation); Appendix F p.174 l.106 |
The LIMR is directed to federate with 'the WHO SMART Guidelines', assuming published packages are reliably available. M…The LIMR is directed to federate with 'the WHO SMART Guidelines', assuming published packages are reliably available. Measured (Aug 2026): of 44 WorldHealthOrganization/smart-* repositories, only 31 publish a fetchable IG package; ~293 authored CQL files sit in repositories with no published package - authored L3 content invisible to every downstream consumer, national LIMRs included. Suggested revision: Acknowledge the global-to-national content supply chain as part of semantic governance: federate only from published, versioned package channels; monitor L3 publication-pipeline health as infrastructure, since national deployments depend on it. Dan Heslinga, MD, Hopena Health, United States of America (Hawaii) |
none | not yet | CS-180 discuss | in the document all mentions on GitHub record | |
| PC-0526✎ edit📣 feedback | received | technical | WHO ai |
C Appendix C: DPI-H Application Component Descriptions §Appendix C (LIMR gov. note 6; CDSE gov. note 7) p.179; 190 l.- anchor: medium |
Both components direct countries to contribute implementation experience back to WHO governance processes, but no concr…Both components direct countries to contribute implementation experience back to WHO governance processes, but no concrete channel is named. Experience shows the loop works when a channel exists: execution-level findings against smart-immunizations filed via the IG's public repository (issue #138 with fix PR #139, Aug 2026) demonstrate implementation-to-WHO feedback functioning at artifact level. Suggested revision: Name the feedback mechanism (the public issue tracker of the relevant smart-* IG repository, or a designated WHO intake) and encourage findings to carry executable reproductions so they can become regression tests in the content's own QA. Dan Heslinga, MD, Hopena Health, United States of America (Hawaii) |
none | not yet | CS-253 discuss | in the document all mentions on GitHub record | |
| PC-0527✎ edit📣 feedback | received | editorial | WHO ai |
5.5 Keeping the architecture open and adaptable §Front matter; 5.5; References p.2; 111 l.- anchor: medium |
Governance of the reference architecture itself is thin: no named custodian, versioning policy, or change process ('liv…Governance of the reference architecture itself is thin: no named custodian, versioning policy, or change process ('living model' intentions stated but not operationalized); the reference list and several glossary entries are placeholders. The living home appears to already exist - the smart-ra implementation guide (smart.who.int/ra; WorldHealthOrganization/smart-ra), where the TWG governance framework is published and ArchiMate-to-IG tooling is under active development - but the published build is v0.1.0 (July 2025), a year behind this draft, and the document never names or links it. Suggested revision: Before publication: complete references/glossary; name the custodian, versioning scheme, and revision cadence; identify the smart-ra IG as the canonical machine-readable home, publish a build synchronized with the consultation text, and route post-consultation feedback through its public issue tracker. Dan Heslinga, MD, Hopena Health, United States of America (Hawaii) |
none | not yet | CS-253 discuss | in the document all mentions on GitHub record | |
| PC-0528✎ edit📣 feedback | received | technical | Financial systems ai |
D.1 Illustrative tools and technologies §Appendix D.1 p.229 ff. l.23 ff. |
examples for Benefits Package Registry missingexamples for Benefits Package Registry missing Suggested revision: add openIMIS "openIMIS is a digital public good which powers versatile solutions for the management of health financing and social protection programs. Designed to be interoperable with other information systems according to the FHIR standard, openIMIS draws upon and contributes to Digital Public Infrastructure." (www.openimis.org) Uwe Wahser, Deutsche Gesellschaft für Technische Zusammenarbeit (GIZ) GmbH, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | |
| PC-0529✎ edit📣 feedback | received | technical | Financial systems ai |
D.2 Country implementation examples §Appendix D.2 p.231 ff. l.91 ff. |
country examples for Benefits Package Registry missingcountry examples for Benefits Package Registry missing Suggested revision: add Nepal (BPR, EHR, HMIS): The national Health Insurance board documents benefit data of the public health insurance scheme in central data-base under openIMIS that can be queried by hospital information systems (e.g the national OpenMRS fork NidanEHR or BAHMNI) through FHIR APIs. The same system also receives and manages electronical claims from the Hospital Accounting Systems and provides aggregated data for the consumption by HMIS. 1) Parajuli S, Shrestha P, Yuh GA, Dhakal N 2025 "Driving Healthcare Transformation: openIMIS as a Catalyst for Interoperability enabling Universal HealthCoverage in Nepal", Poster Presentation, GDHF 2025, Nairobi: https://openimis.atlassian.net/wiki/spaces/OP/pages/5443944455 2) Dhakal R, 2023 "Case Study on Open Source Tools Used for Healthcare Systems", Thesis, University of Kathmandu: https://www.researchgate.net/profile/Rohan-Dhakal/publication/391047459_CASE_STUDY_ON_OPEN_SOURCE_TOOLS_USED_FOR_HEALTHCARE_SYSTEMS/links/6808d7b060241d5140157491/CASE-STUDY-ON-OPEN-SOURCE-TOOLS-USED-FOR-HEALTHCARE-SYSTEMS.pdf 3) Parajuli S, 2026, Webinar Presentation, AEHIN Hour 2026-08-25, https://docs.google.com/presentation/d/11GdwvRt3KugwEeOTwn_FXNDOXzvz2XEeNGXEoD5XUxE/edit?slide=id.g3f845d733eb_0_237#slide=id.g3f845d733eb_0_237, https://youtu.be/cOhv2kIbiF4?si=kSwC5jtd0iOgl63m&t=997 4) HIB 2026, Public Dashboard of the Health Insurance Board of the Government of Nepal: https://dashboard.hib.gov.np/public/ Uwe Wahser, Deutsche Gesellschaft für Technische Zusammenarbeit (GIZ) GmbH, Germany |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0530✎ edit📣 feedback | received | editorial | Editorial ai |
Benefits Package Registry §Appendix BPR 2 p.199 ff. l.33 - 40 anchor: low |
The first paragraph contains a lot of negativity towards existing systems. The statements are true and relevant, but mi…The first paragraph contains a lot of negativity towards existing systems. The statements are true and relevant, but might cause the reader to associate this with the proposed solution. Suggested revision: Try to formulate sentences in a positive way in favor of a BPR, mentioning the drawbacks of existing systems e.g. as examples in a half sentnece afterwards. E.g. Instead of "In most countries today, that knowledge is fragemented" write "A BPR unifies documentation about benefit schemes, donor agreements etc in a single registry, while in many countriies today that knowledge is fragmented." Uwe Wahser, Deutsche Gesellschaft für Technische Zusammenarbeit (GIZ) GmbH, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | |
| PC-0531✎ edit📣 feedback | received | editorial | Financial systems ai |
Benefits Package Registry §Appendix BPR 2 p.200 l.47 - 51 anchor: low |
In democratic countries this transparency would also mean a transparant basis for a public decision-making process on h…In democratic countries this transparency would also mean a transparant basis for a public decision-making process on how to adjust benefits over time to changing economical and epidemiological conditions. Suggested revision: Add one bullet point about participatory policy formulation or adjust the bullet point on government. Uwe Wahser, Deutsche Gesellschaft für Technische Zusammenarbeit (GIZ) GmbH, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | |
| PC-0532✎ edit📣 feedback | received | editorial | Financial systems ai |
Benefits Package Registry §Appendix BPR 3 p.200 l.65 - 68 anchor: low |
The drug list can also contain coverage of brands, e.g. generica vs. original brand plus a substitution order in times …The drug list can also contain coverage of brands, e.g. generica vs. original brand plus a substitution order in times of drug shortages. Suggested revision: Add a word or two in the list point at generica & substitution rules. Uwe Wahser, Deutsche Gesellschaft für Technische Zusammenarbeit (GIZ) GmbH, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | |
| PC-0533✎ edit📣 feedback | received | editorial | Financial systems ai |
Benefits Package Registry §Appendix BPR 3 p.200 l.73 - 75 anchor: low |
Accreditation management missing - this might overlap with facility registries e.g. for QA criteria management & evalut…Accreditation management missing - this might overlap with facility registries e.g. for QA criteria management & evalution, but should at least document the accreditation process & results. Suggested revision: Add a word or two on accreditation. Uwe Wahser, Deutsche Gesellschaft für Technische Zusammenarbeit (GIZ) GmbH, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | |
| PC-0534✎ edit📣 feedback | received | general | No human |
unplaced §General — overall assessment and scope of this submission p.Whole document l.n/a |
The Ministry of Health of Slovenia welcomes this draft and considers it a substantial and useful piece of work. Our com…The Ministry of Health of Slovenia welcomes this draft and considers it a substantial and useful piece of work. Our comments are offered from the position of a country that has operated a national clinical record since 2015 and is now extending it across several care settings through separately procured applications. Our substantive comments concentrate on one structural matter, and we state that openly so the shape of this submission is clear. The guidance treats exchange, coded meaning and logical structure substantively, and each is given named standards or a named component. The persistence layer — the form in which a country's clinical data is held over a lifetime, and the standard that governs it — is not treated in the same way, and the places where the guidance does touch it are not consistent with one another. Because that layer determines what a country can do for decades afterwards, and because it is the layer our own experience bears on most directly, we have commented on each place where it arises. The remaining comments address conformance, cross-border flows, financing, workforce, the goal mappings, the country examples and a number of editorial matters. Suggested revision: No change proposed. This comment is offered as context for those that follow. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | none | all mentions on GitHub record | |
| PC-0535✎ edit📣 feedback | received | general | Metadata registries ai |
Lifelong Health Record §General — register of inconsistencies in the treatment of the persistence and information-model layer p.Whole document l.see list anchor: medium |
This comment lists, in one place, every location the Ministry has identified where the guidance treats the persistence …This comment lists, in one place, every location the Ministry has identified where the guidance treats the persistence of clinical data or the information-model layer, so that the individual comments that follow are read as a set rather than separately. We have set them out this way because a reader encountering these passages in isolation will reasonably draw different conclusions from each, which is the opposite of what guidance of this kind is for. WHERE THE GUIDANCE ALREADY ACCEPTS AN OPEN INFORMATION-MODEL FORMALISM FOR CLINICAL DATA 1. Annex D.1, page 230, lines 36–37 — EHRbase is listed under Lifelong Health Record as "an open-source, openEHR-conformant clinical data repository that stores and queries health data against openEHR archetypes and templates", alongside HAPI FHIR Server at page 229 lines 33–35. 2. Appendix C, page 175, functional requirement 2, status REQUIRED — the LIMR "shall support the representation of models conforming to recognised health data standards, including … openEHR archetypes and templates". 3. Appendix C, page 174, lines 81–85 — multi-formalism support is a core attribute; a national LIMR "should bridge between them rather than mandate one". 4. Appendix C, page 172, architecture placement box — the LIMR "is anchored in internationally recognised standards including HL7 FHIR StructureDefinitions, openEHR archetypes, and WHO SMART Guidelines data dictionaries". 5. Appendix C, page 156, line 43 — ISO 18308:2011 is cited as characterising an EHR architecture. WHERE THE GUIDANCE NAMES ONLY FHIR, OR PRESCRIBES IT FOR PERSISTENCE 6. Section 2.2.2, page 28, lines 148–151 — the Open Standards enabling condition names HL7 FHIR, ICD, LOINC and SNOMED CT. No information-model formalism. 7. Figure 2.2, page 30 — the full-STAC "S" grouping lists HL7 FHIR, ICD, SNOMED CT, LOINC, CQL. No information-model formalism. 8. Section 2.3, principle II, page 32, lines 233–234 — "The architecture points to FHIR-based approaches as the direction of travel." 9. Figure 3.2, page 48, Shared Data Layer — the Lifelong Health Record element is annotated "FHIR-based store". It is the only element in the figure carrying a storage technology. 10. Figure 3.5, page 66 — the same Shared Data Layer is repeated with the identical "FHIR-based store" annotation. 11. Figures 3.2 and 3.5 — the Logical Info Model Repo element lists its artefacts as "FHIR profiles · eObjects · IPS · datasets". openEHR archetypes and templates are absent, contrary to item 2 above. 12. Figures 3.2 and 3.5, Interoperability column — openEHR is listed under "Open standards — Exchange & content". It is an information-model formalism, not an exchange standard. 13. Section 3.6.2, page 74, lines 811–820 — the paragraph naming the standards the architecture references lists nine, across exchange, terminology, identifiers, imaging and content. None for structure, although lines 805–807 state that the LIMR governs structure. WHERE THE INFORMATION-MODEL COMPONENT IS OMITTED OR DEFERRED 14. Section 2.2.1, page 28, capability table — the LIMR is asterisked as "an enabler that can be built up as maturity grows, rather than part of the minimum foundation". 15. Appendix C, page 172, architecture placement box — "Countries should approach the LIMR as a progressive enabler, not an immediate prerequisite." 16. Figure 3.4, page 51 — the Metadata Components group lists the four registries and the Terminology Service; the LIMR is absent. 17. Appendix E, Goal 1, page 236, lines 238–240 — the foundational component list omits the LIMR. WHERE THE GUIDANCE ARGUES THE MINISTRY'S CASE ITSELF 18. Section 3.6.2, page 74, lines 822–830 — "Standards designed primarily for data in motion are highly extensible, and uncoordinated extension produces what are sometimes described as interoperable silos." 19. Section 4.3.3, page 96, lines 319–321 — "A FHIR profile is a representation of that logical model, not a replacement for it." 20. Appendix C, page 173, lines 35–42 — two systems can exchange in HL7 FHIR "and still fail to interoperate meaningfully". 21. Appendix C, page 157, lines 107–110 — the LHR core attribute requires "storage of health data in accordance with the logical information structures published through the LIMR". 22. Section 2.3, principle VIII, page 35, lines 381–389 — the architecture should deliver "clear separation between the data a country owns and the systems that process it", with no mechanism named. Items 6 to 17 are inconsistent with items 1 to 5 and with items 18 to 22. The Ministry's recommendation is that items 6 to 13 be amended to name an open information-model formalism for persisted clinical data alongside HL7 FHIR, and that items 14 to 17 be amended so that a governed minimum information model is treated as foundational. Suggested revision: Each item in the comment section has its own comment in this xls matrix with proposed wording. The changes are consistent with one another and can be made as a set. If only one change is made, it should be Comment No. 8 in this excel — design principle II — because that is the sentence procurement teams will cite. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0536✎ edit📣 feedback | received | technical | Metadata registries ai |
Logical Information Model Repository §General — recommended treatment of clinical data persistence p.Throughout l.2.2.2 (p28–29); 2.3 II (p32); 3.6.2 (p73–74); Figures 3.2 and 3.5 (p48, p66); Appendix C (p155–179); Annex D.1 (p229–230) anchor: medium |
This comment states the Ministry's substantive recommendation in one place, so that it is not distributed across the in…This comment states the Ministry's substantive recommendation in one place, so that it is not distributed across the individual comments that follow. The guidance should name an open information-model formalism for the persistence of clinical data, and should recommend openEHR archetypes and templates for that role, with ISO 13606 as the ISO-ratified equivalent, in the same way that it recommends HL7 FHIR for services and transactions in section 4.3.3. HL7 FHIR should continue to be recommended for exchange, and is also appropriate for the persistence of demographic, administrative and encounter data. Slovenia applies exactly this division nationally. The reasons are matters of design intent and lifecycle cost, not preference. FHIR is designed for data in motion, as section 3.6.2 line 813 states, and its major versions introduce breaking changes — appropriately, because both endpoints of an exchange can upgrade together. A national record that persists clinical data in that form must migrate its entire data estate on the exchange community's release schedule; data at rest cannot run on a cadence set by the needs of data in motion. A two-level model, in which a small stable reference model is separated from clinical content governed as archetypes and templates, allows clinical definitions to change without migrating stored data — which is the outcome the guidance asks for at page 173 lines 55–59, where domain experts update definitions "without depending on software vendors to make those changes", but for which it names no mechanism. Provenance, versioning and audit are carried structurally for every data element rather than added profile by profile, meeting the LHR core attribute at page 157 lines 119–121. And the guidance's own observation at page 96 lines 335–338, that conformance is hardest to retrofit where underlying data structures are not conformant, applies with most force to the record itself. This is not a position peculiar to Slovenia. Catalonia, already present in Annex D.2, has adopted openEHR archetypes for the clinical information layer of its electronic clinical history platform, and a Delphi consensus commissioned by the Spanish Ministry of Health reached the same conclusion independently. Three European health systems of very different scale have converged on the same division of standards by role. The Ministry is not asking for exclusivity, and does not propose that FHIR be excluded from persistence where a country has chosen it. We are asking that the persistence layer be given a named recommended framework, as the exchange layer already has, and that the recommendation reflect what the guidance already accepts in Annex D.1 and requires in Appendix C. Suggested revision: Three specific changes, each proposed in detail in the comments that follow: (1) in section 2.2.2 and Figure 2.2, add an open information-model formalism — openEHR archetypes and templates, or ISO 13606 — to the Open Standards enabling condition and the full-STAC "S" grouping; (2) in section 2.3 principle II, express the direction of travel by layer rather than as a single family; (3) add a subsection to section 4.3, placed before 4.3.3 and parallel to it, for example "4.3.x Clinical content and persistence: the governed information model", since 4.3.1 already establishes that data structures are designed first. Then align Figures 3.2 and 3.5 and the Appendix C material to it. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0537✎ edit📣 feedback | received | general | Metadata registries ai |
3.6 Interoperability Architecture within DPI-H §General — treatment of the persistence layer across the guidance p.Throughout l.3.6 (p71–78); 2.3 (p31–35); Figure 3.2 (p48); Appendix C (p155–179) anchor: medium |
Reading the guidance as a whole, the Ministry observes that three of the four layers of a health data architecture are …Reading the guidance as a whole, the Ministry observes that three of the four layers of a health data architecture are treated substantively and one is not. Exchange is specified in detail with a named recommended framework. Coded meaning is specified with named classifications and terminologies. Logical structure is given a component, the LIMR, with named formalisms in Appendix C. Persistence — the form in which a country's clinical data is held over a lifetime — is addressed once in the body, at page 74 line 830, and only to state that the benefit of aligned models holds "regardless of the underlying exchange or persistence technology". Yet the guidance does make persistence commitments: the LHR core attribute at page 157 lines 107–110 requires storage in accordance with the structures published through the LIMR; a functional requirement at page 160 addresses data storage; Annex D.1 lists both a FHIR server and an openEHR clinical data repository as Lifelong Health Record implementations; and Figure 3.2 annotates the record as a "FHIR-based store". The commitments exist but are scattered and are not consistent with one another. In our experience persistence is the decision with the longest consequences, because clinical data outlives the applications and the exchange-standard versions that move it. Suggested revision: Add a short subsection to section 3.6, parallel to 3.6.2, addressing the persistence layer explicitly: what a country is deciding when it chooses how clinical data is held, why that decision has a different time horizon from exchange, the relationship between the persisted form and the logical models published in the LIMR, and the open formalisms available. Then align Figure 3.2, Principle II and the Appendix C material to it. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0538✎ edit📣 feedback | received | technical | Metadata registries ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 Design Principles — II. Open Standards p.32 l.226–238 |
This principle states that countries should ground implementations in open standards that "reduce dependency on proprie…This principle states that countries should ground implementations in open standards that "reduce dependency on proprietary technology", and then names a single direction: "The architecture points to FHIR-based approaches as the direction of travel" (lines 233–234). No information-model formalism is named anywhere in the principle, and information models appear at line 235 only as something to be distributed, not as something to be expressed in a standard. This is inconsistent with the guidance's own treatment elsewhere: Annex D.1 lists EHRbase, "an open-source, openEHR-conformant clinical data repository that stores and queries health data against openEHR archetypes and templates", as an illustrative Lifelong Health Record implementation (page 230, lines 36–37); Appendix C page 175, functional requirement 2, status Required, obliges the LIMR to support openEHR archetypes and templates; and page 174 lines 81–85 make multi-formalism support a core attribute. A design principle that names one family as the direction of travel, while the component specifications require another alongside it, will be read by procurement teams as settling a question the rest of the document leaves open. Suggested revision: Amend lines 233–238 to express the direction of travel by layer rather than as a single family, for example: "The architecture points to open, openly governed standards as the direction of travel — HL7 FHIR for exchange services and transactions, an open information-model formalism such as openEHR archetypes and templates or ISO 13606 for the logical structure of persisted clinical data, and established classifications and terminologies for coded meaning — while accommodating countries at different stages of readiness …". Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-028 discuss | in the document all mentions on GitHub record | |
| PC-0539✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 Design Principles — III. Interoperability p.32 l.240–263 |
The Ministry supports treating interoperability as a structural property rather than a later integration exercise. The …The Ministry supports treating interoperability as a structural property rather than a later integration exercise. The principle as drafted, however, addresses only one of the two ways a health system achieves it. Its whole substance concerns the topology of exchange — centralised mediator versus distributed capability, federated access, connectivity assumptions. Interoperability achieved at the data layer, where contributing systems write to and read from a shared, governed record rather than exchanging between themselves, is not distinguished from application-to-application exchange at all. The phrase "common data models" appears once, at line 244, undefined and unconnected to the Logical Information Model Repository that section 3.6.2 identifies as governing structure. In Slovenia's experience the distinction is the most consequential one a country makes: where contributing systems conform to one governed record, the number of interfaces to be built, tested and maintained falls with each system added rather than rising, and much of the exchange burden the principle discusses does not arise. Suggested revision: Add after line 244: "Interoperability is achieved in two ways, and countries should be explicit about which they are relying on for a given flow. Data-level integration, in which contributing systems write to and read from a shared record governed by a common information model, removes the need for exchange between those systems. Exchange-level integration, in which systems that hold their own data communicate through standardised services, remains necessary across organisational and national boundaries. The first reduces the number of interfaces a country must build and maintain; the second cannot be avoided entirely. The design question is which flows belong in which category." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-064 discuss | in the document all mentions on GitHub record | |
| PC-0540✎ edit📣 feedback | received | technical | Core architects ai |
2.2.1 What REDDHI is and its foundational core §2.2.1 REDDHI foundational core / Appendix C – LIMR p.28; 172 l.Table 2.2 (p28); architecture placement box (p172) |
The capability table on page 28 marks the Logical Information Model Repository with a note that it is "an enabler that …The capability table on page 28 marks the Logical Information Model Repository with a note that it is "an enabler that can be built up as maturity grows, rather than part of the minimum foundation", and the architecture placement box on page 172 advises countries to approach the LIMR as "a progressive enabler, not an immediate prerequisite". Both are in tension with the guidance elsewhere: page 173 lines 43–50 state that the LIMR "establishes the shared structural agreement before systems are built, rather than attempting to reconcile differences after the fact"; page 95 lines 265–273 state that data models should be defined "before implementation begins" and that the LIMR "is the designated home for these national data models"; and page 96 lines 335–338 note that conformance is hardest to retrofit where underlying data structures are not conformant. A ministry reading only the REDDHI table and the placement box will sequence the record before the model, which is the sequence the guidance warns against. Suggested revision: Distinguish the two things now conflated. Reword both passages so that a governed minimum information model — the mandatory data elements for the components a country is actually implementing — is part of the REDDHI foundational core, while a full repository platform, with authoring, federation, dependency tracking and impact analysis, remains a progressive capability. Suggested replacement for the page 28 note: "A governed minimum model is part of the foundation; the full repository platform and its tooling mature over time." Cross-reference 4.3.1 and 4.3.3 from both locations. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-029 discuss | in the document all mentions on GitHub record | |
| PC-0541✎ edit📣 feedback | received | technical | Metadata registries ai |
2.2.2 The enabling conditions for REDDHI §2.2.2 The enabling conditions for REDDHI p.28–29 l.148–151; Figure 2.2 (p30) |
The Open Standards condition names HL7 FHIR as the primary framework for health data exchange alongside ICD, LOINC and …The Open Standards condition names HL7 FHIR as the primary framework for health data exchange alongside ICD, LOINC and SNOMED CT, and the full-STAC "S" box in Figure 2.2 lists HL7 FHIR, ICD, SNOMED CT, LOINC and CQL. Each is an exchange or terminology standard; no formalism is named for the structure of persisted clinical data. Appendix C requires the LIMR to support openEHR archetypes and templates (page 175, functional requirement 2, status Required) and names them again at pages 172 and 174. The enabling conditions, which are where ministries and procurement teams look, do not reflect what Appendix C requires. Suggested revision: Extend line 148–151 to read, in substance: "grounding implementation in open standards — HL7 FHIR as the primary framework for health data exchange; openEHR archetypes and templates, or ISO 13606, for the logical structure of persisted clinical data; alongside established clinical classifications and terminologies such as ICD, LOINC and SNOMED CT …". Add the corresponding entry to the "S" box in Figure 2.2. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0542✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 Design Principles — V. Modularity p.33 l.286–301 |
The Ministry regards this principle as correct and, as drafted, incomplete in the one respect that determines whether i…The Ministry regards this principle as correct and, as drafted, incomplete in the one respect that determines whether it works. Modularity is defined entirely in terms of component boundaries and interfaces — components "loosely coupled — able to be developed, deployed, replaced, or upgraded independently". Nothing is said about the data those components operate on. In practice, applications that each hold their own clinical data structures are tightly coupled through their data however well their interfaces are specified: replacing one means migrating or re-mapping what it holds, and the independence the principle seeks is not available. Slovenia's national programme is direct evidence. Its clinical applications are procured as separate lots, delivered by different suppliers, and can be added, replaced or extended independently — but only because all of them persist clinical content against one nationally governed information model. The modularity is a property of the shared data layer beneath the applications, not of the application interfaces above it. Suggested revision: Add after line 294: "Modularity at the application layer depends on a shared data layer beneath it. Where each component holds clinical data in structures of its own, components remain coupled through their data however well their interfaces are defined, and replacing one entails migrating what it holds. Countries should therefore establish the governed information model for shared clinical data before, or alongside, the components that will write to it, so that applications can be piloted, replaced and upgraded independently against a stable record. A modular ecosystem of applications above a single standards-based patient record is the arrangement this principle is intended to produce." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-064 discuss | in the document all mentions on GitHub record | |
| PC-0543✎ edit📣 feedback | received | technical | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §2.3 Design Principles — VIII. Data Ownership, Access, and Control p.35 l.381–389 |
Lines 381–389 state the problem precisely: a government "can hold formal ownership of a system while lacking the practi…Lines 381–389 state the problem precisely: a government "can hold formal ownership of a system while lacking the practical ability to access its data, modify it, or move away from the supplier that runs it", and the architecture should place practical control with the public entity "through open standards, documented interfaces, data portability, and clear separation between the data a country owns and the systems that process it". The Ministry endorses this without reservation. The principle names no mechanism by which the separation is achieved. Documented interfaces and portability are necessary but operate after the fact: they describe how data is retrieved from a system that has already determined its structure. Separation is achieved when the structure of the data is defined and governed by the public authority independently of any system, so that a system can be replaced without the data being converted. That is what an open, vendor-neutral information model provides, and it is the concrete expression this principle currently lacks. Suggested revision: Add after line 389: "Separation of this kind is achieved most directly where the structure of the data, and not only its interfaces, is defined and governed by the public authority independently of the systems that process it. Where a country's clinical data conforms to an openly specified information model that it governs, a supplier's system can be replaced without the data being converted; where structure is determined by the system, portability guarantees access to data whose meaning still depends on the system that produced it." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | |
| PC-0544✎ edit📣 feedback | received | technical | Metadata registries ai |
3.2 Reading and navigating the reference architecture §3.2 Reading the architecture / 3.3 The reference architecture in practice — Figures 3.2 and 3.5 p.47–48; 66 l.127–132 (p47); Figure 3.2 (p48) and Figure 3.5 (p66), Shared Data Layer, Health Record element |
Section 3.2 states at lines 127–132 that "an element shown in a view represents a capability or a type of component and…Section 3.2 states at lines 127–132 that "an element shown in a view represents a capability or a type of component and the role it plays, not an instruction to procure a particular system", and that the architecture "leaves the choice of implementation … to the country"; line 117 describes the model as offering "a common structure and vocabulary, not a prescription". In Figure 3.2, however, the Lifelong Health Record element in the Shared Data Layer is annotated "FHIR-based store". That is an implementation prescription for the persistence of the national clinical record, and it is the only element in the figure annotated with a storage technology. The identical annotation appears a second time in Figure 3.5 on page 66, which repeats the same Shared Data Layer, so the prescription is stated twice and both occurrences need the same correction. It also sits uneasily with Appendix C page 155 lines 15–25, which states that the LHR "is defined by its outcome, not by its implementation model"; with section 3.6.2 line 813, which scopes HL7 FHIR to "the exchange-oriented representation of health data"; and with section 4.3.3 lines 319–321. Figure 3.2 is the artefact most likely to be reproduced in national architecture documents, so an annotation of this kind propagates further than the surrounding text. Suggested revision: Replace "FHIR-based store" in the Health Record element in both Figure 3.2 (page 48) and Figure 3.5 (page 66) with a formulation consistent with the LHR core attribute at page 157 lines 107–110. Our recommended replacement is "openEHR / FHIR — stored in conformance with the national logical information model", which names both options the guidance already accepts in Annex D.1; "governed longitudinal store" would also be acceptable if no standard is to be named in the figure. If a storage annotation is retained, apply the same treatment to the other shared data layer elements so that the figure does not single out the clinical record for an implementation constraint the text says countries are free to make themselves. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0545✎ edit📣 feedback | received | technical | Metadata registries ai |
3.3 The reference architecture in practice §3.3 The reference architecture in practice — Figures 3.2 and 3.5 p.48; 66 l.Figure 3.2 (p48) and Figure 3.5 (p66) — Shared Data Layer (Syntax – Structure) and Interoperability column (Open Standards) anchor: medium |
Three points on the semantic and structural elements of Figure 3.2. All three apply equally to Figure 3.5 on page 66, w…Three points on the semantic and structural elements of Figure 3.2. All three apply equally to Figure 3.5 on page 66, which repeats the same layer, and both figures require the same correction. First, the "Syntax – Structure / Logical Info Model Repo" element lists its structural artefacts as "FHIR profiles · eObjects · IPS · datasets". openEHR archetypes and templates do not appear, although Appendix C page 175, functional requirement 2, status Required, states that the LIMR "shall support the representation of models conforming to recognised health data standards, including … openEHR archetypes and templates", and page 174 lines 81–85 describe multi-formalism support as a core attribute. The figure therefore shows a single-formalism repository where the component specification requires a multi-formalism one. Second, in the Interoperability column, openEHR is listed under "Open standards — Exchange & content" alongside HL7 FHIR, IHE and IPS. openEHR is an information-model formalism rather than an exchange standard; classifying it as the latter is the layer confusion this guidance elsewhere works to dispel. Third, the Terminology Service and the Logical Info Model Repo are both marked "Knowledge artefact" while the five registries and the Health Record carry the REDDHI marker; the REDDHI capability table on page 28 lists the Terminology Service as delivering a foundational capability without qualification. Suggested revision: Add "openEHR archetypes and templates" to the artefact list in the Syntax – Structure element, alongside FHIR profiles, so the figure matches functional requirement 2 in Appendix C. Move openEHR from "Exchange & content" to a new grouping in the Open Standards column — for example "Information models" — containing openEHR and ISO 13606, so the column distinguishes the layers as the text does. Mark the Terminology Service as a REDDHI component consistent with the page 28 table, and mark the Logical Info Model Repo consistently with whatever resolution is adopted for the related comment on the REDDHI capability table. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0546✎ edit📣 feedback | received | technical | Metadata registries ai |
3.3 The reference architecture in practice §3.3 The reference architecture in practice — Figures 3.2 and 3.5 p.48; 66 l.Figure 3.2 (p48) and Figure 3.5 (p66) — Shared Data Layer anchor: medium |
A constructive suggestion on the structure of the Shared Data Layer. The layer currently resolves person, workforce, lo…A constructive suggestion on the structure of the Shared Data Layer. The layer currently resolves person, workforce, location and product into separate registry elements, each with its own governance, but represents all clinical content in a single "Health Record" element. In national practice the clinical foundation is not homogeneous: structured clinical content, demographic and administrative data, clinical documents, and codes and value sets have different structures, different rates of change, different retention requirements and, in consequence, different appropriate standards. Slovenia's national architecture decomposes its data layer accordingly — structured clinical data governed by an open information model, demographic and administrative data in HL7 FHIR, clinical documents through IHE profiles, and codes and terminology maintained on a national terminology server — with a common service layer and standardised APIs above it. Representing this distinction in Figure 3.2 would remove the need for a single storage annotation on the Health Record element and would show countries a decision they must in any case make. Suggested revision: Decompose the Health Record element in the Shared Data Layer into its constituent data types — structured clinical content (openEHR), demographic and administrative data (FHIR), and clinical documents (IHE) — shown as one governed record with three typed stores rather than three separate records, with the applicable standard noted against each and the Terminology Service supplying codes across all of them. Alternatively, retain the single element and add a sub-line reading "comprising structured clinical content, demographic and administrative data, and documents, each governed by the standard appropriate to it" and add a list of standards so that it is not just FHIR: openEHR, IHE. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0547✎ edit📣 feedback | received | technical | Metadata registries ai |
3.3 The reference architecture in practice §3.3 The reference architecture in practice — Figure 3.4 p.51 l.Figure 3.4 — Metadata Components group anchor: medium |
The layered view for the Trusted Personal Health Records sub-goal groups the metadata components as Client Registry, Fa…The layered view for the Trusted Personal Health Records sub-goal groups the metadata components as Client Registry, Facility Registry, Health Worker Registry, Product Registry and Terminology Service. The Logical Information Model Repository is not among them, although section 3.6.2 lines 802–809 identifies the Terminology Service and the LIMR as the paired components governing meaning and structure and states that both are required, and the Lifelong Health Record shown immediately above depends on the LIMR for the structures against which it stores and validates data (page 157, lines 107–110). The same omission occurs in Appendix E, Goal 1. A reader working from this view would not know that a structural component exists. Suggested revision: Add the Logical Information Model Repository to the Metadata Components group in Figure 3.4, alongside the Terminology Service, and check the other per-goal views for the same omission. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0548✎ edit📣 feedback | received | technical | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 Semantic Governance Infrastructure p.57 l.380–386 |
Lines 380–382 identify concepts deprecated without notice, version conflicts between systems, and national implementati…Lines 380–382 identify concepts deprecated without notice, version conflicts between systems, and national implementation guides drifting from the models they were derived from. Slovenia has addressed the third of these by requiring that every data-quality rule enforced in an application's user interface is replicated as an executable rule on a national validation server, so that conformance is established against the national model rather than against whichever application submitted the data. We suggest the Semantic Governance Infrastructure explicitly include executable validation of submitted data against published models, since drift is otherwise detected only when analysis fails. Suggested revision: Add to the capabilities described in this section: "Executable validation. The rules that constrain a published model should be maintained as executable artefacts against which contributed data can be validated at the point of submission, so that conformance is enforced by the shared infrastructure rather than by each contributing application." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-058 discuss | in the document all mentions on GitHub record | |
| PC-0549✎ edit📣 feedback | received | general | Editorial ai |
3.6.2 Data and health content standards §3.6.2 Data and health content standards p.73–74 l.793–809; 822–830 |
The Ministry endorses this section. The distinction drawn at lines 793–809 between governed structure and governed mean…The Ministry endorses this section. The distinction drawn at lines 793–809 between governed structure and governed meaning, and the analysis at lines 822–827 of how uncoordinated extension of an exchange standard produces "interoperable silos", match Slovenia's national experience closely. The observation at lines 828–830 that aligning information models at the outset improves interoperability regardless of the underlying exchange or persistence technology is, in our view, the most important sentence in the chapter. We would encourage the drafting team to give this material greater prominence, as set out in our comments on Chapter 2. Suggested revision: No change proposed to the text of this section. We recommend cross-referencing lines 822–830 from section 2.2.2 and from Figure 2.2, so that readers of Chapter 2 reach this analysis. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-070 discuss | in the document all mentions on GitHub record | |
| PC-0550✎ edit📣 feedback | received | technical | Metadata registries ai |
3.6.2 Data and health content standards §3.6.2 Data and health content standards p.74 l.811–830 |
This paragraph lists the standards the architecture references — HL7 FHIR, SNOMED CT and SNOMED GPS, ICD-11, LOINC, GS1…This paragraph lists the standards the architecture references — HL7 FHIR, SNOMED CT and SNOMED GPS, ICD-11, LOINC, GS1 and IDMP identifiers, DICOM, IHE profiles and the international patient summary. Nine standards are named across exchange, terminology, product identification, imaging and content; none is named for the structure of persisted clinical data, although lines 805–807 state that the Logical Information Model Repository governs structure and lines 808–809 that both structure and meaning are required. Line 813 scopes HL7 FHIR to "the exchange-oriented representation of health data", which is correct and which leaves the structure layer stated as a requirement with no candidate named. A reader will reasonably conclude that FHIR answers both layers, which section 4.3.3 lines 319–321 states it does not. Lines 828–830 note the benefit holds regardless of the underlying exchange or persistence technology. We agree, and suggest the guidance goes one step further, since countries must in practice choose. On the basis of a decade of national operation the Ministry would distinguish three roles: the logical structure of persisted clinical data, governed by an open information-model framework; persisted demographic, administrative and encounter data, for which HL7 FHIR is well suited and is how Slovenia uses it; and interoperability, APIs, services and transactions, for which section 4.3.3 already recommends HL7 FHIR. Making the roles explicit helps countries avoid adopting an exchange-oriented representation as a lifelong persistence format, where breaking changes between major versions of the exchange standard become migrations of the entire national data estate. Suggested revision: Two changes. First, amend the standards list from line 813 to name open information-model formalisms alongside the others, e.g.: "— among them HL7 FHIR for the exchange-oriented representation of health data; openEHR archetypes and templates, or ISO 13606, for the logical structure of persisted clinical data, within the EHR architecture requirements of ISO 18308:2011; SNOMED CT (and SNOMED GPS), ICD-11 and LOINC for clinical terminology and classification; …". Naming candidates at this layer, as the guidance already does at every other layer, does not mandate any one of them. Second, add after line 830: "It is useful to distinguish the roles a standard is asked to play. The logical structure of persisted clinical data, the representation of demographic and administrative data, and the exchange of both between systems are different problems with different rates of change. Countries should select standards per role rather than adopting a single representation for all three, and record that selection in the information model and terminology components." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | |
| PC-0551✎ edit📣 feedback | received | general | Core architects ai |
3.6.4 Cross-border health data flows §3.6.4 Cross-border health data flows p.77 l.914–924 |
The description of the European cross-border infrastructure is accurate. Since the entry into force of Regulation (EU) …The description of the European cross-border infrastructure is accurate. Since the entry into force of Regulation (EU) 2025/327, cited at footnote 33, the separation of primary and secondary use that lines 922–924 describe is a legislated obligation for participating states rather than an accompanying legal framework, with consequences for how national components are specified. Countries planning for cross-border exchange may find it useful for the guidance to note that a regional legal framework can impose specification requirements on national DPI-H components, and that this is now the case in one region. Suggested revision: Amend lines 922–924 to note that in the European Union this framework is now established in regulation, and add a sentence: "Where a regional legal framework of this kind applies, its requirements should be treated as inputs to national component specifications from the outset rather than as a later compliance exercise." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-261 discuss | in the document all mentions on GitHub record | |
| PC-0552✎ edit📣 feedback | received | technical | Core architects ai |
3.6.5 Conformance §3.6.5 Conformance / 3.7 Conformance and Testing p.78 l.956–960 |
The Ministry supports the statement that requirements should be expressed testably so that countries can validate confo…The Ministry supports the statement that requirements should be expressed testably so that countries can validate conformance, including the claims of suppliers, before and during procurement. We would add that this is materially easier where the artefacts against which conformance is tested are national assets rather than supplier deliverables. Slovenia requires suppliers to publish archetypes, templates, profiles, terminology bindings, implementation guides and validation rules to a repository designated by the Ministry, as a condition of acceptance. The guidance would be strengthened by naming publication of conformance artefacts as a procurement condition rather than a technical practice. Suggested revision: Add at line 959: "Countries should require, as a condition of acceptance in procurement, that the information models, profiles, terminology bindings, implementation guides and validation rules developed under a contract are published as national assets in a repository the authority controls." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | |
| PC-0553✎ edit📣 feedback | received | general | Metadata registries ai |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 Services and Transactions: FHIR as the Recommended Framework p.96 l.315–321; 331–338 |
The Ministry supports this section, and in particular lines 315–321, which state that a FHIR profile is a representatio…The Ministry supports this section, and in particular lines 315–321, which state that a FHIR profile is a representation of the logical model rather than a replacement for it and that two systems can each be valid FHIR and still diverge in meaning. This matches our national experience precisely. We also support lines 331–338 on progressive conformance and the observation that FHIR compatibility is hardest to retrofit where underlying data structures are not conformant. Our concern is placement rather than content: this analysis appears in Chapter 4, while the enabling conditions in Chapter 2 that shape national procurement do not carry it. Suggested revision: No change proposed to this text. We recommend that a short subsection be added to 4.3 before 4.3.3, parallel in structure to it — for example "4.3.x Clinical content and persistence: the governed information model" — since 4.3.1 already establishes that data structures are designed first, and that section 2.2.2 cross-reference it. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | |
| PC-0554✎ edit📣 feedback | received | technical | Clinical ai |
Lifelong Health Record §Appendix C – Lifelong Health Record, 1 What it is p.155 l.15–25 |
The Ministry supports the position that centralised, federated, hybrid and virtual records are all valid expressions of…The Ministry supports the position that centralised, federated, hybrid and virtual records are all valid expressions of the LHR capability. We note that dependence on a governed logical information model rises as implementations become more federated, not less: where data remain at source and are assembled on demand, there is no single repository in which structure can be enforced, so the comparability of the assembled record rests entirely on shared structural definitions. Readers may draw the opposite inference — that federation reduces the need for a common model — and the guidance would be strengthened by closing that gap explicitly. Suggested revision: Insert after line 25: "The more federated the implementation, the greater the dependence on a governed logical information model. Where data remain at source and are assembled on demand, the comparability of the assembled record rests on shared structural definitions rather than on a common repository, and the logical information model repository correspondingly becomes more important rather than less." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | |
| PC-0555✎ edit📣 feedback | received | editorial | Editorial ai |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 The Roles and Skills Needed to Build and Govern the Architecture p.101 l.502–503 |
The role is given as "Information and FHIR modellers, who design the data models, FHIR profiles, and actor definitions"…The role is given as "Information and FHIR modellers, who design the data models, FHIR profiles, and actor definitions". Naming one standard in a role title narrows how countries staff a function that is not standard-specific: the same team maintains logical information models, terminology bindings and profiles in whichever formalisms the national architecture uses. In Slovenia this function spans openEHR archetypes and templates and FHIR profiles, and is staffed as one capability. Suggested revision: Amend to: "Information modellers, who design the logical information models, the profiles and actor definitions derived from them, and the terminology bindings that make the architecture implementable, and keep them aligned with the …". Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | |
| PC-0556✎ edit📣 feedback | received | general | Core architects ai |
4.1.1 No Country Starts from Zero §4.1.1 No Country Starts from Zero / 4.1.2 Assessing Where You Are p.88 l.14–33 |
In answer to the consultation question on applicability across income settings, the Ministry offers the following about…In answer to the consultation question on applicability across income settings, the Ministry offers the following about the limits of its own experience. Slovenia's ability to mandate a single national information model rests on conditions not universally available: statutory authority to require participation by all providers including private ones, a single payer, a national identity infrastructure already in place, and a population small enough for one editorial authority to govern one model. Countries without these will need different governance instruments to reach the same outcome, and the guidance should not imply that mandate is the only route. We would note, however, that the underlying recommendation is not weaker in constrained settings but stronger: a ministry with a small architecture team gains more from adapting an internationally curated, openly published model library than from authoring national specifications from first principles, which is the capability described at page 174 lines 104–108. Suggested revision: Add to the assessment questions at line 34 onward a fourth consideration: "what statutory, contractual or financing instruments are available to the authority to require conformance to shared specifications, given that few countries can rely on mandate alone". And add to 4.5.3 a sentence noting that adaptation of internationally curated models is generally less demanding of national capacity than de novo specification. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | |
| PC-0557✎ edit📣 feedback | received | general | Core architects ai |
4.6.3 Approaches to Financing §4.6.3 Approaches to Financing p.103 l.592–596 |
The observation that shared components serve many programmes at once and that pooling investment across them is therefo…The observation that shared components serve many programmes at once and that pooling investment across them is therefore efficient matches Slovenia's experience. We would add a practical qualification: pooling is easier to sustain where the shared components are procured and governed as one programme with a single accountable authority. Slovenia is building several foundational components under one co-financed national programme with the National Institute of Public Health as steward, which is what makes a shared information model enforceable across separately procured applications. Where shared components are financed jointly but governed separately, the pooling advantage tends to be lost to divergent specification. Suggested revision: Add after line 596: "Pooled investment is most durable where the pooled components are also governed as one programme under a single accountable authority; joint financing without joint governance tends to reproduce the divergence it was intended to avoid." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | |
| PC-0558✎ edit📣 feedback | received | technical | Metadata registries ai |
E Appendix E: Health Goals to DPI Mapping §Appendix E – Health Goals to DPI Mapping, Goal 1 p.236 l.237–244 |
Goal 1 lists the shared components that the other six goals draw on as "the client, health facility, and health workfor…Goal 1 lists the shared components that the other six goals draw on as "the client, health facility, and health workforce registries, the terminology service, the product registry, and the lifelong health record". The Logical Information Model Repository is absent, although section 3.6.2 lines 802–809 identifies the Terminology Service and the LIMR as the two components that govern meaning and structure respectively and states that both are required, and page 175 lines 135–139 states that without a LIMR each component's data requirements exist in isolation. "Captured once and reused reliably", the goal stated at lines 227–228, depends on shared structure as much as on shared identifiers. Suggested revision: Add the logical information model repository to the component list at lines 238–240, and add a sentence at line 241: "Shared structure is what allows data captured once to be interpreted the same way by every component that reuses it." Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-225 discuss | in the document all mentions on GitHub record | |
| PC-0559✎ edit📣 feedback | received | technical | Metadata registries ai |
Lifelong Health Record §Annex D.1 — Lifelong Health Record / Figures 3.2 and 3.5 / principle II p.229–230; 48; 66; 32 l.33–37 (p229–230); Figures 3.2 and 3.5; 233–234 (p32) |
Annex D.1 lists two illustrative implementations under Lifelong Health Record: HAPI FHIR Server, "an open-source, FHIR-…Annex D.1 lists two illustrative implementations under Lifelong Health Record: HAPI FHIR Server, "an open-source, FHIR-conformant server widely used as a technical foundation for health record repositories", and EHRbase, "an open-source, openEHR-conformant clinical data repository that stores and queries health data against openEHR archetypes and templates". The annex therefore treats both a FHIR server and an openEHR repository as valid technical foundations for the LHR. Figures 3.2 and 3.5, however, both annotate the Lifelong Health Record element as a "FHIR-based store", and design principle II at page 32 lines 233–234 names FHIR-based approaches as the direction of travel. The illustrative annex, the figures and the design principle give countries different answers to the same question. Taken with Appendix C page 175 functional requirement 2, which makes openEHR archetypes a required LIMR formalism, the guidance accepts openEHR in three places and omits it from the three places a ministry or a procurement team will actually read. Suggested revision: Align them. If Annex D.1 is correct that both a FHIR server and an openEHR clinical data repository are valid foundations for the Lifelong Health Record — and the Ministry’s national experience is that both are — then the annotation in Figures 3.2 and 3.5 should read "openEHR / FHIR" rather than "FHIR-based store", and principle II should name both. These are small changes and they remove an inconsistency that any reader comparing the figures with the annex will find immediately. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0560✎ edit📣 feedback | received | general | Metadata registries ai |
Rwanda §Annex D.2 – Country implementation examples p.233 l.151 |
Annex D.2 does not include Slovenia. Slovenia is a relevant case for the Lifelong Health Record, the Logical Informatio…Annex D.2 does not include Slovenia. Slovenia is a relevant case for the Lifelong Health Record, the Logical Information Model Repository and the Open Technologies enabling condition: a national record in production since 2015 in which persisted clinical content has been governed by an open information model throughout, while demographic and administrative data use HL7 FHIR, and in which separately procured applications from several suppliers write into one shared model. No entry currently in the annex illustrates that division of standards by role, or demonstrates supplier interchangeability against a single national model. Suggested revision: Insert after line 151, before the Spain heading (alphabetical order): Slovenia Components illustrated: LHR, Terminology Service, LIMR Slovenia's national Central Patient Data Registry (CRPP), governed by the National Institute of Public Health, has held structured clinical data for the national population since 2015, with participation mandatory for all providers, public and private. It now holds over 330 million documents and receives approximately 200,000 new clinical records each day. Clinical content has been persisted against a nationally governed openEHR information model since the registry opened; demographic and administrative data use HL7 FHIR and documents use IHE profiles, with national code sets maintained on a national terminology server. Health workers can use their own information system or a nationally available professional portal (zVEM+) and citizens a portal and mobile application (zVEM) with some 560,000 active users (citizens), both served from the same governed record. There are several national digital services already built like ePrescriptions, eVaccinations, eReferrals and a recent national programme has extended this model with several national applications that run on the national patient record and platform: family medicine, paediatrics, community nursing, gynaecology, diabetes care, patient-reported outcomes and clinical documents, procured as separate lots and delivered by several suppliers against one shared model. It demonstrates how governing persisted clinical structure separately from the exchange format allows a national record to outlast the applications built on it, and lets capabilities be added without renegotiating structure each time. Suggested footnote source: https://nijz.si/informatika-v-zdravstvu/ezdravje/ (National Institute of Public Health, eZdravje). Also add "Slovenia" to the Annex D.2 entry list in the contents, between "Rwanda" and "Spain". Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0561✎ edit📣 feedback | received | general | Metadata registries ai |
2.2.2 The enabling conditions for REDDHI §2.2.2 The enabling conditions for REDDHI / Annex D.2 — Spain p.28–29; 233 l.148–159; 152–160 |
Evidence published after this draft was prepared may be useful to the drafting team. In August 2026 The Lancet Digital …Evidence published after this draft was prepared may be useful to the drafting team. In August 2026 The Lancet Digital Health published the results of a Delphi consensus commissioned by the Spanish Ministry of Health, in which 152 of 220 nominated national experts reached agreement in a single round on recommendations for a national electronic health record, externally validated by an international advisory board from seven countries. Its recommendations anchor the national architecture on ISO 18308:2011 — the standard this guidance already cites at page 156 line 43 — hold that compliance is best achieved through dual information architecture models, specifically ISO 13606 and openEHR, and recommend HL7 FHIR for the exchange of information at the technical layer with its mapping defined in conjunction with the clinical knowledge model. This is an independent national consensus reaching the same architectural conclusion as our own experience. Suggested revision: Cite this evidence in support of naming an information-model framework in 2.2.2, and consider updating the Spain entry in Annex D.2 to note the national consensus process. Reference: Piera-Jiménez J, Cano I, Carot-Sans G, Cresswell K, Dunscombe R, Freriks G, et al. Recommendations for a national electronic health record in Spain: a Delphi study. Lancet Digit Health. Online first, 19 August 2026, article 101037. doi:10.1016/S2589-7500(26)00060-9. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | |
| PC-0562✎ edit📣 feedback | received | editorial | Editorial ai |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4 p.96; 97 l.339; 369 |
Two different subsections are numbered 4.3.4: "Integration Interfaces with Foundational DPI" at page 96 line 339, and "…Two different subsections are numbered 4.3.4: "Integration Interfaces with Foundational DPI" at page 96 line 339, and "Interoperability Implementation Pathways" at page 97 line 369. The duplication also appears in the table of contents. Suggested revision: Renumber the second occurrence as 4.3.5 and the subsequent "Minimum Conformance and Testing" as 4.3.6, and correct the contents accordingly. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-097 discuss | in the document all mentions on GitHub record | |
| PC-0563✎ edit📣 feedback | received | editorial | Editorial ai |
unplaced §Front matter – page numbering p.1–6 (contents); 1–2 (glossary); 1–7 (executive summary) l.n/a |
The document contains three independent page-numbering sequences that each begin at 1: the contents pages, the glossary…The document contains three independent page-numbering sequences that each begin at 1: the contents pages, the glossary, and the executive summary and body. Printed page "1" therefore occurs three times and "2" twice. Because the comment template asks reviewers to cite section, page and line, references in submitted comments will be ambiguous, and comparison of comments across reviewers will be harder than it needs to be. Suggested revision: Use a single continuous sequence, or number front matter in roman numerals and the body in arabic, so that every page reference is unique. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-254 discuss | all mentions on GitHub record | |
| PC-0564✎ edit📣 feedback | received | editorial | Editorial ai |
Glossary §Glossary p.Glossary pp. 1–2 l.n/a (Business Domain; Digital Infrastructure; Identifiers; and two further entries) anchor: medium |
Five glossary entries carry a highlighted "[Under review]" marker in the version circulated for public comment, includi…Five glossary entries carry a highlighted "[Under review]" marker in the version circulated for public comment, including the definitions of Business Domain and of terms used throughout Chapter 3. Reviewers cannot comment on definitions that are not settled, and terms used normatively in the body should be defined before consultation. Suggested revision: Resolve the marked entries before publication, or state in the front matter which definitions remain provisional so that reviewers know not to rely on them. Katarina Kralj, Ministry of Health, Slovenia |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | |
| PC-0565✎ edit📣 feedback | received | general | No human |
unplaced §1 p.i–iii; 1–110 |
The overall relevance and usability of the framework are clear, and the necessary information is present. WHO makes it …The overall relevance and usability of the framework are clear, and the necessary information is present. WHO makes it clear that a framework serving as worldwide guidance for designing an integrated national digital health system is an unmet need, and this blueprint will stimulate and help countries to create one. IPC also perceives the organisation of digital health across the regions of the world as fragmented, so this connecting framework is welcome. The examples of what DPI-H can offer are important. Suggested revision: No change required — IPC's compliments to WHO on the initiative and on providing this framework. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | all mentions on GitHub record | |
| PC-0566✎ edit📣 feedback | received | general | Editorial ai |
unplaced §1 p.1–110 |
There is room for improvement in usability. Reading and studying the document took the working group many hours, and we…There is room for improvement in usability. Reading and studying the document took the working group many hours, and we had to write our own summary to understand the overall structure. Many figures are far too complicated. The document runs to 241 pages in total; the narrative text ends at page 110 and the remainder is appendices, but this is not evident to a reader opening the file, and a document of that apparent length means many healthcare providers (HCPs) will not read it. Suggested revision: Shorten and simplify: reduce the length of the narrative text, simplify the more complex figures, and add a clear structural overview near the front — stating that the main guidance ends at page 110 and that the appendices are reference material — so readers can navigate the document without constructing their own summary. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-284 discuss | all mentions on GitHub record | |
| PC-0567✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §1 p.i–iii |
The present executive summary provides very little information and does not cover the subject well. A longer and more i…The present executive summary provides very little information and does not cover the subject well. A longer and more informative summary would make the document far more usable. Suggested revision: Rewrite the executive summary so it is long enough to cover the subject properly, summarising purpose, the two-layer architecture, the DPI-H components, REDDHI and the STAC foundation, and the implementation pathways. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-002 discuss | in the document all mentions on GitHub record | |
| PC-0568✎ edit📣 feedback | received | general | Clinical ai |
1.5 The Seven Priority Health Sector Goals §1 p.22–40; 88–103 anchor: medium |
IPC has published a consensus manuscript on statements on the use of digital health, in particular teledermatology, in …IPC has published a consensus manuscript on statements on the use of digital health, in particular teledermatology, in psoriasis (El Komy MHM, Chiricozzi A, Kerkhof P, Armstrong A, Diamei V, Hsu C, et al. Telemedicine and psoriasis: a review based on statements of the telemedicine working group of the International Psoriasis Council. JEADV Clin Pract. 2023;2:19-31. https://doi.org/10.1002/jvc2.93). The following consensus statements are in line with the current WHO initiative and are offered as supporting evidence: legal aspects, cost-effectiveness and reimbursement — Q14 every national healthcare system should legalise and establish preferred teledermatology systems such as live video conferencing (LVC) and store-and-forward (SAF); Q15 security, safety and privacy protocols for data communicated through teledermatology must be established; Q16 SAF and LVC must be reimbursed on par with in-person visits according to national reimbursement systems. Innovation in care — Q27 teledermatology consultations for early diagnosis should be available where culturally acceptable; Q28 teledermatology consultations are suitable for follow-up of patients with psoriasis; Q29 telehealth advice is increasingly used and can serve as a non-diagnostic triage and referral tool. Pictures, AI and automated PASI — Q30 photographs of patients with psoriasis are essential for diagnosis and for concomitant skin diseases; Q31 photograph quality should be optimised by giving patients instructions consistent with American Teledermatology Association guidelines. Access to care — Q36 access to care in underserved areas can be improved by providing a framework for the optimal use of teledermatology. (Q-numbers refer to the IPC consensus publication, not to the WHO draft.) Suggested revision: Cite the IPC teledermatology consensus statements as supporting evidence in the relevant sections, and reflect the reimbursement, privacy and image-quality statements in the guidance on legal aspects, financing and clinical images. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-259 discuss | in the document all mentions on GitHub record | |
| PC-0569✎ edit📣 feedback | received | general | Editorial ai |
2.1 The Reference Architecture Scope §2 p.24–87 anchor: medium |
The DPI-F/DPI-H distinction, the two-layer architecture, the component set, REDDHI, the goal mappings, interoperability…The DPI-F/DPI-H distinction, the two-layer architecture, the component set, REDDHI, the goal mappings, interoperability and conformance are all well explained — but in a language health scientists speak, not the language of healthcare providers or patients. Suggested revision: Add a plain-language layer for clinical and patient audiences: either a short non-technical companion section or plain-language summaries at the start of each architecture chapter. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-004 #21 | in the document all mentions on GitHub record | |
| PC-0570✎ edit📣 feedback | received | No human |
2.1.2 Business services layer §2 p.26–31 anchor: medium |
The implementation guidance in the REDDHI framework, and particularly the STAC foundation, is outstanding — it is the m…The implementation guidance in the REDDHI framework, and particularly the STAC foundation, is outstanding — it is the most valuable part of the document. The table on capabilities and components and the table on DPI-H architecture design are excellent and provide real inspiration for clinicians. Suggested revision: No change required — IPC's compliments to WHO on the REDDHI framework and the STAC foundation. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0571✎ edit📣 feedback | received | technical | Clinical ai |
2.4 Methodology: Mapping Health Goals to DPI-H §2 p.49–52; 114–123 anchor: medium |
OMISSION — there is no guidance anywhere in the framework on the capture, transmission or storage of clinical photograp…OMISSION — there is no guidance anywhere in the framework on the capture, transmission or storage of clinical photographs. IPC recently inventoried the use of digital tools by dermatologists worldwide across all regions (manuscript in preparation); dermatologists use a wide variety of digital tools, in particular for sharing psoriasis images. Images require quality control, consent, privacy, retention, encryption and interoperability, and a reimbursement system in every country. Given siloed healthcare organisation past and present, these images must be retrievable by other HCPs caring for the patient. Psoriasis is a systemic disease with comorbidities including cardiometabolic disease, depression and psoriatic arthritis, so care requires an infrastructure permitting interoperability and easy access for all healthcare workers involved. This matters especially in low-resource countries, where affordable, scalable, interoperable solutions can improve access to specialist care. Suggested revision: Add explicit WHO guidance on consent, quality standards, retention, encryption and interoperability of clinical images as part of the Lifelong Health Record concept, together with the legislative/privacy framework and a reimbursement expectation. Guidance on privacy alongside the medical need for interoperability is mandatory. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-251 discuss | in the document all mentions on GitHub record | |
| PC-0572✎ edit📣 feedback | received | technical | Clinical ai |
2.4 Methodology: Mapping Health Goals to DPI-H §2 p.49–52 anchor: medium |
The reusable, non-siloed system is framed around point-of-care clinical data only, with no provision for patient-report…The reusable, non-siloed system is framed around point-of-care clinical data only, with no provision for patient-reported outcomes (PROs). Suggested revision: Extend the architecture to support standardised collection and longitudinal tracking of patient-reported outcomes (PROs), not only point-of-care clinical data. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-271 discuss | in the document all mentions on GitHub record | |
| PC-0573✎ edit📣 feedback | received | general | Core architects ai |
3.6.4 Cross-border health data flows §3 p.88–103 anchor: medium |
IPC endorses the division of responsibility: WHO provides the blueprint and national healthcare organisations design th…IPC endorses the division of responsibility: WHO provides the blueprint and national healthcare organisations design the national architecture and guidance for digital public infrastructure for the health sector. However, the implementation approach as currently drafted is fairly top-down — national authorities are given the blueprint to apply rather than being engaged in shaping how it is implemented in their own setting. Suggested revision: Retain the division of responsibility between WHO and national authorities, but involve national authorities directly in developing the implementation plan, so that adoption is co-designed with the countries that will operate the infrastructure rather than handed down to them. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-078 discuss | in the document all mentions on GitHub record | |
| PC-0574✎ edit📣 feedback | received | technical | Core architects ai |
Future proofing the Architecture §3 p.104–110 anchor: low |
The document does not address the EU Medical Device Regulation (MDR), although many digital tools supporting clinical d…The document does not address the EU Medical Device Regulation (MDR), although many digital tools supporting clinical decision-making fall within that regulatory framework. Suggested revision: Include brief considerations related to the EU Medical Device Regulation (MDR) to strengthen the feasibility of national adoption in Europe. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | |
| PC-0575✎ edit📣 feedback | received | technical | Core architects ai |
unplaced §3 p.119–121 |
Existing frameworks on aspects of digital health already operate in various areas of the world, but the document does n…Existing frameworks on aspects of digital health already operate in various areas of the world, but the document does not articulate how DPI-H aligns with the European regulatory environment, particularly the GDPR and the European Health Data Space (EHDS), where consent, data minimisation and cross-border interoperability are legally defined. Suggested revision: Add explicit reference to GDPR and the European Health Data Space (EHDS) and explain how DPI-H aligns with them, to support implementation in EU Member States. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-261 discuss | all mentions on GitHub record | |
| PC-0576✎ edit📣 feedback | received | technical | Core architects ai |
3.6.4 Cross-border health data flows §3 p.88–103 anchor: medium |
The document does not reflect the federated governance models present in several European countries, including Italy, w…The document does not reflect the federated governance models present in several European countries, including Italy, where national infrastructures such as the Fascicolo Sanitario Elettronico (FSE 2.0) rely on regional implementation and interoperability. Suggested revision: Add guidance on federated architectures so the framework is applicable in decentralised and regionally implemented national systems. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-024 discuss | in the document all mentions on GitHub record | |
| PC-0577✎ edit📣 feedback | received | general | Core architects ai |
4.6.3 Approaches to Financing §3 p.102–103 anchor: medium |
The document could better support the investment case by pointing to available funding instruments.The document could better support the investment case by pointing to available funding instruments. Suggested revision: Briefly mention how countries may leverage European funding instruments (EU4Health, Digital Europe Programme, PNRR Mission 6) to support DPI-H implementation, making the guidance more actionable for EU Member States. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-115 discuss | in the document all mentions on GitHub record | |
| PC-0578✎ edit📣 feedback | received | general | WHO ai |
4.3.4 Interoperability Implementation Pathways §4 p.98–99 anchor: medium |
It is very important that the guidance provides general principles and gives national organisations the opportunity to …It is very important that the guidance provides general principles and gives national organisations the opportunity to design a national blueprint fit for purpose in their own setting. However, there is no process for incorporating learning from countries back into the guidance. Suggested revision: Recommend that countries work through a quality circle (Plan, Do, Check, Act), and that WHO then collects the national blueprints and shares lessons learned across countries so each country can build on others' experience. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-253 discuss | in the document all mentions on GitHub record | |
| PC-0579✎ edit📣 feedback | received | technical | Core architects ai |
4.2.2 A Phased Implementation Approach §4 p.104–110 anchor: medium |
Artificial intelligence is of major importance, particularly for early diagnosis and for selecting the optimal treatmen…Artificial intelligence is of major importance, particularly for early diagnosis and for selecting the optimal treatment for individual patients, and AI depends on the retrieval of relevant patient data. The guidance does not make patient data input into DPI-H mandatory or bind it to the principles defined for the national digital health infrastructure. Suggested revision: State that patient data input into DPI-H is mandatory and must adhere to the principles defined for the national digital health infrastructure, so that AI applications have the data foundation they require. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-271 discuss | in the document all mentions on GitHub record | |
| PC-0580✎ edit📣 feedback | received | technical | Core architects ai |
unplaced §4 p.41–52 |
Because psoriasis is a systemic disease, data from dermatology, rheumatology and cardiology need to be captured within …Because psoriasis is a systemic disease, data from dermatology, rheumatology and cardiology need to be captured within the same infrastructure rather than as siloed, stand-alone datasets. Such an infrastructure is mandatory for successful application of AI. Suggested revision: Require multi-specialty data (e.g. dermatology, rheumatology, cardiology) to be captured within a single shared infrastructure rather than as siloed datasets, and state this as a precondition for AI applications. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-259 discuss | all mentions on GitHub record | |
| PC-0581✎ edit📣 feedback | received | general | Core architects ai |
unplaced §4 p.55; 109 |
Equity barriers in underserved areas are not sufficiently addressed: variability in digital literacy among healthcare p…Equity barriers in underserved areas are not sufficiently addressed: variability in digital literacy among healthcare professionals (including in Europe), illiteracy and digital illiteracy among patients, limited internet connectivity in rural and mountainous areas such as those in Italy, and cultural factors affecting acceptability. Suggested revision: Add short guidance on minimum digital competencies and structured training for healthcare professionals, and recommendations on offline-first workflows and low-bandwidth solutions for areas with connectivity limitations. Address patient literacy and digital literacy and cultural acceptability explicitly. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-237 #11 | all mentions on GitHub record | |
| PC-0582✎ edit📣 feedback | received | general | Editorial ai |
D Appendix D: Country and Regional Implementation Examples §Appendix D p.229–235 anchor: medium |
The examples are very important and illustrate the key messages very well, but they are grouped at the very end of the …The examples are very important and illustrate the key messages very well, but they are grouped at the very end of the document and organised by country, mostly drawn from national databases, which reduces their practical relevance to the guidance they illustrate. Suggested revision: Place an example with each section of guidance — a case study or two per chapter — rather than grouping them all at the end. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | |
| PC-0583✎ edit📣 feedback | received | technical | Core architects ai |
Kenya §Appendix D p.233–234 anchor: medium |
European coverage among the country and regional illustrations is thin. Appendix D includes Spain (Catalonia) at subnat…European coverage among the country and regional illustrations is thin. Appendix D includes Spain (Catalonia) at subnational level, England in relation to pharmaceutical decision support, and an EU/EEA entry on regional surveillance, but there is no example of a national-level implementation in an EU Member State operating under the EU regulatory framework (GDPR, EHDS) — which is the setting most relevant to readers planning adoption in Europe. Suggested revision: Add at least one national-level European example, such as Italy's Fascicolo Sanitario Elettronico (FSE 2.0) or MyHealth@EU, to illustrate how DPI-H principles translate into practice within the EU regulatory and infrastructural context, alongside the existing subnational and regional entries. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0584✎ edit📣 feedback | received | editorial | Editorial ai |
Executive Summary §General / Front matter p.i–iii; 1–110 |
The document is detailed and should be completed with the recommendations above. The executive summary needs improvemen…The document is detailed and should be completed with the recommendations above. The executive summary needs improvement — it does not cover the subject well and should be long enough to do so. Suggested revision: Expand the executive summary so it covers the subject adequately, and incorporate the recommendations made in the comments above. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-002 discuss | in the document all mentions on GitHub record | |
| PC-0585✎ edit📣 feedback | received | editorial | Editorial ai |
Glossary §Front matter p.i–iii |
A glossary is provided in the front matter, but it is limited to generic architecture terms (application component, app…A glossary is provided in the front matter, but it is limited to generic architecture terms (application component, application service, capability, data object and similar) and does not define the specialist vocabulary the document relies on most heavily — REDDHI, STAC, DPI-F and DPI-H, or the wider acronym set. It is also placed before the main text without being signposted from the chapters where the terms first appear. Suggested revision: Expand the existing glossary to cover the document's core specialist terms and acronyms (REDDHI, STAC, DPI-F, DPI-H and others), and signpost it from the executive summary and from the first use of each term so non-specialist readers can find the definitions. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | |
| PC-0586✎ edit📣 feedback | received | technical | Editorial ai |
2.1.2 Business services layer §2 p.26–31 anchor: medium |
Although the REDDHI framework and the STAC foundation are the most valuable part of the document, they are not given th…Although the REDDHI framework and the STAC foundation are the most valuable part of the document, they are not given the prominence they deserve, and the capabilities/components and DPI-H architecture design tables need more explanation than they currently carry for a clinical reader to interpret them. Suggested revision: Call out REDDHI and the STAC foundation explicitly in the executive summary, and expand the explanatory text accompanying the capabilities/components table and the DPI-H architecture design table so a clinical reader can interpret them without external help. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-004 #21 | in the document all mentions on GitHub record | |
| PC-0587✎ edit📣 feedback | received | No human |
unplaced §Row / comment no. p.Issue |
What we foundWhat we found Suggested revision: Options / proposed action Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | all mentions on GitHub record | ||
| PC-0588✎ edit📣 feedback | received | No ai |
unplaced §Row 16 (comment 6) p.Compliment became a criticism |
Your original comment 5 read "REDDHI framework outstanding — our compliments." The consolidated row keeps the praise bu…Your original comment 5 read "REDDHI framework outstanding — our compliments." The consolidated row keeps the praise but reframes it as a criticism ("not given the prominence it deserves", tables "need more explanation") and types it Technical. Only rows 11 and 19 now read as pure compliments. Suggested revision: (a) Restore as a pure compliment, as you originally wrote it; (b) split into two rows — one compliment on REDDHI/STAC, one Technical comment asking for more prominence and explanation; (c) leave as drafted. Please indicate preference. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | all mentions on GitHub record | ||
| PC-0589✎ edit📣 feedback | received | No ai |
unplaced §Rows 19 and 32 (comments 9 and 22) p.Two comments contradict each other |
Row 19 calls the implementation approach "outstanding" and endorses WHO providing the blueprint while national organisa…Row 19 calls the implementation approach "outstanding" and endorses WHO providing the blueprint while national organisations design their own architecture. Row 32 says the approach is too top-down and national authorities should be involved in shaping implementation. Both are submitted as separate numbered comments and WHO reviewers will read them as inconsistent. Suggested revision: (a) Merge into one comment — endorse the division of responsibility but ask that national authorities be engaged in shaping the implementation plan rather than receiving it; (b) keep row 19 and drop row 32; (c) keep row 32 and drop row 19. Option (a) is recommended as it preserves both points without contradiction. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | all mentions on GitHub record | ||
| PC-0590✎ edit📣 feedback | received | No ai |
unplaced §Row 12 (comment 2) p.Page-count figure clarified |
The 241-page figure is the full PDF. The narrative guidance ends at p.110; pp.111–241 are references and Appendices A–F…The 241-page figure is the full PDF. The narrative guidance ends at p.110; pp.111–241 are references and Appendices A–F. The comment now states this so the length criticism cannot be deflected by pointing out that most of the document is reference material. Suggested revision: Amended. Revert if you prefer the original blunt wording. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | all mentions on GitHub record | ||
| PC-0591✎ edit📣 feedback | received | No ai |
D.2 Country implementation examples §Row 29 (comment 19) p.Factually incorrect — corrected anchor: low |
The comment previously said there are no European examples. Appendix D does contain them: Spain (Catalonia) at subnatio…The comment previously said there are no European examples. Appendix D does contain them: Spain (Catalonia) at subnational level on p.233, England on pharmaceutical decision support and an EU/EEA regional surveillance entry on p.234. As originally written the comment would have been dismissed immediately. Suggested revision: Reworded to say European coverage is thin and lacks a national-level EU Member State example, and to ask for FSE 2.0 or MyHealth@EU. Please confirm this still reflects your intent. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0592✎ edit📣 feedback | received | No ai |
Glossary §Row 31 (comment 21) p.Glossary exists — comment reframed anchor: low |
The comment previously said there are no consolidated definitions. A glossary does exist in the front matter, but it co…The comment previously said there are no consolidated definitions. A glossary does exist in the front matter, but it covers only generic architecture terms (application component, application service, capability, data object and similar) and omits REDDHI, STAC, DPI-F, DPI-H and the wider acronym set. Suggested revision: Reworded to ask that the existing glossary be expanded to cover the core specialist terms and acronyms, and signposted from the chapters. Please confirm. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | ||
| PC-0593✎ edit📣 feedback | received | No ai |
unplaced §Row 32 (comment 22) p.Missing comment restored |
Your comment 8 in the original matrix ("implementation is now fairly top-down / involve the national authorities in imp…Your comment 8 in the original matrix ("implementation is now fairly top-down / involve the national authorities in implementation plan") had not been carried into this consolidated version. It has been added as comment 22. See Q2 above regarding the conflict with row 19. Suggested revision: Added. Resolve alongside Q2. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | all mentions on GitHub record | ||
| PC-0594✎ edit📣 feedback | received | No ai |
unplaced §Column C, rows 11–32 p.Page numbers added |
Page references have been added for every comment, using the document's printed page numbers. Front matter (executive s…Page references have been added for every comment, using the document's printed page numbers. Front matter (executive summary, glossary) is shown as i–iii; the narrative body runs 1–110; Appendix D country examples are 229–235. Suggested revision: Please spot-check the references against the points you intended to make. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | all mentions on GitHub record | ||
| PC-0595✎ edit📣 feedback | received | No ai |
unplaced §Column B, rows 28–31 p.Section numbers may be stale |
Rows 28–29 are tagged section 5 and rows 30–31 section 6, but the document has five chapters only. The country examples…Rows 28–29 are tagged section 5 and rows 30–31 section 6, but the document has five chapters only. The country examples sit in Appendix D and the glossary is front matter, so neither belongs to a numbered section. Suggested revision: Suggest changing these to "Appendix D" and "Front matter" respectively. Not yet changed — confirm and it will be applied. Peter van de Kerkhof, Interational Psoriasis Council, Worldwide |
none | not yet | none | all mentions on GitHub record | ||
| PC-0596✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: From a Philippine perspective, it would benefit from explicitly recognizing countries with decentra…Overall impression: From a Philippine perspective, it would benefit from explicitly recognizing countries with decentralized governance and varying digital maturity across local government units, since implementation and stewardship responsibilities are shared between national and local levels. It would also be useful to emphasize offline and low-bandwidth operation, given connectivity gaps in many areas. Jerico H. Bajador, WHO Philippines, Philippines |
none | not yet | CS-024 discuss | all mentions on GitHub record | |
| PC-0597✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): Yes, broadly.DPI-H components (right set): Yes, broadly. The proposed DPI-H components reflect the core capabilities needed to address the fragmentation that characterizes many health information systems, including those in the Philippines. Shared registries, longitudinal records, interoperability services, and governance mechanisms are appropriate priorities because they enable data reuse, continuity of care, and more efficient investments. However, successful implementation also requires strong institutional capacity and sustainable financing, which should be emphasized alongside the technical components. Jerico H. Bajador, WHO Philippines, Philippines |
none | not yet | CS-024 discuss | all mentions on GitHub record | |
| PC-0598✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Context assumptions: The guidance appears to assume the existence of uniformly strong governance, connectivity, and dig…Context assumptions: The guidance appears to assume the existence of uniformly strong governance, connectivity, and digital capacity. In the Philippine context, the devolved health system and varying levels of readiness among local government units mean that these conditions cannot be taken for granted. The availability of reliable connectivity and nationally adopted digital identity credentials may also be uneven. Jerico H. Bajador, WHO Philippines, Philippines |
none | not yet | CS-024 discuss | all mentions on GitHub record | |
| PC-0599✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: N/A, I have not reviewed the entire draftStrengths: N/A, I have not reviewed the entire draft Jerico H. Bajador, WHO Philippines, Philippines |
none | not yet | none | all mentions on GitHub record | |
| PC-0600✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Concerns / changes: The most important changes would be to explicitly address implementation in decentralized settings,…Concerns / changes: The most important changes would be to explicitly address implementation in decentralized settings, incorporate support for offline and low-bandwidth environments, and provide clearer guidance on capacity building and long-term financing. Jerico H. Bajador, WHO Philippines, Philippines |
none | not yet | CS-024 discuss | all mentions on GitHub record | |
| PC-0601✎ edit📣 feedback | received | general | No ai |
unplaced |
Country / regional examples: Not applicable/not reviewed specificallyCountry / regional examples: Not applicable/not reviewed specifically Jerico H. Bajador, WHO Philippines, Philippines |
none | not yet | none | all mentions on GitHub record | |
| PC-0602✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: There is a need for a multi-vendor and multi-country device interoperability infrastructure that is…Overall impression: There is a need for a multi-vendor and multi-country device interoperability infrastructure that is free of patient identifiable information in remote care. This is completely missing from this document and perpetuates vertically integrated silos for primary IoT data collection. This is a major technical reason why Europe is lagging behind the USA in terms of remote patient monitoring adoption. Such a layer needs to uncouple two highly fragmented and regulated ecosystems: home medtech and health IT. Gilles Lunzenfichter, Medisanté Group AG, Switzerland |
none | not yet | CS-271 discuss | all mentions on GitHub record | |
| PC-0603✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: I am so pleased to see the multi-stated and emphasised need for a true semantic data model as part …Overall impression: I am so pleased to see the multi-stated and emphasised need for a true semantic data model as part of the interoperability framework, while also recognising no such thing exists yet, although open standard syntactic models and vocab models do which are great starting points to build on. BUT, and it's a big but. When I looked for the patient-centred views of the system architecture i found very little evidence, except references to consent management and access rights control, all of which use language that assume a centrally managed method. These are peripheral to an incredibly powerful perspective that this organisation centred view completely ignores. This model assumes an organisation first model for information management. While the data models defined and infrastructure models outlined could be utilised in a patient EMPOWERING way, the underlying theme is of a traditional org first IT style information management model. Patient empowerment in their information management is incredibly powerful as a means to deploy the infrastructure and data models you outline. Yet for a DPI for health, you miss any form of decentralised control model for information sharing, which can and should be an 'and also' mechanism for information flows, especially in countries either with highly decentralised health systems, or those, very common, legacy, highly fragmented care systems at the delivery edge made up of charities, private sector and publicly funded services. The integration and governance burdens for small agile care providers are crushed by this reference architecture you have defined. You have outlined many of the architecture components, it would not take much to give a nod to the need for decentralised models as an integral to this monolithic style organisational first model you have defined. Geoff Revill, Safe Space One Ltd, United Kingdom of Great Britain and Northern Ireland |
none | not yet | CS-043 discuss | all mentions on GitHub record | |
| PC-0604✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Reason for disagreement: You have not clearly identified the need and opportunity for decentralised deployments as part…Reason for disagreement: You have not clearly identified the need and opportunity for decentralised deployments as part of the infrastructure mix, nor have you sufficiently reflected the need for patient empowerment in a next generation health systems architecture, for example for prevention, or self-managed care which are critical components of a broad clinical system architecture. Geoff Revill, Safe Space One Ltd, United Kingdom of Great Britain and Northern Ireland |
none | not yet | CS-043 discuss | all mentions on GitHub record | |
| PC-0605✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): Some of the buildoing blocks are there, but they all assume a organisational information …DPI-H components (right set): Some of the buildoing blocks are there, but they all assume a organisational information empowerment model, with rights access managed centrally, with no nod to the opportunity for patientr empowerment of rights access pro-actively enabled at the healthcare edge. Geoff Revill, Safe Space One Ltd, United Kingdom of Great Britain and Northern Ireland |
none | not yet | CS-043 discuss | all mentions on GitHub record | |
| PC-0606✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Context assumptions: In a care setting, such as Long term Care spanning years across multiple organisations mostly incl…Context assumptions: In a care setting, such as Long term Care spanning years across multiple organisations mostly including care at home, where those organisations are too small/fragmented to understand how to manage their integration suppliers and insufficiently capable on information governance as a core skill (instead emphasising care and clinical skills over digital). Empowering patients through this same architectural semantic model should be covered, especially in the consent management and governance sections. Geoff Revill, Safe Space One Ltd, United Kingdom of Great Britain and Northern Ireland |
none | not yet | CS-043 discuss | all mentions on GitHub record | |
| PC-0607✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: For nation states it helpfully emphasises the critical importance of semantic information exchanges.Strengths: For nation states it helpfully emphasises the critical importance of semantic information exchanges. Geoff Revill, Safe Space One Ltd, United Kingdom of Great Britain and Northern Ireland |
none | not yet | none | all mentions on GitHub record | |
| PC-0608✎ edit📣 feedback | received | general | Metadata registries ai |
unplaced |
Concerns / changes: A rapid shift to build on current open health data standards towards a true semantic model as defin…Concerns / changes: A rapid shift to build on current open health data standards towards a true semantic model as defined in this documentation. Geoff Revill, Safe Space One Ltd, United Kingdom of Great Britain and Northern Ireland |
none | not yet | CS-288 discuss | all mentions on GitHub record | |
| PC-0609✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: The draft is a strong goals-driven enterprise architecture framing for DPI-H, but is not yet operat…Overall impression: The draft is a strong goals-driven enterprise architecture framing for DPI-H, but is not yet operationally complete: securit, consent enforcement remain under-specified for national-scale deployment. Sivanand Lanka, MOSIP, India |
none | not yet | CS-235 discuss | all mentions on GitHub record | |
| PC-0610✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Reason for disagreement: I disagree where the draft asserts implementability without the artefacts national platforms r…Reason for disagreement: I disagree where the draft asserts implementability without the artefacts national platforms require. REDDHI is directionally useful but lacks SLOs, RTO/RPO, and offline/degraded-mode design. The component set omits a first-class Consent Decision capability and under-specifies ABAC/purpose-of-use, claims adjudication, and supply-chain verification. Semantic governance explains LIMR vs Terminology Service well but does not define versioning, deprecation windows, or consumer impact analysis. Conformance/testing is not practical: IHE deferral leaves new DPI-H components without reference test suites or a national/regional conformance authority model. Implementation pathways lack a hard dependency graph, legacy strangler patterns, and an institutional operating model beyond a single National Digital Architect. Financing guidance is conceptually right (recurrent infrastructure) but lacks TCO drivers and procurement gates. Cross-income applicability and country examples are too anecdotal and understate constrained-connectivity, sovereignty, and ops reality. Language is generally clear for architects, but “zero-trust,” “resilient,” and “testable architecture” are over-claimed relative to the technical depth provided. Sivanand Lanka, MOSIP, India |
none | not yet | CS-238 discuss | all mentions on GitHub record | |
| PC-0611✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): Mostly right (registries, LHR, TS, LIMR), but incomplete: add enforceable Consent; claims…DPI-H components (right set): Mostly right (registries, LHR, TS, LIMR), but incomplete: add enforceable Consent; claims adjudication with Benefits Package; product track-and-trace; security/IAM plane beyond RBAC; AI inference controls if AI is in scope. Sivanand Lanka, MOSIP, India |
none | not yet | CS-235 discuss | all mentions on GitHub record | |
| PC-0612✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Context assumptions: Assumes reliable connectivity, mature DPI-F federation, FHIR/terminology capacity, IHE-style testi…Context assumptions: Assumes reliable connectivity, mature DPI-F federation, FHIR/terminology capacity, IHE-style testing, and strong legal consent frameworks—often false in brownfield/LMIC settings. Also underplays offline care, ransomware recovery, licensing/ops cost, and data sovereignty. Sivanand Lanka, MOSIP, India |
none | not yet | CS-238 discuss | all mentions on GitHub record | |
| PC-0613✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: Goals-first method; clear DPI-F vs DPI-H gaps; REDDHI entry concept; LIMR vs TS clarity; interoperability as…Strengths: Goals-first method; clear DPI-F vs DPI-H gaps; REDDHI entry concept; LIMR vs TS clarity; interoperability as a property; builds on OpenHIE/WHO–ITU DHP/DIIG. Sivanand Lanka, MOSIP, India |
none | not yet | none | all mentions on GitHub record | |
| PC-0614✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Concerns / changes: Security & resilience architecture with minimum assurance by data class.Concerns / changes: Security & resilience architecture with minimum assurance by data class. REDDHI SLOs + offline/degraded modes. First-class Consent + ABAC/purpose-of-use. DPI-F↔DPI-H interface contracts. Conformance programme + test kits for new components. Dependency roadmaps, TCO/ops, procurement SLAs. AI control plane. Sivanand Lanka, MOSIP, India |
none | not yet | CS-238 discuss | all mentions on GitHub record | |
| PC-0615✎ edit📣 feedback | received | general | Core architects ai |
D Appendix D: Country and Regional Implementation Examples anchor: medium |
Country / regional examples: Cannot validate here; current examples are too thin and overstate transferability. Strengt…Country / regional examples: Cannot validate here; current examples are too thin and overstate transferability. Strengthen with component mapping, failure modes, cost/governance, and applicability class (high-connectivity vs constrained). Keep tool lists illustrative, not endorsed. Sivanand Lanka, MOSIP, India |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | |
| PC-0616✎ edit📣 feedback | received | general | No ai |
unplaced |
Overall impression: The draft is timely, ambitious and technically strong, providing a much-needed bridge between natio…Overall impression: The draft is timely, ambitious and technically strong, providing a much-needed bridge between national health goals and the shared, governed, standards-based infrastructure needed to achieve them. With progress towards UN SDG 3 remaining uneven, the world needs a globally aligned yet locally adaptable health reference architecture, one capable of enabling truly paperless, person-centred health records and secure semantic interoperability not only between systems, but ultimately across countries. Dr. Padmavathi Roy, United States of America |
none | not yet | none | all mentions on GitHub record | |
| PC-0617✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Reason for disagreement: 1. I disagree Mapping to seven health goals because the the goals-first methodology is a majo…Reason for disagreement: 1. I disagree Mapping to seven health goals because the the goals-first methodology is a major strength, but the detailed mappings referred to in Section 2.4 and Appendix E are not present in the supplied review PDF. Appendix E contains placeholder references rather than the populated goal-to-capability-to-component matrices. This prevents reviewers from verifying traceability and determining whether the mappings are accurate and complete. Please embed the matrices or provide clearly functioning links to the complete mapping artefacts. 2. Country and regional examples - I have selecteds as neither agree or disagree because, the examples are directionally useful but uneven in depth, evidence and precision. A standard case-study format should distinguish strategy, pilot, partial implementation and population-scale operation, and include architecture pattern, governance model, standards used, coverage, measurable outcomes, limitations and dated authoritative sources. The England example should be verified or narrowed, as it may conflate nationally governed medicines terminology with centrally governed pharmaceutical decision-support logic. Dr. Padmavathi Roy, United States of America |
none | not yet | CS-254 discuss | all mentions on GitHub record | |
| PC-0618✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): Overall, I believe the proposed components represent a strong and well-considered foundat…DPI-H components (right set): Overall, I believe the proposed components represent a strong and well-considered foundation for national digital health infrastructure. The core registries, lifelong health record, terminology service and logical information model repository address many of the challenges countries face around fragmented data, inconsistent identification and limited interoperability. I also appreciate that operational systems such as EHRs, claims platforms and supply-chain applications are kept outside the DPI-H boundary while still being able to use the shared infrastructure. There are, however, a few areas that could be clearer. Countries also need an authoritative way to identify healthcare organisations, not only individual workers and physical facilities, including provider groups, payers, laboratories, regulators and other participating institutions. Consent, authorisation, trust, provenance and service-discovery capabilities also need more explicit treatment, particularly where foundational national DPI cannot meet the additional privacy and consent requirements of healthcare. I would also clarify the boundaries of some business-service components. For example, computable clinical knowledge can be governed nationally as a shared asset, while the engine applying that knowledge may operate within local clinical systems. Similarly, HMIS and surveillance capabilities may be delivered through centralised, federated or hybrid arrangements rather than through one national product. Therefore, I see the proposed set as directionally right and a very strong baseline, but not necessarily a fixed or complete list for every country. It would be helpful to classify the components as foundational, context-dependent and advanced, allowing countries to sequence them according to their health priorities, existing infrastructure and level of digital maturity. Dr. Padmavathi Roy, United States of America |
none | not yet | CS-268 discuss | all mentions on GitHub record | |
| PC-0619✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Context assumptions: In large, federated and mixed public–private health systems such as India, the guidance sometimes …Context assumptions: In large, federated and mixed public–private health systems such as India, the guidance sometimes assumes a level of national coordination and institutional authority that may not always exist. Responsibilities are often distributed across national, state and local governments, regulators, private providers and programme agencies. A single national body may therefore find it difficult to designate authoritative registries, enforce common standards or coordinate procurement across the entire ecosystem. The guidance also assumes reasonably mature foundational DPI, legal clarity for health-data sharing, reliable connectivity and digitised source data. In practice, many settings still depend heavily on paper records, have multiple identifiers, experience unreliable connectivity and must provide care to people without formal digital identity. Consent and privacy frameworks may also be evolving or may not yet support granular, cross-organisational exchange. Another assumption is the availability of specialist and financial capacity. Establishing a national digital architect function, FHIR profiles, terminology services, semantic governance and conformance testing requires skills and sustained funding that many countries do not currently have. Some remain dependent on vendors or short-term donor-funded programmes, making long-term national ownership difficult. The guidance would therefore benefit from additional pathways for federated governance, offline-first implementation, interim solutions where foundational DPI is incomplete, regional sharing of specialist services, and a clearly defined minimum viable starting point for countries with limited capacity. Dr. Padmavathi Roy, United States of America |
none | not yet | CS-024 discuss | all mentions on GitHub record | |
| PC-0620✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: To me, the greatest strength of the draft is that it treats digital health as national health-system infrast…Strengths: To me, the greatest strength of the draft is that it treats digital health as national health-system infrastructure rather than as a collection of separate technology projects. Its goals-first approach connects the seven priority health goals to the capabilities, shared components and standards needed to achieve them. This traceability helps countries make investment and procurement decisions based on health outcomes rather than on whichever product or technology is currently available. The distinction between foundational DPI and health-specific DPI is another major strength. The guidance encourages countries to reuse national identity, payment and data-exchange infrastructure where it exists, while recognising that healthcare requires additional capabilities such as clinical identity matching, granular consent, longitudinal records, semantic interoperability and provenance. I also value its practical and adaptable nature. REDDHI provides a direction of travel rather than imposing a rigid compliance model, and the guidance recognises that countries begin from very different levels of maturity. Its advice to assess existing systems, integrate before replacing them and progressively move away from fragmented programme-specific solutions is realistic and valuable. Finally, the draft brings architecture, governance, interoperability, equity, financing and AI readiness into one coherent framework. Treating interoperability as a cross-cutting capability, emphasising governed terminology and information models, and connecting FHIR and IHE standards with conformance testing are particularly strong. Its message that trustworthy AI depends on trusted, representative and well-governed data foundations is both timely and essential. Overall, the draft provides a strong basis for a globally aligned yet locally adaptable reference architecture that can support progress towards SDG 3 and, over time, secure interoperability across organisations and countries. Dr. Padmavathi Roy, United States of America |
none | not yet | none | all mentions on GitHub record | |
| PC-0621✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Concerns / changes: My main concern is the gap between the strength of the conceptual architecture and the level of ope…Concerns / changes: My main concern is the gap between the strength of the conceptual architecture and the level of operational detail needed for countries to implement it. The draft explains the intended direction very well, but some essential implementation artefacts are still missing. In particular, Appendix E contains placeholders rather than the complete goal-to-capability-to-component mappings. These mappings should be included so that reviewers and countries can verify traceability, completeness and architectural gaps. I would also like to see a clearer minimum viable architecture and maturity model. Countries need to understand which components are foundational, which are context-dependent and which are more advanced, together with measurable readiness criteria and decision points for progressing between stages. Additional implementation pathways are needed for federated systems, fragile or resource-constrained settings, incomplete foundational DPI, unreliable connectivity and significant dependence on paper records or donor-funded systems. Some component boundaries also need clarification. The architecture should explicitly address a health-organisation and ecosystem-participant registry, as facilities, individual professionals and the legal organisations operating them are different entities. Consent, authorisation, trust, provenance and service-discovery capabilities also need clearer representation, particularly where foundational DPI does not provide the granularity required for healthcare. The distinction between nationally governed computable clinical knowledge and locally executed decision-support engines should also be strengthened. The conformance section is conceptually strong, but countries will need reusable implementation profiles, test cases, reference datasets, certification governance and continuous testing requirements covering security, privacy, performance and version changes. A system implementing an accepted standard should not be assumed to “arrive tested.” Finally, the financing section would benefit from a practical investment-case template covering total cost of ownership, recurrent expenditure, measurable benefits, risk, cost-sharing and transition from donor to domestic financing. Country examples should also use a consistent, evidence-based format that distinguishes pilots from population-scale implementation and records both achievements and limitations. These changes would preserve the draft’s strong global vision while making it more actionable, measurable and realistic across different national contexts. Dr. Padmavathi Roy, United States of America |
none | not yet | CS-246 discuss | all mentions on GitHub record | |
| PC-0622✎ edit📣 feedback | received | general | Core architects ai |
D.2 Country implementation examples |
Country / regional examples: Overall, the country and regional examples are valuable, but I do not think all of them ar…Country / regional examples: Overall, the country and regional examples are valuable, but I do not think all of them are sufficiently precise or evidenced in their present form. The draft sometimes describes a national strategy, partial rollout or collection of separate systems as though it were already a fully integrated, nationwide capability. Each example should clearly state its implementation status, coverage and date of verification. The most important issues I identified are: 1. England:This example appears materially overstated. England centrally governs SNOMED CT UK and the dictionary of medicines and devices (dm+d), but this is not the same as centrally providing pharmaceutical decision support, including interaction checking, allergy alerts and dosage guidance, across primary and hospital care. NHS England explicitly states that dm+d does not provide decision-support functionality. It supplies terminology and information that other systems may use. NHS guidance also indicates that clinical-system configurations can differ locally. The example should therefore distinguish national terminology governance from decision-support functions implemented by vendors and individual care organisations. [NHS England: dm+d](https://digital.nhs.uk/services/terminology-and-classifications/dm-d) 2. India: The description of ABDM as a federated, consent-based architecture anchored on ABHA is accurate. However, the text should not imply universal implementation. The National Health Authority confirms that participation by citizens, healthcare facilities and private providers is voluntary. Likewise, official IDSP figures for 2025–26 show reporting rates of approximately 78–83%, depending on the surveillance form, not complete reporting by every unit. India should therefore be presented as a national architecture with substantial but still uneven adoption, especially across private providers and states. [ABDM FAQ](https://abdm.gov.in/FAQ) and [NCDC/IDSP implementation figures](https://ncdc.mohfw.gov.in/includes/About/CentresAndDivision/IDSP.php) 3. Kenya: The national HIE direction is correct, but its rollout status should be stated. An official Ministry of Health update reported that the Comprehensive Integrated Health Information System was operational in 17 counties in 2025, with expansion continuing. “A national HIE under phased implementation” would be more accurate than language suggesting complete national consolidation. [Kenya Ministry of Health](https://www.health.go.ke/government-scales-digital-health-reform-drive-accountability-and-efficiency) 4. Rwanda: The HMIS is a strong example, but the claims combine several capabilities that should be evidenced separately. WHO reported completeness and timeliness above 90% for public facilities in 2019, while only about 70% of private facilities were then reporting. The statement should not present the high rate as applying uniformly to the entire health sector. The claims concerning an OpenHIE-aligned longitudinal record, national decision support, laboratory integration and performance-based financing also need specific, current references. Rwanda’s newer National Health Intelligence Center demonstrates integration of multiple data streams, but this is not automatically equivalent to a complete national longitudinal-record exchange. The Spain, Catalonia and Tanzania examples are directionally accurate but need qualification. Spain’s HCDSNS exchanges selected clinical documents rather than providing a complete national health record. Catalonia’s HC3 and climate-health surveillance are valid examples, but access to social-care information should not be described as complete integration without current coverage evidence. Tanzania operates a national DHIS2-based HMIS, but describing it as “one of the more mature” systems is subjective and should be supported by current figures on coverage, completeness and timeliness. Dr. Padmavathi Roy, United States of America |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | |
| PC-0623✎ edit📣 feedback | received | Core architects ai |
D Appendix D: Country and Regional Implementation Examples §Appendix D.2–D.3: Country, Regional and Multi-country Implementation Examples l.94–101, 120–150, 154–194 and 213–219 anchor: medium |
The examples are valuable and mostly directionally accurate, but some describe national strategies, partial rollouts or…The examples are valuable and mostly directionally accurate, but some describe national strategies, partial rollouts or separate systems as fully integrated nationwide capabilities. Spain’s HCDSNS exchanges selected clinical documents rather than a complete record; India’s ABDM and Kenya’s HIE have uneven or phased adoption; Rwanda, Uganda, Catalonia and Tanzania require clearer evidence of coverage and integration; and Tanzania’s description as “one of the more mature” systems is subjective. The England example appears to conflate centrally governed terminology with centrally delivered pharmaceutical decision support. The WHO SMART pilot claims also require country-, use-case- and scale-specific evidence. Suggested revision: For every example, state whether it is operational nationwide, operational with partial coverage, a pilot or planned, together with a last-verified date and an authoritative country source. Revise Spain to “federated exchange of selected clinical documents”; describe England as centrally governing SNOMED CT UK and dm+d, which support locally or vendor-implemented decision support; qualify phased or uneven adoption in India, Kenya, Rwanda, Uganda, Catalonia and Tanzania; and either provide evidence for the claimed WHO SMART pilot outcomes and reduced time and cost or remove those claims. Dr. Padmavathi Roy, United States of America |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-0624✎ edit📣 feedback | received | Metadata registries ai |
D Appendix D: Country and Regional Implementation Examples §Appendix D.2: United Kingdom (England) l.186–194 anchor: medium |
The statement that England centrally governs and provides pharmaceutical decision support, including interaction checki…The statement that England centrally governs and provides pharmaceutical decision support, including interaction checking, allergy alerts and dosage guidance, appears inaccurate as written. England centrally maintains SNOMED CT UK and dm+d, but NHS England explicitly states that dm+d does not provide decision-support functionality. Such functionality is generally implemented and configured within local or vendor-supplied clinical systems. Suggested revision: You may replace with - “England centrally governs national clinical terminologies, including SNOMED CT UK and the dictionary of medicines and devices (dm+d). These standards support consistent medicines-data exchange and can be used by local and vendor-supplied prescribing systems to implement decision-support functions.” A centrally delivered national pharmaceutical decision-support service should not be implied unless a specific authoritative source is provided. Dr. Padmavathi Roy, United States of America |
none | not yet | CS-214 discuss | in the document all mentions on GitHub record | ||
| PC-0625✎ edit📣 feedback | received | WHO ai |
D Appendix D: Country and Regional Implementation Examples §Appendix D.3: WHO SMART Guidelines Pilot Implementations l.213–219 anchor: medium |
The draft does not provide sources establishing that Ethiopia, the Philippines and Uganda have each deployed L3 computa…The draft does not provide sources establishing that Ethiopia, the Philippines and Uganda have each deployed L3 computable logic within national health information systems for the stated clinical areas. It also does not provide evaluation evidence supporting the conclusion that these pilots reduced the time and cost of adapting international guidance. Adaptation of an L2 Digital Adaptation Kit, an L3 technical pilot and operational national deployment are different stages and should not be presented as equivalent. Suggested revision: For each country you may want to, identify the clinical domain, SMART knowledge layer, implementation stage, scale, date and authoritative source. Unless evaluated results are available, replace the final sentence with - “These initiatives are exploring how internationally developed computable guidance can be adapted and tested within national digital health environments.” Remove or qualify the claim concerning reduced time and cost. Dr. Padmavathi Roy, United States of America |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-0626✎ edit📣 feedback | received | general | No ai |
unplaced |
Overall impression: Hugely overrated and unnecessaryOverall impression: Hugely overrated and unnecessary None, United Kingdom of Great Britain and Northern Ireland |
none | not yet | none | all mentions on GitHub record | |
| PC-0627✎ edit📣 feedback | received | general | No ai |
unplaced |
Reason for disagreement: This is an unnecessary intrusion into personal life. Its aim is to tie humanity down for the r…Reason for disagreement: This is an unnecessary intrusion into personal life. Its aim is to tie humanity down for the reasons that are falsely stated and ultimately for the benefits of the funders. We are born of their place with a divine spark at the zygote and money has traded that away for a dark demise and a hidden post human future. The, crestion will not look down well on those who try to build systems that deny freedoms and trap thevinaware souls into slavery. Which is ultimately what this whole document is about. None, United Kingdom of Great Britain and Northern Ireland |
none | not yet | none | all mentions on GitHub record | |
| PC-0628✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: Its a Trojan horse designed to remove personal freedomsStrengths: Its a Trojan horse designed to remove personal freedoms None, United Kingdom of Great Britain and Northern Ireland |
none | not yet | none | all mentions on GitHub record | |
| PC-0629✎ edit📣 feedback | received | general | No ai |
unplaced |
Concerns / changes: I would like to see individuality and freedom of choice along with privacy give back to the divine …Concerns / changes: I would like to see individuality and freedom of choice along with privacy give back to the divine life on the realm. Where it belongs not in the hands of anonymous reptiles. None, United Kingdom of Great Britain and Northern Ireland |
none | not yet | none | all mentions on GitHub record | |
| PC-0630✎ edit📣 feedback | received | No ai |
unplaced §NA l.NA |
NANA Suggested revision: NA None, United Kingdom of Great Britain and Northern Ireland |
none | not yet | none | all mentions on GitHub record | ||
| PC-0631✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: The guidance overstates the role of central architecture in driving digital transformation, whereas…Overall impression: The guidance overstates the role of central architecture in driving digital transformation, whereas experience in health systems suggests that successful capabilities more often emerge through local implementation and are standardised after demonstrating value. This risks encouraging investment in architecture and governance exercises that produce either generic strategic statements or burdensome compliance specifications, at the expense of funding practical implementations that generate evidence, adoption and learning. Joern Guy Suess, CSIRO, Australia |
none | not yet | CS-245 discuss | all mentions on GitHub record | |
| PC-0632✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Reason for disagreement: The document is focussed on high-level concepts and does not underline that a) interoperabilit…Reason for disagreement: The document is focussed on high-level concepts and does not underline that a) interoperability is an arising property of local implementations and b) concrete testing and implementation examples are not a procedural afterthought, but the starting point of developing digital infrastructure, and finally c) the homogenisation process that leads to bottom-up interoperability is missing entirely, as the assumption is for a top-down process in the first place. Joern Guy Suess, CSIRO, Australia |
none | not yet | CS-245 discuss | all mentions on GitHub record | |
| PC-0633✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): I would agree that ultimately one would aim to arrive at this set of components. However,…DPI-H components (right set): I would agree that ultimately one would aim to arrive at this set of components. However, as stated earlier, even such higher-level facilities are likely to go through generations and revisions, forced by usage pressures. Building such facilities green fields seems to entail significant risk. It is probably better to elevate well-working local implementations to a national level, rather that starting with the assumption that a component 'be built and they will come'. Joern Guy Suess, CSIRO, Australia |
none | not yet | CS-245 discuss | all mentions on GitHub record | |
| PC-0634✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Context assumptions: Testing with near-real synthetic data and workflows is completely underrepresented. The focus on w…Context assumptions: Testing with near-real synthetic data and workflows is completely underrepresented. The focus on workflows, which are the essential element of treatment is weak or missing. Joern Guy Suess, CSIRO, Australia |
none | not yet | CS-085 discuss | all mentions on GitHub record | |
| PC-0635✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: Raises awareness of FHIR and interoperability as the essential reusable element of national DPI-H.Strengths: Raises awareness of FHIR and interoperability as the essential reusable element of national DPI-H. Joern Guy Suess, CSIRO, Australia |
none | not yet | none | all mentions on GitHub record | |
| PC-0636✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Concerns / changes: The document needs a reality-check based on actual project experience. I assume that this will find…Concerns / changes: The document needs a reality-check based on actual project experience. I assume that this will find that practical, emerging engineering work outperforms top-down architecture. Based on that, the document should be designed to emphasize methods of supporting local implementations to merge on the national level to form DPI-H as an outcome. Joern Guy Suess, CSIRO, Australia |
none | not yet | CS-245 discuss | all mentions on GitHub record | |
| PC-0637✎ edit📣 feedback | received | general | No ai |
unplaced |
Country / regional examples: yes, as far as I can tell.Country / regional examples: yes, as far as I can tell. Joern Guy Suess, CSIRO, Australia |
none | not yet | none | all mentions on GitHub record | |
| PC-0638✎ edit📣 feedback | received | Core architects ai |
4.2 Charting a Path to REDDHI §4.2 Charting a Path (or equivalent implementation guidance section) l.Relevant paragraphs describing implementation pathways and architecture adoption anchor: medium |
The guidance places strong emphasis on centrally planned architecture and governance as the primary driver of digital t…The guidance places strong emphasis on centrally planned architecture and governance as the primary driver of digital transformation. In practice, many successful digital health capabilities emerge through locally implemented solutions that are subsequently standardised and scaled once value has been demonstrated. Suggested revision: Add an explicit implementation-led pathway that recognises local innovation, pilot deployments and operational validation as legitimate entry points for DPI-H adoption. The reference architecture should position itself as a framework for documenting, assessing and scaling proven implementations, rather than implying that transformation must begin with central architectural design. Joern Guy Suess, CSIRO, Australia |
none | not yet | CS-245 discuss | in the document all mentions on GitHub record | ||
| PC-0639✎ edit📣 feedback | received | general | No ai |
unplaced |
Overall impression: It is an important milestone in architectural approaches to information systems development. This w…Overall impression: It is an important milestone in architectural approaches to information systems development. This was a missing canonical piece that was necessary for WHO to propagate the enterprise continuum framework of TOGAF. Without this, countries will have to create and define their own architectures out of necessity. WHO and ITU would've missed out on a great opportunity to share artifacts to the regions and the countries. Alvin Valeriano de Borja Marcelo, Asia eHealth Information Network Community of Interoperability Labs, Philippines |
none | not yet | none | all mentions on GitHub record | |
| PC-0640✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): Right set, yes, but it is not yet in complete form for use in regions and countries. Ther…DPI-H components (right set): Right set, yes, but it is not yet in complete form for use in regions and countries. There is a gap between global (this document) and regional/national implementations. Alvin Valeriano de Borja Marcelo, Asia eHealth Information Network Community of Interoperability Labs, Philippines |
none | not yet | CS-262 discuss | all mentions on GitHub record | |
| PC-0641✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Context assumptions: Gap 1: No regional interpretation layer.Context assumptions: Gap 1: No regional interpretation layer. Countries are left to independently interpret the WHO–ITU DPI-H Reference Architecture with no shared regional profile, resulting in duplicated interpretation effort and divergent architectural choices across otherwise similar health systems. Gap 2: The WPRO RAF domains, while significant, still lack a technical execution arm. The WPRO Regional Action Framework's socio-technical infrastructure and digital health solutions domains describe *what* countries should achieve but not the shared technical mechanism for *how* — a role AP-COIL's member labs, tooling, and testing mandate is designed to fill. Gap 3: Countries will start creating reference implementations, but without coordination, these will not be interoperable with each other. Unless organized through a transparent, regional networking approach, country-level work (such as the proposed Philippines' reference implementation on Open Health Stack – see Annex) risks remaining a single-country artifact instead of a reusable regional pattern other countries can adapt. Gap 4: No feedback loop upward/region-ward. Country and regional implementation lessons rarely reach WHO/ITU or the emerging global open-source foundations (e.g., Open Health Stack Software Foundation) in a structured way. Alvin Valeriano de Borja Marcelo, Asia eHealth Information Network Community of Interoperability Labs, Philippines |
none | not yet | CS-262 discuss | all mentions on GitHub record | |
| PC-0642✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: Thank you for publishing a landmark document on a global digital health architecture built on digital public…Strengths: Thank you for publishing a landmark document on a global digital health architecture built on digital public infrastructure (DPI-H). The Asia eHealth Information Network (AeHIN), created by the World Health Organization in 2012, has long espoused the Mind/Fill the GAPS framework, in which “Architecture” is a key component. Our comments and suggestions are as follows: Observation 1. The WHO–ITU Reference Architecture Guidance for Digital Public Infrastructure for Health (DPI-H) gives countries advice on the TOGAF/ArchiMate-based enterprise architecture framework — organized around seven priority health goals and the REDDHI (Resilient Essential Data and Digital Health Infrastructure) concept — for moving from strategic intent to coherent technical implementation. It is explicitly designed as a technology-neutral blueprint that individual countries adapt to their own context, not a single deployable system. The work is comprehensive and solid. Observation 2. A regional framework already exists to receive it. The Regional Action Framework on Digital Health in the Western Pacific, endorsed by Member States at the 75th WHO Regional Committee for the Western Pacific (2024), organizes country actions around five domains — governance, socio-technical infrastructure, financing and economics, digital health solutions, and data — guided by principles of equity, open innovation, accountability, pragmatism, and sustainability. Member-state consultations during its formulation repeatedly surfaced standards and interoperability (the S in GAPS) and governance and leadership (the G in GAPS) as the priorities countries most need help operationalizing. Alvin Valeriano de Borja Marcelo, Asia eHealth Information Network Community of Interoperability Labs, Philippines |
none | not yet | none | all mentions on GitHub record | |
| PC-0643✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Concerns / changes: Summary Action: Build a community of practice around the Reference ArchitectureConcerns / changes: Summary Action: Build a community of practice around the Reference Architecture To fill these translation gaps, the Asia eHealth Information Network, together with the Pacific Health Information Network, jointly announce the creation of the Asia-Pacific COIL (AP-COIL). The goals of AP-COIL are: 1. Rapid, systematic, structured dissemination of the WHO-ITU Reference Architecture. AeHIN and PHIN will host webinars and feature resource persons from WHO-ITU as speakers. The regional networks will pull in the right audience in each region and country. 2. Formalizing the Asia-Pacific Community of Interoperability Labs (AP-COIL) as a community of practice aligning the global, regional, and national reference architectures. WPRO/SEARO regional experts will be invited to provide guidance and oversight. 3. Empowering the AP-COIL to craft the regional implementation guides along with a regional reference implementation on Open Health Stack (tbc). This regional effort can begin from the best practices and lessons learned from the International Patient Summary for the Hajj as a use case. 4. Committing the AP-COIL members to continuously connect their country's efforts to the regional interoperability blueprint and ensure alignment through continuous knowledge sharing. Attached as Part 2 are the AP-COIL Concept Note (Part 2) and the proposal for a Philippine-specific reference implementation using OpenHealthStack (annex). Both are needed to show alignment of the WHO-ITU Reference Architecture for Digital Public Infrastructure with the WPRO/SEARO Regional Action Frameworks and a national digital health strategy. Alvin Valeriano de Borja Marcelo, Asia eHealth Information Network Community of Interoperability Labs, Philippines |
none | not yet | CS-262 discuss | all mentions on GitHub record | |
| PC-0644✎ edit📣 feedback | received | general | Core architects ai |
D.3 Regional and multi-country examples anchor: medium |
Country / regional examples: No inaccuracies noted. Observation: No mention was made of regional networks such as Asia …Country / regional examples: No inaccuracies noted. Observation: No mention was made of regional networks such as Asia eHealth Information Network and multilaterals such as ASEAN and SPC, all of which enrich the experience of their member countries and can serve as effective vehicles for collaboration and knowledge sharing. Not mentioning these regional networks and their role in strengthening standards adoption as a group will be a big missed opportunity. Alvin Valeriano de Borja Marcelo, Asia eHealth Information Network Community of Interoperability Labs, Philippines |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | |
| PC-0645✎ edit📣 feedback | received | Core architects ai |
3.4.3 Strategic governance §3.4.3 Strategic governance l.319 anchor: medium |
Mention the regional networksMention the regional networks Suggested revision: "and engage proactively with national health financing mechanisms, 319 development partners, multilateral institutions, and regional networks (such as AeHIN, PHIN, RECAINSA, HELINA)." Alvin Valeriano de Borja Marcelo, Asia eHealth Information Network Community of Interoperability Labs, Philippines |
none | not yet | CS-113 discuss | in the document all mentions on GitHub record | ||
| PC-0646✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: The draft is technically thorough and well-structured, covering the architecture landscape comprehe…Overall impression: The draft is technically thorough and well-structured, covering the architecture landscape comprehensively. However, it reads primarily from the perspective of national governments and large institutions, and would benefit from stronger guidance on how the architecture applies at the last mile, where community health workers, offline environments, and resource-constrained field operations are the reality for the majority of the populations this infrastructure is meant to serve. Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | CS-239 discuss | all mentions on GitHub record | |
| PC-0647✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): The core components are well chosen and reflect the building blocks that national digital…DPI-H components (right set): The core components are well chosen and reflect the building blocks that national digital health systems genuinely need. From practical experience deploying community health registry infrastructure in Kenya and Zambia, the Client Registry, Health Facility Registry, Health Management Information System, and Public Health Surveillance Platform are the components that matter most at the point of delivery. The inclusion of the Lifelong Health Record is aspirationally important but may be premature as a priority component for low-income settings where foundational data capture is still inconsistent. The guidance would benefit from being more explicit about which components represent a minimum viable starting point versus longer-term goals, so that countries with limited resources can sequence implementation realistically rather than feeling they must address everything at once. Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | CS-246 discuss | all mentions on GitHub record | |
| PC-0648✎ edit📣 feedback | received | general | No ai |
unplaced |
Context assumptions: NowhereContext assumptions: Nowhere Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | none | all mentions on GitHub record | |
| PC-0649✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: The REDDHI concept is the strongest contribution in the document. Framing resilience and essential data infr…Strengths: The REDDHI concept is the strongest contribution in the document. Framing resilience and essential data infrastructure as a foundational baseline rather than an aspirational goal is exactly the right approach for low and middle income settings, and naming it clearly gives countries and development partners a shared reference point for investment conversations. The mapping of health goals to architecture components is also genuinely useful — it connects technical design decisions to health outcomes in a way that non-technical stakeholders including ministries and donors can engage with. The governance section is more thorough than most comparable guidance documents and reflects hard-won lessons from real implementations. Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | none | all mentions on GitHub record | |
| PC-0650✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Concerns / changes: The guidance underserves the last-mile implementation context. Community health workers are the pri…Concerns / changes: The guidance underserves the last-mile implementation context. Community health workers are the primary point of contact for the majority of people that DPI-H is intended to reach, yet the architecture is largely described from the perspective of facility-based systems and national platforms. Offline-first data synchronization, which is essential in low-connectivity field environments, receives minimal treatment. From direct experience managing data synchronization across 250,000 household records in rural field conditions, the failure modes that matter most that is partial sync conflicts, device-level data loss, bandwidth-constrained record capture are not addressed in the current draft. The guidance would be significantly stronger with a dedicated section on last-mile architecture considerations, covering offline-capable data collection, CHW-facing application requirements, and how community-level data flows connect to national registries. Tools like KoboToolbox, ODK, and CommCare are widely used across Sub-Saharan Africa for exactly this purpose but are not meaningfully referenced in the implementation guidance. Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | CS-239 discuss | all mentions on GitHub record | |
| PC-0651✎ edit📣 feedback | received | general | Core architects ai |
Kenya |
Country / regional examples: The Kenya example is broadly accurate in describing the direction of national digital heal…Country / regional examples: The Kenya example is broadly accurate in describing the direction of national digital health investment but does not reflect the significant implementation gaps that exist between national policy and ground-level delivery. Kenya's community health information system has faced persistent challenges with data quality, device management, and last-mile connectivity that are not captured in the example. Acknowledging these gaps alongside the achievements would make the examples more useful as honest reference points for other countries at similar stages, rather than presenting an overly optimistic picture that may not reflect what implementers will actually encounter. Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | CS-208 discuss | in the document all mentions on GitHub record | |
| PC-0652✎ edit📣 feedback | received | Core architects ai |
2.2 Resilient Essential Data and Digital Health Infrastructure (REDDHI) §2.2 anchor: medium |
The REDDHI framework does not adequately address offline-first data synchronization requirements. In low-connectivity f…The REDDHI framework does not adequately address offline-first data synchronization requirements. In low-connectivity field environments across Sub-Saharan Africa, data collection cannot depend on live connectivity. CHW-facing applications must be able to capture and store data locally and sync reliably to national registries when connectivity is restored. This failure mode is one of the most common causes of data loss and integrity issues in real deployments. Suggested revision: Add a dedicated subsection within REDDHI on offline-first architecture requirements, specifying minimum offline capability standards for field-facing applications and describing acceptable synchronization approaches for low-bandwidth environments. Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | ||
| PC-0653✎ edit📣 feedback | received | Core architects ai |
3.5 DPI-H Application Components §3.5 anchor: medium |
The component descriptions focus on facility-based and national platform levels. Community health worker workflows, whi…The component descriptions focus on facility-based and national platform levels. Community health worker workflows, which represent the primary data collection and service delivery point for the majority of populations DPI-H is intended to reach, are not addressed as a distinct architecture concern. In Kenya and Zambia, CHW-facing applications are where most household and community-level health data originates, yet there is no component or interface description that covers this layer. Suggested revision: Recognize CHW-facing application requirements as a distinct architecture concern, either as a component or as a defined interface layer, with guidance on how community-level data flows connect to the foundational shared data layer. Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | CS-025 discuss | in the document all mentions on GitHub record | ||
| PC-0654✎ edit📣 feedback | received | Core architects ai |
4.3 Profiles and Specifications for Implementation §4.3 anchor: medium |
The implementation chapter does not reference widely deployed open source tools such as KoboToolbox, ODK, CommCare, and…The implementation chapter does not reference widely deployed open source tools such as KoboToolbox, ODK, CommCare, and OpenSRP that are already in active use across Sub-Saharan Africa. Countries implementing DPI-H will frequently be building on or integrating with these existing tools rather than starting from scratch. The absence of any mapping between these tools and the architecture components leaves a significant practical gap. Suggested revision: Add a mapping or reference table in the implementation chapter that identifies commonly used open source and global good tools alongside the DPI-H components they fulfil, helping countries assess what they already have and what gaps remain. Mercy Chepngeno, GeoApnet, Kenya |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-0655✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: The draft provides a strong, coherent and practical reference architecture that successfully connec…Overall impression: The draft provides a strong, coherent and practical reference architecture that successfully connects health-system goals with shared digital capabilities, interoperability, governance and implementation pathways across different levels of country maturity. Its main opportunity for improvement is to make several cross-cutting requirements more architecturally explicit, particularly consent and permissions management, AI/ML lifecycle governance, longitudinal data lifecycle management and safe synchronisation across federated or offline environments. Ruslan Kurmashev, Independent Researcher, Ireland |
none | not yet | CS-235 discuss | all mentions on GitHub record | |
| PC-0656✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): Broadly, yes. The proposed components represent a coherent and useful core set for nation…DPI-H components (right set): Broadly, yes. The proposed components represent a coherent and useful core set for national digital health infrastructure, particularly the Client, Facility, Workforce and Product Registries, the Lifelong Health Record, Terminology Service, Logical Information Model Repository, Computable Decision Support Engine, HMIS and Public Health Surveillance Platform. I particularly support the distinction between shared foundational components and reusable business-service components, rather than treating programme-specific applications as DPI-H. My main reservation is not that major components are missing, but that several cross-cutting capabilities need more explicit architectural treatment. Consent and permissions management is described as a foundational REDDHI capability and is required by the Lifelong Health Record, but it is not articulated with the same level of interface and lifecycle detail as the named components. Similarly, learned AI/ML models may be deployed across several components or point-of-service systems, but the architecture would benefit from a cross-cutting lifecycle profile covering model identity, versioning, validation, monitoring and accountability. I would therefore retain the proposed component set while strengthening these cross-cutting service profiles rather than necessarily adding new centralised components. Ruslan Kurmashev, Independent Researcher, Ireland |
none | not yet | CS-235 discuss | all mentions on GitHub record | |
| PC-0657✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Context assumptions: The guidance is generally strong in recognising different levels of digital maturity, resource ava…Context assumptions: The guidance is generally strong in recognising different levels of digital maturity, resource availability and connectivity, so I do not see a major assumption that all countries start from similar conditions. However, implementation may still implicitly depend on institutional capacities that are uneven across settings: sustained governance of shared national components, clear assignment of data stewardship and decision rights, technical capacity to maintain standards and information models over time, and the ability to enforce consistent access and consent policies across fragmented or federated systems. In lower-capacity settings, reliable connectivity, mature national identity infrastructure, specialist interoperability expertise and long-term financing may also be incomplete or unstable. I therefore suggest distinguishing more explicitly between capabilities that may mature progressively and minimum non-negotiable properties-particularly security, auditability, provenance and safe handling of conflicting data-that should remain required even at early stages of implementation. Offline and federated environments deserve particular attention: "reliable synchronisation" is necessary, but clinically significant conflicting updates need explicit minimum conflict-resolution and reconciliation rules. Ruslan Kurmashev, Independent Researcher, Ireland |
none | not yet | CS-239 discuss | all mentions on GitHub record | |
| PC-0658✎ edit📣 feedback | received | general | No ai |
unplaced |
Strengths: The greatest strength is that the guidance treats digital health infrastructure as shared national capabilit…Strengths: The greatest strength is that the guidance treats digital health infrastructure as shared national capability rather than as a collection of disease-specific or programme-specific systems. This directly addresses fragmentation, duplicated investment and vendor dependency. A second major strength is the clear distinction between foundational DPI and health-specific DPI-H, allowing health systems to build on national identity, payment and data-exchange infrastructure without assuming that general-purpose DPI can meet all health-sector requirements. Third, interoperability is treated correctly as a cross-cutting architectural property rather than as a single middleware product. The combination of open standards, semantic governance, terminology services, common information models and conformance testing gives the architecture substantially more implementation value than a high-level policy framework alone. Finally, REDDHI is a useful concept because it provides countries with a direction of travel and a minimum foundation without presenting the architecture as a single fixed end-state. The emphasis on different starting points, progressive implementation and national adaptation makes the guidance relevant across different levels of digital maturity. Ruslan Kurmashev, Independent Researcher, Ireland |
none | not yet | none | all mentions on GitHub record | |
| PC-0659✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Concerns / changes: My main concerns are not with the overall architecture, but with several cross-cutting requirements…Concerns / changes: My main concerns are not with the overall architecture, but with several cross-cutting requirements that would benefit from more explicit and testable specification. 1. Consent and permissions architecture. Consent and authorisation are treated as foundational capabilities, and the Lifelong Health Record depends on consent-management services, but the architecture does not provide an equivalent cross-cutting service profile defining consent representation, lifecycle, interfaces, revocation propagation, delegated/proxy authority and audit. 2. AI/ML lifecycle governance. Chapter 5 provides strong principles for responsible AI, including evaluation, equity, human oversight and monitoring for drift. However, learned models used across decision support, analytics, surveillance or point-of-service applications should be traceable to a unique model/version, accountable owner, intended use, validation evidence, deployment status and monitoring state. 3. Longitudinal record lifecycle. The LHR appropriately emphasises immutable history and provenance, but the requirement that records should “never be deleted” should be reconciled more explicitly with correction of wrong-person attribution, logical withdrawal and legally required erasure. 4. Offline and federated consistency. The guidance supports offline operation and federated architectures, but minimum semantics for conflicting concurrent updates should be clearer. Clinically material conflicts should not be silently overwritten or presented as a single authoritative fact before reconciliation. 5. Minimum security floor. Graduated assurance is appropriate for countries with different levels of maturity, but essential security properties-authentication, authorisation, least privilege, confidentiality, auditability, integrity and recovery-should remain explicit minimum requirements even where more advanced assurance mechanisms are introduced progressively. Addressing these issues would make the architecture more implementable and testable without making it more prescriptive about specific technologies. Ruslan Kurmashev, Independent Researcher, Ireland |
none | not yet | CS-235 discuss | all mentions on GitHub record | |
| PC-0660✎ edit📣 feedback | received | general | No ai |
unplaced |
Country / regional examples: I did not review the country and regional implementation examples in sufficient depth to i…Country / regional examples: I did not review the country and regional implementation examples in sufficient depth to independently verify their accuracy, so I do not want to flag any potential inaccuracies without appropriate source verification. Ruslan Kurmashev, Independent Researcher, Ireland |
none | not yet | none | all mentions on GitHub record | |
| PC-0661✎ edit📣 feedback | received | Core architects ai |
Executive Summary §Executive Summaruy l.12 |
Add at the end of the paragraph "Given the existing fragmentation in the HIS, DPI-H also provides the means to integrat…Add at the end of the paragraph "Given the existing fragmentation in the HIS, DPI-H also provides the means to integrate information across existing disconnected components of the HIS." Martin Bratschi, Vital Strategies, Switzerland |
none | not yet | CS-002 discuss | in the document all mentions on GitHub record | ||
| PC-0662✎ edit📣 feedback | received | Core architects ai |
1.2 Why health needs more than foundational DPI §1.2 l.starting from 172 anchor: medium |
I think Section 1.2 makes a strong (too strong?) case on why the health sector needs more than foundational DPI - and I…I think Section 1.2 makes a strong (too strong?) case on why the health sector needs more than foundational DPI - and I agree that the health sector has special needs. However, i think this section neglects how the health sector can benefit even from partial foundational DPI. As far as I see, foundational DPI are being built very rapidly (i would rephrase "DPIs do not yet exist" on line 192 - i think this is increasingly not true (https://dpimap.org/)). For the ID function of the foundational DPI, the national ID number should be used as / linked to the health identifier when available; for patients that don't have a national ID number they can get a health-only number. You say this at the end of Box 1.2, but i think this point (i.e., health should use foundational DPI to the maximum potential and utility for the health sector) should be highlighted further / more prominent. As an additional specific comment, i don't think that Line198 is what the foundational ID layer of DPI is trying to do - health specific data should stay in the health sector and not be in the foundational DPI. Suggested revision: Add a paragraph on page 13 (before 1.2.1) to indicate how the health sector should use foundational DPI to the maximum potential and utility for the health sector. For each of sections 1.2.1, 1.2.2 and 1.2.3 add to the current text (which currently just stresses how health needs extra) a paragraph to say how the health sector can use the foundational DPI to its maximum potential and utility. Martin Bratschi, Vital Strategies, Switzerland |
none | not yet | CS-011 discuss | in the document all mentions on GitHub record | ||
| PC-0663✎ edit📣 feedback | received | general | No ai |
unplaced |
Overall impression: This guidance provides a comprehensive overview of the desirable form of digital infrastructure in …Overall impression: This guidance provides a comprehensive overview of the desirable form of digital infrastructure in the health sector, covering such perspectives as common data platforms, standardization, interoperability among systems, and governance. In particular, the concepts for the efficient and secure sharing and use of health information, as well as the direction of data linkage through the use of common platforms, provide useful reference points for advancing digital transformation in the health sector. The guidance also highlights the importance of taking information security and the protection of personal information into account from the planning and design stages of health information systems. Going forward, it is hoped that further knowledge and experience will be accumulated regarding implementation practices in different countries, including approaches to ensuring interoperability with existing systems and facilitating system migration. International Affairs Division, Minister’s Secretariat, Ministry of Health, Labour and Welfare(MHLW) JAPAN, Japan |
none | not yet | none | all mentions on GitHub record | |
| PC-0664✎ edit📣 feedback | received | general | Editorial human |
unplaced |
Overall impression: Norway finds the rationale for establishing an additional health-specific Digital Public Infrastruc…Overall impression: Norway finds the rationale for establishing an additional health-specific Digital Public Infrastructure for Health (DPI-H) layer on top of the broader DPI foundation to be well justified and supports this approach. While the document is comprehensive, it is also extensive and complex. Norway appreciates the inclusion of reading guidance, summary illustrations, and overview figures, which significantly enhance accessibility and help readers navigate the content Information Management and Methods Division, The Norwegian Directorate of Health, Norway |
none | not yet | none | all mentions on GitHub record | |
| PC-0665✎ edit📣 feedback | received | general | No human |
unplaced |
Reason for disagreement:Reason for disagreement: Information Management and Methods Division, The Norwegian Directorate of Health, Norway |
none | not yet | none | all mentions on GitHub record | |
| PC-0666✎ edit📣 feedback | received | general | Editorial human |
unplaced |
Strengths: Finally, Norway/IMDI welcomes WHO's leadership in developing this guidance. The document has the potential t…Strengths: Finally, Norway/IMDI welcomes WHO's leadership in developing this guidance. The document has the potential to become an important global reference for countries seeking to establish sustainable, interoperable, and scalable digital health ecosystems. Its alignment with broader health system strengthening objectives provides a valuable basis for supporting Universal Health Coverage, Health for All, and the Sustainable Development Goals. Norway/IMDI has extensive experience in the development and implementation of digital solutions and recognises well the presented considerations supporting of a common digital architecture for health. The document successfully articulates the unique requirements of the health sector and demonstrates why health information systems require specific governance, interoperability, security, and architectural considerations, as well as emerging topics such as artificial intelligence and the importance of high-quality data as prerequisites for future innovation. While the document is comprehensive, it is also extensive and complex. Norway appreciates the inclusion of reading guidance, summary illustrations, and overview figures, which significantly enhance accessibility and help readers navigate the content. Information Management and Methods Division, The Norwegian Directorate of Health, Norway |
none | not yet | none | all mentions on GitHub record | |
| PC-0667✎ edit📣 feedback | received | general | WHO ai |
unplaced |
Concerns / changes: While Norway/IMDI strongly supports the overall direction of the guidance, several areas could be s…Concerns / changes: While Norway/IMDI strongly supports the overall direction of the guidance, several areas could be strengthened further. We acknowledge WHOs important role in sharing knowledge, guiding and promoting alignment in health architecture globally. We understand that the primary audience for this guidance is at national-level focusing on national implementation. However, we do believe that the document would benefit from a stronger global perspective as health challenges inevitably transcend national boundaries, and consequently pandemics, public health surveillance, cross-border healthcare, international research collaboration, and global data sharing require cross border considerations. WHO's normative role and existing global public goods facilitates such collaboration, and we recommend this to be more explicitly leveraged throughout this guidance document. (Specified in bullet point 1). Under this heading, Norway/IMDI recommends a stronger emphasis on WHO's own terminologies and classifications. WHO-FIC, including ICD, ICF, ICHI, and ATC, ICD-O and others, should be positioned as primary reference models whenever semantic interoperability and terminology governance are discussed. These internationally governed and widely adopted systems provide an important foundation for global comparability, data reuse, and equitable access. We therefore specifically recommend references to WHO standards to precede references to non-WHO terminologies, which may instead be presented as complementary solutions where appropriate. (Specified in bullet point 2). For some background, see: https://www.who.int/standards/classifications/clinician-documentation-hub). We also suggest that you may consider highlighting use of WHO products in AI. As mentioned above, the WHO-FIC Foundation provides a globally governed semantic resource that can support trusted AI applications through standardized concepts and classifications (https://www.who.int/standards/classifications/frequently-asked-questions/icd-11-implementation, see bullet point 28). We further suggest that the guidance would benefit from greater visibility of WHO's mature governance models. The longstanding governance arrangements supporting WHO classifications demonstrate how Member States, clinicians, technical experts, and subject-matter specialists can collaborate to develop and maintain global health standards. Including these experiences in the consideration or as examples could provide valuable lessons for countries establishing their own governance structures (https://www.who.int/publications/m/item/who-fic-family-paper). (Specified in bullet point 3). Finally, Norway/IMDI recommends strengthening the strategic role of clinical and public health leadership within the governance framework. While clinical expertise is referenced throughout the document, clinical governance does not appear to be given the same strategic prominence as architecture, security, and interoperability governance. Based on Norway/IMDI's experience, a key factor for succeeding on in digital health architecture development, is to involve clinical and public health expertise throughout all stages of development and implementation, including at the highest decision-making levels. This ensures patient safety, quality of care, and public health objectives are adequately addressed also under the development of digital architecture. Information Management and Methods Division, The Norwegian Directorate of Health, Norway |
none | not yet | CS-278 #17 | all mentions on GitHub record | |
| PC-0668✎ edit📣 feedback | received | Metadata registries ai |
3.3 The reference architecture in practice §3.6.2 and more l.812-814 and more |
This comment covers the same change in several sections/text/illustrations:This comment covers the same change in several sections/text/illustrations: Emphasize the use of WHO products throughout the full document so that references to the WHO standards precede references to non-WHO terminologies by the wording. This will enhance usability of guidance to all global users, obtaining equity by including LMICs. General suggestion for alteration: suggested alteration "WHO-standards and terminologies like (WHO-FIC and ICD, ATC, ICD-O and more), with the addition of […]when relevant" Identified areas for adjustment: 1. Section 3.6.2 – line 812-814: ; SNOMED CT (and SNOMED GPS), ICD-11 and LOINC for clinical terminology and classification 2. Table in Product registry, Appendix C, just above line 502 by the box " Relevant standards". This table box needs som tidying, and misses mentioning that ICD cover more than clinical indications, and the mentioneing of ATC and ICHI 3. Section 4.5.2 - line 505-506: …(for example to SNOMED CT/GPS, ICD-11 and LOINC) 4. Figure 3.3 and 3.5) DHI-H Reference Architecture Integrated wiew, under interoperability and open standards, terminology. 5. Figure 3.4.3 NHDD Framework: Content Structure, upper box. Suggested revision: Refer to numbered bullet point above, and exchange text as followed: 1. Suggested change: "The architecture references, rather than reinvents, established and openly governed standards, among them HL7 FHIR for the exchange-oriented representation of health data; WHO reference classifications ICD, ICF and ICHI and ICD-O for clinical terminology and classification; additionally SNOMED CT (and SNOMED GPS), and LOINC [...]" 2. Suggest change: WHO-standards and terminologies like (WHO-FIC and ICD, ICHI, ICD-O and more), with the addition of SNOMED CT/GPS ), HL7 FHIR Medication and Medication […]when relevant" 3. Suggested change: Terminology and semantic specialists, who curate value sets, code systems, and mappings (for example WHO-standards and terminologies like WHO-FIC and ICD, ATC, ICD-O and more, with the addition of SNOMED CT and LOINC when relevant) and operate the semantic governance processes. 4. Suggested change: "(WHO-FIC and ICD, SNOMED CT, LOINC)" 5.Suggested change: "Reference / Administrative Code Sets (e.g. WHO-FIC/ICD/ICF/ICHI, ATC, SNOMED CT, LOINC). Information Management and Methods Division, The Norwegian Directorate of Health, Norway |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-0669✎ edit📣 feedback | received | Metadata registries ai |
3.5.3 How the components are organised §3.5.3 l.683-685 anchor: medium |
This is an important example and should build on common global goods and highlight the WHO products. This will enhance …This is an important example and should build on common global goods and highlight the WHO products. This will enhance usability of guidance to all global users, obtaining equity by including LMICs. Suggested revision: Blue font text should primarily use the WHO-FIC terminologies and/or classifications where possible. Similarly black font should highlight the WHO-owned products of global goods. Information Management and Methods Division, The Norwegian Directorate of Health, Norway |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-0670✎ edit📣 feedback | received | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §3.4.5 l.480-482 anchor: medium |
The topic requires considerable tougth, and is some what simplified in text and figure. We recommend to include and bui…The topic requires considerable tougth, and is some what simplified in text and figure. We recommend to include and build on mature experiences in WHO's mature governance models, see elaborate and updated description https://cdn.who.int/media/docs/default-source/classification/who-fic-network/conduct-of-the-who-family-of-international-classifications-network-2024-update.pdf?sfvrsn=b650e3d3_4 Suggested revision: "Several exist to draw on, firstly within the WHO Family of International Classifications Conduct paper (link), and further the HL7's Unified Terminology Governance (UTG) process for consensus-based authoring [...]" Information Management and Methods Division, The Norwegian Directorate of Health, Norway |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-0671✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: IHE International strongly supports the direction of the DPI-H Reference Architecture and welcomes …Overall impression: IHE International strongly supports the direction of the DPI-H Reference Architecture and welcomes its explicit alignment with IHE specifications and testing. With the revisions recommended, the guidance can go further: it can direct countries not only to use international standards, but also to participate in the international, open, consensus-based processes that close gaps, maintain specifications, and verify interoperability over time. Aaron Goldmuntz, IHE International, United States of America |
none | not yet | CS-262 discuss | all mentions on GitHub record | |
| PC-0672✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
DPI-H components (right set): Leverage IHE's Foundational Work as an Implementation LayerDPI-H components (right set): Leverage IHE's Foundational Work as an Implementation Layer IHE specifications complement standards such as HL7 FHIR, DICOM, HL7 CDA or HL7 v2, and could similarly complement the terminology standards referenced by the draft WHO handbook. IHE provides the use-case aggregation and definition, together with the implementation layer that makes those standards work together in real clinical and operational workflows. IHE profiles define actor responsibilities, coordinated transactions, content and terminology constraints, required options, cross-profile dependencies, and testable conformance expectations. The draft already applies this approach in selected areas, notably its use of IHE Mobile Care Services Discovery (mCSD) for facility and workforce registry functions and IHE Sharing Valuesets, Codes, and Maps (SVCM) for terminology services. The same discipline should be applied consistently across the architecture. The following examples are illustrative rather than exhaustive and should be validated against the final DPI-H use cases and selected profile versions. DPI-H capability 1. Client identity and matching Illustrative IHE assets: PIXm, PDQm, PMIR How the assets can be leveraged: Patient identity query, cross-referencing, synchronization, and merge patterns. 2. Facility, workforce, service and endpoint directories Illustrative IHE assets: mCSD How the assets can be leveraged: Federated discovery and update of organizations, practitioners, locations, services, and exchange endpoints. 3. Lifelong record and document exchange Illustrative IHE assets: MHD, MHDS, XDS.b How the assets can be leveraged: Mobile/FHIR-based and established document-sharing patterns that can support distributed or hybrid architectures. 4. Federated and cross-border discovery and access Illustrative IHE assets: XCA, XCPD How the assets can be leveraged: Gateway, patient discovery, query, and retrieval patterns across autonomous communities and jurisdictions. 5. Terminology services Illustrative IHE assets: SVCM How the assets can be leveraged: Standards-based sharing and use of code systems, value sets, and concept maps. 6. International Patient Summary exchange Illustrative IHE assets: sIPS How the assets can be leveraged: A workflow profile for sharing IPS content using established actors and transactions. 7. Trust, authorization, audit and consent Illustrative IHE assets: ATNA, IUA, BALP, XUA, PCF How the assets can be leveraged: Reusable security, authorization, audit-event, user-assertion, and consent patterns. 8. Diagnostic imaging exchange Illustrative IHE assets: XDS-I, XCA-I and IHE Radiology profiles How the assets can be leveraged: Standards-based discovery and exchange of imaging information across enterprises and communities. Illustrative mapping only; profile selection should be governed by the final use case, applicable options, dependencies, version, and testing requirements. Additional comment on Introduction and health goals (Sections 1.4–1.5, 2.4 and Appendix E) Make each health goal traceable to a clinical or operational workflow, the international profiles that support it, and measurable acceptance criteria. Validate these links with clinicians, patients, public-health users, and implementers. Apply the global-core, national-extension principle to this mapping. Aaron Goldmuntz, IHE International, United States of America |
none | not yet | CS-262 discuss | all mentions on GitHub record | |
| PC-0673✎ edit📣 feedback | received | general | Core architects ai |
4.3 Profiles and Specifications for Implementation anchor: medium |
Context assumptions: Prevent National Implementation Guidance from Recreating FragmentationContext assumptions: Prevent National Implementation Guidance from Recreating Fragmentation The primary concern arises as the draft moves from the global reference architecture to national implementation. Sections 3.6.2 and 4.3 state that standards selection and binding are made nationally and that countries should define minimum data models, actors, roles, services, transactions, and FHIR-based profiles. National governance is indispensable, but these passages could be interpreted as inviting every country to create its own technical specifications for requirements that are fundamentally shared across borders. That approach would risk producing different national interpretations of the same base standards, duplicative specification and testing costs, country-by-country customization for suppliers, reduced portability of solutions, and new barriers to regional and cross-border exchange. It would also impose the greatest burden on countries with the fewest standards-development and testing resources. In practical terms, it could propagate the 'interoperable silos' that the draft itself correctly warns against. This also impacts the ability for the industry to consistently implement the specifications across different jurisdictions and for the national authorities to provide coordinated test beds to validate such implementations (e.g. at IHE Connectathons, or through Projectathons). National programs should retain authority over law, policy, governance, consent, language, terminology localization, implementation validation, procurement, and truly jurisdiction-specific workflows. They should not independently redefine reusable actors, transactions, APIs, security patterns, or information structures and terminologies when suitable international specifications already exist. Local requirements should be implemented as governed extensions to a common international core, with clear provenance, versioning, and conformance rules. Aaron Goldmuntz, IHE International, United States of America |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | |
| PC-0674✎ edit📣 feedback | received | general | No human |
unplaced |
Strengths: IHE International appreciates the opportunity to comment on this important draft. We strongly support its ce…Strengths: IHE International appreciates the opportunity to comment on this important draft. We strongly support its central premises: health digital public infrastructure should be built on shared foundations; interoperability should be treated as a cross-cutting capability rather than a single product or middleware layer; implementations should rely on open, publicly governed specifications; and conformance should be testable. These principles are closely aligned with IHE's mission and with more than 25 years of work profiling international standards into implementable, testable interoperability specifications. We particularly welcome Sections 3.6 and 3.7, including the recognition in Section 3.7.3 that IHE is a principal example of a framework that can be accommodated directly within the reference architecture. The draft appropriately explains that, where an interaction corresponds to an IHE transaction, the architecture can defer to the IHE specification for protocol details and to IHE conformance tooling for testing. That is an important and accurate foundation. Aaron Goldmuntz, IHE International, United States of America |
none | not yet | none | all mentions on GitHub record | |
| PC-0675✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Concerns / changes: IHE strongly endorses the overall direction of the guidance and its emphasis on shared foundations,…Concerns / changes: IHE strongly endorses the overall direction of the guidance and its emphasis on shared foundations, interoperability, and testable conformance. Our recommendations are intended to strengthen this foundation and support consistent, sustainable implementation. In particular, an explicit global-core, national-extension approach, supported by reuse of international profiles and testing resources, would help countries put the guidance into practice while reducing duplication. Core recommendation: Adopt an explicit 'global core, national extension' policy. Countries should first reuse applicable international standards and IHE profiles. When a genuine gap exists, countries and regional bodies should work with the relevant international Standards Development Organizations and established profiling organizations through open, consensus-based processes. National specifications should be limited to transparent extensions or constraints needed for jurisdiction-specific policy and practice, while preserving interoperability with the international core. Publish and maintain a living DPI-H-to-standards mapping WHO and ITU should publish a maintained companion mapping from each DPI-H component, actor, service, and interaction to applicable international standards and profiles. For each entry, the mapping should identify the relevant actor or role, transaction or operation, status and version, dependencies, conformance resources, and known gaps. The current draft's detailed use of mCSD and SVCM provides a strong model, but similarly relevant IHE assets should be surfaced for e.g. identity, document exchange, federated access, trust, audit, consent, IPS exchange, and imaging. Offer of Collaboration IHE International is ready to collaborate with WHO, ITU, GDHP international SDOs - through the JIC, OpenHIE, countries, and the vendor and clinical communities to make this architecture actionable. IHE can support a detailed mapping of DPI-H components and interactions to existing IHE profiles; route identified gaps through its international domain committees and open public-comment process; advance new or updated specifications through trial implementation; contribute test plans, tools, and reference data; coordinate global and regional Connectathons and exploratory testing events; and help countries develop procurement language grounded in verifiable interoperability requirements. This collaboration would reduce duplication, improve the consistency and maintainability of national implementations, strengthen supplier accountability, and accelerate regional and cross-border interoperability. It would also allow investments made in one country to contribute to a reusable global public good. The essential message is simple: national adaptation should build on a shared international core, not create a new core for every country. IHE stands ready to help WHO and ITU translate that principle into profiles, testable requirements, and a robust global implementation ecosystem. Selected References IHE International: IHE Profiles and Development Lifecycle https://www.ihe.net/resources/profiles/ IHE General Introduction https://profiles.ihe.net/GeneralIntro/ch-1.html IHE Connectathon https://www.ihe.net/testing/connectathon/ IHE IT Infrastructure Technical Framework and Published Profiles https://profiles.ihe.net/ITI/ IHE Mobile Care Services Discovery (mCSD) https://profiles.ihe.net/ITI/mCSD/volume-1.html Aaron Goldmuntz, IHE International, United States of America |
none | not yet | CS-262 discuss | all mentions on GitHub record | |
| PC-0676✎ edit📣 feedback | received | general | No human |
unplaced |
Country / regional examples: IHE’s comments focus on the architecture, international standards and profiles, and confor…Country / regional examples: IHE’s comments focus on the architecture, international standards and profiles, and conformance and testing. This submission does not assess the accuracy of the individual country and regional implementation examples. Aaron Goldmuntz, IHE International, United States of America |
none | not yet | none | all mentions on GitHub record | |
| PC-0677✎ edit📣 feedback | received | Core architects ai |
3.6.2 Data and health content standards §Executive Summary; DPI-H design principles; Sections 3.6.2 and 4.3 anchor: medium |
Make international reuse a cross-cutting design principleMake international reuse a cross-cutting design principle The 'global core, national extension' principle should appear in the Executive Summary, the DPI-H design principles, Section 3.6.2, and the opening of Section 4.3. Repetition is warranted because these sections reach different audiences. The guidance should make clear that open standards are not merely documents to cite; they are governed by international communities and lifecycle processes that country representatives are invited to and should engage in. Add standards and profile discovery before national specification Before a country designs a new model, actor, transaction, API, or test, the implementation method should require a documented landscape review. That review should map each DPI-H capability and interaction to applicable international standards, IHE profiles, other established implementation guides, and available test assets. Only residual, unmet requirements should enter a national gap analysis and ultimately an effort to standardize the solution across the ecosystem. Route generalizable gaps into international consensus processes When the architecture identifies a missing international specification, the default response should not be a separate national invention. WHO and ITU should encourage countries to submit the need, use case, and proposed requirements to the responsible international SDO or profiling organization. This is especially relevant where the draft itself identifies an active standardization gap, such as interaction models for Logical Information Model Repository capabilities. A shared backlog would enable expert review, implementation feedback, public comment, coordinated maintenance, and reuse by many countries. The Global Digital Health Partnership (GDHP) as collaboration of national digital health agencies and WHO through its engagement with the Joint Initiative Council (JIC) of all relevant digital health standardization organizations provides a venue for this, as has been demonstrated with the International Patient Summary specifications. Suggested revision: Proposed cross-cutting principle Countries should adopt a global-core, national-extension approach. Before creating a new data model, actor, transaction, interface, terminology definition or implementation profile, national programs should evaluate and reuse applicable specifications maintained by recognized international Standards Development Organizations and established profiling organizations. National requirements should be expressed as transparent extensions or constraints that preserve interoperability with the international core. When a generalizable gap is identified, countries and regional bodies should work with the responsible international organization through an open, consensus-based process so that the resulting specification can be reviewed, tested, maintained, and reused globally. Proposed addition at the beginning of Section 4.3 Profiles for implementation should be selected through a reuse-first process: first map each DPI-H capability and interaction to existing international standards, IHE profiles, and other established implementation guides; identify only the residual unmet requirements; submit generalizable gaps to the relevant international development process; define a national extension only where a jurisdiction-specific requirement remains; and publish computable conformance artifacts and test plans for both the international core and the extension. Aaron Goldmuntz, IHE International, United States of America |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-0678✎ edit📣 feedback | received | Core architects ai |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 anchor: medium |
Clarify the complementary roles of HL7 FHIR and IHEClarify the complementary roles of HL7 FHIR and IHE IHE strongly supports the draft's endorsement of HL7 FHIR as a recommended exchange framework. However, HL7 FHIR conformance alone does not define an end-to-end interoperable workflow. IHE profiles apply HL7 FHIR and other standards (e.g. DICOM, IEEE) to defined use cases, actors, transactions, options, and security dependencies. Section 4.3.3 should therefore direct countries first to existing globally governed HL7 FHIR implementation guides, like the IHE Profiles on HL7 FHIR are, and IHE profiles in general. Language should be avoided that could encourage independent national recreation of equivalent specifications. The guidance should also retain a practical transition path for mature, interoperable non-FHIR implementations and mixed environments. Suggested revision: Proposed addition to Section 4.3.3 HL7 FHIR should be treated as a foundational exchange standard, while IHE profiles and other implementation guides provide the use-case-level specification needed for interoperable workflows. Countries should adopt existing globally governed FHIR implementation guides, like HL7 FHIR based IHE profiles, wherever applicable rather than independently defining equivalent resources, terminologies, actors, operations, and transaction patterns. Any national profile should preserve a clearly identified international core and document only the additional national constraints or extensions. Aaron Goldmuntz, IHE International, United States of America |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-0679✎ edit📣 feedback | received | Core architects ai |
4.3.5 Minimum Conformance and Testing §4.3.5 anchor: medium |
Expand conformance into a full testing lifecycleExpand conformance into a full testing lifecycle Section 4.3.5 should go beyond the creation of country-specific test beds. Countries should reuse international test plans, validators, simulators, reference data, and test-management tooling wherever possible. The lifecycle should include specification validation, developer self-testing, peer-to-peer multi-vendor interoperability testing, and, where required, formal conformity assessment. The guidance should distinguish these forms of evidence clearly: participation in an IHE Connectathon provides intensive implementation feedback and a baseline indication of profile conformance, while formal certification requires an authorized conformity assessment program. For national extensions, the country should add only the tests required for the extension while retaining the international core test suite. Procurement should require transparent evidence tied to named profile versions, actors, options, and transactions rather than a broad, non-specific claim of standards compliance. Suggested revision: Proposed addition to Section 4.3.5 Countries should reuse established international test plans, validators, simulators, reference data, and test-management tooling, thereby also pooling the resources to establish and maintain these assets. Testing should progress from developer self-testing to multi-party interoperability testing and, where required, formal conformity assessment. National extensions should add tests for the extension while retaining the international core test suite. Procurement evidence should identify the exact profile version, actor, option, and transaction tested. Aaron Goldmuntz, IHE International, United States of America |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-0680✎ edit📣 feedback | received | general | Core architects ai |
unplaced |
Overall impression: The draft provides a strong and useful foundation for designing interoperable, trustworthy, and hum…Overall impression: The draft provides a strong and useful foundation for designing interoperable, trustworthy, and human centred digital public infrastructure for health. I particularly value its attention to responsible AI and meaningful human oversight, while seeing scope to strengthen the behavioural and psychosocial dimensions of oversight, including trust calibration, automation bias, vulnerable users, and the conditions under which human review remains substantively effective. Onour Impram, Marmara University, Türkiye |
none | not yet | CS-250 discuss | all mentions on GitHub record | |
| PC-0681✎ edit📣 feedback | received | general | Core architects ai |
5.4 Readiness, oversight, and responsible adoption anchor: medium |
Context assumptions: In the emerging technologies and AI section, the guidance may assume that the presence of human re…Context assumptions: In the emerging technologies and AI section, the guidance may assume that the presence of human review is sufficient to provide meaningful oversight. In practice, human reviewers may defer excessively to AI outputs because of automation bias, perceived model authority, time pressure, or poorly calibrated trust. This is particularly important in health contexts involving vulnerable users, where formal human involvement may exist without providing an effective capacity to question, override, or correct an AI supported decision. Onour Impram, Marmara University, Türkiye |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0682✎ edit📣 feedback | received | general | No human |
unplaced |
Strengths: A major strength is that the guidance treats digital health infrastructure as more than a technical interope…Strengths: A major strength is that the guidance treats digital health infrastructure as more than a technical interoperability problem. Its attention to governance, responsible use of emerging technologies, trustworthy AI, and human oversight provides an important foundation for health systems that must remain safe, equitable, and accountable as AI capabilities become more deeply integrated into care and public health infrastructure. Onour Impram, Marmara University, Türkiye |
none | not yet | none | all mentions on GitHub record | |
| PC-0683✎ edit📣 feedback | received | general | Core architects ai |
5.4 Readiness, oversight, and responsible adoption anchor: medium |
Concerns / changes: I would encourage the guidance to operationalize meaningful human oversight more explicitly as a be…Concerns / changes: I would encourage the guidance to operationalize meaningful human oversight more explicitly as a behavioural and organizational capability, rather than primarily as the presence of a human reviewer. Effective oversight requires that people can detect potential errors, question AI recommendations, understand uncertainty, resist inappropriate deference, and meaningfully override or escalate decisions when necessary. Evaluation should therefore consider trust calibration, automation bias, perceived model authority, workload, and actual override behaviour, in addition to technical model performance. For conversational and mental health related AI, I would also recommend attention to psychosocial risks that can affect human agency, including perceived empathy, emotional reliance, and excessive epistemic dependence on an AI system. These factors may influence whether users and professionals continue to exercise independent judgement even when formal human oversight mechanisms are present. Explicitly incorporating these behavioural dimensions would strengthen the guidance for high impact and vulnerable user contexts. Onour Impram, Marmara University, Türkiye |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | |
| PC-0684✎ edit📣 feedback | received | Core architects ai |
5.3 Where artificial intelligence can support the health system §5.3 (p. 107) l.134–138 anchor: medium |
The recommendation to begin with assistive tools under human oversight is well judged, but the effectiveness of that ov…The recommendation to begin with assistive tools under human oversight is well judged, but the effectiveness of that oversight should not be inferred simply from the presence of a human reviewer. In consequential health decisions, automation bias, perceived model authority, time pressure, and miscalibrated trust can result in nominal human review without meaningful capacity to detect, challenge, or correct an AI-supported output. Suggested revision: Consider adding: “Human oversight should be designed and evaluated as an effective capability, rather than only as the presence of a human reviewer. For consequential uses, implementers should assess whether reviewers can identify and question potential errors, interpret uncertainty, resist inappropriate deference to automated outputs, and override or escalate AI-supported decisions when necessary Onour Impram, Marmara University, Türkiye |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | ||
| PC-0685✎ edit📣 feedback | received | Core architects ai |
5.4.2 Trustworthy AI in a health setting §5.4.2, p. 108 l.155 to 168 anchor: medium |
The inclusion of meaningful human oversight and repeated evaluation is a major strength. I would suggest broadening eva…The inclusion of meaningful human oversight and repeated evaluation is a major strength. I would suggest broadening evaluation beyond model behaviour alone to include the behaviour of the human AI system. A technically accurate model can still contribute to unsafe outcomes if clinicians or users become over reliant on it, fail to exercise independent judgement, or rarely use available override and escalation mechanisms. These risks are especially relevant in sensitive and high impact health contexts. Suggested revision: Consider adding: “Evaluation should include relevant human AI interaction outcomes alongside model performance. Depending on the use case, these may include calibration of trust and reliance, automation bias, actual override or escalation behaviour, workload, and the ability of users or professionals to maintain independent judgement. For AI systems that interact directly with patients, particularly in sensitive domains such as mental health, evaluation should also consider whether perceived empathy, emotional reliance, or excessive epistemic dependence may undermine human agency.” Onour Impram, Marmara University, Türkiye |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | ||
| PC-0686✎ edit📣 feedback | received | Core architects ai |
C Appendix C: DPI-H Application Component Descriptions §Sections 2.2.1 and 2.3; Appendix C - Lifelong Health Record. p. 28; p. 35, lines 355-379; p. 161, Requirements 13-14. anchor: medium |
Consent capability is under-specified. Consent, authorisation and privacy are defined as foundational REDDHI capabiliti…Consent capability is under-specified. Consent, authorisation and privacy are defined as foundational REDDHI capabilities, and the Lifelong Health Record has a Required dependency on consent-management services. However, the reference architecture does not provide a corresponding cross-cutting service/interface specification with the same level of clarity as the named DPI-H components. This creates a capability-to-implementation traceability gap. Suggested revision: Define a technology-neutral Consent/Permissions Management service profile across DPI-H. At minimum, specify consent representation, grant/modify/revoke lifecycle, subject and delegate identity, purpose, data scope, permitted recipient, effective period, revocation propagation, enforcement responsibility and auditability. Allow this profile to be implemented through national/foundational consent infrastructure where available, or through a health-sector capability where required; do not mandate a single centralised consent component. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-235 discuss | in the document all mentions on GitHub record | ||
| PC-0687✎ edit📣 feedback | received | Core architects ai |
C Appendix C: DPI-H Application Component Descriptions §Sections 5.3-5.4.3, pp. 107-109, especially lines 109-169; Appendix C - Computable Decision Support Engine, pp. 181-189. anchor: medium |
AI/ML lifecycle governance should be explicit across the architecture. Chapter 5 appropriately requires representative …AI/ML lifecycle governance should be explicit across the architecture. Chapter 5 appropriately requires representative data, evaluation, human oversight and monitoring for model drift. Appendix C also provides strong lifecycle governance for computable decision logic. However, the architecture does not explicitly define how learned AI/ML models deployed through decision support, surveillance, analytics or point-of-service applications should be identified, versioned and linked to validation and monitoring evidence. Suggested revision: Define a cross-cutting AI/ML lifecycle governance profile rather than a mandatory central AI component. Consequential AI outputs should be traceable to a unique model identifier/version, accountable owner, intended use, validation population and context, relevant performance evidence, deployment status, human-oversight requirements, monitoring/drift criteria, and suspension/rollback/decommission status. Existing CDSE versioning, audit and rollback patterns can be referenced as an architectural precedent. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-0688✎ edit📣 feedback | received | Clinical ai |
C Appendix C: DPI-H Application Component Descriptions §Appendix C - Lifelong Health Record, pp. 159-163, Requirements 3-4 and governance; Client Registry, p. 119, Requirement 6. anchor: medium |
LHR immutability should be reconciled with correction and legally required erasure. The LHR requires that records shall…LHR immutability should be reconciled with correction and legally required erasure. The LHR requires that records shall never be deleted, that previous versions remain retrievable, and that reconciliation actions are auditable. Elsewhere, the guidance recognises removal of erroneous records, data-subject rights, and deletion where legally required. The relationship between immutability, logical withdrawal, correction of wrong-person attribution and legally mandated erasure is therefore unclear. Suggested revision: Clarify data-lifecycle semantics. Preserve immutable version history for ordinary clinical amendments where lawful, while distinguishing: (a) correction/amendment; (b) logical withdrawal or suppression; (c) controlled unlinking/reassignment of wrong-person data; and (d) legally mandated erasure. Specify how these actions propagate across federated nodes, replicas and backups while retaining only the audit evidence permitted by applicable law. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-0689✎ edit📣 feedback | received | Core architects ai |
Lifelong Health Record §Appendix C - Lifelong Health Record, pp. 160-162, Requirements 4, 18 and 19. anchor: low |
Offline/federated synchronisation needs minimum conflict-resolution semantics. The LHR correctly requires offline opera…Offline/federated synchronisation needs minimum conflict-resolution semantics. The LHR correctly requires offline operation, reliable synchronisation, versioning and reconciliation of duplicate or conflicting records. However, 'reliable synchronisation' does not define the minimum semantics for concurrent clinically significant updates across offline or federated nodes. Silent overwrite or premature presentation of one version as authoritative could create clinical-safety risk. Suggested revision: Define a technology-neutral synchronisation and conflict-management profile covering resource/event identity, provenance and versioning, duplicate and replay handling, source-authority rules, preservation of competing versions, safe automatic reconciliation, escalation of clinically material conflicts, clinician-visible indication of unresolved conflicts, auditability, and propagation of the resolved state. Clinically material conflicts should not be silently overwritten. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-175 discuss | in the document all mentions on GitHub record | ||
| PC-0690✎ edit📣 feedback | received | Core architects ai |
C Appendix C: DPI-H Application Component Descriptions §Section 2.3, p. 35, lines 363-379; Appendix C - Client Registry, p. 120, Requirement 14; Lifelong Health Record, p. 161, Requirement 14. anchor: medium |
Delegated/proxy authority should be modelled as a lifecycle, not inferred from relationships. The Client Registry model…Delegated/proxy authority should be modelled as a lifecycle, not inferred from relationships. The Client Registry models parent-child and guardian relationships, while the LHR enforces individual consent preferences. The architecture does not explicitly distinguish a relationship record from current authority to grant, modify or withdraw permissions on another person's behalf. Relationship alone should not imply permission authority. Suggested revision: Extend the consent/permissions profile to support delegated or proxy authority as a governed, time-bounded relationship. Represent the subject, representative/delegate, legal or governance basis, scope, purpose/data category, effective period, status, modification, expiry/revocation and audit provenance. Client Registry relationships may support identity resolution but should not themselves imply decision-making authority; national law should determine who is authorised and under what conditions. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-236 #10 | in the document all mentions on GitHub record | ||
| PC-0691✎ edit📣 feedback | received | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §Section 2.3 - Trust and Security, p. 36, lines 401-427. anchor: medium |
Graduated assurance should retain a minimum security floor. The graduated-assurance approach appropriately allows count…Graduated assurance should retain a minimum security floor. The graduated-assurance approach appropriately allows countries with different maturity levels to progress. However, the guidance does not clearly distinguish controls that may mature over time from minimum security properties that should be present from initial operation of components processing identifiable or sensitive health data. Suggested revision: Define a technology-neutral minimum security floor across DPI-H. Assurance mechanisms may mature over time, but core properties such as actor identification/authentication, explicit authorisation, least privilege, confidentiality, auditability, integrity/provenance, incident containment and secure recovery should not become optional solely because technical maturity is lower. Where stronger assurance cannot yet be achieved, residual risk and compensating controls should be documented. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-0692✎ edit📣 feedback | received | Core architects ai |
Lifelong Health Record §Section 1.5, pp. 21-22, lines 429-432; Section 2.3, pp. 35-36; Appendix C - Lifelong Health Record, pp. 161-162, Requirements 14-17. anchor: medium |
Reuse should remain purpose-bound and carry interoperable policy metadata. The guidance appropriately supports 'capture…Reuse should remain purpose-bound and carry interoperable policy metadata. The guidance appropriately supports 'capture once, use many times' and elsewhere recognises purpose limitation, data minimisation and access governance. For reuse across federated systems, however, policy constraints also need a machine-readable form so that the receiving system can enforce the applicable purpose, confidentiality and handling rules. Suggested revision: Qualify the principle consistently as: 'Capture once, use many times - for authorised purposes, under applicable governance, and using only the data necessary for each purpose.' Add a cross-cutting requirement for standards-based policy metadata capable of expressing nationally defined confidentiality/sensitivity classes, permitted purposes, consent or other authorisation references, handling restrictions and provenance, with those constraints preserved during exchange and federated access. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-252 discuss | in the document all mentions on GitHub record | ||
| PC-0693✎ edit📣 feedback | received | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §Section 2.3 - Data ownership/consent discussion, p. 35, lines 352-379. anchor: medium |
Clarify consent as individual agency, not the universal legal basis for processing. The statement that 'Consent is the …Clarify consent as individual agency, not the universal legal basis for processing. The statement that 'Consent is the primary mechanism through which individuals exercise these rights' may be read as positioning consent as the primary authority for health-data processing generally. Elsewhere, the guidance correctly recognises processing under other legal authorities, including defined clinical and public-health functions. Suggested revision: Suggested wording: 'Consent is an important mechanism through which individuals exercise agency and preferences over access to and sharing of their health information, where consent is applicable under the relevant legal and governance framework. Health-data processing may also occur under other lawful authorities, subject to appropriate safeguards, purpose limitation and individual rights.' Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-0694✎ edit📣 feedback | received | Clinical ai |
C Appendix C: DPI-H Application Component Descriptions §Appendix C - Lifelong Health Record, p. 161, Requirement 13. anchor: medium |
Break-glass access needs minimum emergency-access governance. The LHR appropriately requires emergency/break-glass acce…Break-glass access needs minimum emergency-access governance. The LHR appropriately requires emergency/break-glass access and full audit capture, but audit logging alone does not define when an override is justified, what scope of data may be accessed, how long the override lasts, or how inappropriate use is subsequently detected and reviewed. Suggested revision: Define a technology-neutral minimum break-glass profile requiring authenticated actor identity, documented reason/purpose, proportionate and time-bounded access, complete audit provenance, and post-hoc review or monitoring for inappropriate use. Where appropriate and lawful, support transparency or notification to the individual. National law and clinical policy should determine qualifying emergency circumstances and category-specific restrictions. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | ||
| PC-0695✎ edit📣 feedback | received | Core architects ai |
1.4 DPI-H Principles §Section 1.4 - Autonomy and Sovereignty, p. 21, lines 412-416. anchor: medium |
Sovereignty should emphasise effective control and substitutability. The statement that countries should not be depende…Sovereignty should emphasise effective control and substitutability. The statement that countries should not be dependent on actors outside their jurisdiction may be interpreted as requiring technological or hosting self-sufficiency. Elsewhere, the guidance appropriately allows private-sector hosting, regional shared infrastructure, international standards and cross-border federated services. Suggested revision: Reframe sovereignty in terms of effective governance control, continuity, portability and substitutability rather than absence of external dependency. Explicitly recognise that external or regional providers may be used where countries retain control over critical data and governance, maintain viable exit/transition arrangements, and can continue essential functions without unacceptable vendor or jurisdictional lock-in. Ruslan Kurmashev, (not stated), (not stated) |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | ||
| PC-0696✎ edit📣 feedback | received | general | Financial systems ai |
C Appendix C: DPI-H Application Component Descriptions §Section 2.4.2; Appendix C, Benefits Package Registry; Appendix D. anchor: medium |
Making the health–social protection connection more concrete. A worked example of a couple countries (the one I know be…Making the health–social protection connection more concrete. A worked example of a couple countries (the one I know best is Türkiye’s Integrated Social Assistance Information System (ISAIS) with a role in income assessment for General Health Insurance) would make the health–social protection connection even better. So one could distinguish identification, eligibility assessment and enrolment, and show how institutional coordination and digital interoperability support publicly financed coverage and responses to changing household circumstances. To inform adaptation across country settings, the example can document transferable lessons and limitations, including institutional prerequisites, remaining coverage gaps and safeguards limiting personal data exchange. UNICEF, (not stated) |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | |
| PC-0697✎ edit📣 feedback | received | general | Financial systems ai |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §Sections 2.4.2 and 4.4. anchor: medium |
Measuring financial protection and benefits for children (or other vulnerable groups) a bit more explicitly. While the …Measuring financial protection and benefits for children (or other vulnerable groups) a bit more explicitly. While the draft recognises financial protection, the proposed monitoring framework could more clearly distinguish digital-system performance, formal insurance coverage and effective access to affordable care. A small set of illustrative indicators could track unmet healthcare needs, catastrophic or impoverishing health expenditure, and coverage gaps among children, disaggregated by household income, disability and geography, using household surveys alongside administrative data. Linking these findings to budget allocations and expenditure on services benefiting children would help demonstrate whether digitalization improves equitable public spending and informs corrective financing decisions. UNICEF, (not stated) |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | |
| PC-0698✎ edit📣 feedback | received | general | Core architects ai |
C Appendix C: DPI-H Application Component Descriptions §Section 2.3; Appendix C, Client Registry and Lifelong Health Record. anchor: medium |
Translating rights-based principles into enforceable safeguards. The commitment to inclusive registration needs to be r…Translating rights-based principles into enforceable safeguards. The commitment to inclusive registration needs to be reconciled with the Client Registry’s designation of address, contact information and mother’s/guardian’s name as mandatory, so that missing information cannot become a barrier to registration or care. The guidance can specify assisted and non-digital access routes, accessible explanations of adverse eligibility decisions, and timely human review and appeal mechanisms. For children, it can also address evolving capacities, adolescent confidentiality and appropriate limits on parental or guardian access to lifelong records. UNICEF, (not stated) |
none | not yet | CS-100 discuss | in the document all mentions on GitHub record | |
| PC-0699✎ edit📣 feedback | received | general | Financial systems ai |
3.4.3 Strategic governance §Sections 3.4.3 and 4.6. anchor: medium |
Strengthening the public-finance guidance and protect equitable access. The financing section can be a bit stronger wit…Strengthening the public-finance guidance and protect equitable access. The financing section can be a bit stronger with an illustrative multi-year costing and budgeting framework covering initial investment, recurrent operations, workforce capacity, cybersecurity and replacement costs, with clear responsibilities across participating institutions. The section can benefit from distinguishing cash-releasing savings from improvements in staff productivity and recognise that reaching previously excluded populations may increase legitimate service expenditure. Proposed cost-recovery arrangements, usage tiers and access restrictions can include explicit safeguards against passing costs to patients or excluding under-resourced providers serving disadvantaged children and families. UNICEF, (not stated) |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | |
| PC-0700✎ edit📣 feedback | received | Core architects ai |
1.1.3 Building on existing foundations §Ch. 1, §1.5 (Seven Priority Health Sector Goals); Ch. 3, §3.7.5 (Validating goals and adoption); Ch. 4, §4.4 (Measuring progress and impact) anchor: medium |
Success is validated through conformance, adoption and coverage metrics. No goal or metric addresses whether the receiv…Success is validated through conformance, adoption and coverage metrics. No goal or metric addresses whether the receiving actor acts appropriately on exchanged information. A message can arrive complete, coded and conformant, and still leave the receiver unable to decide what to do. Moreover, 'capture once, use many times' assumes reuse is free; in practice information must be transformed to fit each receiver's role and context (informational metamorphosis), and this transformation is neither designed nor governed. Suggested revision: Add to §4.4 (and reference from §3.7.5) an explicit pragmatic outcome measure: periodic, scenario-based assessment of whether receiving actors take the appropriate next action on the basis of exchanged records. Additionally, design and govern receiver-appropriate views of shared records (role- and context-specific transformations), rather than assuming one representation serves all. Position appropriateness-of-action as the ultimate validation criterion of the seven goals. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-014 discuss | in the document all mentions on GitHub record | ||
| PC-0701✎ edit📣 feedback | received | Metadata registries ai |
F Appendix F: Semantic Governance Infrastructure: capability details §Ch. 2, §2.2.2 (Enabling conditions / open standards); Ch. 3, §3.4.5 (SGI); Appendix F anchor: medium |
The draft rightly notes SNOMED CT licensing, and SGI covers release management. However, it nowhere states as a require…The draft rightly notes SNOMED CT licensing, and SGI covers release management. However, it nowhere states as a requirement that all participating systems must operate on the same versions of the same code systems and value sets. Divergent versions allow one code to carry a changed or deprecated meaning across systems — undermining precisely the semantic consistency the architecture exists to provide. Suggested revision: State explicitly (in §2.2.2 and in the SGI capability categories) that version alignment of terminologies and value sets across all consuming systems is a conformance requirement, with coordinated national release windows, deprecation notice periods, and migration testing as SGI-governed processes. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-0702✎ edit📣 feedback | received | Metadata registries ai |
3.7 Conformance and Testing across Architecture and Components §Ch. 4, §4.3.1–4.3.3 (Data models first; FHIR); Ch. 3, §3.7 (Conformance and testing); Logical Information Model Repository (App. C) anchor: medium |
The LIMR governs logical models, and FHIR is recommended for exchange. Experience with national clinical information mo…The LIMR governs logical models, and FHIR is recommended for exchange. Experience with national clinical information models (e.g. the Netherlands’ zibs, per ISO 13972) shows the translation from logical model to technical artefact (FHIR profile, storage model) is not inherently one-to-one; meaning can shift or be lost in that step even when systems are technically conformant. Suggested revision: Add to §3.7 a requirement for semantic fidelity testing across the translation step: round-trip verification that data instantiated from a logical model, exchanged via its technical representation, and re-interpreted at the receiving end preserves the governed meaning — not only structural/technical conformance. Reference ISO 13972 for clinical information model quality requirements. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | ||
| PC-0703✎ edit📣 feedback | received | Core architects ai |
1.2.2 Data exchange DPI and Interoperability in the health sector §Ch. 1, §1.2.2; Ch. 3, §3.6 (Interoperability architecture); Glossary (definition of interoperability) anchor: medium |
The draft implicitly treats non-structured information as text awaiting structuring (‘machine-processable rather than l…The draft implicitly treats non-structured information as text awaiting structuring (‘machine-processable rather than locked in free text’). Clinical information also exists in interpretive and tacit/narrative states that resist faithful coding; forcing them into structure distorts rather than captures them. These states carry a large share of real clinical decision-making. Suggested revision: Acknowledge in §1.2.2 and §3.6 the limits of structuring: name the interpretive and narrative states of clinical information as first-class concerns, state that the architecture supports (rather than replaces) their human carriers — the conversation, the handover, the narrative note — and caution against measuring digitisation progress by the elimination of free text. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-257 discuss | in the document all mentions on GitHub record | ||
| PC-0704✎ edit📣 feedback | received | Clinical ai |
Lifelong Health Record §Goal 4 (Trusted Personal Health Records); Lifelong Health Record (App. C) anchor: low |
The individual appears primarily as a rights-holder and, ‘where applicable’, a data source. The person is also a knowle…The individual appears primarily as a rights-holder and, ‘where applicable’, a data source. The person is also a knowledge source: the holder of context, corrections, and narrative that no provider system records — often decisive for safe care (allergies, adherence, home circumstances). Suggested revision: Extend the LHR component requirements with a governed citizen-contribution channel: the ability for individuals (and, where authorised, informal carers) to add structured and narrative contributions and corrections to their record, with provenance and review workflow, so the record reflects lived reality as well as institutional data. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-271 discuss | in the document all mentions on GitHub record | ||
| PC-0705✎ edit📣 feedback | received | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §Ch. 3, §3.4.5 (SGI — governance layers and capability categories); Ch. 5, §5.2 |
SGI’s feedback loop runs from consuming applications back into the governance cycle. It does not yet include feedback f…SGI’s feedback loop runs from consuming applications back into the governance cycle. It does not yet include feedback from care outcomes and receiver comprehension — e.g. terms or models that are systematically misread at the point of care. Suggested revision: Add to the SGI capability categories (and Appendix F) a capability for pragmatic feedback: structured intake of evidence that governed content is misinterpreted or fails to support appropriate action in practice, feeding the authoring/publication cycle. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-0706✎ edit📣 feedback | received | Core architects ai |
Future proofing the Architecture §Ch. 5 (Future proofing; AI) anchor: medium |
We strongly endorse Chapter 5’s framing. One principle deserves to be stated explicitly: an AI model must not be the te…We strongly endorse Chapter 5’s framing. One principle deserves to be stated explicitly: an AI model must not be the terminal interpreter of clinical information. Its outputs become trustworthy data only when a human author has checked, integrated and signed them. Suggested revision: Add a sentence to §5.4.2 stating that AI outputs affecting care, eligibility or resources require a human author of record who verifies and signs the resulting data before it enters the Lifelong Health Record or downstream decision processes — consistent with the chapter’s auditability principle. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-247 discuss | in the document all mentions on GitHub record | ||
| PC-0707✎ edit📣 feedback | received | Core architects ai |
Glossary §Glossary; §3.6.5; terms marked ‘[Under review]’ anchor: medium |
Several glossary terms are under review and ‘Health Information Exchange’ is still to be included. Since the pragmatic …Several glossary terms are under review and ‘Health Information Exchange’ is still to be included. Since the pragmatic level (comments 1, 4, 6) is currently absent from the definitions, the revision of the glossary is the natural place to anchor it. Suggested revision: When finalising the glossary, define pragmatic interoperability (shared use of exchanged information for appropriate action) alongside the existing definition of interoperability, and align the conformance chapter’s vocabulary with it. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-0708✎ edit📣 feedback | received | Metadata registries ai |
4.5 Roles, Skills, and Capacity §Ch. 4, §4.5–4.6 (Roles, skills, capacity; financing) anchor: medium |
SGI presupposes sustained institutional capacity (committees, curation, release management) that is scarcest in the LMI…SGI presupposes sustained institutional capacity (committees, curation, release management) that is scarcest in the LMICs this guidance most aims to serve. The financing and capacity sections are thin relative to what the governance model demands. Suggested revision: Expand §4.5–4.6 with a minimal viable SGI staffing/costing model and options for regional pooling of semantic governance (shared curation across countries, as §3.4.6 hints), so the governance burden matches realistic capacity. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-0709✎ edit📣 feedback | received | Metadata registries ai |
Logical Information Model Repository §Ch. 3, §3.4.5 (SGI); Ch. 4, §4.3.1–4.3.3 (Data models first); Logical Information Model Repository (App. C) anchor: low |
The architecture governs the stewardship of information models (SGI, LIMR) but does not standardise how models are made…The architecture governs the stewardship of information models (SGI, LIMR) but does not standardise how models are made. Current artefact standards allow too many degrees of freedom: the same clinical concept can be modelled in many valid but incompatible ways, so two fully conformant implementations may still diverge semantically. A related, unnamed risk is the boundary problem: qualifiers, modifiers and localisations can be expressed in either the terminology or the information model, and this overlap breeds divergence. Suggested revision: Require (in §3.4.5 and App. C) that artefacts in the LIMR be produced with a declared, uniform modelling method — one generic semantic pattern from which artefacts are derived by specialisation, with mandatory context (what, where, when, who, how, why) at capture — and test that meaning survives its application. The emerging CEN/ISO 13606 part 3 (SIAMM) work is one standards-track candidate; the requirement itself should remain method-neutral, preserving the draft's neutrality between modelling schools. Explicitly name — and assign governance responsibility for — the boundary problem between coding systems and information models. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | ||
| PC-0710✎ edit📣 feedback | received | Clinical ai |
3.5 DPI-H Application Components §Component catalogue (Ch. 3; App. C); goals on continuity of care anchor: medium |
Among the proposed components there is no component for the shared, multi-professional care plan — the living object st…Among the proposed components there is no component for the shared, multi-professional care plan — the living object stating who does what, when, and towards which goals for a specific person. 'Care plan' appears only in passing inside other components, never as an architectural object with its own repository, governance and exchange rules. Of the three recognised kinds of continuity of care — informational (data follows the person), management (one coherent shared plan), relational (being cared for by people who know you) — the draft covers essentially only the first and equates it with the whole. Suggested revision: Add a Shared Care Plan component to the catalogue: a governed repository and exchange rules for multi-professional, cross-organisational, long-term plans (building on existing patterns such as FHIR CarePlan and the International Patient Summary), as the architectural carrier of management continuity. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-069 discuss | in the document all mentions on GitHub record | ||
| PC-0711✎ edit📣 feedback | received | Clinical ai |
unplaced §Ch. 1 (framing and examples); actor definitions throughout |
The draft's implicit care model is episodic and programme-centric (HIV, TB, immunisation examples). Across 254 pages, '…The draft's implicit care model is episodic and programme-centric (HIV, TB, immunisation examples). Across 254 pages, 'integrated care', 'social care' and 'long-term care' do not appear; 'caregiver' appears once; 'chronic' four times. The person with multiple chronic conditions whose care spans health and social services over years — precisely the population that most needs shared infrastructure — is absent as a design case. Suggested revision: Include integrated, long-term and social care explicitly in the framing and priority use cases; add social-care professionals and informal caregivers to the recognised actors; and include a worked example of a multimorbid person supported by a multi-professional, cross-organisational team over time. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-255 discuss | all mentions on GitHub record | ||
| PC-0712✎ edit📣 feedback | received | Core architects ai |
Spain §Cross-border and regional sections; examples citing Spain, Catalonia and EU-wide surveillance anchor: medium |
The European Health Data Space (EHDS) — the largest legal and infrastructural implementation of exactly these ideas, es…The European Health Data Space (EHDS) — the largest legal and infrastructural implementation of exactly these ideas, establishing citizen rights, mandated exchange formats and cross-border channels for primary and secondary use — is never mentioned, although EU examples are cited. Suggested revision: Add an EHDS alignment section mapping DPI-H components to EHDS obligations and formats (e.g. the European exchange format and patient summary), so European implementers can position themselves and other regions can learn from the largest live implementation. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-261 discuss | in the document all mentions on GitHub record | ||
| PC-0713✎ edit📣 feedback | received | Core architects ai |
2.2 Resilient Essential Data and Digital Health Infrastructure (REDDHI) §REDDHI (Ch. 2–3); Ch. 4, §4.4 anchor: medium |
REDDHI is rightly defined as a condition of maturity to be approached gradually and verified through observable signs —…REDDHI is rightly defined as a condition of maturity to be approached gradually and verified through observable signs — but the draft offers no structured self-assessment instrument with which a country can locate itself and plan progression. Suggested revision: Connect REDDHI to the existing tradition of maturity models — for example SCIROCCO, the European twelve-dimension self-assessment for integrated-care readiness, used for planning rather than grading — or provide a REDDHI maturity instrument with dimensions and observable indicators. EN13606 Association (one co-author community), (not stated) |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | ||
| PC-0714✎ edit📣 feedback | received | technical | Financial systems ai |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2; Table 2.4 |
Proposed redraft of section 2.4.2 (health financing worked example) and Table 2.4. Full replacement text is provided ve…Proposed redraft of section 2.4.2 (health financing worked example) and Table 2.4. Full replacement text is provided verbatim in the source document 'Updating Table 2.4 (HB/IM/MJ update)'. WHO, (not stated) |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | |
| PC-0715✎ edit📣 feedback | received | Financial systems ai |
1.2.3 Payments DPI and financial transactions in the health sector anchor: medium |
I have two broader comments: I think the narrative is written from a very specific view point, outside HF or even outsi…I have two broader comments: I think the narrative is written from a very specific view point, outside HF or even outside health systems, with assumptions from that outside point of view. But for somebody from within HF, these assumptions appear quite unusual. I wonder whether it is needed to outline those (external) assumptions, more so considering that our target audience are health system people, and not IT people necessarily. One of these assumptions is about what payments DPI are. However, this document does not explain what these are. I am guessing (and there is a hint at one point) that this refers to digital wallets/digital payment systems such as Mtiba or alike. But why would we consider this as “payments DPI”. Why is the GIFMIS not considered as a core example/element of payments DPI? So depending on where you stand, this may be viewed completely different. To avoid confusion, I suggest simply completely removing these assumptions. And just remain descriptive and explain what is needed from the DPI system view. WHO, (not stated) |
none | not yet | CS-037 discuss | in the document all mentions on GitHub record | ||
| PC-0716✎ edit📣 feedback | received | Financial systems ai |
Distinguishing the Benefits Package Registry, Contract & Benefits Management System, and Beneficiary Registry anchor: low |
My other main comment is on the beneficiary registry. I remember that we had once discussed this in one of the Friday m…My other main comment is on the beneficiary registry. I remember that we had once discussed this in one of the Friday meetings. Even then, I was not fully following and unclear what the group members had in mind. I cannot relate this to our HF framework and core HF functions. I would appreciate if we can again take 10 minutes at the next Friday meeting and quickly review/reflect. WHO, (not stated) |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0717✎ edit📣 feedback | received | Financial systems ai |
unplaced |
Also, at one point in the document, the para starts out with benefit design, but then jumps to benefit provision (see t…Also, at one point in the document, the para starts out with benefit design, but then jumps to benefit provision (see the comments in the text). WHO, (not stated) |
none | not yet | none | all mentions on GitHub record | ||
| PC-0718✎ edit📣 feedback | received | Financial systems ai |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing anchor: low |
Two smaller points: Re the eight sub-goal of safeguards: reading this para, I don’t consider this as HF specific, actua…Two smaller points: Re the eight sub-goal of safeguards: reading this para, I don’t consider this as HF specific, actually not even health sector specific. So I suggest removing this as a sub-goal and shift it to a higher level wherever it would fit best. I have also removed the distinction between PFM (budget formation and budget monitoring – PS: budget execution is missing) and health coverage management. I tried to rephrase so that we can keep the subsequent sub-tasks (not sub-goals), but as PFM cuts across HF functions, and vice versa, and given that they operate on different dimensions, presenting them as these two domains in this way doesn’t work really. WHO, (not stated) |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | ||
| PC-0719✎ edit📣 feedback | received | Core architects ai |
unplaced |
We should be explicit that this is a reference architecture rather than a prescribed end-state EA. Its purpose is to pr…We should be explicit that this is a reference architecture rather than a prescribed end-state EA. Its purpose is to provide a set of capabilities and design considerations that countries can adapt according to their own context, and implementation priorities. Estonia evolved within the context of mature digital governance, infrastructure, and capability. Not where most countries would start. Countries are at different stages of their interoperability journey, and many will require shared interoperability capabilities to reduce complexity, support consistent policy, and accelerate adoption. The aspirations overtime could be greater distribution of responsibilities across participating systems. In my views, countries may choose a lighter or more capability rich interoperability layer based on their context - reference architecture should guide design thinking and considerations, not prescribe it. CSIRO, (not stated) |
none | not yet | CS-042 discuss | all mentions on GitHub record | ||
| PC-0720✎ edit📣 feedback | received | Core architects ai |
unplaced |
From: https://www.digitalhealth.gov.au/sites/default/files/documents/csr-8169-health-connect-australia-architechture8.p…From: https://www.digitalhealth.gov.au/sites/default/files/documents/csr-8169-health-connect-australia-architechture8.pdf: Australia offers a middle reference point. Not all interoperability capabilities should sit in a central ESB, and not all health specific capabilities should be pushed entirely to endpoints. Instead, it adopts an architecture in which nationally shared capabilities coexist with locally owned systems, with responsibilities distributed according to where they provide the greatest value – I feel this aligns with our current RA understanding as well. Finally, one key lesson from ‘OpenHIE discussions with countries’ is that each box is often interpreted as requiring a separate systems or procurements, kicking off another debate. It might be useful to clarify that these DPI-H RA boxes represent reference capabilities and not target state, standalone platforms. Smaller or more centralised countries may choose to consolidate multiple capabilities within a single solution/platform/system and still achieve the intended outcomes. CSIRO, (not stated) |
none | not yet | CS-245 discuss | all mentions on GitHub record | ||
| PC-0721✎ edit📣 feedback | received | Core architects ai |
2.2 Resilient Essential Data and Digital Health Infrastructure (REDDHI) anchor: medium |
Several things struck me: There is still a need to be clear on what essential is for countries (bare minimum and countr…Several things struck me: There is still a need to be clear on what essential is for countries (bare minimum and country specific) and negotiating the expectation within DDA that REDDHI is one mechanism to bring our different projects together under one chapeau (‘the kitchen sink of what’s on the menu’); A possible country menu approach is one way of being country driven and responding to county priorities, but again this needs to be focused on core elements of REDDHI As we try and ‘retrofit’ the second D into the original REDHI it will need some rethinking graphically so the data and digital elements are more of a continuum or at least together (I know you tried this previously with the patient journey which worked well and some of the other graphics but need to balance the person centred approach with the systems perspective) – I will ask Wendy to take a stab at this as she was suggesting this and see what we come up with next week. Balancing PHC and AI expectations / outcomes through more than word smithing requires much more dialogue there are five remaining issues I think worth discussing further Defining ‘essential’ REDDHI financial and technical needs?: On one hand, the current version expanded beyond the original concept and it’s like ‘apple pie’ that nobody can say no to! (as we have more inputs and try and retrofit data aspects), to potentially include ‘too broad’ a range of data and digital health norms & standards, and we need to focus on REDDHI being a state and what is ‘essential’ for countries; One the other hand, each country is different and maybe we (WHO) need to offer a ‘range of options’ for norms / standards to address their country priorities and what countries see as ‘essential’ and ‘investable’ in. Perhaps countries need to define what is essential for them and not us – but selection from a range of norms and standards? Country ownership, country driven and resilient financing: In addition to technical data and digital health norms and standards, we need to look at structures within Govt planning and financing cycles & processes (to ensure MoF and key banks are included in broader planning and budgeting processes for laying foundations within, and beyond, the health sector) These Govt. ‘structures’ are also important for a) data and digital sovereignty, b) national legal agreements on sharing and financing and c) accountability and oversight. Perhaps we need to map out country planning cycles and existing coordination structures that include departments of planning and financing, NSOs and partnership coordination mechanisms Ensuring data standards are incorporated (but don’t delay / disrupt digital health DPI work to date): The list of data standards to be considered is on slide 7 – surveys needs further discussion on whether they are included or not; Modernization country-facing data analytics package needs further clarity but lies at heart of HMIS capacity and ability to analyze data for action; Front line health worker perspective still missing HMIS (slide put together to consider - ‘two sides of one coin’ i) person centred journey with need for personalized approaches and ii) systems view point for digital and data – what the Govt system needs to have secure, trusted quality data to make decisions REDDHI as a way of uniting tools / projects / a chapeau for DDA resource mobilization? It may be too broad, and everyone may need to see ‘their’ project in it, but some mentioned REDDHI (as concept & goal), with a robust ToC, could drive pulling together of tools / assessments / approaches for norms & standards for DDA when we approach donors / funders for our work (continuum of data / digital / AI); Norms and standards are highlighted in slide 7 i ) survey or not and ii) assessment / maturity tools to provide basis of country maturity ready for assessment (or not eg. SCORE / MONITOR) Being more driven by country needs and showing impact: Appetite of REDDHI concept to be used as ‘menu’ of WHO norms and standards and potential structures to be supported to get to ‘REDDHI state’ / health goals – leaves countries more in driver’s seat to pick and choose what they need; Obv. needs series of regional office sensitization and RO’s driving country selection and coordinating support, together with HQ WG as part of work plan – needs to happen soon. WHO, (not stated) |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | ||
| PC-0722✎ edit📣 feedback | received | Core architects ai |
Health Facility Registry anchor: medium |
I was again checking the HF registry section and wanted to comment on the use of the term “CGR.” At WHO, we have genera…I was again checking the HF registry section and wanted to comment on the use of the term “CGR.” At WHO, we have generally avoided this terminology and instead use “geospatial registry,” which is a broader and more globally applicable concept. Many advanced countries may not readily adopt the CGR concept because they already have well-established and continuously updated addressing systems. In addition, geospatial registries are cross-cutting in nature and not specific to the health sector. For this reason, I would be cautious about introducing terminology that may not be fully endorsed or used across sectors beyond health. My suggestion is to replace references to CGR with “national geospatial registry” or simply “geospatial registry,” depending on the context in which the term is used. "a national geospatial (common geo) registry" → "a national geospatial registry" — page 76 "or a common geo-registry" → "or a geospatial registry" — page 117 "The Common Geo-Registry (CGR) is a cross-sectoral foundational component…" → "The geospatial registry is…" — page 135 "…synchronised with — a Common Geo-Registry or equivalent geospatial reference source…" → "…a geospatial registry or equivalent reference source…" — page 137 Heading "Relationship with a Common Geo-Registry" → "Relationship with a geospatial registry" — page 137 "…specifically a Common Geo-Registry (CGR); a cross-sectoral…" → "…specifically a geospatial registry;…" — page 137 "…shall support integration with a Common Geo-Registry (CGR) or equivalent authoritative geospatial source." → "…integration with a geospatial registry or equivalent authoritative source." — page 141 "(5) Common Geo-Registry integration is introduced as a new requirement…" → "(5) geospatial registry integration…" — page 143 "…verified against a Common Geo-Registry or equivalent authoritative geospatial source…" → "…verified against a geospatial registry or equivalent authoritative source…" — page 144 "…canonical identifiers from the Common Geo-Registry (where available)…" → "…identifiers from the geospatial registry (where available)…" — page 144 "…(and foundational Common Geo Registry (CGR) where available)…" → "…(and foundational geospatial registry where available)…" — page 232 (this same sentence also recurs on page 236, so change both) WHO, (not stated) |
none | not yet | CS-267 discuss | in the document all mentions on GitHub record | ||
| PC-0723✎ edit📣 feedback | received | WHO ai |
1.5.1 The Health Sector Goals anchor: medium |
1. The WHO Nomenclature Regulations, and the Member State obligations they create for mortality and morbidity reporting…1. The WHO Nomenclature Regulations, and the Member State obligations they create for mortality and morbidity reporting, are not referenced anywhere; the use of classifications is framed throughout as an elective national standards choice (p. 73). 2. The first health goal promises "population analytics including CRVS and mortality" (p. 22), yet the document contains no death certification or cause-of-death coding pathway — the phrase "cause of death" does not occur in its 254 pages. 3. A Required Terminology Service capability calls for the import of "local modifications of ICD and SNOMED CT" (TSF-1, p. 167). Modification of the international content is not permitted under either standard's licence and would undermine comparability; national extension and addition are the correct concepts. 4. ICHI does not appear in the document; ICF appears twice in passing; WHO-FIC once. The ICD-11 delivery infrastructure (API, coding tool), the annual update cycle, and the cost-free availability of the WHO classifications are not mentioned, while the licensing arrangements of other terminologies are described in some detail (pp. 20, 165, 171). 5. The AI chapter grounds trustworthy AI in governed terminology but does not consider knowledge-graph representations — the model on which the ICD-11 Foundation is built. The draft nowhere references the WHO Nomenclature Regulations or the Member State obligations they create — classification use is framed throughout as elective national standards selection. A floor for Member States should include the obligations Member States already stand on. TS requirement TSF-1 makes "local modifications of ICD and SNOMED CT" a Required import capability — something neither license permits, and which would compromise the statistical comparability the architecture promises. This is easily addressed with extension and national-addition language. Goal 1 promises "population analytics including CRVS and mortality," yet the document contains no death certification or cause-of-death coding pathway; the phrase "cause of death" does not occur in its 254 pages. WHO, (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-0724✎ edit📣 feedback | received | Core architects ai |
D.2 Country implementation examples |
I would like to suggest including illustrative use cases, which would also allow for examples from South America and ad…I would like to suggest including illustrative use cases, which would also allow for examples from South America and add value to the document. For the section on National Implementations (page 83), I am sharing the case of Uruguay in two alternative versions for your consideration. DRAFT ENTRY A — Technical interoperability architecture emphasis Historia Clínica Electrónica Nacional (HCEN) is Uruguay's federated national longitudinal health record (LHR) and clinical-document exchange, developed and operated by the Salud.uy program of AGESIC (Agencia de Gobierno Electrónico y Sociedad de la Información y del Conocimiento) in conjunction with the Ministerio de Salud Pública. Architected as an IHE-based health information exchange rather than a central data store, the HCEN operates as a national interoperability node in which clinical documents remain in the custody of the institution that generated them while a central platform indexes and brokers their exchange in real time; its core components are the Índice Nacional de Usuarios de Salud, an Enterprise Master Patient Index implementing the IHE PIX/PDQ profiles for unique patient identification, the Registro Nacional de Documentos Clínicos (an IHE XDS.b document registry), a Bus de Salud (Enterprise Service Bus) serving as the single access point, a Sistema de Auditoría conformant to the IHE ATNA profile, and an Appliance/Conector Salud deployed at each provider that exposes the IHE XDS.b service interface. Each provider — both the public ASSE and the private mutualistas/IAMC of the Sistema Nacional Integrado de Salud (SNIS) — maintains its own institutional electronic record (HCE/HCD) and local document repository, generating standards-based electronic clinical documents (HL7 CDA R2, with HL7 v2 XML messaging, DICOM imaging, and the terminologies SNOMED CT including a Uruguayan national extension, LOINC and CIE-10) and registering each event's metadata in the national Registro de Eventos within 24 hours, enabling assembly of a longitudinal record across the country's mixed public-private landscape and exchange over the dedicated Red Salud network and AGESIC's Plataforma de Interoperabilidad (Interoperabilyty Platform). (https://www.gub.uy/agencia-gobierno-electronico-sociedad-informacion-conocimiento/historia-clinica-electronica-nacional). DRAFT ENTRY B — Governance/institutional and public-private SNIS continuity-of-care emphasis Historia Clínica Electrónica Nacional (HCEN) is Uruguay's nationally governed, federated longitudinal health record (LHR), conceived as the central instrument for continuity of care across the Sistema Nacional Integrado de Salud (SNIS), the country's universal mixed public-private health system. It is delivered by the Salud.uy program, launched in 2012 under an inter-institutional agreement among the Presidency of the Republic, the Ministerio de Salud Pública (MSP), the Ministerio de Economía y Finanzas (MEF) and AGESIC, which provides its institutional home and embeds it within Uruguay's broader digital-state infrastructure — the Plataforma de Gobierno Electrónico and its Plataforma de Interoperabilidad (PDI), the Red Salud private network, and the national digital identity used for citizen and professional authentication — with co-financing of roughly USD 21 million from the Inter-American Development Bank. Adopting a federated model that respects each institution's technological autonomy, the HCEN leaves clinical data in the custody of the public ASSE and the private mutualistas/IAMC that generated it while a state-operated central platform indexes events and brokers their secure, audited exchange, so that a user's information is available to any treating team regardless of provider or location; participation was made mandatory for all public and private providers by Decreto 242/017 (2017), with the adoption plan set by Ordenanza 1085/017, event-registration duties by Decreto 122/019, and provider incorporation by Ley 19.670, all operating within the data-protection guarantees of Ley 18.331 and a treatment-purposes consent model that is implied unless the patient opts out via the "Mi Historia Clínica Digital" citizen portal. Widely cited by the IDB and PAHO as one of Latin America's most advanced national digital-health systems — with 95% of the population holding at least one clinical document by end-2020 and more than 170 million documents registered by 2022 — the HCEN demonstrates how a national interoperability node can knit a fragmented public-private provider landscape into a single longitudinal record centered on the patient/user (https://www.gub.uy/agencia-gobierno-electronico-sociedad-informacion-conocimiento/historia-clinica-electronica-nacional) IADB, (not stated) |
none | not yet | CS-203 discuss | in the document all mentions on GitHub record | ||
| PC-0725✎ edit📣 feedback | received | Core architects ai |
Health Workforce Registry |
Broad feedback: Align the approach more closely with the NHWA framework rather than focusing solely on registries. Heal…Broad feedback: Align the approach more closely with the NHWA framework rather than focusing solely on registries. Health workforce data originate from multiple sources, including HR and payroll systems, professional registers, education systems, censuses, labour force surveys, and sources outside the health sector such as national statistical offices, ministries of finance and higher education, and private institutions. Adopt a comprehensive workforce perspective. The architecture should support data on workforce numbers, distribution, skills, education, inflows and outflows, employment, and future workforce needs—not only registration data. As emphasized in our NHWA training, priority challenges should guide how data are selected and organized. Strengthen the focus on data quality and multi-source integration. The role of triangulation(key to HWF data) should be made more explicit, highlighting the need to combine and validate information from different sources rather than relying on a single system. The architecture should also recognize the importance of analytical and evidence-generation capacities, involving HRH experts and analysts alongside IT specialists. Reinforce governance arrangements, particularly incentives and safeguards for data sharing and data privacy/confidentiality. Private-sector, military, and other stakeholders may require clear benefits, protections, sustainable financing, and differentiated access arrangements before they can contribute data and participate in the architecture. References: NHWA Handbook, [who.int/publications-detail-redirect/national-health-workforce-accounts-implementation-guide]NHWA implementation guide, HWF occupational mapping, HWF terminology WHO, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-0726✎ edit📣 feedback | received | Metadata registries ai |
2.2.2 The enabling conditions for REDDHI l.Area 1 anchor: medium |
Clarifying the Distinct and Complementary Roles of Core Terminology Standards The DPI-H draft correctly identifies SNOM…Clarifying the Distinct and Complementary Roles of Core Terminology Standards The DPI-H draft correctly identifies SNOMED CT, ICD-11, and LOINC as open terminology standards forming the semantic foundation of the Terminology Service component. We welcome this recognition. However, the current text, in particular Section 3.4.5 and the REDDHI Open Standards list, groups these standards as equivalent alternatives without articulating their distinct clinical domains and governance structures. This framing may lead countries to conclude that implementing one standard fulfills the requirement for all, which would produce functionally incomplete national Terminology Services. We recommend the framework include a brief characterisation of each standard's primary clinical scope: ● SNOMED CT provides comprehensive clinical concept coverage: diagnoses, findings, procedures, body structures, substances, and more, enabling semantic interoperability across all domains of clinical care. It is maintained by SNOMED International, an independent not-for-profit standards development organisation operating under a national member model. ● ICD-11, maintained by WHO, is the international standard for mortality and morbidity statistics, disease classification, and reimbursement coding. It is a WHO product and is already mandated in many WHO Member States. ● LOINC, stewarded by the Regenstrief Institute, is the global standard for representing health observations, measurements, survey instruments and documents. Regenstrief Institute is a local, national and global leader dedicated to a world where better information empowers people to end disease and realize true health. ● UCUM stewarded by the Regenstrief Institute is the code system intended to include all units of measures being contemporarily used in international science, engineering, and business. ● HL7 FHIR® (Fast Healthcare Interoperability Resources), published by HL7 International, is the prevailing API-based standard for health data exchange. It provides the technical architecture through which terminology standards are bound to clinical systems, including the FHIR Terminology Service specification referenced in DPI-H Section 3.4.5. We recommend Section 3.4.5 include a brief table or text passage illustrating how these standards operate together within a national Terminology Service deployment, rather than listing them as interchangeable alternatives. 2. SNOMED International; Regenstrief Institute; HL7 International, International |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | ||
| PC-0727✎ edit📣 feedback | received | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure l.Area 2 |
Semantic Governance Infrastructure (SGI) — A Joint Partnership Offer The DPI-H framework introduces Semantic Governance…Semantic Governance Infrastructure (SGI) — A Joint Partnership Offer The DPI-H framework introduces Semantic Governance Infrastructure (SGI) as a new national-level governance architecture and, notably, cites SNOMED International's National Release Center (NRC) model as one of the only tested frameworks for SGI implementation. We commend this recognition of the NRC model as a proven reference. The current text, however, describes SGI as a national responsibility without establishing a formal relationship between national SGI bodies and the international standards organisations that develop and maintain the underlying terminologies. This creates a governance gap: countries may establish SGI processes independently, leading to fragmentation, duplicated effort, and in the absence of international guidance semantic divergence across national implementations. SNOMED International and Regenstrief collectively offer to serve as formal International SGI Reference Partners to WHO and ITU. In practice, this would mean: ● SNOMED International: providing National Release Centre (NRC) governance templates, Snowstorm (open-source FHIR Terminology Server), SNOMED CT Browser, and training resources to countries establishing SGI bodies aligned to the NRC model. ● Regenstrief Institute: providing a LOINC Terminology FHIR Service, with resources that include code system, value set, concept map and questionnaire. Regenstrief also provides LOINC Panels and Forms,UCUM specifications and education and training guidance and laboratory for countries establishing national observation and units of measure catalogues within their SGI. We propose that the DPI-H framework explicitly recognise our two organisations as reference implementation partners for SGI, and that WHO/ITU establish a formal Technical Advisory Group comprising representatives of SNOMED International, Regenstrief Institute, the WHO, and additional Standards Development Organization participation, such as HL7 International, to develop SGI implementation guidance for national programmes. 3. SNOMED International; Regenstrief Institute; HL7 International, International |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-0728✎ edit📣 feedback | received | Metadata registries ai |
3.7 Conformance and Testing across Architecture and Components l.Area 3 anchor: medium |
FHIR Terminology Conformance: A Ready-Made Testing Framework Section 3.7 of the DPI-H draft describes a testable, machi…FHIR Terminology Conformance: A Ready-Made Testing Framework Section 3.7 of the DPI-H draft describes a testable, machine-readable architecture in which national implementations are verified against published conformance profiles. This is precisely the architecture that the HL7 FHIR Terminology Service specification was designed to support. SNOMED International and Regenstrief Institute acknowledge and support that HL7 International has published a mature FHIR Terminology Service capability model, including operations for CodeSystem lookup, ValueSet expansion, and concept translation, each of which maps directly to the DPI-H Terminology Service functions described in Section 3.4.5. Additionally, SNOMED International's Snowstorm server and Regenstrief's LOINC FHIR Terminology Service both implement this specification and are available as open-source reference implementations. We recommend that: ● The DPI-H conformance framework (Section 3.7) explicitly reference the HL7 FHIR Terminology Service specification (HL7 FHIR R4/R5, http://hl7.org/fhir/terminology-service.html) as the baseline conformance model for national Terminology Service implementations. ● We recommend that the organizations be invited to jointly develop a DPI-H Terminology Service Conformance Profile that countries can use to verify their implementations against the DPI-H standard. ● WHO/ITU consider an open reference implementation programme, in which nationally deployed instances of Snowstorm (SNOMED CT) and the LOINC FHIR API are certified as conformant reference implementations. 4. SNOMED International; Regenstrief Institute; HL7 International, International |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | ||
| PC-0729✎ edit📣 feedback | received | Metadata registries ai |
Terminology Service l.Area 4 anchor: medium |
Open Access for Low- and Middle-Income Countries DPI-H is explicitly designed to support countries at all stages of dig…Open Access for Low- and Middle-Income Countries DPI-H is explicitly designed to support countries at all stages of digital health maturity, with particular focus on low- and middle-income countries (LMICs). The framework's Terminology Service requirement must therefore be achievable without prohibitive licensing costs. We note that an open access pathway already exists across our two organisations' standards, and we recommend that the DPI-H framework make this explicit: ● SNOMED International's SNOMED CT Global Patient Set (GPS) is freely available to all countries regardless of membership status, providing a clinically curated subset of SNOMED CT for use in LMIC settings without licensing cost. Corrections on inaccurately stated GPS information within the DPI-H will be submitted in the formal SNOMED International individual response. ● LOINC is available at no charge under an open license, It is available for use in commercial and non-commercial in accordance with terms of use provisions. ● UCUM is available at no charge under an open license available for use in commercial and non-commercial in accordance with terms of use provisions. We recommend Section 3.4.5 and the REDDHI Open Standards annex include explicit reference to the GPS as the LMIC-accessible entry point for SNOMED CT, and that the Licensing footnote (currently footnote 47 in the draft) be expanded to articulate the full open access pathway across SNOMED CT and LOINC. Conclusion Regenstrief and SNOMED International steward terminology and interoperability standards collectively used in over 80 countries and deployed in hundreds of millions of patient records worldwide. We have each independently arrived at a shared conviction: the DPI-H framework is a significant and timely contribution to global health informatics, and it deserves a robust, internationally coordinated implementation architecture. In this letter, we do not write to advocate for the interests of any single organisation. We write to offer the collective technical capacity of the global health standards community, freely and in partnership, to help WHO and ITU translate this ambitious framework into working national infrastructure. We would welcome the opportunity to meet with the DPI-H technical team at a mutually convenient time to discuss this response in depth, and we stand ready to contribute to any joint technical working group WHO and ITU may convene. We submit this response in the spirit of the collaborative, multilateral, open-standards approach that DPI-H itself espouses. Respectfully submitted, SNOMED International ____________________________ Don Sweete, Chief Executive Officer SNOMED International [email removed] Regenstrief Institute (LOINC) ____________________________ Marjorie Rallins, Executive Director, Health Data Standards Regenstrief Institute [email removed] This response is submitted to the WHO/ITU DPI-H public consultation. It represents the collective views of SNOMED International and the Regenstrief Institute with support from HL7 International. It does not constitute the individual policy positions of any single member organisation of HL7 International or the membership of SNOMED International. Enquiries may be directed to the contacts below. SNOMED International contact: Kelly Kuru, Chief Executive Communications & Collaborations | [email removed] Regenstrief International contact: Marjorie Rallins, Executive Director, Health Data Standards | [email removed] SNOMED International; Regenstrief Institute; HL7 International, International |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-0730✎ edit📣 feedback | received | No human |
C Appendix C: DPI-H Application Component Descriptions §1. Whole document; Appendix C – Terminology Service (pp. 164–171) l.#1 anchor: medium |
The draft correctly identifies LOINC as one of the core internationally recognized terminologies a national Terminology…The draft correctly identifies LOINC as one of the core internationally recognized terminologies a national Terminology Service (TS) must host and manage, alongside ICD-11 and SNOMED CT/GPS, and the glossary definition accurately reflects LOINC's full scope (measurements, observations, and documents — not laboratory results alone). Suggested revision: No change requested. Noted as a strength worth preserving in future revisions. Regenstrief Institute (LOINC, UCUM), United States |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0731✎ edit📣 feedback | received | Metadata registries ai |
C Appendix C: DPI-H Application Component Descriptions §2. Appendix C – “Federation and alignment with international sources” (p. 166) and Governance item (5), “International coordination” (p. 171) l.#2 anchor: medium |
Regenstrief Institute, LOINC's steward, is named alongside SNOMED International, SNOMED CT’s steward and WHO-FIC as an …Regenstrief Institute, LOINC's steward, is named alongside SNOMED International, SNOMED CT’s steward and WHO-FIC as an anchor body for federation and international coordination — the only place LOINC's governing organization is identified. This requirement is classed “Recommended,” not “Required,” and the text does not describe how synchronization with LOINC releases, or submission of national term requests to Regenstrief, would work in practice. Suggested revision: Elevate federation/synchronization for the three core terminologies (ICD-11, SNOMED CT, LOINC) from Recommended to Required, consistent with how code system and value set versioning were elevated elsewhere in the same appendix. Add a short explanatory note describing LOINC's release cadence and Regenstrief's process for receiving national/local term submissions. Regenstrief Institute (LOINC, UCUM), United States |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-0732✎ edit📣 feedback | received | Metadata registries ai |
C Appendix C: DPI-H Application Component Descriptions §3. p. 29 footnote (standards licensing); Appendix C – “Licensing management” and Governance item (4), “Licensing obligations” (pp. 166–171) l.#3 anchor: medium |
The document devotes a footnote and two governance provisions to SNOMED CT's licensing model and national member-fee ob…The document devotes a footnote and two governance provisions to SNOMED CT's licensing model and national member-fee obligations but never notes that LOINC is freely available worldwide at no cost, with no membership requirement. This asymmetry could leave national planners with the impression that all three core terminologies carry licensing costs. Suggested revision: Add a parallel footnote or sentence clarifying that LOINC is released under a, open license with no license fee, so that licensing/budget implications are distinguished clearly across the three core terminologies. Regenstrief Institute (LOINC, UCUM), United States |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-0733✎ edit📣 feedback | received | Metadata registries ai |
Logical Information Model Repository §4. §3.5.3.2, LIMR/TS comparison table – blood- pressure worked example (pp. 68–70) l.#4 anchor: medium |
The document's only detailed worked example involving LOINC treats it purely as the downstream target of a concept map …The document's only detailed worked example involving LOINC treats it purely as the downstream target of a concept map from a SNOMED CT concept (271649006 → LOINC 8480-6), rather than as a primary code system with its own structure (panels, question/answer conventions, document and observation typing). This may understate LOINC's role as a first-class terminology. Suggested revision: Add a second worked example in which LOINC is the primary code system — e.g., a laboratory order/result or clinical document use case — to balance the SNOMED-CT-first framing of the existing example. Regenstrief Institute (LOINC, UCUM), United States |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-0734✎ edit📣 feedback | received | Metadata registries ai |
C Appendix C: DPI-H Application Component Descriptions §5. §3.5.3.2 concept-map example (pp. 68–70); Appendix C – “Concept map management” (p. 165) l.#5 anchor: medium |
The SNOMED CT–to–LOINC concept-map example effectively re-derives a mapping relationship without reference to the exist…The SNOMED CT–to–LOINC concept-map example effectively re-derives a mapping relationship without reference to the existing, LOINC Ontology: LOINC- SNOMED CT Interoperability Solution already published by Regenstrief and SNOMED International Suggested revision: Add a citation/footnote pointing implementers to the existing LOINC Ontology: LOINC-SNOMED CT Interoperability Solution so national teams build on established work rather than re-mapping independently. Regenstrief Institute (LOINC, UCUM), United States |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | ||
| PC-0735✎ edit📣 feedback | received | Editorial ai |
2.2.2 The enabling conditions for REDDHI §6. Document- wide – footnotes and citations l.#6 anchor: medium |
The document footnotes URLs for WHO SMART Guidelines, the SNOMED CT licensing note, the OpenHIE Terminology Service spe…The document footnotes URLs for WHO SMART Guidelines, the SNOMED CT licensing note, the OpenHIE Terminology Service specification, and the IHE SVCM specification, but includes no citation or link to LOINC (loinc.org) or to Regenstrief Institute. Suggested revision: Add a footnote citing loinc.org (and Regenstrief Institute's role as steward) at first mention of LOINC, consistent with the citation treatment given to the other named standards and specifications. Regenstrief Institute (LOINC, UCUM), United States |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | ||
| PC-0736✎ edit📣 feedback | received | Metadata registries ai |
C Appendix C: DPI-H Application Component Descriptions §7. Appendix C – “Value set management” and “Core attributes” (pp. 165, 167–168) l.#7 anchor: medium |
LOINC's own conventions for panels and standardized answer lists (LOINC Answer List / LL codes) are not mentioned, even…LOINC's own conventions for panels and standardized answer lists (LOINC Answer List / LL codes) are not mentioned, even though the Value Set Management requirements (intensional/extensional value sets) apply directly to how LOINC panels and answer lists are represented and consumed in practice. Suggested revision: Add a brief note under “Value set management” citing LOINC panels and standardized answer lists as a concrete example, alongside the existing SNOMED CT/ICD examples. Regenstrief Institute (LOINC, UCUM), United States |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | ||
| PC-0737✎ edit📣 feedback | received | Editorial ai |
3.5.3.1 The foundational shared data layer §8. General – ordering convention throughout the document Closing We appreciate WHO's opportunity to comment including example finalization. Please l.#8 anchor: medium |
In every list pairing the three core terminologies, LOINC consistently appears last (“SNOMED CT, ICD-11, LOINC” or “ICD…In every list pairing the three core terminologies, LOINC consistently appears last (“SNOMED CT, ICD-11, LOINC” or “ICD-11, SNOMED CT, LOINC”). Combined with the LOINC-as-downstream-example pattern noted in Comment 4, this may cumulatively read as treating LOINC as secondary. continued leadership in developing shared digital on this draft. We would welcome the opportunity content, worked mappings, or review of subsequent direct any follow-up questions to the contact listed Suggested revision: No substantive change needed; noted for awareness. Varying the ordering in a future revision or stating explicitly that no priority is implied by list order, would remove any ambiguity. health infrastructure and the to provide further technical input — drafts — as this guidance moves toward above. Regenstrief Institute (LOINC, UCUM), United States |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0738✎ edit📣 feedback | received | Core architects ai |
1.5.1 The Health Sector Goals §§1.5.1 Goal 3 & App. E (p.22, 236–237); cf. §3.6.1 (p.73) l.C1 anchor: medium |
§3.6 already provides shared data exchange — distributed mediation, eventing, a participant registry — and we support i…§3.6 already provides shared data exchange — distributed mediation, eventing, a participant registry — and we support it. What no component owns is following a commitment through: tracking whether a referral was actioned, noticing the follow-up that never happens, closing the loop. §3.6.1 lists "orchestrating a multi-step transaction" among the mediation functions, but that routes one exchange in flight — not a commitment's lifecycle across time: a referral (accepted → attended → outcome, or the follow-up that never comes) or a claim (eligibility → pre-auth → settlement, or the claim that stalls). Goal 3 asks for exactly this ("coordinate care over time… while tracking adherence and quality"), but the draft folds it into the CDSE and into "care-coordination and referral tools" outside DPI-H. We recommend recognising this as a shared capability, distinct from decision support. The §2.1.1 test for shared infrastructure — reusable, stable interface, no lock-in, foundational not programme-specific — is met by it. We mean the shared exchange between systems — not every consuming application (an EMR or a payroll system is rightly application-layer). (On whether such a capability may be transactional, see C2.) It makes breaks in continuity visible; it does not assume the digital layer can resolve the underlying service-delivery constraint — a vacancy, or a lack of capacity — and it should be designed for real conditions: intermittent connectivity, workforce gaps, weak supervision, and incomplete facility-capability information. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-256 discuss | in the document all mentions on GitHub record | ||
| PC-0739✎ edit📣 feedback | received | Core architects ai |
3.1 The architecture description approach §Box 3.1 & §3.5.1 (p.63–64); cf. §1.2.3 (p.16), §3.6.3 (p.75) l.C2 anchor: medium |
Box 3.1 requires DPI-H components to be "non-transactional… not point-of-care workflow engines or clinical transaction …Box 3.1 requires DPI-H components to be "non-transactional… not point-of-care workflow engines or clinical transaction processors." The concern is sound — shared infrastructure should not concentrate control, or make its operator accountable for clinical or financial decisions(§3.6.3) — but the rule is too broad. The draft's own foundational example, payments DPI ("rails for moving money securely and at scale between parties", §1.2.3), is transactional and is bedrock public infrastructure; it meets the concern by keeping settlement and balances with the banks. A coordination or claims fabric (C1, C3) works the same way — it carries the transaction and keeps processing and authoritative decisions with the participants. The draft's own architecture already contains a stateful, lifecycle-tracking DPI-H component: the Public Health Surveillance Platform does "case registration and management… outcome tracking" and contact "follow-up" — so the criterion is not even applied consistently within DPI-H today. We recommend refining the criterion: a DPI-H component may carry transactions provided it keeps processing and control with the participants rather than concentrating them. The other Box 3.1 tests — shared, reusable, publicly governed, open, technology-neutral — continue to hold the boundary. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0740✎ edit📣 feedback | received | Core architects ai |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §§2.4.2 financing (p.39); §4.3.4 (p.98) l.C3 anchor: medium |
The same pattern in financing. The draft says "only one genuinely new DPI-H component emerges from the financing analys…The same pattern in financing. The draft says "only one genuinely new DPI-H component emerges from the financing analysis: the Benefits Package Registry," and its appendix places the Contract & Benefits Management System — which "processes claims and contributions" — explicitly outside DPI-H, as a "functional application." We agree the processing belongs there. But a claim also runs a lifecycle across autonomous payers and providers — coverage/eligibility, pre-authorisation, submission, adjudication, settlement — and nothing owns the shared exchange that carries it between them and flags a stall. That exchange — protocol, directory, trust, governance — is the fabric we mean; adjudication and payment stay with the parties (a DPI-H construct on the refined criterion in C2). We are not asking for the claims-processing system to be DPI-H, and this is not a central claims switch. We recommend recognising the shared claims-exchange fabric as a DPI-H construct. One fabric idea covers coordination and claims. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | ||
| PC-0741✎ edit📣 feedback | received | Core architects ai |
E Appendix E: Health Goals to DPI Mapping §Supply-chain goal; Product & Supplier Registries (App. C) l.C3a anchor: medium |
The same pattern a third time, in the supply chain. The Product and Supplier Registries are DPI-H components, but "the …The same pattern a third time, in the supply chain. The Product and Supplier Registries are DPI-H components, but "the operational systems that run the supply chain — forecasting, order, warehouse, procurement, transport, and dispensing applications" sit outside DPI-H. Yet a requisition runs a lifecycle across supplier → warehouse → facility (order → dispatch → transport → receipt), and nothing tracks it to completion or flags a stall. This shows the draft's boundary choice — shared registries as DPI-H, dynamic multi-party exchange as application-layer — recurring across clinical care, financing, and supply chain. We recommend recognising the shared exchange fabric (C1, C2) as applying to all three, rather than treating exchange as an application concern in each domain separately. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-0742✎ edit📣 feedback | received | Clinical ai |
Computable Decision Support Engine §App. C — CDSE, "Care coordination" row (p.181, 184–188) l.C4 |
Illustrates C1 in the clinical instance. The draft's only new Goal-3 component is the CDSE, and it labels one CDSE feat…Illustrates C1 in the clinical instance. The draft's only new Goal-3 component is the CDSE, and it labels one CDSE feature "Care coordination." The CDSE is stateless and fires at the point of care, so it cannot detect a non-event — the referral no one actions, the follow-up that never closes. We recommend (a) renaming that feature "Care-plan and pathway guidance," and (b) stating that the CDSE does not coordinate care across systems or over time — pointing to C1. We support the CDSE, scoped to decision support. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-069 discuss | in the document all mentions on GitHub record | ||
| PC-0743✎ edit📣 feedback | received | Core architects ai |
3.5.3 How the components are organised §§3.5.3 taxonomy; CDSE↔HMIS (p.66–70, 184–185) l.C5 anchor: medium |
The draft has a component for the individual at the point of care (CDSE) and one for the population in aggregate (HMIS)…The draft has a component for the individual at the point of care (CDSE) and one for the population in aggregate (HMIS). A third job sits between them: tracking one person's care commitments across systems and over time. No component owns it. We recommend naming this layer and placing the C1 capability in it. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-069 discuss | in the document all mentions on GitHub record | ||
| PC-0744✎ edit📣 feedback | received | Core architects ai |
1.4 DPI-H Principles §§1.4 Autonomy & Sovereignty (p.21); Box 3.1 technology- neutral (p.64) l.C6 anchor: medium |
Two faces of one point. (a) "Autonomy and Sovereignty" can be read as building and operating everything nationally, whi…Two faces of one point. (a) "Autonomy and Sovereignty" can be read as building and operating everything nationally, which defeats reuse and cost-control; we suggest clarifying that it means choice, control, and exit/migration rights, in line with the Reusability and Public Governance principles. (b) "Technology-neutral" covers neutral specification and standard interfaces — already in the §3.5.1 bullets — but not the implementation. A neutral spec on a proprietary stack still locks a country in. We recommend adding that implementations use open, non-proprietary technology. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | ||
| PC-0745✎ edit📣 feedback | received | Core architects ai |
1.5 The Seven Priority Health Sector Goals §§1.5 "Governed well" (p.21); principle VIII (p.34) l.C7 anchor: medium |
The counterweight to "capture once, use many times" is missing where it is introduced. REDDHI is Resilient Essential Da…The counterweight to "capture once, use many times" is missing where it is introduced. REDDHI is Resilient Essential Data; "Essential" now governs only the floor (data that must exist). We suggest extending it to the ceiling too — capturing and sharing only what is essential, minimised at source. Principle VIII already makes minimisation the default "with any departure justified" (p.34); the goals narrative and the central-pull data flows read as unjustified departures. We recommend naming minimisation, purpose-limitation, and need-based disclosure in the "Governed well" framing, and preferring minimisation at source. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-100 discuss | in the document all mentions on GitHub record | ||
| PC-0746✎ edit📣 feedback | received | Core architects ai |
3.4 Governance of Digital Health Architectures and DPI-H §Governanc e principle I (p.31); §3.4 (p.53–63) l.C8 anchor: medium |
Governance is framed around data quality; §3.4 says nothing about privacy, consent, minimisation, purpose-limitation, o…Governance is framed around data quality; §3.4 says nothing about privacy, consent, minimisation, purpose-limitation, or access control (those live only in principles VIII–IX). We recommend treating data protection as a core governance dimension alongside data quality — good governance answers not only "is the data good?" but "is it collected, shared, and accessed lawfully, minimally, and with consent?" CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | ||
| PC-0747✎ edit📣 feedback | received | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §§2.3 principle VIII (p.35); component set (App. C) l.C8a anchor: medium |
Consent runs through the draft — it "should be represented in a common, standards-based form and carried with the data …Consent runs through the draft — it "should be represented in a common, standards-based form and carried with the data it governs as that data moves between systems" — yet it appears only as a design principle: "a health-sector consent capability may be needed" (§2.3, VIII). It is never a named shared component alongside the registries. Given data protection as a governance dimension (C8), minimisation (C7), and that a coordination or claims fabric must carry consent with each handoff, we recommend recognising a shared consent capability — granular, revocable, carried-with-data — as a DPI-H component in its own right, rather than a "may be needed" aside. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-235 discuss | in the document all mentions on GitHub record | ||
| PC-0748✎ edit📣 feedback | received | Core architects ai |
3.4.2 Governance principles §§3.4.2 "Prevention of resource overuse" (p.54–55) l.C9 anchor: medium |
This principle is framed mainly as rationing, which concedes scarcity where the first answer is often to grow capacity.…This principle is framed mainly as rationing, which concedes scarcity where the first answer is often to grow capacity. But capacity and funding constraints are real — especially at state and district level — so scaling cannot always meet demand. We recommend designing for scale and graceful degradation: scaling (elastic and distributed) where capacity can grow, funded by usage-linked contribution; degrading gracefully rather than locking users out where resources are genuinely finite; and guarding against abuse rather than legitimate use (e.g. changing "protected from overuse" (p.55) to "protected from abuse"). CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-050 discuss | in the document all mentions on GitHub record | ||
| PC-0749✎ edit📣 feedback | received | Core architects ai |
5.2 Why data foundations determine what AI can deliver §§5.2 AI foundations (p.105–106 ) l.C10 anchor: medium |
The AI-foundations list leans on longitudinal data but omits the time dimension of semantics. Terminologies and models …The AI-foundations list leans on longitudinal data but omits the time dimension of semantics. Terminologies and models change over the span longitudinal data covers; without version-aware, point-in-time semantics and cross-version mappings, models inherit drift along the time axis. We recommend adding versioning and temporal consistency as an explicit AI foundation. The draft already has the primitives — Terminology/LIMR versioning, point-in-time benefit definitions. This should also extend to deterministic services whose definitions change over time. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-119 discuss | in the document all mentions on GitHub record | ||
| PC-0750✎ edit📣 feedback | received | Core architects ai |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §§4.3.3 FHIR (p.96); §3.6, §2.3 Open Standards (p.71–77, 32) l.C11 anchor: medium |
We support FHIR for records, summaries, and the LHR. Coordinating between autonomous systems is a network problem — dis…We support FHIR for records, summaries, and the LHR. Coordinating between autonomous systems is a network problem — discovery, capability catalog, multi-party contract with state — for which network protocols can fit better than record-exchange standards. And "open-standards compliance" should not be read as "FHIR" (other open standards exist). We recommend framing interoperability as protocol-appropriate-to-function. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-0751✎ edit📣 feedback | received | Core architects ai |
2.3 DPI-H Reference Architecture Design Principles §§2.3 principles VIII–IX (p.31–36) l.C12 anchor: medium |
A coordination capability can confirm that a handoff happened without revealing the clinical content — carrying the eve…A coordination capability can confirm that a handoff happened without revealing the clinical content — carrying the event and its state, not the record. This is a concrete form of the draft's own minimisation and privacy-by-design, and removes a class of consent risk. We recommend naming metadata-/attestation-only coordination as a reference privacy pattern. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-015 discuss | in the document all mentions on GitHub record | ||
| PC-0752✎ edit📣 feedback | received | Core architects ai |
4.4 Measuring Progress and Impact §§4.4 Measuring Progress (p.98–99) l.C13 anchor: medium |
Goal 3 sets no coordination measure. We recommend adding follow-up / referral completion as a Goal-3 indicator — the mo…Goal 3 sets no coordination measure. We recommend adding follow-up / referral completion as a Goal-3 indicator — the most actionable coordination measure. In one real network, only ~7% of referrals were completed (4,707 of 67,478). Completion is an operational, leading measure, not the end in itself: where feasible it should be linked to downstream service delivery and outcomes — whether the person received the appropriate service in time, and whether continuity of care improved. A shared capability makes this visible and improvable. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | ||
| PC-0753✎ edit📣 feedback | received | Core architects ai |
1.2.1 Identity DPI and Identification in Healthcare §§1.2.1 & Box 1.2 (p.13–14) l.C14 anchor: medium |
The draft does not mandate a central health ID — Box 1.2 (pt 5) allows multiple context-specific identifiers, and the C…The draft does not mandate a central health ID — Box 1.2 (pt 5) allows multiple context-specific identifiers, and the Client Registry allows centralised, federated, or hybrid implementation as an EMPI over local IDs (p.67, 115, 117). But this is clear only in Ch.3 and App. C. We recommend surfacing the federated/multi-identifier stance in §1.2.1/Box 1.2 so a reader does not infer a single central health ID. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-009 discuss | in the document all mentions on GitHub record | ||
| PC-0754✎ edit📣 feedback | received | Metadata registries ai |
3.4.5 Semantic Governance Infrastructure §§3.4.5 Global/national/local content (p.61) l.C15 anchor: medium |
The draft warns that "a maximalist global model… will not be adopted," but does not state the positive rule. We recomme…The draft warns that "a maximalist global model… will not be adopted," but does not state the positive rule. We recommend adding it: keeping the shared core minimal, and reaching through governed national/local extension. A minimal core is what enables the extensibility the draft wants; the maturity spectrum can reference it. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-0755✎ edit📣 feedback | received | Core architects ai |
3.7 Conformance and Testing across Architecture and Components §§3.7 Conformance and Testing (p.78–86) l.C16 anchor: medium |
The conformance model is presented as the model (an ArchiMate-typed formalism). Other valid conformance ecosystems exis…The conformance model is presented as the model (an ArchiMate-typed formalism). Other valid conformance ecosystems exist (IHE, FHIR IG testing). We recommend presenting §3.7 as a reference model — alternatives acceptable where they meet the objectives and map to the reference, in line with the draft's own "adopt, adapt, or map" language (§3.7.1). CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-0756✎ edit📣 feedback | received | Core architects ai |
3.4.2 Governance principles §§3.4.2 Subsidiarity bullet (p.54) l.C17 anchor: medium |
The bullet's second sentence describes separation of mandate and execution — the next bullet — and partly the converse …The bullet's second sentence describes separation of mandate and execution — the next bullet — and partly the converse of subsidiarity. We recommend keeping Subsidiarity to "authority at the lowest effective level," and moving the operational-vs-strategic matching into "Separation of mandate and execution." CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-050 discuss | in the document all mentions on GitHub record | ||
| PC-0757✎ edit📣 feedback | received | Core architects ai |
4.2.4 The Role of the National Digital Architect §Ch.4; §4.2.4 National Digital Architect (p.88–103) l.C18 |
We support the National Digital Architect as a lasting in-government role. We recommend also naming a transitional comp…We support the National Digital Architect as a lasting in-government role. We recommend also naming a transitional composition/integration ("weaver") function that assembles DPGs into a working national stack and owns the seams before a national curator exists, handed off as capacity grows. WHO supplies the blueprint; composing it into a working, accountable stack is a distinct capability. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | ||
| PC-0758✎ edit📣 feedback | received | Editorial ai |
3.5.3.1 The foundational shared data layer §§3.5.3.1 LHR bullet (p.67) l.Ed1 anchor: medium |
The Lifelong Health Record sentence carries editing residue — a trailing fragment "person-centred that," a duplicated "…The Lifelong Health Record sentence carries editing residue — a trailing fragment "person-centred that," a duplicated "capability that that maintains," and a repeated "It is defined to allow centralised, federated, or hybrid…" clause. We recommend cleaning the full sentence. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | CS-060 discuss | in the document all mentions on GitHub record | ||
| PC-0759✎ edit📣 feedback | received | No human |
1.4 DPI-H Principles §§1.4 DPI-H Principles (p.20) l.A1 anchor: medium |
We agree. Interoperability, reusability, open standards, public governance, security/privacy, sovereignty — all match o…We agree. Interoperability, reusability, open standards, public governance, security/privacy, sovereignty — all match our position. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0760✎ edit📣 feedback | received | No human |
2.2 Resilient Essential Data and Digital Health Infrastructure (REDDHI) §§2.2 REDDHI (p.26–30) l.A2 anchor: medium |
We agree, strongly. REDDHI as a condition of self-sustaining maturity, not a product to procure; "no country starts fro…We agree, strongly. REDDHI as a condition of self-sustaining maturity, not a product to procure; "no country starts from zero." CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0761✎ edit📣 feedback | received | No human |
1.3.1 The Cost of Fragmentation §§1.3.1 Cost of Fragmentation (p.17) l.A3 anchor: medium |
We agree with the quadratic-cost-of-fragmentation argument — and note it applies to coordination, not only data exchang…We agree with the quadratic-cost-of-fragmentation argument — and note it applies to coordination, not only data exchange (supports C1–C3). CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0762✎ edit📣 feedback | received | No human |
Logical Information Model Repository §App. C — Terminology, LIMR, SMART Guidelines L3 (p.164–180) l.A4 anchor: medium |
We support this. Governing clinical knowledge apart from the apps that use it answers the "guidelines locked in PDFs" p…We support this. Governing clinical knowledge apart from the apps that use it answers the "guidelines locked in PDFs" problem. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0763✎ edit📣 feedback | received | No human |
2.3 DPI-H Reference Architecture Design Principles §§2.3 Interoperability (p.32); §3.6.1 (p.72); §3.4.2 (p.54–55) l.A5 anchor: medium |
We thank the authors for this. Interoperability as a distributed capability, not a central box. The line between integr…We thank the authors for this. Interoperability as a distributed capability, not a central box. The line between integration and interoperability — "bilateral connections… do not scale nationally." The warning that deferring interoperability or creating central dependencies breeds technical and political debt. These match our implementation experience. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0764✎ edit📣 feedback | received | No human |
3.5 DPI-H Application Components §§3.5 registries (p.65); §3.5.3.1 LHR (p.67); Client Registry (App. C); §3.6.4 (p.77) l.A6 anchor: medium |
We agree. A single authoritative source is a governance property, not a deployment topology; registries and the LHR may…We agree. A single authoritative source is a governance property, not a deployment topology; registries and the LHR may be centralised, federated, or hybrid. Cross-border exchange follows the same pattern — data held nationally, exchanged on demand, no central supranational store (§3.6.4). CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0765✎ edit📣 feedback | received | No human |
2.3 DPI-H Reference Architecture Design Principles §§2.3 Sustainability (p.33); §4.2 phased path (p.89–93) l.A7 anchor: medium |
We support this. Shared investment over duplication; demonstrable value; standards and technologies in-country teams ca…We support this. Shared investment over duplication; demonstrable value; standards and technologies in-country teams can maintain and evolve; a phased, entry-point-aware path to REDDHI. CoWEAVE - Medtronic LABS; eGov Foundation; Open Healthcare Network Foundation, International |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-0766✎ edit📣 feedback | received | Editorial agent |
unplaced §Whole document p.Whole document l.Whole document |
Excessive use of em dashes ("—") throughout the document.Excessive use of em dashes ("—") throughout the document. The writing style appears overly AI-generated and can feel unnatural to readers. Suggested revision: Replace unnecessary em dashes with standard punctuation (full stops, commas, semicolons) and revise sentence structure where appropriate to achieve a more natural, professional tone.Aidaa Michael Anywar, EY DHEC, Germany |
none | not yet | CS-283 discuss | all mentions on GitHub record | ||
| PC-0767✎ edit📣 feedback | received | Core architects WHO agent, medium |
1.1.1 What is a reference architecture, and why does it matter for the health sector? §1.1.1 p.19 l.Lines 14-18 |
Describing the reference architecture as an “authoritative reference point” could imply that countries are expected to …Describing the reference architecture as an “authoritative reference point” could imply that countries are expected to conform normatively to every element, whereas the document later describes it as adaptable and non-prescriptive. Suggested revision: Replace “authoritative reference point” with “common reference point,” or clarify the extent to which the architecture is intended to be normative. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-008 discuss | in the document all mentions on GitHub record | ||
| PC-0768✎ edit📣 feedback | received | Core architects agent, medium |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §1.1.2 p.20 l.Lines 56-61 |
The DPI-H definition is presented as settled terminology, although DPI-H is still an evolving concept and the precise b…The DPI-H definition is presented as settled terminology, although DPI-H is still an evolving concept and the precise boundary of health-specific public infrastructure is not universally established. Suggested revision: Introduce it as the working definition adopted by this guidance. For example: “For the purposes of this guidance, DPI-H refers to…” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-007 discuss | in the document all mentions on GitHub record | ||
| PC-0769✎ edit📣 feedback | received | Core architects agent |
1.1.2 Understanding Digital Public Infrastructure (DPI) and health Digital Public Infrastructure (DPI-H) §1.1.2 p.20 l.Lines 57-61 |
The definition requires DPI-H to be “publicly governed,” but the minimum attributes of public governance are not specif…The definition requires DPI-H to be “publicly governed,” but the minimum attributes of public governance are not specified. This may lead countries to interpret public ownership, public operation, and public accountability as equivalent. Suggested revision: Add a concise definition covering public authority over policy, access conditions, change control, audit rights, service obligations, data portability, and supplier exit arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-007 discuss | in the document all mentions on GitHub record | ||
| PC-0770✎ edit📣 feedback | received | Core architects agent |
1.2 Why health needs more than foundational DPI §1.2 p.24 l.Lines 173-184 |
Foundational DPI is repeatedly presented as identity, payments, and data exchange. These are common DPI categories, but…Foundational DPI is repeatedly presented as identity, payments, and data exchange. These are common DPI categories, but the formulation may be read as an exhaustive taxonomy and excludes trust services, digital credentials, consent, geospatial infrastructure, and notification services that some countries may treat as foundational. Suggested revision: Clarify that identity, payments, and data exchange are the principal foundational DPI categories considered by this guidance, but that national DPI portfolios may include additional shared capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-011 discuss | in the document all mentions on GitHub record | ||
| PC-0771✎ edit📣 feedback | received | Core architects agent |
1.2.1 Identity DPI and Identification in Healthcare §1.2.1 p.25 l.Box 1.2 anchor: medium |
The Client Registry is described as the health sector’s “identity DPI.” This risks collapsing several distinct health-i…The Client Registry is described as the health sector’s “identity DPI.” This risks collapsing several distinct health-identity capabilities into one component, including identity resolution, authentication, credentials, consent, assurance, and trust services. Suggested revision: Describe the Client Registry as the health sector’s authoritative person-identity resolution and cross-referencing component, which works with foundational identity, authentication, consent, and national trust infrastructure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-009 discuss | in the document all mentions on GitHub record | ||
| PC-0772✎ edit📣 feedback | received | Core architects agent |
1.2.2 Data exchange DPI and Interoperability in the health sector §1.2.2 p.26 l.Lines 211 - 223 and Box 1.3 |
The section covers technical, structural, and semantic interoperability but gives limited attention to process or workf…The section covers technical, structural, and semantic interoperability but gives limited attention to process or workflow interoperability. Correctly formatted and coded data may still be unusable if the receiving organisation cannot incorporate it into its operational workflow. Suggested revision: Add organisational and workflow interoperability explicitly, including alignment of roles, processes, responsibilities, and operational responses to exchanged information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-0773✎ edit📣 feedback | received | technical | Core architects agent, medium |
1.3.1 The Cost of Fragmentation §1.3.1 p.28 l.Lines 283-290 |
The statement that the economic cost of fragmentation “grows quadratically” is only strictly valid under an all-to-all …The statement that the economic cost of fragmentation “grows quadratically” is only strictly valid under an all-to-all point-to-point integration model. Not every system necessarily connects to every other system. Suggested revision: Qualify the claim: “In the worst case, a point-to-point integration landscape can approach quadratic growth as the number of connected systems increases.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-013 discuss | in the document all mentions on GitHub record | |
| PC-0774✎ edit📣 feedback | received | Core architects agent |
1.4 DPI-H Principles §1.4 and 2.3 p.31 - 32 and 42 - 48 l.Sections 1.4 and 2.3 anchor: medium |
The DPI-H principles in Section 1.4 and the architecture design principles in Section 2.3 overlap considerably, particu…The DPI-H principles in Section 1.4 and the architecture design principles in Section 2.3 overlap considerably, particularly for interoperability, governance, security, sovereignty, openness, and sustainability. The distinction between the two sets is explained but remains difficult to apply. Suggested revision: Consolidate them into a structured hierarchy of public-interest principles, architecture principles, and implementation principles, or provide a mapping table showing how every DPI-H principle is operationalised by the design principles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-017 discuss | in the document all mentions on GitHub record | ||
| PC-0775✎ edit📣 feedback | received | WHO Core architects agent, low |
1.5 The Seven Priority Health Sector Goals §1.5 p.32 - 34 l.Lines 423-516 |
The seven priority health-sector goals provide a useful organising framework, but the method used to select exactly the…The seven priority health-sector goals provide a useful organising framework, but the method used to select exactly these seven goals is not sufficiently transparent in this section. Suggested revision: Summarise the selection method, evidence base, consultation process, alternatives considered, and rationale for treating leadership and governance as a principle rather than a separate goal. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-023 discuss | in the document all mentions on GitHub record | ||
| PC-0776✎ edit📣 feedback | received | Core architects agent |
DPI-H Reference Architecture Framework §Chapter 2 introduction p.24 l.Lines 3-11 anchor: low |
The introduction appropriately describes the architecture as adaptive and non-prescriptive. However, “engage with at th…The introduction appropriately describes the architecture as adaptive and non-prescriptive. However, “engage with at the level that is relevant to them” is vague and does not explain whether countries may omit components, alter relationships, or redefine component boundaries. Suggested revision: Clarify the permissible forms of adaptation. For example: “Countries may adopt, adapt, combine, federate, or defer individual components, provided that the capabilities, interfaces, governance responsibilities, and resulting deviations are explicitly documented.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-0777✎ edit📣 feedback | received | Editorial Metadata registries agent, medium |
DPI-H Reference Architecture Framework §Chapter 2 introduction p.24 l.Lines 12-17 anchor: low |
The phrase “core registries and semantic and terminology services” may imply that semantic services and terminology ser…The phrase “core registries and semantic and terminology services” may imply that semantic services and terminology services are separate categories. Later sections distinguish the Terminology Service from the Logical Information Model Repository, while semantic governance is described as a broader capability. Suggested revision: Replace with a senteance like: “core registries, a Terminology Service, governed logical information models, and the related semantic-governance capabilities.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-030 discuss | in the document all mentions on GitHub record | ||
| PC-0778✎ edit📣 feedback | received | Core architects agent, medium |
DPI-H Reference Architecture Framework §Chapter 2 introduction p.24 l.Lines 18-26 anchor: low |
The text states that TOGAF works from business goals through capabilities and application services “to the technical co…The text states that TOGAF works from business goals through capabilities and application services “to the technical components.” However, the architecture deliberately limits its treatment of the technology layer and focuses primarily on application components. Suggested revision: Replace “technical components” with “application components and their supporting specifications,” or explicitly describe how far the architecture addresses the technology layer. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-030 discuss | in the document all mentions on GitHub record | ||
| PC-0779✎ edit📣 feedback | received | Core architects agent |
2.1 The Reference Architecture Scope §2.1 p.24-25 l.Lines 29-41 |
The section defines the scope at the level of a national health system but does not fully address subnational, regional…The section defines the scope at the level of a national health system but does not fully address subnational, regional, cross-border, or multi-country architectures. This may be problematic for decentralised countries where health-system authority and infrastructure are distributed. Suggested revision: State that the national level is the principal frame of reference, while components and governance may be realised nationally, subnationally, regionally, or through federated arrangements according to constitutional and institutional context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-024 discuss | in the document all mentions on GitHub record | ||
| PC-0780✎ edit📣 feedback | received | Core architects agent |
2.1 The Reference Architecture Scope §2.1 p.25 l.Lines 33-41 |
The scope excludes electronic medical records, order-management systems, warehouse-management systems, and disease-spec…The scope excludes electronic medical records, order-management systems, warehouse-management systems, and disease-specific tools because they consume shared infrastructure. This boundary is conceptually useful, but the document does not provide a consistent test for mixed platforms that implement both shared and operational capabilities. Suggested revision: Add guidance stating that DPI-H classification applies to the relevant capability or logical component, not necessarily to an entire deployed product. A single platform may realise both DPI-H components and operational applications, but the responsibilities and interfaces must remain logically separable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-025 discuss | in the document all mentions on GitHub record | ||
| PC-0781✎ edit📣 feedback | received | Core architects agent |
2.1 The Reference Architecture Scope §2.1 p.25 l.Lines 39-41 |
The statement that a component should not be interpreted as a prescription to procure a specific system is important, b…The statement that a component should not be interpreted as a prescription to procure a specific system is important, but it does not explain how countries should package components for procurement. Separate procurement of every logical component could create unnecessary fragmentation. Suggested revision: Add a note that logical components may be procured or implemented together where appropriate, provided that component boundaries, interfaces, data ownership, portability, and conformance obligations remain explicit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-0782✎ edit📣 feedback | received | Core architects agent |
2.1 The Reference Architecture Scope §2.1 p.25 l.Lines 42-45 |
The section says the architecture is organised across two “distinct but related layers,” but later figures and descript…The section says the architecture is organised across two “distinct but related layers,” but later figures and descriptions refer to additional layers and cross-cutting elements, including functional applications, foundational DPI, cross-cutting enablers, and technology. Suggested revision: Clarify that the two layers refer specifically to the internal organisation of DPI-H application components, not to the complete layered architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0783✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
2.1.1 Metadata registries and foundational components §2.1.1 p.25 l.Lines 46-53 |
The heading uses “Metadata registries,” while the listed components include the Lifelong Health Record, Terminology Ser…The heading uses “Metadata registries,” while the listed components include the Lifelong Health Record, Terminology Service, and Logical Information Model Repository. These are not all metadata registries. The terminology may therefore misrepresent the scope of the layer. Suggested revision: Rename the layer consistently as the foundational shared data and semantic layer, with “core metadata registries” as one category within it. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0784✎ edit📣 feedback | received | Core architects agent |
2.1.1 Metadata registries and foundational components §2.1.1 p.25 l.Lines 47-58 |
The section says that components in the first layer may be reusable “potentially across sectors,” but the Lifelong Heal…The section says that components in the first layer may be reusable “potentially across sectors,” but the Lifelong Health Record and health-specific terminology and information models are primarily health-sector resources. Cross-sector reusability is therefore not a reliable inclusion criterion for the entire layer. Suggested revision: Distinguish between components reused across health programmes and components potentially reused across sectors. Make cross-programme reuse the minimum criterion for DPI-H and cross-sector reuse an additional characteristic where applicable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0785✎ edit📣 feedback | received | Core architects agent, medium |
2.1.1 Metadata registries and foundational components §2.1.1 p.25 l.Lines 53-58 |
The practical test states that components failing the foundational-layer criteria “belong at the application layer.” Ho…The practical test states that components failing the foundational-layer criteria “belong at the application layer.” However, the next subsection introduces a business-services layer that also contains DPI-H application components. The phrase “application layer” is therefore ambiguous. Suggested revision: Replace “application layer” with “functional or point-of-service application layer outside DPI-H,” or explicitly state whether the intended destination is the DPI-H business-services layer or the non-DPI-H operational layer. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0786✎ edit📣 feedback | received | Core architects agent |
2.1.2 Business services layer §2.1.2 p.25-26 l.Lines 61-77 |
The business-services layer contains shared components such as the Computable Decision Support Engine, HMIS, and Public…The business-services layer contains shared components such as the Computable Decision Support Engine, HMIS, and Public Health Surveillance Platform. Some of these may execute operational or transactional functions, which appears to conflict with the later criterion that DPI-H components should be non-transactional. Suggested revision: Refine the component criterion from “non-transactional” to a more precise distinction, such as: “not primarily responsible for local point-of-service workflow or programme-specific transaction processing.” Then assess each business-service component against the revised criterion. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0787✎ edit📣 feedback | received | technical | Clinical agent |
2.1.2 Business services layer §2.1.2 p.25-26 l.Lines 66-73 |
The description implies that a Computable Decision Support Engine directly evaluates a patient’s record and delivers re…The description implies that a Computable Decision Support Engine directly evaluates a patient’s record and delivers recommendations at the point of care. In practice, decision support may be embedded in applications, invoked through standardised services, or distributed across rules engines and knowledge services. Suggested revision: Use implementation-neutral wording: “Computable decision-support capabilities evaluate relevant patient and contextual data against governed computable guidance and make recommendations, alerts, or assessments available to authorised consuming applications.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | |
| PC-0788✎ edit📣 feedback | received | Core architects agent |
2.1.2 Business services layer §2.1.2 p.26 l.Lines 71-77 |
The HMIS is described as shared infrastructure because it supports several domains. Reuse across domains alone may not …The HMIS is described as shared infrastructure because it supports several domains. Reuse across domains alone may not be sufficient to classify an operational analytics and reporting system as DPI-H. The distinction between an HMIS as a shared service and DHIS2 or similar operational implementations requires greater precision. Suggested revision: Define which HMIS capabilities qualify as DPI-H, such as shared indicator definitions, aggregate data services, and reusable reporting infrastructure, and which programme-specific dashboards or workflows remain functional applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | ||
| PC-0789✎ edit📣 feedback | received | Core architects agent |
2.1.2 Business services layer §2.1.2 p.26 l.Lines 78-84 |
Governance is described as a cross-cutting property rather than a feature of a component. Later component descriptions …Governance is described as a cross-cutting property rather than a feature of a component. Later component descriptions nonetheless include detailed component-level governance requirements. These positions are compatible but the relationship is not made explicit. Suggested revision: Clarify that governance is cross-cutting at architecture level but must be instantiated through component-specific ownership, stewardship, access, lifecycle, and accountability arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-029 discuss | in the document all mentions on GitHub record | ||
| PC-0790✎ edit📣 feedback | received | Core architects agent |
2.1.3 Relationship to foundational DPI §2.1.3 p.26 l.Lines 86-91 |
The statement that the architecture does not “redefine or duplicate” foundational DPI is sound, but the document later …The statement that the architecture does not “redefine or duplicate” foundational DPI is sound, but the document later permits health to establish interim identity, consent, trust, and exchange capabilities. Without transition rules, temporary health-sector capabilities may become permanent parallel infrastructure. Suggested revision: Require every interim health-sector substitute for absent foundational DPI to include a documented transition, interoperability, and decommissioning or convergence plan. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-011 discuss | in the document all mentions on GitHub record | ||
| PC-0791✎ edit📣 feedback | received | Core architects agent |
2.1.3 Relationship to foundational DPI §2.1.3 p.26 l.Lines 92-96 |
The section advises countries not to implement the full scope at once but does not yet state the criteria for prioritis…The section advises countries not to implement the full scope at once but does not yet state the criteria for prioritising one foundational component over another. Suggested revision: Introduce prioritisation criteria such as urgency of the selected use cases, dependency centrality, existing maturity, data quality, governance readiness, implementation cost, equity impact, and expected cross-programme reuse. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-026 discuss | in the document all mentions on GitHub record | ||
| PC-0792✎ edit📣 feedback | received | Core architects agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.26-27 l.Lines 101-116 |
REDDHI is described as a “direction of travel,” a “condition of self-sustaining national digital health maturity,” and …REDDHI is described as a “direction of travel,” a “condition of self-sustaining national digital health maturity,” and not a fixed destination. This is useful but remains difficult to operationalise. Countries may struggle to distinguish REDDHI from general digital-health maturity. Suggested revision: Provide a concise formal definition of REDDHI and identify its distinguishing characteristics relative to existing digital-health maturity frameworks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | ||
| PC-0793✎ edit📣 feedback | received | Core architects agent, medium |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27 l.Lines 108-129 |
REDDHI is expanded as “Resilient Essential Data and Digital Health Infrastructure,” but the relationship among “resilie…REDDHI is expanded as “Resilient Essential Data and Digital Health Infrastructure,” but the relationship among “resilient,” “essential,” “data,” and “digital health infrastructure” remains linguistically and conceptually unclear. Suggested revision: Add a short explanation that identifies which capabilities are essential, which properties make them resilient, and how data infrastructure differs from the wider digital-health infrastructure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | ||
| PC-0794✎ edit📣 feedback | received | Core architects Clinical agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27 l.Lines 117-123 |
The section identifies a core starting point consisting of metadata registries, the Lifelong Health Record, and data ex…The section identifies a core starting point consisting of metadata registries, the Lifelong Health Record, and data exchange. Treating the Lifelong Health Record as part of the minimum starting point may be unrealistic in countries that lack reliable digital capture, identity resolution, connectivity, or governance. Suggested revision: Present the LHR as a progressively realised capability. Allow the initial foundation to begin with identity, facility and workforce reference data, minimum exchange specifications, and selected longitudinal datasets driven by priority use cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | ||
| PC-0795✎ edit📣 feedback | received | Core architects agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27 l.Lines 118-122 |
The text refers to “a core set of metadata registries,” but later Table 2.2 also includes terminology, consent, authent…The text refers to “a core set of metadata registries,” but later Table 2.2 also includes terminology, consent, authentication, information models, and governance. The prose and table therefore describe different versions of the foundational core. Suggested revision: Define one authoritative REDDHI foundational-core list and use it consistently in the narrative, Table 2.2, Section 3.5, Appendix C, and the implementation phases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | ||
| PC-0796✎ edit📣 feedback | received | editorial | Editorial agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27 l.Lines 119-120 |
The sentence after “the means to exchange data between them” begins with “These” after a semicolon and contains an unne…The sentence after “the means to exchange data between them” begins with “These” after a semicolon and contains an unnecessary capital letter. Suggested revision: Replace the semicolon and capitalisation with: “…the means to exchange data between them. These registries are interdependent…” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-027 discuss | in the document all mentions on GitHub record | |
| PC-0797✎ edit📣 feedback | received | Core architects agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27 l.Lines 124-129 |
The proposed REDDHI markers remain mostly binary, such as whether registries exist or data is exchanged. They do not ad…The proposed REDDHI markers remain mostly binary, such as whether registries exist or data is exchanged. They do not adequately assess coverage, quality, use, resilience, governance, or institutional sustainability. Suggested revision: Define measurable indicators for each marker, including population coverage, programme reuse, API availability, conformance, data completeness, update latency, uptime, recovery capability, governance maturity, domestic financing, and user adoption. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | ||
| PC-0798✎ edit📣 feedback | received | Core architects agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.27-28 l.Lines 130-140 and Table 2.2 |
The phrase “minimum viable foundation” may encourage countries to treat the listed components as a universal package, a…The phrase “minimum viable foundation” may encourage countries to treat the listed components as a universal package, although needs and dependencies differ considerably by selected use case and national context. Suggested revision: Replace with a phrase like “minimum viable foundation for the selected national priorities,” and identify a small universal baseline separately from use-case-dependent components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | ||
| PC-0799✎ edit📣 feedback | received | Core architects agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.28 l.Table 2.2, “Authentication and access management” |
Authentication and access management are attributed to foundational identity DPI and national trust infrastructure, whi…Authentication and access management are attributed to foundational identity DPI and national trust infrastructure, while the Client and Workforce Registries provide roles and identity resolution. However, identity, authentication, authorisation, professional role, and consent are distinct concerns and should not be combined. Suggested revision: Separate the row into: person and workforce identity resolution; authentication and credentials; role and attribute management; authorisation and policy enforcement; and consent representation and enforcement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-235 discuss | in the document all mentions on GitHub record | ||
| PC-0800✎ edit📣 feedback | received | Core architects agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.28 l.Table 2.2, “Standards-based data exchange across systems” |
The “components that deliver it” column lists registries and the Terminology Service as common references but does not …The “components that deliver it” column lists registries and the Terminology Service as common references but does not identify the exchange services, gateways, endpoints, event brokers, APIs, trust services, or mediation functions through which technical interoperability is realised. Suggested revision: Rename the column to “Components and cross-cutting capabilities that support it,” and include standards-based endpoints, defined exchange patterns, trust services, audit, and mediation where required. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-029 discuss | in the document all mentions on GitHub record | ||
| PC-0801✎ edit📣 feedback | received | Core architects agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.28 l.Table 2.2, “Data governance, quality, and audit” |
The table associates data governance, quality, and audit mainly with registries, the Terminology Service, LIMR, and SGI…The table associates data governance, quality, and audit mainly with registries, the Terminology Service, LIMR, and SGI. Governance and audit apply to all DPI-H components, and clinical-data quality cannot be governed solely through metadata components. Suggested revision: State that these are architecture-wide responsibilities supported by component-level stewardship, provenance, audit, validation, quality rules, monitoring, and remediation processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-029 discuss | in the document all mentions on GitHub record | ||
| PC-0802✎ edit📣 feedback | received | Core architects agent |
2.2.1 What REDDHI is and its foundational core §2.2.1 p.28 l.Table 2.2, “Consent, authorisation, and privacy” |
Consent, authorisation, and privacy are grouped in a single row even though they have different legal and technical pur…Consent, authorisation, and privacy are grouped in a single row even though they have different legal and technical purposes. Consent does not always provide the legal basis for healthcare-data processing, and authorisation is not equivalent to consent. Suggested revision: Split the row into separate capabilities for consent or preference management, legal-basis and purpose management, authorisation and access control, and privacy-policy enforcement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-235 discuss | in the document all mentions on GitHub record | ||
| PC-0803✎ edit📣 feedback | received | Core architects agent |
2.2.2 The enabling conditions for REDDHI §2.2.2 p.28-29 l.Lines 143-165 |
The “full-STAC” approach provides a memorable framing, but the four open dimensions do not cover all enabling condition…The “full-STAC” approach provides a memorable framing, but the four open dimensions do not cover all enabling conditions described elsewhere, such as governance, financing, workforce capacity, cybersecurity, legal authority, service management, and institutional ownership. Suggested revision: Present full-STAC as a technical and content foundation within a broader set of REDDHI enabling conditions, rather than as the complete set of enabling conditions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-031 discuss | in the document all mentions on GitHub record | ||
| PC-0804✎ edit📣 feedback | received | Core architects agent |
2.2.2 The enabling conditions for REDDHI §2.2.2 p.28-29 l.Lines 147-150 |
The text identifies FHIR as the primary framework for health-data exchange. This is directionally appropriate, but nati…The text identifies FHIR as the primary framework for health-data exchange. This is directionally appropriate, but national ecosystems may also need DICOM, HL7 v2, CDA, IHE profiles, openEHR, GS1, and specialised public-health or supply-chain standards. Suggested revision: State that FHIR is the recommended primary framework for new health-data exchange specifications, while established standards should be retained or profiled where they remain appropriate, with governed transformation and migration pathways. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | ||
| PC-0805✎ edit📣 feedback | received | Core architects agent |
2.2.2 The enabling conditions for REDDHI §2.2.2 p.29 l.Lines 151-153 |
“Open technologies” is not defined. It may be interpreted as requiring open-source software, although open technology, …“Open technologies” is not defined. It may be interpreted as requiring open-source software, although open technology, open standards, source availability, open licensing, and vendor neutrality are separate considerations. Suggested revision: Define whether “open technologies” means open-source software, openly documented technology, royalty-free implementation, replaceability, or a combination. Avoid presenting open source alone as sufficient protection against lock-in. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-028 discuss | in the document all mentions on GitHub record | ||
| PC-0806✎ edit📣 feedback | received | technical | WHO Metadata registries agent, medium |
2.2.2 The enabling conditions for REDDHI §2.2.2 p.29 l.Lines 157-159 |
SMART Guidelines are described as “open content.” Some associated standards, terminology bindings, or implementation de…SMART Guidelines are described as “open content.” Some associated standards, terminology bindings, or implementation dependencies may have licensing or access conditions. Suggested revision: Qualify the statement by distinguishing openly published guideline artefacts from third-party terminology or implementation dependencies that may carry separate licensing conditions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-028 discuss | in the document all mentions on GitHub record | |
| PC-0807✎ edit📣 feedback | received | Editorial agent, medium |
2.2.2 The enabling conditions for REDDHI §2.2.2 p.30 l.Figure 2.2 anchor: medium |
Figure 2.2 is expected to explain REDDHI’s essential and resilient dimensions, full-STAC foundations, and place in nati…Figure 2.2 is expected to explain REDDHI’s essential and resilient dimensions, full-STAC foundations, and place in national architecture. The accompanying narrative does not provide a concise textual interpretation for readers who cannot inspect the figure or who use assistive technologies. Suggested revision: Add a short paragraph immediately after the figure explaining the main relationships and provide meaningful alternative text in the published digital version. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-030 discuss | in the document all mentions on GitHub record | ||
| PC-0808✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3 p.31 l.Lines 179-191 |
The section states that every architecture design principle translates a DPI-H principle into actionable decisions. No …The section states that every architecture design principle translates a DPI-H principle into actionable decisions. No explicit one-to-one or many-to-many mapping is provided, making the claim difficult to verify. Suggested revision: Add a mapping table showing which Section 1.4 principles are operationalised by each Section 2.3 design principle and identifying any principles without a corresponding design rule. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-017 discuss | in the document all mentions on GitHub record | ||
| PC-0809✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.I p.31-32 l.Lines 194-223 |
The governance principle correctly prioritises data quality, but it may imply that minimum data-quality thresholds can …The governance principle correctly prioritises data quality, but it may imply that minimum data-quality thresholds can be defined universally before a component becomes operational. Fitness for purpose differs by use case and risk. Suggested revision: Require use-case-specific data-quality criteria, including completeness, accuracy, timeliness, consistency, provenance, and acceptable error thresholds, with stricter levels for safety-critical use cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-243 discuss | in the document all mentions on GitHub record | ||
| PC-0810✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.I p.31 l.Lines 204-215 |
The principle says contributors should gain value from the data they enter, which is important, but no design mechanism…The principle says contributors should gain value from the data they enter, which is important, but no design mechanism is suggested. Suggested revision: Add practical mechanisms such as reducing duplicate reporting, returning validated information to source systems, providing data-quality feedback, showing operational dashboards, and integrating reporting into routine workflows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-243 discuss | in the document all mentions on GitHub record | ||
| PC-0811✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.II p.32 l.Lines 226-237 |
The section allows lighter-weight formats in lower-readiness contexts if a progression path toward open-standards compl…The section allows lighter-weight formats in lower-readiness contexts if a progression path toward open-standards compliance exists. However, it does not define the minimum requirements for that progression path. Suggested revision: Require a documented target standard, responsible authority, timeline, mapping specification, conformance checkpoints, versioning approach, and exit criteria for transitional formats. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-099 discuss | in the document all mentions on GitHub record | ||
| PC-0812✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.III p.32 l.Lines 240-254 |
The warning against architecting interoperability around a single central mediator is valuable, but the wording may ove…The warning against architecting interoperability around a single central mediator is valuable, but the wording may overcorrect by implying that centralised mediation is inherently unsuitable. In some contexts, central mediation can improve governance, security, and operational simplicity. Suggested revision: Present centralised, federated, distributed, and hybrid mediation as context-dependent options. Define their respective risks, benefits, prerequisites, and resilience requirements rather than favouring one topology implicitly. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-0813✎ edit📣 feedback | received | technical | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.III p.32 l.Lines 247-254 |
The statement that federated implementations are particularly useful where continuous central connectivity cannot be as…The statement that federated implementations are particularly useful where continuous central connectivity cannot be assumed is only partially correct. Federated nodes may still depend on remote data sources, identity services, or online discovery. Federation does not automatically provide offline resilience. Suggested revision: Clarify that resilience in low-connectivity settings requires local availability, caching, asynchronous exchange, conflict resolution, and store-and-forward capabilities, regardless of whether the wider topology is federated. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | |
| PC-0814✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.IV p.33 l.Lines 265-282 |
The sustainability principle addresses whole-of-life cost but does not explicitly include environmental sustainability,…The sustainability principle addresses whole-of-life cost but does not explicitly include environmental sustainability, energy use, hardware lifecycle, hosting efficiency, or secure disposal. Suggested revision: Add environmental sustainability as a consideration, proportionate to context, including energy consumption, infrastructure efficiency, equipment lifecycle, electronic waste, and climate resilience. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-111 discuss | in the document all mentions on GitHub record | ||
| PC-0815✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.V p.33 l.Lines 286-300 |
Modularity is defined mainly through component independence. However, independently deployable components can still be …Modularity is defined mainly through component independence. However, independently deployable components can still be tightly coupled through shared databases, proprietary data models, coordinated release cycles, or undocumented dependencies. Suggested revision: Expand the test for modularity to include independent data ownership, explicit API contracts, version compatibility, no mandatory shared database, documented dependencies, and independent replacement or upgrade. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-064 discuss | in the document all mentions on GitHub record | ||
| PC-0816✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.VI p.33-34 l.Lines 304-321 |
The principle places significant emphasis on technologies local teams can maintain. This is appropriate, but it may uni…The principle places significant emphasis on technologies local teams can maintain. This is appropriate, but it may unintentionally discourage specialised technology that is necessary for national-scale security, terminology, or clinical safety. Suggested revision: Add a proportionality statement: specialised technology may be used where justified, provided there is a realistic operating model, knowledge-transfer plan, documentation, support arrangement, and reduction of single-supplier dependency. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-242 discuss | in the document all mentions on GitHub record | ||
| PC-0817✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.VII p.34 l.Lines 325-343 |
The design principle focuses mainly on infrastructural participation and graceful degradation. Equity also concerns acc…The design principle focuses mainly on infrastructural participation and graceful degradation. Equity also concerns accessibility, language, disability, gender, affordability, digital literacy, and risk of discriminatory data practices. Suggested revision: Expand the principle to include accessible interfaces, multilingual support, assisted and non-digital pathways, affordability, disability inclusion, representative testing, and monitoring for differential outcomes across population groups. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | ||
| PC-0818✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.VIII p.34-35 l.Lines 346-378 |
The section describes consent as the “primary mechanism” through which individuals exercise data rights. In healthcare,…The section describes consent as the “primary mechanism” through which individuals exercise data rights. In healthcare, data processing may rely on several legal bases, and consent may not be valid or appropriate in every care, public-health, or statutory context. Suggested revision: Replace with a sentence like: “Consent is one important mechanism through which individuals exercise choices over data use, alongside statutory rights, transparency, access, correction, objection, and other protections established by applicable law.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-0819✎ edit📣 feedback | received | technical | Core architects Clinical agent, medium |
2.3 DPI-H Reference Architecture Design Principles §2.3.VIII p.35 l.Lines 362-365 |
The statement that consent can be “carried with the data” may be interpreted as embedding a static consent object in ev…The statement that consent can be “carried with the data” may be interpreted as embedding a static consent object in every exchanged record. Consent and access policy may change after data creation, requiring current policy evaluation. Suggested revision: Clarify that data should carry or reference sufficient policy, purpose, provenance, and consent metadata to permit evaluation against the current authoritative policy or consent record at the point of access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-235 discuss | in the document all mentions on GitHub record | |
| PC-0820✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.VIII p.35 l.Lines 380-388 |
Practical public control is appropriately distinguished from formal ownership, but data portability and interfaces alon…Practical public control is appropriately distinguished from formal ownership, but data portability and interfaces alone do not guarantee operational control. Suggested revision: Add requirements for configuration portability, full metadata export, audit-data access, documented deployment and recovery procedures, encryption-key governance, transition support, and supplier exit testing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | ||
| PC-0821✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.IX p.35-36 l.Lines 392-421 |
The section introduces graduated assurance but may be read as allowing weak security indefinitely in lower-capacity set…The section introduces graduated assurance but may be read as allowing weak security indefinitely in lower-capacity settings. Some minimum protections should apply irrespective of maturity. Suggested revision: Define a non-negotiable security baseline, including secure communications, least privilege, audit logging, vulnerability management, backup and recovery, incident response, and protection of administrative access. Graduated assurance should apply above that baseline. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-0822✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.IX p.36 l.Lines 415-420 |
The text allows countries to proceed without national trust infrastructure while acknowledging the risks, but it does n…The text allows countries to proceed without national trust infrastructure while acknowledging the risks, but it does not specify how those risks should be assessed, accepted, or mitigated. Suggested revision: Require documented risk assessment, accountable risk acceptance, compensating controls, time-limited exceptions, monitoring, and a roadmap toward stronger assurance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-0823✎ edit📣 feedback | received | Core architects agent |
2.3 DPI-H Reference Architecture Design Principles §2.3.X p.36-37 l.Lines 429-444 |
The ethics principle focuses strongly on secondary use and AI training. Ethical architectural concerns also include exc…The ethics principle focuses strongly on secondary use and AI training. Ethical architectural concerns also include exclusion, surveillance, power asymmetry, group harms, inappropriate linkage, and repurposing of infrastructure. Suggested revision: Expand the principle to require ethical and human-rights impact assessment for high-risk architectural decisions, including identity linkage, biometrics, cross-sector data sharing, population profiling, and secondary-use platforms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-244 discuss | in the document all mentions on GitHub record | ||
| PC-0824✎ edit📣 feedback | received | Core architects agent |
2.4 Methodology: Mapping Health Goals to DPI-H §2.4 p.37-38 l.Lines 452-472 |
The goals-first approach is a strong organising concept, but insufficient methodological detail is provided to reproduc…The goals-first approach is a strong organising concept, but insufficient methodological detail is provided to reproduce or independently validate the mapping. Suggested revision: Describe the participants, evidence sources, modelling steps, validation method, review criteria, treatment of disagreement, and version-control process used to derive the goal-to-capability-to-component mappings. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-023 discuss | in the document all mentions on GitHub record | ||
| PC-0825✎ edit📣 feedback | received | Core architects agent |
2.4 Methodology: Mapping Health Goals to DPI-H §2.4 p.37-38 l.Lines 466-472 |
The methodology combines top-down derivation with bottom-up consideration of known components. This is pragmatic but in…The methodology combines top-down derivation with bottom-up consideration of known components. This is pragmatic but introduces a risk that familiar components shape the results, despite the claim that the architecture is goals-first. Suggested revision: Explain how the process controlled for component-led bias, including whether capabilities were derived before candidate components were considered and how alternatives were evaluated. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-023 discuss | in the document all mentions on GitHub record | ||
| PC-0826✎ edit📣 feedback | received | Core architects agent |
2.4 Methodology: Mapping Health Goals to DPI-H §2.4 p.38 l.Lines 473-478 |
The recurrence of components across goals is used to justify their classification as DPI-H. Recurrence demonstrates reu…The recurrence of components across goals is used to justify their classification as DPI-H. Recurrence demonstrates reuse potential but does not, by itself, establish public-good characteristics, governance feasibility, cost-effectiveness, or appropriateness as shared national infrastructure. Suggested revision: Treat recurrence as one criterion among several. Add public-interest value, standards-based accessibility, lifecycle stability, governance viability, cost-effectiveness, and avoidance of unjustified centralisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0827✎ edit📣 feedback | received | Core architects agent |
2.4 Methodology: Mapping Health Goals to DPI-H §2.4 p.38 l.Lines 479-485 |
Legal, governance, workforce, organisational, and change-management considerations are described as sitting beyond the …Legal, governance, workforce, organisational, and change-management considerations are described as sitting beyond the architecture’s structural description. This could reinforce an artificial separation between architecture and implementation, even thoug Suggested revision: Add an accountability model covering the shared component owner, application owner, data steward, standards authority, implementer, and service-delivery authority. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-038 discuss | in the document all mentions on GitHub record | ||
| PC-0828✎ edit📣 feedback | received | Core architects agent |
2.4.1 How each health goal is articulated §2.4.1 p.38 l.Lines 487-499 |
The four-part articulation structure does not explicitly include assumptions, risks, indicators, governance responsibil…The four-part articulation structure does not explicitly include assumptions, risks, indicators, governance responsibilities, or contextual dependencies. These are needed to make the mapping actionable. Suggested revision: Extend the structure to include enabling conditions, responsible stakeholders, measurable outcomes, assumptions, risks, foundational-DPI dependencies, and relevant conformance criteria. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-034 discuss | in the document all mentions on GitHub record | ||
| PC-0829✎ edit📣 feedback | received | Editorial agent |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2 p.39 l.Table 2.4 |
The table title reads “components that supports them,” which is grammatically incorrect.The table title reads “components that supports them,” which is grammatically incorrect. Suggested revision: Change to: “Health financing capabilities and the DPI-H components that support them.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | ||
| PC-0830✎ edit📣 feedback | received | technical | Financial systems agent |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2 p.39 l.Table 2.4, “Pricing and reimbursing accurately” |
Product Registry and Terminology Services are presented as sufficient support for accurate pricing and reimbursement. P…Product Registry and Terminology Services are presented as sufficient support for accurate pricing and reimbursement. Pricing also depends on contracts, tariffs, payment methods, provider agreements, benefit rules, clinical coding policies, and claims-adjudication logic. Suggested revision: Expand the supporting capabilities to include the Benefits Package Registry, relevant contracting and tariff-management systems, claims rules, provider agreements, and coding standards. Clarify which are DPI-H and which are operational systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-036 discuss | in the document all mentions on GitHub record | |
| PC-0831✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2 p.39 l.Lines 514-519 |
The claim that only one genuinely new DPI-H component emerges from the financing analysis may be too strong. The analys…The claim that only one genuinely new DPI-H component emerges from the financing analysis may be too strong. The analysis also depends on beneficiary or enrolment information, provider contracting, claims rules, and financial-accountability capabilities. Suggested revision: Qualify the claim: “Within the component set and scope adopted by this reference architecture, the principal additional shared reference component is the Benefits Package Registry.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-0832✎ edit📣 feedback | received | Financial systems agent |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2 p.39-40 l.Lines 520-526 |
The section appropriately places claims engines and scheme-administration platforms outside DPI-H, but the boundary bet…The section appropriately places claims engines and scheme-administration platforms outside DPI-H, but the boundary between authoritative benefit definitions and executable adjudication rules is not fully explicit. Suggested revision: State that the Benefits Package Registry publishes authoritative definitions and machine-readable rules where appropriate, while operational systems execute enrolment, authorisation, adjudication, contracting, and payment workflows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-0833✎ edit📣 feedback | received | Core architects agent, medium |
The Reference Architecture for DPI-H §Chapter 3 introduction p.41 l.Lines 1-13 anchor: low |
The chapter clearly explains that the reference architecture connects health goals to capabilities and shared infrastru…The chapter clearly explains that the reference architecture connects health goals to capabilities and shared infrastructure. However, the distinction between a reference model, a reference architecture, and a country-specific architecture is not sufficiently clear. These terms may be interpreted differently by policymakers and technical teams. Suggested revision: Add a short explanation distinguishing the three concepts: the reference model defines the common vocabulary and elements; the reference architecture defines their relationships and design constraints; and a country architecture adopts, adapts, or maps these elements to its national context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-042 discuss | in the document all mentions on GitHub record | ||
| PC-0834✎ edit📣 feedback | received | Core architects agent |
The Reference Architecture for DPI-H §Chapter 3 introduction p.41 l.Lines 10-13 anchor: low |
The statement that countries may “set aside elements” is appropriately flexible, but it could be interpreted as allowin…The statement that countries may “set aside elements” is appropriately flexible, but it could be interpreted as allowing countries to omit essential capabilities without documenting the consequences. Suggested revision: Add: “Where elements are omitted, combined, or substantially modified, countries should document the rationale, affected capabilities, relevant risks, and any alternative arrangements through which the intended outcomes will be achieved.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-042 discuss | in the document all mentions on GitHub record | ||
| PC-0835✎ edit📣 feedback | received | Editorial agent |
The Reference Architecture for DPI-H §Chapter 3 introduction p.41 l.Lines 15-24 anchor: low |
The chapter overview lists Sections 3.1 to 3.6 but does not mention Section 3.7 on conformance and testing, even though…The chapter overview lists Sections 3.1 to 3.6 but does not mention Section 3.7 on conformance and testing, even though this is one of the document’s main contributions. Suggested revision: Add a final bullet: “Section 3.7 describes how the architecture and its components can be assessed through conformance profiles, testing, coverage, and goal validation.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-254 discuss | in the document all mentions on GitHub record | ||
| PC-0836✎ edit📣 feedback | received | Editorial agent, medium |
3.1 The architecture description approach §3.1 p.41 - 42 l.Lines 26-46 |
The explanation of architecture terminology is accurate but dense for readers who are unfamiliar with enterprise-archit…The explanation of architecture terminology is accurate but dense for readers who are unfamiliar with enterprise-architecture modelling. Terms such as element, relationship, application service, motivation element, and architecture domain are introduced together before a simple example is provided. Suggested revision: Start the section with one concise health example, such as tracing trusted personal health records from the goal through identity and record-management capabilities to the Client Registry and Lifelong Health Record. Then introduce the ArchiMate terminology used to represent that chain. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-0837✎ edit📣 feedback | received | Editorial agent, medium |
3.1 The architecture description approach §3.1 p.42 l.Lines 34-46 |
The description of ArchiMate is appropriate for enterprise architects but may be excessive for policymakers, programme …The description of ArchiMate is appropriate for enterprise architects but may be excessive for policymakers, programme managers, donors, and procurement teams. The existing reading guide marks this section as optional for most non-technical readers, but the chapter does not provide a non-technical summary before introducing the modelling language. Suggested revision: Add a brief “What non-technical readers need to know” box explaining that the formal model provides consistent naming, traceability, comparison, and conformance checking. Retain the detailed ArchiMate explanation for technical readers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-0838✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.42 l.Lines 34-46 |
The section suggests that using ArchiMate makes the architecture authorable, checkable, and comparable. ArchiMate provi…The section suggests that using ArchiMate makes the architecture authorable, checkable, and comparable. ArchiMate provides a structured modelling language, but it does not automatically guarantee semantic consistency, model quality, completeness, or conformance. Suggested revision: Qualify the claim by stating that ArchiMate enables automated and manual checking when supported by agreed modelling conventions, identifiers, validation rules, governance, and quality-assurance processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-0839✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.42 l.Lines 43-46 |
The statement that ArchiMate is “broadly adopted” may overstate its practical accessibility in countries with limited e…The statement that ArchiMate is “broadly adopted” may overstate its practical accessibility in countries with limited enterprise-architecture capacity. Availability of the language and tools does not ensure the availability of trained modellers or sustainable modelling governance. Suggested revision: Acknowledge that ArchiMate expertise may be limited in some settings and provide a simplified adoption pathway, including reusable templates, training resources, minimum modelling conventions, and non-ArchiMate representations that map to the formal model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-0840✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.42 l.Lines 49-55 |
The text states that the formal architecture can become a set of criteria against which a candidate architecture is che…The text states that the formal architecture can become a set of criteria against which a candidate architecture is checked for completeness and consistency. However, the criteria, validation rules, and minimum mandatory relationships are not defined in this section. Suggested revision: Cross-reference the specific conformance rules in Section 3.7 and identify which checks can be automated, which require expert review, and which elements or relationships are mandatory for a valid national mapping. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-0841✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.42 l.Lines 56-62 |
The document says that only a subset of ArchiMate element and relationship types is used, but it does not explain the s…The document says that only a subset of ArchiMate element and relationship types is used, but it does not explain the selection criteria or identify the excluded modelling concerns. Important areas such as business processes, roles, requirements, constraints, technology, and implementation sequencing appear later or are only partially represented. Suggested revision: Explain why the selected subset is sufficient for the reference architecture’s scope. Identify additional ArchiMate constructs that country models may need for workflows, organisational responsibility, requirements, constraints, technology deployment, migration, and implementation planning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-0842✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.43 l.Table 3.1, “Stakeholder” |
The stakeholder element includes patients, workers, agencies, and regulators, but the examples do not include organisat…The stakeholder element includes patients, workers, agencies, and regulators, but the examples do not include organisations responsible for foundational DPI, financing, standards, procurement, data protection, or civil society. These stakeholders are important to DPI-H governance and implementation. Suggested revision: Expand the examples to include foundational-DPI authorities, Ministries of Finance, procurement bodies, data-protection authorities, standards bodies, civil society, professional councils, and development partners. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-040 discuss | in the document all mentions on GitHub record | ||
| PC-0843✎ edit📣 feedback | received | Core architects agent, medium |
3.1 The architecture description approach §3.1 p.43 l.Table 3.1, “Outcome” |
The example outcome, “a defined share of citizens issued with a verifiable health record,” focuses on issuance rather t…The example outcome, “a defined share of citizens issued with a verifiable health record,” focuses on issuance rather than meaningful access, usability, coverage, continuity, or health benefit. It may incentivise output measurement without demonstrating value. Suggested revision: Replace or supplement it with outcome measures such as the proportion of the eligible population able to access a usable record, the proportion of encounters supported by relevant longitudinal information, and measurable improvement in continuity of care. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-040 discuss | in the document all mentions on GitHub record | ||
| PC-0844✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.43 l.Table 3.1, “Application component” |
The definition states that an application component is a deployable piece of software that provides functionality and h…The definition states that an application component is a deployable piece of software that provides functionality and holds the data it manages. Some valid components may provide shared services without holding authoritative data, while federated components may access data held elsewhere. Suggested revision: Revise the definition to: “A modular and independently identifiable unit of application functionality that exposes defined services and may manage or access defined data objects. It may be realised by one or more deployed software systems.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-040 discuss | in the document all mentions on GitHub record | ||
| PC-0845✎ edit📣 feedback | received | Editorial agent, medium |
3.1 The architecture description approach §3.1 p.43 l.Table 3.1, “Product” |
“Product” is defined as a coherent offering bundling services and data, with a digital health wallet as the example. El…“Product” is defined as a coherent offering bundling services and data, with a digital health wallet as the example. Elsewhere, “product” predominantly refers to health commodities managed by the Product Registry. Using the same term for two distinct concepts may confuse readers. Suggested revision: Label the modelling concept as ArchiMate Product wherever it is used, and clarify that it is distinct from a medicine, device, vaccine, or commodity represented in the Product Registry. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | ||
| PC-0846✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.43 - 44 l.Table 3.1 and Lines 71 - 76 |
The summary of relationships says that a component is “composed of the functions and data objects it contains.” In Arch…The summary of relationships says that a component is “composed of the functions and data objects it contains.” In ArchiMate, composition and access relationships have different meanings. A component accesses data objects rather than necessarily containing them. Suggested revision: Correct the explanation so that composition is used for true whole-part relationships, while access represents reading, writing, or otherwise interacting with data objects. Ensure the diagrams and machine-readable model use the same distinction. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-040 discuss | in the document all mentions on GitHub record | ||
| PC-0847✎ edit📣 feedback | received | Editorial agent, medium |
3.1 The architecture description approach §3.1 p.44 l.Table 3.2 |
The table columns “ArchiMate relationship,” “Relationship type,” and “What it represents” appear structurally inconsist…The table columns “ArchiMate relationship,” “Relationship type,” and “What it represents” appear structurally inconsistent. The table repeats the relationship name rather than clearly distinguishing the source element, relationship, and target element. Suggested revision: Restructure the table using the columns: Source element, Relationship, Target element, and Meaning in the DPI-H architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-040 discuss | in the document all mentions on GitHub record | ||
| PC-0848✎ edit📣 feedback | received | Core architects agent, medium |
3.1 The architecture description approach §3.1 p.44 l.Table 3.2 |
Only four relationships are introduced as the structural basis of the model, but Table 3.3 later adds assignment and tr…Only four relationships are introduced as the structural basis of the model, but Table 3.3 later adds assignment and triggering, and Section 3.7 adds further element types. Readers may incorrectly assume that Table 3.2 is the complete relationship set. Suggested revision: State that Table 3.2 introduces the core relationship types used for goal-to-component traceability, while Table 3.3 and Section 3.7 provide the extended set required for behavioural modelling and conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-0849✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.45 l.Figure 3.1 anchor: medium |
Figure 3.1 states that “each lower element realises the one above.” This oversimplifies the architecture because not al…Figure 3.1 states that “each lower element realises the one above.” This oversimplifies the architecture because not all relationships in the traceability chain are realisation relationships. For example, capabilities may serve goals, outcomes realise goals, and components may realise services. Suggested revision: Revise the figure and caption to show the correct relationship type at each step. Avoid presenting all vertical relationships as realisation. Provide a legend identifying serving, realisation, composition, and access relationships. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-040 discuss | in the document all mentions on GitHub record | ||
| PC-0850✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.45 l.Table 3.3, “Application Component → Realisation → Application Component” |
The row states that an application component realises another application component because “a concrete system realises…The row states that an application component realises another application component because “a concrete system realises an actor role.” Modelling an actor role as an Application Component may be pragmatic for alignment with IHE, but it risks conflating an abstract role with a structural software component. Suggested revision: Explain that this is a deliberate modelling convention adopted for compatibility with IHE actor-based conformance. Document the convention formally and consider using a stereotype, property, or naming rule to distinguish abstract actor roles from concrete systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-0851✎ edit📣 feedback | received | Core architects agent |
3.1 The architecture description approach §3.1 p.45 - 46 l.Table 3.3 |
Table 3.3 lists relationships but does not indicate their cardinality, directionality constraints, mandatory status, or…Table 3.3 lists relationships but does not indicate their cardinality, directionality constraints, mandatory status, or validation rules. These are necessary if the model is intended to support automated completeness and conformance checking. Suggested revision: Publish a machine-readable modelling profile defining permitted source-target combinations, relationship direction, required properties, cardinalities where applicable, mandatory relationships, identifiers, and validation rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-0852✎ edit📣 feedback | received | Editorial agent, medium |
3.1 The architecture description approach §3.1 p.45 - 46 l.Table 3.3 |
The table includes Application Function and Application Interaction even though Table 3.1 does not define them. They ar…The table includes Application Function and Application Interaction even though Table 3.1 does not define them. They are only formally introduced later in Section 3.7. Suggested revision: Either add these elements to Table 3.1 with concise definitions or remove them from Table 3.3 and introduce them only in Section 3.7. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-0853✎ edit📣 feedback | received | Editorial agent |
3.1 The architecture description approach §3.1 p.45 - 46 l.Table 3.3 |
The terminology changes between noun and verbal forms, such as “Realises” in the narrative and “Realisation” in the tab…The terminology changes between noun and verbal forms, such as “Realises” in the narrative and “Realisation” in the table, and “Serves” versus “Serving.” Although both forms may be valid in context, the variation is difficult for non-specialist readers. Suggested revision: Use the official ArchiMate relationship names consistently in tables and diagrams, and explain the corresponding verbal form once in the narrative. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-040 discuss | in the document all mentions on GitHub record | ||
| PC-0854✎ edit📣 feedback | received | Core architects agent, medium |
3.2 Reading and navigating the reference architecture §3.1 p.46 - 47 l.Lines 92-102 anchor: low |
The section describes several complementary outputs, including the narrative, detailed model, simplified views, and an …The section describes several complementary outputs, including the narrative, detailed model, simplified views, and an online reference. However, it does not provide a clear location, persistent identifier, ownership model, publication schedule, or version relationship among them. Suggested revision: Identify where each artefact will be published, its version number, licence, responsible maintainer, update frequency, and relationship to the version of the narrative guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-253 discuss | in the document all mentions on GitHub record | ||
| PC-0855✎ edit📣 feedback | received | Core architects WHO agent, medium |
3.2 Reading and navigating the reference architecture §3.1 p.46 l.Lines 95-102 anchor: low |
The model is described as the authoritative source for element-level detail while it continues to evolve separately fro…The model is described as the authoritative source for element-level detail while it continues to evolve separately from the stable narrative. This creates a risk that the guidance and the model diverge or that conformance requirements change without a controlled publication process. Suggested revision: Introduce formal versioning and release governance. Each published guidance version should reference a specific model release, with change logs, compatibility rules, deprecation periods, and effective dates for conformance requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-253 discuss | in the document all mentions on GitHub record | ||
| PC-0856✎ edit📣 feedback | received | Core architects agent |
3.2 Reading and navigating the reference architecture §3.2 p.46 - 47 l.Lines 103-115 |
The three suggested viewpoints cover health-system function, realisation, and motivation. Procurement, implementation, …The three suggested viewpoints cover health-system function, realisation, and motivation. Procurement, implementation, security, governance, information, and migration viewpoints are not identified, although these audiences and concerns are central to the guidance. Suggested revision: Add recommended views for procurement and conformance, governance and accountability, security and privacy, information and terminology, implementation sequencing, legacy transition, and foundational-DPI integration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-041 discuss | in the document all mentions on GitHub record | ||
| PC-0857✎ edit📣 feedback | received | Core architects agent |
3.2 Reading and navigating the reference architecture §3.2 p.47 l.Lines 112-114 |
The statement that the same element appears consistently across views assumes stable identifiers and controlled reuse. …The statement that the same element appears consistently across views assumes stable identifiers and controlled reuse. The document does not specify how element identity is maintained across diagrams, exports, versions, or country adaptations. Suggested revision: Require globally unique and persistent identifiers for architecture elements, with controlled labels, version metadata, status, provenance, and machine-readable mappings across releases and country models. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-253 discuss | in the document all mentions on GitHub record | ||
| PC-0858✎ edit📣 feedback | received | Core architects agent |
3.2 Reading and navigating the reference architecture §3.2 p.47 l.Lines 115-120 |
Countries are encouraged to adapt the model by adjusting, extending, or setting aside elements. However, no practical a…Countries are encouraged to adapt the model by adjusting, extending, or setting aside elements. However, no practical adaptation workflow is provided. This limits usability for country architecture teams. Suggested revision: Add a stepwise adaptation method: establish national goals and baseline; select reference elements; map existing systems; identify gaps and overlaps; document adaptations; validate dependencies; assign governance; define transition states; and publish the national model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-041 discuss | in the document all mentions on GitHub record | ||
| PC-0859✎ edit📣 feedback | received | Core architects agent |
3.2 Reading and navigating the reference architecture §3.2 p.47 l.Lines 121-125 |
Legal, governance, workforce, organisational, and change-management considerations are described as sitting beyond the …Legal, governance, workforce, organisational, and change-management considerations are described as sitting beyond the architecture’s structural description. This could reinforce an artificial separation between architecture and implementation, even though these factors constrain architectural choices. Suggested revision: Clarify that these considerations are not represented fully in the core structural views but remain architecture requirements and constraints that must be linked to relevant components, services, and implementation decisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-041 discuss | in the document all mentions on GitHub record | ||
| PC-0860✎ edit📣 feedback | received | Core architects agent, medium |
3.2 Reading and navigating the reference architecture §3.2 p.47 l.Lines 127 - 131, note on reading the views |
The note correctly explains that one platform may realise several elements and one element may be distributed across se…The note correctly explains that one platform may realise several elements and one element may be distributed across several systems. However, this distinction appears late and is essential to interpreting the two-layer architecture and component catalogue. Suggested revision: Move this explanation to Section 2.1 or repeat it prominently when the two-layer model is first introduced. Include it in the procurement guidance to prevent one-component-one-product interpretations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-041 discuss | in the document all mentions on GitHub record | ||
| PC-0861✎ edit📣 feedback | received | Core architects agent |
3.2 Reading and navigating the reference architecture §3.2 p.47 l.Lines 127-131 |
The section allows an element to be realised centrally, federatively, or distributively, but it does not define the min…The section allows an element to be realised centrally, federatively, or distributively, but it does not define the minimum behaviours that must remain consistent across those topologies. Suggested revision: For every component, define topology-independent requirements covering authoritative responsibility, interfaces, identifiers, data consistency, discovery, access control, audit, conformance, availability, and lifecycle management. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-041 discuss | in the document all mentions on GitHub record | ||
| PC-0862✎ edit📣 feedback | received | Core architects agent, medium |
3.3 The reference architecture in practice §3.3 p.48 l.Figure 3.2 anchor: medium |
Figure 3.2 combines goals, capabilities, functional applications, DPI-H components, cross-cutting enablers, foundationa…Figure 3.2 combines goals, capabilities, functional applications, DPI-H components, cross-cutting enablers, foundational DPI, and technology in one view. Although comprehensive, its density may make the two-layer DPI-H structure harder rather than easier to understand. Suggested revision: Provide three complementary figures: a simplified conceptual view for policy audiences, a DPI-H component-layer view for planners and procurement teams, and the full traceability view for architects. Ensure all figures use consistent layer names and visual conventions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0863✎ edit📣 feedback | received | Editorial agent |
3.3 The reference architecture in practice §3.3 p.48 l.Figure 3.2 caption anchor: medium |
The figure caption is long and attempts to explain nearly the complete architecture. Readers must retain too many conce…The figure caption is long and attempts to explain nearly the complete architecture. Readers must retain too many concepts before examining the figure. Suggested revision: Shorten the caption to the figure’s main purpose and move the detailed layer-by-layer explanation into the body text or a structured legend. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0864✎ edit📣 feedback | received | Editorial agent, medium |
3.3 The reference architecture in practice §3.3 p.49 l.Lines 144-150 |
The text acknowledges that the comprehensive view is dense and directs most readers to simplified goal views. However, …The text acknowledges that the comprehensive view is dense and directs most readers to simplified goal views. However, it does not indicate where all simplified views can be found or whether every goal has one. Suggested revision: Provide a table listing each health goal, the corresponding simplified and detailed views, the intended audience, and the location of the online model or appendix entry. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-034 discuss | in the document all mentions on GitHub record | ||
| PC-0865✎ edit📣 feedback | received | Core architects agent |
3.3 The reference architecture in practice §3.3 p.49 l.Lines 151-160 |
The traceability explanation moves from goals and sub-goals to outcomes, capabilities, services, components, and data. …The traceability explanation moves from goals and sub-goals to outcomes, capabilities, services, components, and data. It does not explicitly show assumptions, enabling policies, foundational-DPI dependencies, responsible stakeholders, or indicators. Suggested revision: Extend the goal views or linked documentation to include foundational-DPI dependencies, governance responsibilities, key assumptions, risks, measurable outcomes, and conformance criteria. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-034 discuss | in the document all mentions on GitHub record | ||
| PC-0866✎ edit📣 feedback | received | Core architects Clinical agent, medium |
3.3 The reference architecture in practice §3.3 p.49 l.Lines 161-170 |
In the trusted personal health-record example, identity, longitudinal records, and consent are mapped to the Client Reg…In the trusted personal health-record example, identity, longitudinal records, and consent are mapped to the Client Registry and LHR, with information surfaced through a digital health wallet. This may imply that a digital wallet is the preferred or necessary access mechanism. Suggested revision: Describe the wallet as one possible access channel alongside portals, applications, printed or verifiable documents, assisted access, and other nationally appropriate mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-0867✎ edit📣 feedback | received | Clinical Core architects agent, medium |
3.3 The reference architecture in practice §3.3 p.49 - 50 l.Lines 161 - 170 and Figure 3.3 |
The personal-health-record example assumes that individuals can interact digitally with their records. It does not visi…The personal-health-record example assumes that individuals can interact digitally with their records. It does not visibly address people without smartphones, digital identity, connectivity, literacy, legal documentation, or capacity to manage consent independently. Suggested revision: Add assisted and non-digital access pathways, delegated access, accessibility requirements, caregiver arrangements, child and guardian access, and mechanisms for people without foundational identity or personal devices. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-0868✎ edit📣 feedback | received | Core architects agent, medium |
3.3 The reference architecture in practice §3.3 p.50 l.Figure 3.3 |
The simplified goal view includes cross-cutting enablers, but the narrative does not explain how terminology, informati…The simplified goal view includes cross-cutting enablers, but the narrative does not explain how terminology, information models, consent, trust, security, and exchange patterns jointly enable the personal-health-record goal. Suggested revision: Add a concise explanation beneath the figure showing how the Client Registry, LHR, Terminology Service, LIMR, consent capability, trust infrastructure, and interoperability specifications work together. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-0869✎ edit📣 feedback | received | Clinical Core architects agent |
3.3 The reference architecture in practice §3.3 p.51 l.Lines 180 - 189 and Figure 3.4 |
The quality and continuity-of-care example identifies patient history integration, care-protocol management, and decisi…The quality and continuity-of-care example identifies patient history integration, care-protocol management, and decision support. It does not explicitly include referral management, care-plan reconciliation, medication reconciliation, transitions of care, or provider communication. Suggested revision: Review the capability mapping and add the missing continuity-of-care capabilities where supported by the architecture. If these remain functions of operational applications, state this explicitly and identify their dependencies on DPI-H. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-0870✎ edit📣 feedback | received | Editorial agent |
3.3 The reference architecture in practice §3.3 p.51 - 52 l.Figures 3.4 and 3.5 anchor: medium |
Figure numbering is potentially confusing. Section 3.3 uses Figure 3.4, while Section 3.4 later uses Figures 3.4.1, 3.4…Figure numbering is potentially confusing. Section 3.3 uses Figure 3.4, while Section 3.4 later uses Figures 3.4.1, 3.4.2, and 3.4.3. This could complicate cross-referencing and final publication. Suggested revision: Use a single sequential figure-numbering convention throughout Chapter 3, or consistently adopt section-based numbering for all figures, such as Figure 3.3-1 and Figure 3.4-1. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-254 discuss | in the document all mentions on GitHub record | ||
| PC-0871✎ edit📣 feedback | received | Core architects agent |
3.3 The reference architecture in practice §3.3 p.52 - 53 l.Lines 194-212 |
The recurrence of registries across goals is used to justify prioritising them. Recurrence demonstrates reuse, but prio…The recurrence of registries across goals is used to justify prioritising them. Recurrence demonstrates reuse, but prioritisation should also account for governance readiness, data quality, implementation capacity, dependency risk, equity, cost, and immediate country priorities. Suggested revision: State that cross-goal recurrence is one prioritisation factor and provide additional criteria for selecting the order in which shared components are established or strengthened. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-026 discuss | in the document all mentions on GitHub record | ||
| PC-0872✎ edit📣 feedback | received | Core architects agent |
3.3 The reference architecture in practice §3.3 p.53 l.Lines 202-207 |
The section refers to “digital public infrastructure for health” as the shared components and distinguishes it from fun…The section refers to “digital public infrastructure for health” as the shared components and distinguishes it from functional applications. However, it does not repeat the two internal DPI-H layers introduced in Section 2.1, reducing continuity between the framework and practical view. Suggested revision: Explicitly show and name the foundational shared data layer and business-services layer in the practical architecture view and accompanying narrative. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0873✎ edit📣 feedback | received | Core architects agent |
3.3 The reference architecture in practice §3.3 p.53 l.Lines 207-212 |
Interoperability, governance, law, and policy are described as “cross-cutting enablers” that should not be mistaken for…Interoperability, governance, law, and policy are described as “cross-cutting enablers” that should not be mistaken for infrastructure. Some of these enablers nevertheless require concrete technical services, such as audit, consent, trust, certificate, policy-management, and terminology services. Suggested revision: Distinguish cross-cutting capabilities and policies from the technical services that implement or enforce them. Clarify which services are represented as components, which are provided by foundational DPI, and which remain implementation choices. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0874✎ edit📣 feedback | received | Core architects agent |
3.3 The reference architecture in practice §3.3 p.53 l.Lines 213-216 |
The document says that divergence from the reference becomes visible and can be reasoned about. This depends on countri…The document says that divergence from the reference becomes visible and can be reasoned about. This depends on countries using comparable modelling conventions and recording the rationale for divergence, which are not yet required here. Suggested revision: Require national adaptations to maintain explicit mappings to reference elements and to document whether each element is adopted, adapted, replaced, combined, deferred, or excluded, including the rationale and effect on conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-0875✎ edit📣 feedback | received | Core architects agent |
3.4.1 Purpose and framing §3.4.1 p.53-54 l.Lines 222-247 |
The section provides a strong definition of governance but does not clearly distinguish governance of the national digi…The section provides a strong definition of governance but does not clearly distinguish governance of the national digital-health architecture from governance of individual DPI-H components, shared data assets, standards, and operational services. These levels involve different decision rights and accountable bodies. Suggested revision: Introduce a governance-level model covering: national digital-health architecture governance; DPI-H portfolio governance; component governance; data and semantic governance; and operational service governance. Explain how decisions and escalations move between these levels. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-044 discuss | in the document all mentions on GitHub record | ||
| PC-0876✎ edit📣 feedback | received | Editorial agent |
3.4.1 Purpose and framing §3.4.1 p.53 l.Lines 222-227 |
The governance definition is conceptually strong but expressed as a long sentence containing decision authority, accoun…The governance definition is conceptually strong but expressed as a long sentence containing decision authority, accountability, trustworthiness, sustainability, equity, and semantic consistency. This may be difficult for non-specialist readers. Suggested revision: Divide the definition into two sentences and add a plain-language summary. For example: “Governance determines who may make which decisions, how those decisions are made, and how decision-makers are held accountable. Its purpose is to keep shared infrastructure trustworthy, equitable, sustainable, and responsive over time.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-052 discuss | in the document all mentions on GitHub record | ||
| PC-0877✎ edit📣 feedback | received | Core architects agent |
3.4.1 Purpose and framing §3.4.1 p.53 l.Lines 229-237 |
The statement that countries beginning with authoritative registries and agreed decision rights “tend to progress,” whi…The statement that countries beginning with authoritative registries and agreed decision rights “tend to progress,” while those beginning with application components “tend to fragment,” is plausible but presented as a general finding without evidence or qualification. Suggested revision: Either provide supporting evidence or qualify the statement as an implementation observation. Explain that application-led entry points can still contribute to coherent architecture when they conform to shared governance, standards, interfaces, and national transition plans. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-0878✎ edit📣 feedback | received | Core architects agent |
3.4.1 Purpose and framing §3.4.1 p.54 l.Lines 239-247 |
The section appropriately allows centralised, federated, and hybrid implementation. However, it assumes that each count…The section appropriately allows centralised, federated, and hybrid implementation. However, it assumes that each country can identify a “single accountable source” for every authoritative registry. In decentralised or federal systems, legal authority may be divided across jurisdictions or professional bodies. Suggested revision: Replace “single accountable source” with “clearly defined authoritative responsibility.” Allow authority to be distributed across recognised sources, provided that governance, conflict resolution, record reconciliation, and national interoperability responsibilities are explicit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-051 discuss | in the document all mentions on GitHub record | ||
| PC-0879✎ edit📣 feedback | received | Core architects agent |
3.4.1 Purpose and framing §3.4.1 p.54 l.Lines 244-247 |
The statement “Governance, in this sense, is a policy matter; implementation pattern is not” is too absolute. Implement…The statement “Governance, in this sense, is a policy matter; implementation pattern is not” is too absolute. Implementation topology affects concentration of power, accountability, resilience, security, access, and operational control, all of which are governance concerns. Suggested revision: Replace with something like: “Governance should remain distinct from implementation topology, but the selected topology must be assessed for its governance, accountability, resilience, security, and sovereignty implications.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-044 discuss | in the document all mentions on GitHub record | ||
| PC-0880✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.54-55 l.Lines 249-288 |
The governance principles cover subsidiarity, mandate separation, representation, financing, resource use, transparency…The governance principles cover subsidiarity, mandate separation, representation, financing, resource use, transparency, and adaptability. They do not explicitly include legality, privacy, security, clinical safety, data stewardship, conflict of interest, or independence from supplier influence. Suggested revision: Add principles covering legal authority and rights protection, security and clinical safety, responsible data stewardship, conflict-of-interest management, supplier independence, and proportionality of controls. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | ||
| PC-0881✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.54 l.Lines 250-252 |
The subsidiarity principle states that authority should sit at the lowest level where it can be exercised effectively. …The subsidiarity principle states that authority should sit at the lowest level where it can be exercised effectively. However, no criteria are provided for determining effectiveness or identifying decisions that must remain national. Suggested revision: Add criteria based on legal mandate, cross-jurisdictional impact, data sensitivity, systemic risk, need for national consistency, technical competence, cost, and proximity to affected communities. Provide examples of national, subnational, and component-level decisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-050 discuss | in the document all mentions on GitHub record | ||
| PC-0882✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.54 l.Lines 253-256 |
The separation between strategic governance and operational governance is useful, but the principle may be difficult to…The separation between strategic governance and operational governance is useful, but the principle may be difficult to implement in small or low-capacity settings where the same body or individuals must initially perform both functions. Suggested revision: Cross-reference Section 3.4.7 and state here that mandate and execution must be logically separated even where they are temporarily housed within one body. Require documented roles, agendas, decisions, and conflict-management procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-045 discuss | in the document all mentions on GitHub record | ||
| PC-0883✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.54 l.Lines 257-264 |
Inclusive representation is framed around rural populations, women, displaced persons, and under-resourced systems. Oth…Inclusive representation is framed around rural populations, women, displaced persons, and under-resourced systems. Other groups at risk of exclusion, including persons with disabilities, linguistic minorities, Indigenous communities, children, older people, people without legal identity, and digitally excluded populations, are not explicitly recognised. Suggested revision: Broaden the examples and require each country to identify affected and underrepresented groups through a contextual equity and human-rights assessment rather than relying on a fixed list. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-048 discuss | in the document all mentions on GitHub record | ||
| PC-0884✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.54 l.Lines 257-264 |
The principle calls for representation with genuine weight but does not define how participation influences decisions. …The principle calls for representation with genuine weight but does not define how participation influences decisions. Representation without voting rights, agenda-setting power, accessible materials, or feedback obligations may remain symbolic. Suggested revision: Require governance terms of reference to define nomination, voting or decision rights, quorum, agenda-setting, accessible participation, compensation where appropriate, publication of responses, and mechanisms showing how stakeholder input affected decisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-048 discuss | in the document all mentions on GitHub record | ||
| PC-0885✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.54-55 l.Lines 265-271 |
Financial sustainability is appropriately established as a governance mandate, but the principle focuses mainly on cont…Financial sustainability is appropriately established as a governance mandate, but the principle focuses mainly on continuity of funding. It does not sufficiently address affordability, value for money, cost transparency, technical debt, or the distribution of costs and benefits. Suggested revision: Expand the mandate to include total cost of ownership, affordability, value realisation, cost allocation, cost transparency, technical-debt management, and equitable distribution of investment and operating costs. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | ||
| PC-0886✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.55 l.Lines 272-277 |
“Prevention of resource overuse” introduces a commons-based framing but may be interpreted as allowing restrictions on …“Prevention of resource overuse” introduces a commons-based framing but may be interpreted as allowing restrictions on essential health use because an actor generates high demand. Heavy use may reflect legitimate population need rather than misuse. Suggested revision: Rename the principle Fair and sustainable use of shared capacity. Distinguish legitimate high demand from avoidable, abusive, inefficient, or uncompensated use, and require safeguards against restricting essential health services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-050 discuss | in the document all mentions on GitHub record | ||
| PC-0887✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.55 l.Lines 278-280 |
Transparency is required only for disclosure to “appropriate stakeholders,” which leaves substantial discretion and may…Transparency is required only for disclosure to “appropriate stakeholders,” which leaves substantial discretion and may permit governance decisions affecting the public to remain inaccessible. Suggested revision: Define a presumption of public disclosure for policies, standards, major decisions, performance reports, and resource-allocation criteria, with limited exceptions for security, confidentiality, procurement sensitivity, and protected personal information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | ||
| PC-0888✎ edit📣 feedback | received | Core architects agent |
3.4.2 Governance principles §3.4.2 p.55 l.Lines 281-288 |
The adaptability principle supports ongoing evaluation but does not establish a formal review cadence, triggers for ext…The adaptability principle supports ongoing evaluation but does not establish a formal review cadence, triggers for extraordinary review, or responsibility for implementing lessons. Suggested revision: Require periodic governance review and event-triggered review following major incidents, legal changes, significant architecture changes, supplier failure, material inequity findings, or persistent service-performance problems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | ||
| PC-0889✎ edit📣 feedback | received | Core architects agent |
3.4.3 Strategic governance §3.4.3 p.55 l.Lines 290-304 |
Strategic governance responsibilities are clearly described, but authority over national standards, architecture except…Strategic governance responsibilities are clearly described, but authority over national standards, architecture exceptions, procurement conformance, risk acceptance, and component retirement is not explicit. Suggested revision: Add responsibility for approving national architecture standards, granting and reviewing exceptions, enforcing procurement alignment, accepting systemic risks, resolving cross-component conflicts, and authorising the retirement or replacement of shared components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-044 discuss | in the document all mentions on GitHub record | ||
| PC-0890✎ edit📣 feedback | received | Core architects agent |
3.4.3 Strategic governance §3.4.3 p.55 l.Lines 295-303 |
The strategic body is expected to safeguard equity and sustainability, but no measurable indicators or reporting obliga…The strategic body is expected to safeguard equity and sustainability, but no measurable indicators or reporting obligations are specified. Suggested revision: Require an annual public governance report covering access and coverage, service performance, equity impacts, financial sustainability, standards conformance, incidents, architecture exceptions, stakeholder participation, and corrective actions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | ||
| PC-0891✎ edit📣 feedback | received | Core architects agent |
3.4.3 Strategic governance §3.4.3 p.55-56 l.Lines 306-311 |
The statement that inadequate funding, inequity, and overuse are the ways shared public infrastructure “most characteri…The statement that inadequate funding, inequity, and overuse are the ways shared public infrastructure “most characteristically fails” is broad and potentially unsupported. Failures may also arise from weak adoption, poor data quality, security incidents, unclear accountability, supplier lock-in, or political instability. Suggested revision: Reframe these as three important failure modes rather than the characteristic failure modes. Add adoption, data quality, security, institutional ownership, interoperability, and supplier dependency to the risk framework. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-0892✎ edit📣 feedback | received | Core architects agent |
3.4.3 Strategic governance §3.4.3 p.56 l.Lines 312-319 |
The section recommends a multistakeholder funding model and possible contribution or fee structures. Charging for acces…The section recommends a multistakeholder funding model and possible contribution or fee structures. Charging for access to shared infrastructure could create barriers for small providers, community organisations, or under-resourced regions. Suggested revision: Add equity safeguards, including exemptions or subsidies for essential and low-resource users, transparent cost-allocation principles, prohibition of discriminatory access, and assessment of whether fees could reduce health-service availability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-114 discuss | in the document all mentions on GitHub record | ||
| PC-0893✎ edit📣 feedback | received | Core architects agent |
3.4.3 Strategic governance §3.4.3 p.56 l.Lines 312-319 |
Reserve and contingency mechanisms are recommended but not linked to service criticality, recovery needs, or national b…Reserve and contingency mechanisms are recommended but not linked to service criticality, recovery needs, or national budgeting processes. Suggested revision: Require financial-resilience planning based on component criticality, including minimum operating reserves, continuity funding, supplier-failure contingencies, emergency procurement authority, and transition funding for replacement or migration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | ||
| PC-0894✎ edit📣 feedback | received | Core architects agent |
3.4.3 Strategic governance §3.4.3 p.56 l.Lines 320-326 |
The proposed equity mechanisms focus on representation within governance bodies but do not require assessment of actual…The proposed equity mechanisms focus on representation within governance bodies but do not require assessment of actual distributional effects arising from architecture decisions. Suggested revision: Require an equity-impact assessment for major decisions, examining who gains access, who bears data-entry and compliance burdens, who may be excluded, and whether benefits and risks are distributed fairly across regions and population groups. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | ||
| PC-0895✎ edit📣 feedback | received | Core architects agent |
3.4.3 Strategic governance §3.4.3 p.56 l.Lines 327-332 |
Usage tiers and contribution requirements are proposed without defining the technical and governance data needed to mea…Usage tiers and contribution requirements are proposed without defining the technical and governance data needed to measure usage accurately. This may be difficult where shared infrastructure is federated or implemented across multiple operators. Suggested revision: Require consistent service metering, privacy-preserving usage measurement, agreed attribution rules, auditable cost models, and governance review before usage data is used to impose restrictions or charges. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-050 discuss | in the document all mentions on GitHub record | ||
| PC-0896✎ edit📣 feedback | received | Core architects agent |
3.4.4 Operational governance §3.4.4 p.56-57 l.Lines 334-357 |
Operational governance includes master-data, release, change, service-level, incident, interoperability, and semantic-g…Operational governance includes master-data, release, change, service-level, incident, interoperability, and semantic-governance responsibilities. It does not explicitly cover cybersecurity operations, vulnerability management, continuity testing, backup and recovery, supplier management, or privacy incident handling. Suggested revision: Expand operational governance to include security operations, vulnerability and patch management, business continuity and disaster recovery, privacy incidents, supplier performance, capacity management, configuration management, and periodic resilience testing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-0897✎ edit📣 feedback | received | Core architects Metadata registries Clinical agent, low |
3.4.4 Operational governance §3.4.4 p.56 l.Lines 339-346 |
The master-data list includes client, facility, workforce, product, and terminology registries. Terminology is not mast…The master-data list includes client, facility, workforce, product, and terminology registries. Terminology is not master data in exactly the same sense as records of persons, facilities, workers, or products, and the LHR and LIMR are not mentioned. Suggested revision: Distinguish entity master-data governance from terminology governance, information-model governance, and longitudinal clinical-data stewardship. Identify the appropriate governance responsibility for each asset class. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-0898✎ edit📣 feedback | received | Core architects agent |
3.4.4 Operational governance §3.4.4 p.56 l.Lines 340-346 |
The text uses “owns” and “stewards” when describing data responsibilities but does not define ownership, custodianship,…The text uses “owns” and “stewards” when describing data responsibilities but does not define ownership, custodianship, stewardship, accountability, and source authority. These terms can have different legal meanings across countries. Suggested revision: Add a responsibility model defining authoritative source, accountable authority, custodian, steward, processor or operator, and data contributor. Use these terms consistently across all component descriptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-038 discuss | in the document all mentions on GitHub record | ||
| PC-0899✎ edit📣 feedback | received | Core architects Metadata registries agent |
3.4.4 Operational governance §3.4.4 p.56-57 l.Lines 347-352 |
Release management and change management are described separately, but the relationship between technical releases, sem…Release management and change management are described separately, but the relationship between technical releases, semantic-content releases, policy changes, and organisational adoption is not explained. Suggested revision: Define an integrated change model covering technical software releases, API and profile changes, terminology and model releases, policy changes, data migration, stakeholder communication, training, compatibility, rollback, and adoption monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | ||
| PC-0900✎ edit📣 feedback | received | Core architects agent |
3.4.4 Operational governance §3.4.4 p.57 l.Lines 352-357 |
Service levels and semantic conformance are included in operational governance, but the section does not require object…Service levels and semantic conformance are included in operational governance, but the section does not require objective acceptance criteria or independent verification for critical components. Suggested revision: Require measurable service-level indicators, conformance test results, data-quality thresholds, security controls, and evidence of independent or governance-approved verification before major releases become operational. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | ||
| PC-0901✎ edit📣 feedback | received | Core architects agent, medium |
3.4.4 Operational governance §3.4.4 p.57 l.Lines 358-361 |
Evaluation of unintended consequences is mentioned, but there is no mechanism for receiving and acting on feedback from…Evaluation of unintended consequences is mentioned, but there is no mechanism for receiving and acting on feedback from health workers, patients, implementers, or excluded communities. Suggested revision: Establish continuous feedback channels, user-support data analysis, incident and complaint review, field observation, periodic user research, and defined pathways for translating findings into operational and strategic decisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | ||
| PC-0902✎ edit📣 feedback | received | Core architects Clinical agent |
3.4.4 Operational governance §3.4.4 p.57 l.Lines 362-371 |
Escalation triggers are useful but mainly cover scope, resource use, conflict, security incidents, and funding constrai…Escalation triggers are useful but mainly cover scope, resource use, conflict, security incidents, and funding constraints. Clinical-safety risks, persistent data-quality failures, legal non-compliance, supplier failure, and inequitable access are missing. Suggested revision: Add escalation triggers for clinical-safety risk, serious privacy violations, systemic data-quality problems, legal or regulatory non-compliance, supplier insolvency or lock-in, prolonged service failure, and identified discriminatory impacts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-046 discuss | in the document all mentions on GitHub record | ||
| PC-0903✎ edit📣 feedback | received | Core architects agent |
3.4.4 Operational governance §3.4.4 p.57 l.Lines 362-371 |
The section requires escalations to be time-bound but does not identify decision deadlines, temporary controls, or auth…The section requires escalations to be time-bound but does not identify decision deadlines, temporary controls, or authority during unresolved cases. Suggested revision: Require severity-based response times, named decision owners, interim risk controls, continuity arrangements, documentation requirements, and appeal or review mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-046 discuss | in the document all mentions on GitHub record | ||
| PC-0904✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57-58 l.Lines 373-398 |
The section provides a strong rationale for semantic governance, but SGI is described both as an “infrastructure” and a…The section provides a strong rationale for semantic governance, but SGI is described both as an “infrastructure” and as a non-technical governance capability. The word infrastructure may lead readers to expect a new platform or product. Suggested revision: Consider renaming it Semantic Governance Framework and Capabilities, or state prominently and consistently that SGI is an institutional and operational capability supported by tools, not a separate software component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-0905✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.Lines 373-385 |
SGI is initially linked to metadata registries, terminology, and information models. Semantic consistency also depends …SGI is initially linked to metadata registries, terminology, and information models. Semantic consistency also depends on implementation guides, profiles, mappings, data dictionaries, measures, computable guidelines, and transformation specifications. Suggested revision: Expand the governed artefact scope to include implementation guides, profiles, extensions, data elements, value sets, concept maps, mappings, indicators, measures, computable guidelines, and exchange specifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-0906✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57 l.Lines 373-385 |
Client, facility, workforce, and product registries are described as metadata registries. These registries contain auth…Client, facility, workforce, and product registries are described as metadata registries. These registries contain authoritative entity data, not only metadata. Applying “metadata registry” to all of them may be conceptually misleading. Suggested revision: Use core authoritative registries and semantic artefact repositories as the broader category. Reserve “metadata registry” for catalogues or registries whose primary content is metadata. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-0907✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.57-58 l.Lines 386-398 |
The advice to invest first in committees, roles, decision rights, and processes is sensible, but some countries may nee…The advice to invest first in committees, roles, decision rights, and processes is sensible, but some countries may need basic tooling to make governance feasible where staff capacity is limited and assets are already fragmented. Suggested revision: Reframe this as proportional co-development: establish minimum governance roles and decision rights first, while introducing fit-for-purpose tooling incrementally to support traceability, workflow, versioning, publication, and distribution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-0908✎ edit📣 feedback | received | Metadata registries agent, medium |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.58 l.Lines 400-416 |
The distinction between SGI and runtime services is valuable. However, the document presents cross-registry semantic go…The distinction between SGI and runtime services is valuable. However, the document presents cross-registry semantic governance as a new aspect introduced by DPI-H without sufficiently qualifying similar work in standards organisations, national terminology centres, metadata repositories, and enterprise data-governance programmes. Suggested revision: Clarify that the contribution is the integration and explicit architectural treatment of these capabilities across DPI-H components, rather than claiming that cross-asset semantic governance itself is entirely new. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-0909✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.58 l.Lines 400-416 |
Runtime terminology lookup and validation are described, but the runtime role of information models is less clear. Logi…Runtime terminology lookup and validation are described, but the runtime role of information models is less clear. Logical models may be transformed into implementation artefacts and validators rather than queried directly during every transaction. Suggested revision: Distinguish design-time governance, publication-time artefact generation, deployment-time conformance, and runtime validation for both terminology and information-model assets. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-058 discuss | in the document all mentions on GitHub record | ||
| PC-0910✎ edit📣 feedback | received | Metadata registries agent, medium |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.58 l.Lines 418-430 |
The three-layer model uses “content and application layer” for clinical systems, analytics platforms, and applications.…The three-layer model uses “content and application layer” for clinical systems, analytics platforms, and applications. This combines governed content with the systems that consume it, although content artefacts also exist in the governance and runtime layers. Suggested revision: Rename the third layer Consumption, implementation, and feedback layer, and represent governed content as flowing from authoring and publication into runtime distribution and consuming implementations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-0911✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.59 l.Figure 3.4.1 anchor: medium |
The figure should make the feedback loop from implementation to governance explicit, including local change requests, i…The figure should make the feedback loop from implementation to governance explicit, including local change requests, implementation problems, usage evidence, and identified gaps. Without this, semantic governance may appear primarily top-down. Suggested revision: Ensure the figure shows bidirectional flows: publication and distribution downward; implementation feedback, local requests, adoption data, and quality issues upward. Add clear ownership and decision points. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-0912✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.59-60 l.Lines 437-450 and SGI capability table |
The five capability categories provide a useful structure, but validation, testing, dependency management, impact analy…The five capability categories provide a useful structure, but validation, testing, dependency management, impact analysis, localisation, translation, and deprecation management are distributed implicitly rather than clearly visible. Suggested revision: Add these as explicit capabilities or show their mapping across the five categories. In particular, identify dependency and impact analysis as mandatory for changes affecting linked terminologies, models, profiles, and guidelines. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-0913✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.59-60 l.SGI capability table, “Monitoring” anchor: medium |
Monitoring combines adherence to governance rules, content quality, use, and adoption. These require different indicato…Monitoring combines adherence to governance rules, content quality, use, and adoption. These require different indicators, data sources, accountabilities, and responses. Suggested revision: Divide monitoring into at least: governance-process performance; artefact quality and conformance; implementation adoption; runtime use; and observed outcomes or interoperability failures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-0914✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.60 l.SGI capability table, “Distribution” anchor: medium |
Distribution across “a range of consumption modalities” is mentioned but does not explicitly cover offline packages, lo…Distribution across “a range of consumption modalities” is mentioned but does not explicitly cover offline packages, low-bandwidth access, version-pinned releases, local mirrors, or synchronisation in intermittently connected settings. Suggested revision: Add distribution patterns for online APIs, downloadable packages, local mirrors, offline bundles, event notifications, and version-pinned releases, with integrity verification and synchronisation requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-0915✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.60 l.Lines 445-450 |
Policy is described as cutting across all five capability categories, but governance also depends on decision rights, a…Policy is described as cutting across all five capability categories, but governance also depends on decision rights, accountability, funding, skills, and institutional authority. Policy alone is not the connective tissue. Suggested revision: Replace “policy” with “governance arrangements,” encompassing policies, legal authority, roles, decision rights, accountability, financing, competencies, and operating procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-0916✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.60 l.Lines 452-463 |
The maturity-spectrum approach is appropriate, but the text does not define the minimum semantic-governance capability …The maturity-spectrum approach is appropriate, but the text does not define the minimum semantic-governance capability required at the earliest stage. Countries could deploy registries without even basic naming, versioning, ownership, or change control. Suggested revision: Define a minimum baseline comprising named ownership, unique artefact identifiers, versioning, provenance, approval authority, publication status, change log, basic quality review, and a mechanism for communicating updates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-0917✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.60-61 l.Lines 452-467 and Figure 3.4.2 |
SGI maturity is described using a terminology-management maturity model adapted across all metadata components. A termi…SGI maturity is described using a terminology-management maturity model adapted across all metadata components. A terminology-specific model may not fully address information models, registry schemas, mappings, implementation guides, and computable guidelines. Suggested revision: Develop or reference a broader semantic-governance maturity model and explain which terminology-model dimensions can be reused and which additional capabilities are needed for other asset types. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-0918✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.61 l.Figure 3.4.2 anchor: medium |
The maturity spectrum is adapted from an external model, but the criteria distinguishing each maturity level are not fu…The maturity spectrum is adapted from an external model, but the criteria distinguishing each maturity level are not fully described in the main text. Readers may interpret maturity as technology sophistication rather than governance capability. Suggested revision: Provide a table defining each maturity level across governance, people, process, content, technology, adoption, and measurement dimensions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-0919✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.61 l.Lines 469-485 |
The top-down and upward-sensing model is valuable, but it does not explicitly address multilingual localisation, local …The top-down and upward-sensing model is valuable, but it does not explicitly address multilingual localisation, local clinical concepts with no international equivalent, or mappings that are context-dependent and cannot be treated as exact equivalence. Suggested revision: Add governance for language variants, local extensions, unmapped concepts, mapping equivalence, context and purpose of mappings, confidence, review dates, and communication of mapping limitations to consuming systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | ||
| PC-0920✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.61 l.Lines 477-485 |
HL7 UTG, SNOMED National Release Centres, and OpenHIE are useful references, but they represent different scopes and go…HL7 UTG, SNOMED National Release Centres, and OpenHIE are useful references, but they represent different scopes and governance models. The text may imply that they can be combined straightforwardly into one national SGI. Suggested revision: Add a comparison of their scope, authority, artefacts, licensing, participation model, and applicability. Clarify that countries must define how these external governance processes interact with national authority. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-0921✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.62 l.Figure 3.4.3 anchor: medium |
A hierarchical global-national-facility terminology model may be too linear. Content can originate from regional networ…A hierarchical global-national-facility terminology model may be too linear. Content can originate from regional networks, professional bodies, laboratories, public-health programmes, vendors, and local communities, with multiple peer-to-peer relationships. Suggested revision: Present the model as a federated governance ecosystem rather than a strict hierarchy. Show global, regional, national, programme, institutional, and local sources with governed publication and feedback pathways. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-0922✎ edit📣 feedback | received | Metadata registries agent |
3.4.5 Semantic Governance Infrastructure §3.4.5 p.62 l.Lines 491-493 |
The section says SGI should not be treated as optional, while earlier sections describe the LIMR as an enabler that can…The section says SGI should not be treated as optional, while earlier sections describe the LIMR as an enabler that can be built as maturity grows. This may create uncertainty about which SGI capabilities are essential at the REDDHI starting point. Suggested revision: Distinguish the minimum semantic-governance baseline, which is required from the outset, from advanced SGI capabilities that can mature progressively alongside the Terminology Service, LIMR, and national implementation guides. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-0923✎ edit📣 feedback | received | Core architects agent |
3.4.6 Regional governance considerations §3.4.6 p.62 l.Lines 495-502 |
Regional governance is described mainly in relation to legal authority, sovereignty, and dispute resolution. It gives l…Regional governance is described mainly in relation to legal authority, sovereignty, and dispute resolution. It gives limited attention to differences in language, terminology editions, digital maturity, financing, infrastructure, and operational capacity across participating countries. Suggested revision: Expand regional considerations to include multilingual interoperability, maturity differences, shared-service funding, capacity support, service-level variation, cross-border incident response, and phased participation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-053 discuss | in the document all mentions on GitHub record | ||
| PC-0924✎ edit📣 feedback | received | Core architects agent |
3.4.6 Regional governance considerations §3.4.6 p.62 l.Lines 503-509 |
The recommendation that a regional strategic body should have authority to make binding decisions may not be legally or…The recommendation that a regional strategic body should have authority to make binding decisions may not be legally or politically feasible in every regional arrangement. Some regional organisations operate through voluntary coordination or mutual recognition. Suggested revision: Present binding regional authority as one model. Include alternatives such as treaty-based authority, mutual-recognition arrangements, coordinated national decisions, voluntary standards adoption, and shared-service agreements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-053 discuss | in the document all mentions on GitHub record | ||
| PC-0925✎ edit📣 feedback | received | Core architects agent |
3.4.6 Regional governance considerations §3.4.6 p.62-63 l.Lines 503-515 |
Regional governance is given a financial-sustainability mandate, but no options are provided for allocating costs acros…Regional governance is given a financial-sustainability mandate, but no options are provided for allocating costs across countries with different population sizes, income levels, usage, and ability to pay. Suggested revision: Add cost-sharing models based on equal contribution, population, usage, income, benefit, or blended formulas, with solidarity mechanisms and protection against excluding lower-resource participants. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-053 discuss | in the document all mentions on GitHub record | ||
| PC-0926✎ edit📣 feedback | received | Core architects agent |
3.4.6 Regional governance considerations §3.4.6 p.63 l.Lines 511-515 |
The layered regional-governance model appropriately separates regional and national authority but does not address conf…The layered regional-governance model appropriately separates regional and national authority but does not address conformance assessment, trust-list management, certificate governance, cross-border terminology services, or incident coordination. Suggested revision: Add these shared operational governance areas and define the handoff between regional and national authorities for conformance, trust, security incidents, terminology, identity, consent, and service continuity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-053 discuss | in the document all mentions on GitHub record | ||
| PC-0927✎ edit📣 feedback | received | Core architects agent |
3.4.7 Governance maturity considerations §3.4.7 p.63 l.Lines 517-528 |
The maturity discussion correctly recognises that early-stage countries may use one committee for strategic and operati…The maturity discussion correctly recognises that early-stage countries may use one committee for strategic and operational governance. However, it does not address safeguards against concentration of authority or conflicts of interest in this transitional arrangement. Suggested revision: Require role separation within the committee, documented decision categories, conflict-of-interest declarations, independent review for high-risk decisions, transparent records, and a time-bound roadmap toward stronger institutional separation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-045 discuss | in the document all mentions on GitHub record | ||
| PC-0928✎ edit📣 feedback | received | Core architects agent |
3.4.7 Governance maturity considerations §3.4.7 p.63 l.Lines 529-532 |
Governance maturity assessment is recommended, but no assessment dimensions, evidence requirements, scoring approach, o…Governance maturity assessment is recommended, but no assessment dimensions, evidence requirements, scoring approach, or link to implementation sequencing are provided. Suggested revision: Provide a governance-maturity assessment covering legal authority, institutional mandate, decision rights, stakeholder participation, data stewardship, semantic governance, security, financing, service management, procurement enforcement, and monitoring. Link results to the national roadmap. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-054 discuss | in the document all mentions on GitHub record | ||
| PC-0929✎ edit📣 feedback | received | Core architects agent |
3.4.7 Governance maturity considerations §3.4.7 p.63 l.Lines 517-532 |
Governance maturity is discussed mainly as institutional capacity. Political commitment, administrative stability, corr…Governance maturity is discussed mainly as institutional capacity. Political commitment, administrative stability, corruption risk, procurement integrity, regulatory independence, and public trust may also determine whether formal governance structures work in practice. Suggested revision: Acknowledge these contextual conditions and recommend risk-based mitigation, transparency measures, independent oversight, audit, public reporting, and staged delegation of authority. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-054 discuss | in the document all mentions on GitHub record | ||
| PC-0930✎ edit📣 feedback | received | Core architects agent |
3.5 DPI-H Application Components §3.5 p.63 l.Lines 536-542 |
The section introduces DPI-H application components as digital resources established once and reused by many programmes…The section introduces DPI-H application components as digital resources established once and reused by many programmes. “Established once” may imply one national software deployment, which conflicts with the document’s support for federated, distributed, and hybrid implementations. Suggested revision: Replace “establishes once” with “governs as a shared national capability,” clarifying that the capability may be realised by one or more coordinated systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-0931✎ edit📣 feedback | received | Core architects agent, medium |
3.5 DPI-H Application Components §3.5 p.63 l.Lines 536-542 |
The section is central to policymakers, architects, procurement teams, and donors, but the detailed component descripti…The section is central to policymakers, architects, procurement teams, and donors, but the detailed component descriptions are placed in a very long technical appendix. A concise comparative overview of all components is missing from the main section. Suggested revision: Add a summary table listing each component, its purpose, layer, principal capabilities, key data, main dependencies, likely authoritative authority, and distinction from related operational applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-062 discuss | in the document all mentions on GitHub record | ||
| PC-0932✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.63-64 l.Lines 544-549 |
The section says a component “earns” DPI-H designation by satisfying a set of criteria. However, it does not explain th…The section says a component “earns” DPI-H designation by satisfying a set of criteria. However, it does not explain the assessment method used to determine that every component in the proposed architecture satisfies those criteria. Suggested revision: Add a component-assessment matrix showing how each proposed component meets the defining criteria, including any partial compliance, exceptions, or context-dependent classification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-062 discuss | in the document all mentions on GitHub record | ||
| PC-0933✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 549-550 |
Reusability “without modification to its core design” may be unrealistic. Shared components often require configurable …Reusability “without modification to its core design” may be unrealistic. Shared components often require configurable workflows, jurisdictional extensions, localisation, terminology bindings, and deployment-specific security controls. Suggested revision: Replace with a statement like: “Reusable across multiple programmes and use cases without changes that compromise its core function, public interfaces, or conformance obligations.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0934✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 551-552 |
Stable standards-based interfaces are appropriate, but the requirement does not address versioning, backward compatibil…Stable standards-based interfaces are appropriate, but the requirement does not address versioning, backward compatibility, deprecation, event interfaces, bulk exchange, or offline distribution. Suggested revision: Expand the criterion to require versioned interfaces, compatibility policies, published deprecation periods, standard query and event patterns, machine-readable specifications, and appropriate bulk or offline access mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0935✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 553-555 |
“Foundational health system functions” is not defined precisely enough to distinguish DPI-H components from widely reus…“Foundational health system functions” is not defined precisely enough to distinguish DPI-H components from widely reused operational platforms. A system may serve several programmes without constituting public infrastructure. Suggested revision: Define foundational functions using additional tests such as dependency centrality, authoritative responsibility, public-interest value, lifecycle stability, cross-programme reuse, non-discriminatory access, and difficulty of efficient duplication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0936✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 556-557 |
Public governance is treated as a defining property, but it is unclear whether components not currently publicly govern…Public governance is treated as a defining property, but it is unclear whether components not currently publicly governed are excluded from DPI-H or may become DPI-H once appropriate governance is established. Suggested revision: Clarify that DPI-H classification describes the target governance condition. Existing systems may provisionally realise the capability, but should not be treated as conformant DPI-H components until public accountability, access, control, and lifecycle arrangements are established. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0937✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 556-560 |
The criteria distinguish public governance from lifecycle governance but do not explicitly require sustainable financin…The criteria distinguish public governance from lifecycle governance but do not explicitly require sustainable financing, an operating model, service ownership, or supplier-exit arrangements. Suggested revision: Add criteria requiring accountable service ownership, a sustainable operating model, recurrent financing, support arrangements, data and configuration portability, continuity planning, and supplier transition provisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0938✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 561-563 |
The criterion that DPI-H components should be “non-transactional” conflicts with components such as the Computable Deci…The criterion that DPI-H components should be “non-transactional” conflicts with components such as the Computable Decision Support Engine, HMIS, Public Health Surveillance Platform, and possibly the Lifelong Health Record, all of which may process operational transactions. Suggested revision: Replace “non-transactional” with: “not primarily responsible for local point-of-service workflow or programme-specific transaction processing.” Assess every proposed component against the revised criterion. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0939✎ edit📣 feedback | received | Editorial Core architects agent, medium |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 561-563 |
“Orchestrates national-level data” is used to describe non-transactional infrastructure. Orchestration normally implies…“Orchestrates national-level data” is used to describe non-transactional infrastructure. Orchestration normally implies active coordination of transactions or workflows, making the description internally contradictory. Suggested revision: Replace with phrase liek: “maintains or provides shared data, reference information, or reusable services to operational systems.” Reserve “orchestration” for components that genuinely coordinate transactions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0940✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 564-567 |
Functional stability is treated as a defining characteristic, but national health infrastructure must evolve with clini…Functional stability is treated as a defining characteristic, but national health infrastructure must evolve with clinical guidance, law, technology, and health-system needs. Stability should apply to contracts and purpose, not to functionality remaining unchanged. Suggested revision: Define stability as predictable evolution: stable purpose, governed interfaces, semantic versioning, backward compatibility where appropriate, published migration paths, and controlled deprecation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0941✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 568-571 |
Technology neutrality is appropriate at reference-architecture level, but several later requirements recommend or depen…Technology neutrality is appropriate at reference-architecture level, but several later requirements recommend or depend on particular technologies and standards, particularly FHIR. The relationship between technology neutrality and standards endorsement needs clarification. Suggested revision: State that technology neutrality permits different conformant implementations, while the architecture may still specify mandatory or recommended open standards needed for interoperability and conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-0942✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64 l.Lines 573-576 |
The text states that a qualifying component justifies shared investment and governance. Meeting architectural criteria …The text states that a qualifying component justifies shared investment and governance. Meeting architectural criteria does not automatically demonstrate cost-effectiveness or justify national investment. Suggested revision: Add that investment decisions require a country-specific business case covering demand, alternatives, current assets, total cost of ownership, governance readiness, expected reuse, benefits, risks, and implementation capacity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0943✎ edit📣 feedback | received | Core architects agent, medium |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64-65 l.Box 3.1 anchor: medium |
Box 3.1 repeats the criteria from the preceding text almost verbatim. This adds length without providing a more usable …Box 3.1 repeats the criteria from the preceding text almost verbatim. This adds length without providing a more usable decision aid. Suggested revision: Convert the box into a scored or evidence-based assessment checklist with columns for criterion, required evidence, assessment question, and potential exception. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-062 discuss | in the document all mentions on GitHub record | ||
| PC-0944✎ edit📣 feedback | received | Core architects agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.64-65 l.Box 3.1 anchor: medium |
The criteria do not explicitly include security, privacy, resilience, accessibility, equity, data quality, conformance …The criteria do not explicitly include security, privacy, resilience, accessibility, equity, data quality, conformance testability, or operational sustainability, although these are central DPI-H principles elsewhere. Suggested revision: Add these criteria or indicate that compliance with all Section 1.4 and Section 2.3 principles is mandatory and must be evidenced as part of component assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-061 discuss | in the document all mentions on GitHub record | ||
| PC-0945✎ edit📣 feedback | received | Core architects agent, medium |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.65 l.Lines 580-590 |
Civil registration, vital statistics, and national geospatial registries are categorically placed in foundational DPI. …Civil registration, vital statistics, and national geospatial registries are categorically placed in foundational DPI. In some countries, CRVS or geospatial services may not be governed or delivered as DPI, and health may operate sector-specific capabilities. Suggested revision: Describe these as potential foundational or cross-sector authoritative capabilities. Where unavailable, health may maintain interim functionality with an explicit integration and transition plan. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-267 discuss | in the document all mentions on GitHub record | ||
| PC-0946✎ edit📣 feedback | received | WHO Core architects agent, medium |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.65 l.Lines 586-590 |
CRVS is grouped with cross-sector infrastructure, but vital-event registration has direct and substantial health-sector…CRVS is grouped with cross-sector infrastructure, but vital-event registration has direct and substantial health-sector participation. The boundary between health-generated birth or death notifications and authoritative civil registration is not explained. Suggested revision: Clarify that health systems may generate and exchange notifications or medical cause-of-death information, while the legally authoritative civil registration function remains with the designated civil authority. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-267 discuss | in the document all mentions on GitHub record | ||
| PC-0947✎ edit📣 feedback | received | Core architects agent, medium |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.65 l.Lines 592-600 |
The policy-level definition describes a registry as a single authoritative source, while implementation may be centrali…The policy-level definition describes a registry as a single authoritative source, while implementation may be centralised, federated, or hybrid. “Single source” can still be misread as requiring one physical repository. Suggested revision: Use “authoritative national reference” or “authoritative source arrangement,” and distinguish logical authority from physical storage and organisational distribution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-051 discuss | in the document all mentions on GitHub record | ||
| PC-0948✎ edit📣 feedback | received | Financial systems agent |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.65 l.Lines 597-600 |
The Benefits Package Registry is contrasted with claims and payment systems, but its boundary with beneficiary enrolmen…The Benefits Package Registry is contrasted with claims and payment systems, but its boundary with beneficiary enrolment, provider contracting, tariff management, prior authorisation, and executable claims rules is not established here. Suggested revision: Add a concise boundary statement and cross-reference the detailed comparison in Appendix C. Specify which information is authoritative reference content and which processes remain operational. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-0949✎ edit📣 feedback | received | Core architects Editorial agent, medium |
3.5.1 What Distinguishes a DPI-H Application Component §3.5.1 p.65 l.Lines 601-605 |
The section acknowledges alternative names such as MPI and registry versus catalogue, but a general naming and synonym …The section acknowledges alternative names such as MPI and registry versus catalogue, but a general naming and synonym policy is not provided for the architecture. This may hinder country mapping. Suggested revision: For every component, publish preferred name, accepted synonyms, excluded meanings, and mapping guidance for common national or vendor terminology. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | ||
| PC-0950✎ edit📣 feedback | received | Core architects agent |
3.5.2 How each component is described §3.5.2 p.65-66 l.Lines 608-620 |
The common component-description structure is useful, but the list does not explicitly include ownership, service model…The common component-description structure is useful, but the list does not explicitly include ownership, service model, maturity dependencies, implementation options, non-functional requirements, risks, or transition considerations. Suggested revision: Extend the template to include accountable authority, operating model, maturity prerequisites, topology options, non-functional requirements, security and privacy, migration considerations, measurable outcomes, and known standards gaps. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-063 discuss | in the document all mentions on GitHub record | ||
| PC-0951✎ edit📣 feedback | received | Core architects agent, medium |
3.5.2 How each component is described §3.5.2 p.66 l.Lines 614-620 |
The section says requirements use a tiered model of SHALL, SHOULD, and MAY, while Appendix C tables mainly use Required…The section says requirements use a tiered model of SHALL, SHOULD, and MAY, while Appendix C tables mainly use Required, Recommended, and occasionally Optional. This creates normative ambiguity. Suggested revision: Select one normative convention and apply it consistently. Prefer recognised standards terminology: SHALL for mandatory requirements, SHOULD for recommended requirements with documented exceptions, and MAY for optional capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-0952✎ edit📣 feedback | received | Core architects agent |
3.5.2 How each component is described §3.5.2 p.66 l.Lines 614-620 |
Requirement status alone does not define conformance. The document does not consistently identify test methods, evidenc…Requirement status alone does not define conformance. The document does not consistently identify test methods, evidence, applicable profiles, conditional requirements, or implementation-option dependencies. Suggested revision: Add fields for conformance statement, test method, expected evidence, applicable standard or profile, conditional applicability, actor role, and required test data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-063 discuss | in the document all mentions on GitHub record | ||
| PC-0953✎ edit📣 feedback | received | Core architects agent |
3.5.2 How each component is described §3.5.2 p.66 l.Lines 616-619 |
The template gives functional and data requirements but does not clearly distinguish universal requirements from countr…The template gives functional and data requirements but does not clearly distinguish universal requirements from country-configurable requirements or staged maturity targets. Suggested revision: Classify requirements as universal baseline, conditional by use case, conditional by maturity, jurisdiction-specific, or advanced target-state capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-063 discuss | in the document all mentions on GitHub record | ||
| PC-0954✎ edit📣 feedback | received | Core architects agent |
3.5.2 How each component is described §3.5.2 p.66 l.Lines 608-620 |
The component descriptions are intended for planning and procurement, but they do not include indicative implementation…The component descriptions are intended for planning and procurement, but they do not include indicative implementation dependencies or sequencing. Countries may procure a component without the governance or data foundations needed to operate it effectively. Suggested revision: Add prerequisites and dependencies to each description, including governance readiness, authoritative data sources, terminology and model dependencies, foundational DPI integration, workforce needs, and transition requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-063 discuss | in the document all mentions on GitHub record | ||
| PC-0955✎ edit📣 feedback | received | Core architects agent |
3.5.3 How the components are organised §3.5.3 p.66 l.Lines 622-630; Figure 3.5 |
Figure 3.5 includes point-of-care applications, DPI-H components, cross-cutting enablers, foundational DPI, and technol…Figure 3.5 includes point-of-care applications, DPI-H components, cross-cutting enablers, foundational DPI, and technology. The two internal DPI-H layers are not sufficiently prominent in the caption, which may weaken the intended two-layer concept. Suggested revision: Visually separate and label the foundational shared data layer and business-services layer within the DPI-H boundary. Use a distinct boundary for non-DPI-H operational applications and foundational DPI. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0956✎ edit📣 feedback | received | Editorial agent |
3.5.3 How the components are organised §3.5.3 p.66 l.Figure 3.5 anchor: medium |
The figure caption is highly detailed and similar to the earlier Figure 3.2 caption. The purpose and difference between…The figure caption is highly detailed and similar to the earlier Figure 3.2 caption. The purpose and difference between Figures 3.2 and 3.5 are not immediately clear. Suggested revision: State explicitly that Figure 3.2 traces goals and capabilities, while Figure 3.5 focuses on application-component organisation. Remove duplicated caption wording. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0957✎ edit📣 feedback | received | Core architects agent |
3.5.3 How the components are organised §3.5.3 p.66 l.Figure 3.5 anchor: medium |
The layered visual may be interpreted as a strict technology stack in which every upper layer depends synchronously on …The layered visual may be interpreted as a strict technology stack in which every upper layer depends synchronously on all lower layers. This may not reflect asynchronous, federated, offline, or progressively implemented environments. Suggested revision: Add a note that the layers express logical dependency and reuse, not mandatory physical deployment order, centralisation, or synchronous runtime dependency. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-266 discuss | in the document all mentions on GitHub record | ||
| PC-0958✎ edit📣 feedback | received | Core architects agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 633-636 |
The text states that the metadata registries and LHR “make up REDDHI,” but Section 2.2 defines REDDHI more broadly as a…The text states that the metadata registries and LHR “make up REDDHI,” but Section 2.2 defines REDDHI more broadly as a maturing condition supported by governance, interoperability, standards, terminology, consent, trust, and resilience. Suggested revision: Replace with a sentence like: “form part of the essential technical foundation for progress toward REDDHI.” Avoid equating a set of components with REDDHI itself. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-064 discuss | in the document all mentions on GitHub record | ||
| PC-0959✎ edit📣 feedback | received | Core architects Clinical agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 633-650 |
The layer is called the “foundational shared data layer,” but it contains both authoritative entity registries and the …The layer is called the “foundational shared data layer,” but it contains both authoritative entity registries and the LHR, which holds or assembles clinical data. The category is clearer than “metadata registries,” but the distinct data responsibilities should be visible. Suggested revision: Subdivide the layer conceptually into authoritative entity references, longitudinal health-data capability, and semantic and structural foundations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-064 discuss | in the document all mentions on GitHub record | ||
| PC-0960✎ edit📣 feedback | received | Core architects agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 637-646 |
The list of core registries includes clients, facilities, workforce, and products, but no explicit organisation or prov…The list of core registries includes clients, facilities, workforce, and products, but no explicit organisation or provider-organisation registry is included. The Facility Registry does not necessarily represent legal organisations, payers, laboratories, suppliers, regulators, or networks. Suggested revision: Assess whether a shared organisation registry or organisation-identification capability is required. If it is expected from foundational DPI or another component, state this explicitly and describe the relationship. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-268 discuss | in the document all mentions on GitHub record | ||
| PC-0961✎ edit📣 feedback | received | Core architects agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 640-643 |
The Facility Registry and Workforce Registry are listed separately, but health service discovery often depends on organ…The Facility Registry and Workforce Registry are listed separately, but health service discovery often depends on organisations, locations, practitioners, practitioner roles, services, and relationships among them. The proposed boundaries may not fully represent the mCSD model cited later. Suggested revision: Clarify how organisations, facilities or locations, practitioners, practitioner roles, services, and organisational affiliations are distributed across components and queried as a coherent service directory. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-268 discuss | in the document all mentions on GitHub record | ||
| PC-0962✎ edit📣 feedback | received | Clinical Core architects agent, medium |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 646-650 |
The LHR is described as maintaining a longitudinal record while allowing centralised, federated, or hybrid implementati…The LHR is described as maintaining a longitudinal record while allowing centralised, federated, or hybrid implementation. “Maintains” may incorrectly suggest that all conformant implementations persist a consolidated national record. Suggested revision: Replace with sentecne like: “provides governed longitudinal access to an individual’s health information, whether through consolidated storage, federated retrieval, or a hybrid arrangement.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-0963✎ edit📣 feedback | received | Clinical Core architects agent, medium |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 646-650 |
Treating the LHR as foundational may be unrealistic where facilities still depend on paper records, basic registers, or…Treating the LHR as foundational may be unrealistic where facilities still depend on paper records, basic registers, or poorly connected programme systems. The document does not define a minimum viable LHR scope. Suggested revision: Define progressive LHR maturity levels, beginning with priority summaries or datasets, selected facilities and programmes, and document exchange before advancing to comprehensive structured longitudinal information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-0964✎ edit📣 feedback | received | Editorial agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 646-650 |
The final sentence contains the fragment “person-centred that,” indicating an unfinished editing error.The final sentence contains the fragment “person-centred that,” indicating an unfinished editing error. Suggested revision: Delete the fragment and proofread the paragraph before publication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-060 discuss | in the document all mentions on GitHub record | ||
| PC-0965✎ edit📣 feedback | received | Core architects agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 651-658 |
The paragraph explains the interdependence of client, facility, workforce, LHR, and product registries. It does not add…The paragraph explains the interdependence of client, facility, workforce, LHR, and product registries. It does not address whether all provenance must resolve synchronously to authoritative registries at runtime or whether historical references and cached identifiers are acceptable. Suggested revision: Clarify that consuming records should retain stable identifiers and sufficient historical provenance. Runtime dependence on live registry availability should be minimised through caching, versioned references, and asynchronous reconciliation where appropriate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-0966✎ edit📣 feedback | received | Core architects agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 651-658 |
Countries are told to adopt registries in a sequence suited to their priorities, but no method is provided for managing…Countries are told to adopt registries in a sequence suited to their priorities, but no method is provided for managing inconsistent identifiers and source lists during the transition. Suggested revision: Add transition guidance covering source-system inventory, temporary crosswalks, canonical identifier assignment, duplicate resolution, data-quality remediation, phased onboarding, coexistence, and retirement of local master lists. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-0967✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 659-666 |
The Terminology Service and LIMR are described as components that provide meaning and structure. Semantic interoperabil…The Terminology Service and LIMR are described as components that provide meaning and structure. Semantic interoperability also depends on use-context, provenance, data-capture guidance, implementation guides, mappings, constraints, and workflow interpretation. Suggested revision: Clarify that the TS and LIMR are core enabling components within a broader semantic-governance ecosystem and do not alone guarantee semantic interoperability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-0968✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.67 l.Lines 664-666 |
The LIMR is described as constraining “uncontrolled local variation.” Local variation is not inherently undesirable and…The LIMR is described as constraining “uncontrolled local variation.” Local variation is not inherently undesirable and may be clinically or culturally necessary. The problem is undocumented or non-interoperable variation. Suggested revision: Replace with sentence like: “governs necessary national and local variation through explicit extensions, constraints, mappings, versioning, and conformance rules.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-0969✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.68 l.Lines 674-679 |
The comparison states that one component controls syntax and the other controls semantics. This is an oversimplificatio…The comparison states that one component controls syntax and the other controls semantics. This is an oversimplification. Information models also carry semantics through element definitions, context, constraints, relationships, and terminology bindings, while syntax usually concerns technical representation. Suggested revision: Replace the syntax-versus-semantics distinction with structure and contextual meaning versus coded concept meaning. State that both contribute to semantic interoperability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-0970✎ edit📣 feedback | received | Metadata registries agent, medium |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.68-70 l.Table 3.5 |
The LIMR and Terminology Service comparison is helpful but very long for the main chapter. Its length interrupts the ar…The LIMR and Terminology Service comparison is helpful but very long for the main chapter. Its length interrupts the architectural narrative and may be more suitable for an appendix or implementation guide. Suggested revision: Retain a concise comparison covering purpose, artefacts, lifecycle, users, and relationship in the main text. Move detailed examples and operational distinctions to Appendix C or a dedicated semantic-governance annex. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-0971✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.68 l.Table 3.5, “Core question answered” |
The blood-pressure example uses SNOMED CT concept 271649006 for systolic blood pressure and LOINC 8480-6 as an “equival…The blood-pressure example uses SNOMED CT concept 271649006 for systolic blood pressure and LOINC 8480-6 as an “equivalent.” These codes may represent related observations in different terminology models rather than simple exact equivalence. Suggested revision: Avoid presenting the relationship as unqualified equivalence. State that mappings have context, purpose, and equivalence properties and must be governed and validated for the intended use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | ||
| PC-0972✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.68-69 l.Table 3.5, blood-pressure examples |
The example data model specifies decimal blood-pressure values in mmHg, but it does not mention terminology and unit st…The example data model specifies decimal blood-pressure values in mmHg, but it does not mention terminology and unit standards such as UCUM or formal profiling and validation. Suggested revision: Include unit coding and validation in the example, and explain that data types, units, terminology bindings, invariant rules, and cardinalities must be represented in implementation artefacts and tested together. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-067 discuss | in the document all mentions on GitHub record | ||
| PC-0973✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.69 l.Table 3.5, “When it is used” |
The example says a system calls the Terminology Service each time a clinician opens the screen and again on save. This …The example says a system calls the Terminology Service each time a clinician opens the screen and again on save. This may be impractical in low-connectivity settings and is not required for every implementation. Suggested revision: State that runtime terminology may be delivered through live service calls, validated caches, synchronised packages, embedded version-pinned expansions, or other conformant mechanisms appropriate to the context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-0974✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.69 l.Table 3.5, “When it is used” |
The LIMR is described primarily as a design-time asset, while runtime validation is optional. In lower-capacity setting…The LIMR is described primarily as a design-time asset, while runtime validation is optional. In lower-capacity settings, implementation artefacts may be generated centrally and distributed rather than directly consulted by every developer or system. Suggested revision: Clarify the possible use patterns: central model authoring, generated implementation guides and schemas, distributed validation artefacts, procurement reference, and optional runtime validation services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-0975✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.69 l.Table 3.5, “Relationship to each other” |
The relationship is described as bidirectional because terminology changes can affect models. The inverse impact is als…The relationship is described as bidirectional because terminology changes can affect models. The inverse impact is also important: information-model changes may require new value sets, new concepts, revised mappings, or terminology requests. Suggested revision: Describe dependency and change-impact analysis in both directions and require coordinated release planning, compatibility assessment, and notification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-0976✎ edit📣 feedback | received | Metadata registries agent, medium |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.69-70 l.Table 3.5, “Risk if absent” |
The table labels absence of an LIMR as “semantic fragmentation” and absence of a Terminology Service as “semantic drift…The table labels absence of an LIMR as “semantic fragmentation” and absence of a Terminology Service as “semantic drift.” These labels overlap and may imply a cleaner separation than exists in practice. Suggested revision: Use more specific labels: structural inconsistency and contextual divergence for absent governed models, and coded-concept inconsistency and terminology drift for absent terminology governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-0977✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.70 l.Table 3.5, “Standards it uses or produces” |
FHIR profiles, openEHR archetypes, and SMART Guidelines data dictionaries are listed together but operate at different …FHIR profiles, openEHR archetypes, and SMART Guidelines data dictionaries are listed together but operate at different abstraction levels and do not map automatically to one technology-neutral logical model. Suggested revision: Explain that the LIMR may govern linked artefacts across multiple formalisms. Require documented transformation or traceability relationships rather than assuming automatic equivalence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-0978✎ edit📣 feedback | received | Metadata registries agent |
3.5.3.1 The foundational shared data layer §3.5.3.1 p.70 l.Table 3.5, “Standards it uses or produces” |
The terminology side lists FHIR terminology resources and major code systems but omits unit standards such as UCUM and …The terminology side lists FHIR terminology resources and major code systems but omits unit standards such as UCUM and may underrepresent local or national code systems. Suggested revision: Add UCUM and explicitly include nationally governed and local code systems, naming systems, identifier systems, and mapping artefacts where no appropriate international terminology exists. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-067 discuss | in the document all mentions on GitHub record | ||
| PC-0979✎ edit📣 feedback | received | Core architects agent |
3.5.3.2 The business services layer §3.5.3.2 p.70-71 l.Lines 687-692 |
The business-services layer is described as shared reusable infrastructure extending the foundational layer. The criter…The business-services layer is described as shared reusable infrastructure extending the foundational layer. The criteria for determining why each listed service belongs in DPI-H rather than the functional-application layer remain insufficiently demonstrated. Suggested revision: Add a component-by-component classification matrix applying the Section 3.5.1 criteria and documenting why national shared provision is justified. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-062 discuss | in the document all mentions on GitHub record | ||
| PC-0980✎ edit📣 feedback | received | Core architects Clinical agent |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 693-701 |
The CDSE, Public Health Surveillance Platform, and HMIS are described at markedly different levels of abstraction. The …The CDSE, Public Health Surveillance Platform, and HMIS are described at markedly different levels of abstraction. The CDSE is an engine, the surveillance platform is a broad platform, and the HMIS can represent an entire national system. Suggested revision: Normalise component granularity. Define each as a bounded capability or logical component with clear services, data responsibilities, exclusions, and interfaces. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | ||
| PC-0981✎ edit📣 feedback | received | Clinical Core architects agent, medium |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 693-694 |
The Computable Decision Support Engine is presented as one shared component. Clinical decision support may be distribut…The Computable Decision Support Engine is presented as one shared component. Clinical decision support may be distributed among knowledge repositories, rules services, application-integrated logic, and point-of-care workflow integration. Suggested revision: Separate governed computable knowledge from execution services and workflow integration, or explain that the CDSE is a logical capability that may be realised through several distributed components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | ||
| PC-0982✎ edit📣 feedback | received | Core architects WHO agent, medium |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 695-696 |
“Public Health Surveillance Platform” is broad and may include case reporting, event-based surveillance, laboratory sur…“Public Health Surveillance Platform” is broad and may include case reporting, event-based surveillance, laboratory surveillance, contact management, analytics, alerts, and response coordination. Some of these are programme-specific or operational. Suggested revision: Define the shared surveillance capabilities included in DPI-H and distinguish them from disease-specific workflows, outbreak-management tools, laboratory systems, and emergency-response applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | ||
| PC-0983✎ edit📣 feedback | received | Core architects agent, medium |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 697-701 |
The HMIS is positioned as a shared population-level reporting component, but the term is often used for the broader set…The HMIS is positioned as a shared population-level reporting component, but the term is often used for the broader set of people, processes, policies, data, and systems supporting health management information. Treating HMIS solely as an application component may be misleading. Suggested revision: Use a more precise component name such as Aggregate Health Information and Indicator Service, or explain that the application component represents only the shared digital services within the wider HMIS. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | ||
| PC-0984✎ edit📣 feedback | received | Core architects Clinical agent, medium |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 697-701 |
The distinction between HMIS operating at population level and CDSE operating at individual level is useful but incompl…The distinction between HMIS operating at population level and CDSE operating at individual level is useful but incomplete. Decision support can also operate at population level, and HMIS outputs may support facility-level or individual follow-up. Suggested revision: Present individual-versus-population level as a typical emphasis rather than a strict architectural boundary. Define components by their services and data responsibilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | ||
| PC-0985✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 702-706 |
The Supplier Registry is classified as health-specific infrastructure, although suppliers may serve multiple government…The Supplier Registry is classified as health-specific infrastructure, although suppliers may serve multiple government sectors and may already exist in national business, tax, procurement, or legal-entity registries. Suggested revision: Treat the Supplier Registry as a health-sector extension or view of foundational business and procurement registries where available. Define the health-specific attributes that justify a DPI-H capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-0986✎ edit📣 feedback | received | Supply chain agent |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 702-706 |
The Supplier Registry overlaps potentially with the Product Registry, Facility Registry, organisation registry, procure…The Supplier Registry overlaps potentially with the Product Registry, Facility Registry, organisation registry, procurement systems, and national business registries. The authoritative source for supplier identity and regulatory status is not clear. Suggested revision: Define the authoritative responsibility for legal identity, health-sector qualification, product authorisation, facility status, sanctions, and procurement eligibility. Use cross-references rather than duplicating the same entity data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-0987✎ edit📣 feedback | received | Financial systems agent |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 707-709 |
Defining what is covered, for whom, and under which conditions may combine three separate concerns: benefit definitions…Defining what is covered, for whom, and under which conditions may combine three separate concerns: benefit definitions, scheme definitions, and beneficiary eligibility. The Benefits Package Registry should not become an operational eligibility or enrolment system. Suggested revision: Limit the component to authoritative definitions and rules. State that enrolment, beneficiary records, real-time eligibility determination, contracting, authorisation, claims adjudication, and payment remain operational capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-0988✎ edit📣 feedback | received | Core architects agent |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 710-712 |
The text says the business-services layer is “no less essential” to a complete, sustainable architecture. This may conf…The text says the business-services layer is “no less essential” to a complete, sustainable architecture. This may conflict with REDDHI’s emphasis on prioritising an essential foundational core and may imply that every country ultimately needs every listed component. Suggested revision: State that business-service components become relevant according to national goals, use cases, institutional arrangements, and existing capabilities. Avoid implying universal implementation of every component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-026 discuss | in the document all mentions on GitHub record | ||
| PC-0989✎ edit📣 feedback | received | Core architects agent |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 713-718 |
The section states that the two layers describe the full scope of DPI-H application components. This may prematurely cl…The section states that the two layers describe the full scope of DPI-H application components. This may prematurely close the architecture to additional shared components, such as consent, trust, service directories, organisation identifiers, notification services, document registries, or future nationally shared capabilities. Suggested revision: Describe the catalogue as the component set identified in the current release, subject to governed extension and revision. Publish criteria and a process for proposing, assessing, adding, merging, or retiring components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-065 discuss | in the document all mentions on GitHub record | ||
| PC-0990✎ edit📣 feedback | received | Core architects agent |
3.5.3.2 The business services layer §3.5.3.2 p.71 l.Lines 713-718 |
The component catalogue may be interpreted as a universal target architecture even where countries already provide func…The component catalogue may be interpreted as a universal target architecture even where countries already provide functions through different institutional or technical arrangements. Suggested revision: Emphasise capability coverage rather than component-name conformity. Countries should be able to demonstrate that required capabilities and governance outcomes are achieved through alternative, mapped arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-0991✎ edit📣 feedback | received | Core architects agent |
3.6 Interoperability Architecture within DPI-H §3.6 p.71-72 l.Lines 722-742 |
The section appropriately presents interoperability as a property of the architecture, but the phrase “no single system…The section appropriately presents interoperability as a property of the architecture, but the phrase “no single system can hold all of this, and none should attempt to” is too absolute. Some national or institutional platforms may legitimately consolidate broad datasets while remaining interoperable and well governed. Suggested revision: Qualify the statement: “No single system should be assumed to hold or control all relevant health information. Countries may consolidate selected datasets where justified, while preserving interoperability, proportionality, data rights, resilience, and clear governance.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-0992✎ edit📣 feedback | received | Editorial Core architects agent, medium |
3.6 Interoperability Architecture within DPI-H §3.6 p.71-72 l.Lines 722-742 |
The opening paragraph introduces many actor categories and interoperability dimensions at once. The main architectural …The opening paragraph introduces many actor categories and interoperability dimensions at once. The main architectural message may be difficult for non-technical readers to identify. Suggested revision: Add a concise opening definition: “Interoperability is the governed ability of independent systems and organisations to exchange and use information consistently, securely, and for an agreed purpose.” Follow with the detailed dimensions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-0993✎ edit📣 feedback | received | Core architects agent, medium |
3.6 Interoperability Architecture within DPI-H §3.6 p.72 l.Lines 727-730 |
The text defines interoperability partly through information being “timely, secure, clinically meaningful and usable.” …The text defines interoperability partly through information being “timely, secure, clinically meaningful and usable.” Not all DPI-H exchanges are clinical. The architecture also covers financing, supply chain, workforce, facilities, and public health. Suggested revision: Replace “clinically meaningful” with “meaningful and fit for the intended clinical, public-health, administrative, financial, or supply-chain purpose.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-0994✎ edit📣 feedback | received | Core architects agent |
3.6 Interoperability Architecture within DPI-H §3.6 p.72 l.Lines 731-742 |
The four identified dimensions are technical, structural, semantic, and organisational. Process or workflow interoperab…The four identified dimensions are technical, structural, semantic, and organisational. Process or workflow interoperability is included only indirectly under organisational interoperability, although it is essential to acting on exchanged information. Suggested revision: Explicitly include process and workflow interoperability, or explain that it is a defined part of organisational interoperability. Address roles, trigger events, expected actions, responsibility, and integration into operational workflows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-0995✎ edit📣 feedback | received | Core architects agent |
3.6 Interoperability Architecture within DPI-H §3.6 p.72 l.Lines 731-742 |
The section describes interoperability as being realised through content standards, information models, exchange patter…The section describes interoperability as being realised through content standards, information models, exchange patterns, trust, and transport. It gives less visibility to identifiers, service discovery, endpoint discovery, version negotiation, provenance, and error handling. Suggested revision: Add these as supporting interoperability capabilities and show how they relate to registries, foundational trust services, implementation guides, and operational exchange mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-0996✎ edit📣 feedback | received | Core architects agent |
3.6 Interoperability Architecture within DPI-H §3.6 p.72 l.Lines 737-742 |
The section assumes that legal basis, consent, data-sharing agreements, and governance can be established coherently ac…The section assumes that legal basis, consent, data-sharing agreements, and governance can be established coherently across all exchanging organisations. In fragmented or decentralised settings, these arrangements may be incomplete or inconsistent. Suggested revision: Add a staged pathway allowing countries to begin with bounded use cases, defined participants, limited datasets, explicit legal authority, and controlled exchange agreements before scaling nationally. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-246 discuss | in the document all mentions on GitHub record | ||
| PC-0997✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.72 l.Lines 745-757 |
The section correctly warns against interpreting an interoperability layer as one centrally procured software product. …The section correctly warns against interpreting an interoperability layer as one centrally procured software product. However, it may understate the value that shared mediation, service discovery, audit, security, and routing infrastructure can provide. Suggested revision: Clarify that the problem is not shared mediation itself, but treating interoperability as being fully delivered by one product. Shared infrastructure may realise selected mediation capabilities within a broader distributed interoperability architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-0998✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.72 l.Lines 747-754 |
The discussion characterises the OpenHIE interoperability layer as a single point of entry and associates it with conce…The discussion characterises the OpenHIE interoperability layer as a single point of entry and associates it with concentration of control, failure, and procurement bottlenecks. OpenHIE describes logical roles that can be implemented through different products and deployment patterns. The comparison may therefore be unnecessarily reductive. Suggested revision: Present OpenHIE more neutrally. Distinguish the logical interoperability layer from a particular centralised deployment and cite country evidence where central implementations produced the stated problems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-0999✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.72 l.Lines 755-757 |
Interoperability is said to be represented as one capability in the architecture and realised through context-specific …Interoperability is said to be represented as one capability in the architecture and realised through context-specific mechanisms. A single capability element may be too broad to support meaningful conformance, ownership, gap analysis, or implementation planning. Suggested revision: Decompose interoperability into subordinate capabilities such as service and endpoint discovery, identity and trust, transport, routing, orchestration, structural validation, semantic validation, mapping, consent enforcement, provenance, audit, and monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | ||
| PC-1000✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.72 l.Lines 759-765 |
The section distinguishes direct integration from interoperability and associates interoperability with open, publicly …The section distinguishes direct integration from interoperability and associates interoperability with open, publicly governed specifications. This is useful, but direct point-to-point exchanges can still be interoperable when both systems conform to the same reusable public specifications. Suggested revision: Clarify that topology does not determine interoperability. A direct connection can be interoperable if it uses shared, reusable, publicly governed specifications and avoids bespoke bilateral semantics or behaviour. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1001✎ edit📣 feedback | received | Editorial agent, medium |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.72 l.Lines 759-765 |
“Interoperability, in its true sense” suggests that other recognised definitions are invalid and may make the guidance …“Interoperability, in its true sense” suggests that other recognised definitions are invalid and may make the guidance appear unnecessarily prescriptive. Suggested revision: Replace with with something like: “For the purposes of this guidance, interoperability is used in the stronger sense of conformance to shared, reusable, and openly governed specifications.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1002✎ edit📣 feedback | received | Core architects Metadata registries agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.72 l.Lines 761-765 |
The section states that systems conform “at their boundaries,” but does not explain whether internal data may differ fr…The section states that systems conform “at their boundaries,” but does not explain whether internal data may differ from national models or what transformation obligations apply at the boundary. Suggested revision: State that systems may retain internal models, provided they expose conformant external interfaces and preserve meaning, provenance, precision, and traceability through governed mappings and transformations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | ||
| PC-1003✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.73 l.Lines 768-775 |
The distinction between mediation as a role and topology as an arrangement is valuable. However, routing, transformatio…The distinction between mediation as a role and topology as an arrangement is valuable. However, routing, transformation, authentication, orchestration, and audit are grouped together as if they always form one mediation role. These may have different authorities, locations, and risk profiles. Suggested revision: Decompose mediation into distinct capabilities and state that each may be realised centrally, locally, at gateways, at endpoints, or through shared services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | ||
| PC-1004✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.73 l.Lines 768-788 |
The text repeatedly warns that a central bus creates a single point of control or failure. A properly engineered centra…The text repeatedly warns that a central bus creates a single point of control or failure. A properly engineered central or clustered service can provide redundancy, governance, and consistent enforcement, while distributed architectures can also concentrate control through central trust services or registries. Suggested revision: Present the risks as design-dependent rather than inherent. Compare centralised, distributed, and hybrid patterns using governance, resilience, scalability, observability, security, cost, and operational-capacity criteria. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1005✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.73 l.Lines 777-788 |
The possible locations of mediation are described, but countries are not given a decision framework for selecting among…The possible locations of mediation are described, but countries are not given a decision framework for selecting among them. Suggested revision: Add a decision table covering existing infrastructure, transaction volume, latency, connectivity, participant capability, security requirements, governance model, observability, local support capacity, and failure impact. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | ||
| PC-1006✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.73 l.Lines 781-788 |
Foundational data exchange is described as neutral transport, while health-specific mediation is located at endpoints. …Foundational data exchange is described as neutral transport, while health-specific mediation is located at endpoints. In practice, foundational exchange platforms may provide routing, authentication, audit, policy enforcement, eventing, and service discovery beyond basic transport. Suggested revision: Define a capability boundary rather than assuming a narrow foundational platform. Countries should map the capabilities already provided by foundational DPI and implement only the additional health-specific semantic, clinical, consent, and workflow capabilities required. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1007✎ edit📣 feedback | received | Core architects agent |
3.6.1 Interoperability as a capability, not just a component §3.6.1 p.73 l.Lines 786-788 |
The statement that mediation is realised “at the endpoints of an exchange over a neutral transport” conflicts with the …The statement that mediation is realised “at the endpoints of an exchange over a neutral transport” conflicts with the immediately preceding acknowledgement that mediation may occur through a central bus, distributed access points, gateways, or multiple mechanisms. Suggested revision: Replace with something like: “Mediation may be realised at endpoints, gateways, shared services, access points, or a combination of these, over transport arrangements selected for the national context.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | ||
| PC-1008✎ edit📣 feedback | received | Metadata registries agent |
3.6.2 Data and health content standards §3.6.2 p.73 l.Lines 791-808 |
The section presents structure and coded meaning as the two concerns determining whether meaning is preserved. Context,…The section presents structure and coded meaning as the two concerns determining whether meaning is preserved. Context, provenance, negation, uncertainty, temporal meaning, workflow state, and the intended purpose of data are also essential. Suggested revision: Expand the semantic model to include context, provenance, time, certainty, units, authorship, intended use, and relevant workflow state, as represented through governed information models and exchange specifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-1009✎ edit📣 feedback | received | Metadata registries agent |
3.6.2 Data and health content standards §3.6.2 p.73 l.Lines 795-799 |
The blood-pressure example refers to body site and patient state but does not mention units, measurement method, device…The blood-pressure example refers to body site and patient state but does not mention units, measurement method, device, body position, or time, all of which may affect interpretation. Suggested revision: Use a complete but concise example showing that reliable interpretation depends on values, units, components, method, position, timing, provenance, and terminology. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-1010✎ edit📣 feedback | received | Metadata registries agent |
3.6.2 Data and health content standards §3.6.2 p.73 l.Lines 801-808 |
The architecture assigns meaning to the Terminology Service and structure to the LIMR. As noted in Section 3.5, informa…The architecture assigns meaning to the Terminology Service and structure to the LIMR. As noted in Section 3.5, information models also carry contextual semantics, so the dictionary-and-grammar analogy is useful but incomplete. Suggested revision: State that the Terminology Service governs coded concept meaning, while the LIMR governs structure, context, constraints, and terminology bindings. Both contribute to semantic meaning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-263 discuss | in the document all mentions on GitHub record | ||
| PC-1011✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 810-819 |
The list of standards is informative but mixes exchange frameworks, terminologies, classifications, identifier standard…The list of standards is informative but mixes exchange frameworks, terminologies, classifications, identifier standards, imaging standards, integration profiles, and content specifications without categorising their roles. Suggested revision: Present the standards in a structured table covering purpose, domain, artefact type, governance body, licensing considerations, and national profiling requirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-1012✎ edit📣 feedback | received | Metadata registries agent, medium |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 810-819 |
The phrase “established and openly governed standards” is applied broadly to standards with differing access, licensing…The phrase “established and openly governed standards” is applied broadly to standards with differing access, licensing, participation, and intellectual-property arrangements. SNOMED CT, for example, has licensing conditions despite recognised governance processes. Suggested revision: Use “recognised standards governed through established standards-development or maintenance processes,” and document relevant licensing, access, localisation, and implementation conditions separately. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-1013✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 812-815 |
The standards list omits several relevant standards or specifications, including UCUM for units and potentially HL7 v2,…The standards list omits several relevant standards or specifications, including UCUM for units and potentially HL7 v2, CDA, openEHR, ISO identification standards, and public-health or supply-chain exchange standards. Suggested revision: Clarify that the list is illustrative and add a standards-selection framework. Include important standards used by legacy and specialised systems, together with transition and coexistence guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-1014✎ edit📣 feedback | received | Core architects Clinical agent, medium |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 815-819 |
The International Patient Summary is described as defining the meaningful minimum for “a given exchange.” IPS defines a…The International Patient Summary is described as defining the meaningful minimum for “a given exchange.” IPS defines a particular patient-summary use case, not a generic minimum for all health exchanges. Suggested revision: Revise to: “Content specifications such as the International Patient Summary define a meaningful minimum dataset for particular exchange use cases.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | ||
| PC-1015✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 816-819 |
The section states that national standards selections and bindings are recorded in information-model and terminology co…The section states that national standards selections and bindings are recorded in information-model and terminology components, but it does not address governance of implementation guides, API specifications, transport profiles, security profiles, and workflow definitions. Suggested revision: Identify a governed national interoperability-specification repository or publication process covering implementation guides, capability statements, profiles, extensions, terminology bindings, transport, security, workflows, and test artefacts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-070 discuss | in the document all mentions on GitHub record | ||
| PC-1016✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 821-829 |
The warning that use of the same standard can create “interoperable silos” is important. However, the proposed remedy f…The warning that use of the same standard can create “interoperable silos” is important. However, the proposed remedy focuses mainly on a nationally governed information model and gives less attention to implementation guides, terminology versions, workflow agreements, and conformance testing. Suggested revision: State that semantic interoperability requires coordinated national models, profiles, extensions, terminology bindings, workflow specifications, version policies, and conformance testing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-070 discuss | in the document all mentions on GitHub record | ||
| PC-1017✎ edit📣 feedback | received | Metadata registries agent |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 821-829 |
Requiring a nationally governed information model may be difficult in countries with limited modelling capacity. The te…Requiring a nationally governed information model may be difficult in countries with limited modelling capacity. The text does not describe how international or regional artefacts can be adopted with minimal national adaptation. Suggested revision: Add a progressive pathway: adopt suitable international or regional models first, document only necessary national constraints and extensions, and develop broader national modelling governance as capacity grows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-070 discuss | in the document all mentions on GitHub record | ||
| PC-1018✎ edit📣 feedback | received | Core architects agent |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 831-838 |
The rule that the consuming side should provide the adapter may not work in all integration scenarios. The party best a…The rule that the consuming side should provide the adapter may not work in all integration scenarios. The party best able to create and maintain an adapter depends on ownership, expertise, data quality, procurement, and interface control. Suggested revision: Replace the fixed rule with a responsibility principle: adapter ownership should be assigned explicitly to the party best positioned to preserve meaning and maintain the mapping, with governance approval and clear accountability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | ||
| PC-1019✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 831-838 |
Adapters are said to perform representational translation only and not alter clinical meaning. In practice, conversion …Adapters are said to perform representational translation only and not alter clinical meaning. In practice, conversion between models can involve loss, approximation, aggregation, or contextual transformation. Suggested revision: Require transformation specifications to document semantic equivalence, information loss, assumptions, unmapped elements, provenance, validation, error handling, and fitness for the intended use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | ||
| PC-1020✎ edit📣 feedback | received | Metadata registries Core architects Clinical agent, medium |
3.6.2 Data and health content standards §3.6.2 p.74 l.Lines 831-838 |
The section does not describe how adapters and mappings are tested or governed, although they can materially affect cli…The section does not describe how adapters and mappings are tested or governed, although they can materially affect clinical meaning and safety. Suggested revision: Require mapping review, representative test cases, round-trip testing where appropriate, terminology validation, regression testing, clinical-safety review, version control, and monitoring of transformation errors. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | ||
| PC-1021✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.74-75 l.Lines 841-854 |
The section clearly locates clinical semantics and consent outside neutral transport. However, it may imply that all he…The section clearly locates clinical semantics and consent outside neutral transport. However, it may imply that all health-specific requirements are endpoint responsibilities. Shared health-sector services may legitimately provide terminology, validation, policy, or mediation functions. Suggested revision: State that health-specific capabilities may be provided by endpoints, shared DPI-H services, gateways, or combinations of these, while foundational transport should not be required to interpret clinical content. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1022✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.75 l.Lines 851-854 |
Foundational data exchange is described as providing “non-repudiable” transport. Non-repudiation requires specific cryp…Foundational data exchange is described as providing “non-repudiable” transport. Non-repudiation requires specific cryptographic, identity, evidentiary, and legal arrangements and should not be assumed for every foundational exchange platform. Suggested revision: Replace with “secure, authenticated, and auditable transport, with non-repudiation where supported by the applicable trust, signature, logging, and legal framework.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1023✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.75 l.Lines 856-862 |
The transport is instructed to move and log health data without transforming or interpreting its clinical content. Some…The transport is instructed to move and log health data without transforming or interpreting its clinical content. Some exchange services may need to inspect metadata for routing, validation, access policy, malware scanning, or data-loss prevention. Suggested revision: Distinguish prohibited clinical reinterpretation from permitted technical inspection and validation. Define which metadata or payload processing is allowed, for what purpose, under whose authority, and with what privacy safeguards. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1024✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.75 l.Lines 856-862 |
“Semantic alignment should take place at the source” is too restrictive. Receiving systems may need local transformatio…“Semantic alignment should take place at the source” is too restrictive. Receiving systems may need local transformations, terminology translation, validation, or contextualisation, particularly when exchanging across languages, jurisdictions, and legacy standards. Suggested revision: Replace with a sentence like: “Meaning should be normalised as close to the authoritative source as practicable, with governed transformations permitted at defined boundaries when source-side alignment is not feasible.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | ||
| PC-1025✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.75 l.Lines 864-876 |
The foundational exchange example appears closely aligned to one specific building-block pattern involving gateways, RE…The foundational exchange example appears closely aligned to one specific building-block pattern involving gateways, REST interfaces, event notifications, signatures, and transaction logs. This may not represent all national data-exchange DPI. Suggested revision: Present it as one illustrative capability pattern rather than a general definition of foundational exchange DPI. Keep requirements technology-neutral and outcome-based. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1026✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.75 l.Lines 864-876 |
Signed transactions, national gateways, PKI, and sophisticated logging may not be immediately available in lower-resour…Signed transactions, national gateways, PKI, and sophisticated logging may not be immediately available in lower-resource environments. The section does not define a safe minimum transitional approach. Suggested revision: Specify baseline controls for early-stage exchange, including authenticated channels, endpoint registration, minimum audit data, access agreements, integrity checks, incident response, and a roadmap toward stronger cryptographic assurance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-246 discuss | in the document all mentions on GitHub record | ||
| PC-1027✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.75 l.Lines 869-874 |
The statement that foundational exchange is recommended across networks but not required between co-located systems cou…The statement that foundational exchange is recommended across networks but not required between co-located systems could be misread as allowing co-located systems to bypass national data, semantic, security, and audit requirements. Suggested revision: Clarify that co-located systems may use direct local integration but should still conform to applicable national information models, terminology, security, provenance, audit, and interface requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1028✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.75-76 l.Lines 878-895 |
The section presents distributed access points, central buses, gateways, and direct connections as exchange patterns, b…The section presents distributed access points, central buses, gateways, and direct connections as exchange patterns, but these categories overlap. A distributed access point may itself use a gateway, service bus, or event broker. Suggested revision: Present the patterns across separate dimensions, such as control topology, transport pattern, interaction style, mediation location, and data persistence. Explain that implementations combine choices across these dimensions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | ||
| PC-1029✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.75-76 l.Lines 878-895 |
The requirement to avoid unmanaged bilateral connections is appropriate, but managed direct connections can be practica…The requirement to avoid unmanaged bilateral connections is appropriate, but managed direct connections can be practical and conformant. The distinction between managed and unmanaged point-to-point exchange needs definition. Suggested revision: Define managed direct exchange as using registered endpoints, shared standards, documented ownership, conformance testing, monitoring, security controls, lifecycle management, and maintained mappings. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1030✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.76 l.Lines 888-894 |
Store-and-forward and publish-subscribe are presented as supporting intermittent connectivity. These patterns require d…Store-and-forward and publish-subscribe are presented as supporting intermittent connectivity. These patterns require durable messaging, local queues, identity continuity, duplicate handling, reconciliation, and conflict management, which are not described. Suggested revision: Add minimum requirements for message persistence, delivery status, retry, deduplication, ordering where required, expiry, reconciliation, conflict resolution, security, and monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | ||
| PC-1031✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.76-77 l.Figure 3.6 and legend anchor: medium |
Figure 3.6 is valuable, but it may imply that the patterns are mutually comparable alternatives at the same abstraction…Figure 3.6 is valuable, but it may imply that the patterns are mutually comparable alternatives at the same abstraction level. Direct connections, gateways, access-point governance, service buses, and publish-subscribe describe different architectural aspects. Suggested revision: Rework the figure as a set of composable patterns or add a note explaining their different dimensions and how they may coexist in one exchange flow. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | ||
| PC-1032✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.76-77 l.Figure 3.6 and legend anchor: medium |
The legend states that dashed lines carry registration, logging, and oversight “with no data content.” Logs and registr…The legend states that dashed lines carry registration, logging, and oversight “with no data content.” Logs and registry interactions may contain personal, transactional, or sensitive metadata even when they do not carry clinical payloads. Suggested revision: Replace with a sentence like: “Dashed line: control-plane exchange for registration, logging, monitoring, or oversight; it does not represent transfer of the primary clinical payload but may contain protected metadata.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-075 discuss | in the document all mentions on GitHub record | ||
| PC-1033✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.76-77 l.Figure 3.6 and legend anchor: medium |
The diagram does not visibly represent offline nodes, delayed synchronisation, network segmentation, or fallback operat…The diagram does not visibly represent offline nodes, delayed synchronisation, network segmentation, or fallback operations, despite their importance to lower-resource settings. Suggested revision: Add an offline or intermittently connected pattern, or annotate publish-subscribe and store-and-forward implementations with delayed synchronisation and recovery behaviour. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | ||
| PC-1034✎ edit📣 feedback | received | Core architects agent |
3.6.3 Interoperability between DPI-H and foundational DPI §3.6.3 p.76-77 l.Figure 3.6 anchor: medium |
The figure shows exchange topology but not the conformance boundaries or profiles to which each endpoint, gateway, acce…The figure shows exchange topology but not the conformance boundaries or profiles to which each endpoint, gateway, access point, or broker must conform. Suggested revision: Add conformance points or an accompanying table identifying the interfaces, actor roles, applicable specifications, test responsibilities, and audit requirements for each pattern. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-075 discuss | in the document all mentions on GitHub record | ||
| PC-1035✎ edit📣 feedback | received | Core architects agent |
3.6.4 Cross-border health data flows §3.6.4 p.77 l.Lines 905-911 |
Cross-border exchange is described as relying on federated exchange through national gateways rather than a central sup…Cross-border exchange is described as relying on federated exchange through national gateways rather than a central supranational store. This is a useful pattern but should not be presented as the only legitimate architecture. Suggested revision: Present national-gateway federation as the preferred pattern in the cited examples while allowing other legally governed arrangements, such as regional services, shared repositories for limited datasets, or direct trusted-authority exchange. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-077 discuss | in the document all mentions on GitHub record | ||
| PC-1036✎ edit📣 feedback | received | Core architects agent, medium |
3.6.4 Cross-border health data flows §3.6.4 p.77 l.Lines 913-923 |
The European example combines current services and services planned for later implementation. Without clear dates or st…The European example combines current services and services planned for later implementation. Without clear dates or status, readers may interpret all listed exchanges as already operational across participating countries. Suggested revision: Distinguish operational services from planned or phased services and identify the applicable implementation timeframe and authoritative source. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-261 discuss | in the document all mentions on GitHub record | ||
| PC-1037✎ edit📣 feedback | received | Core architects agent |
3.6.4 Cross-border health data flows §3.6.4 p.77 l.Lines 913-923 |
The description risks blending MyHealth@EU primary-use exchange with the wider European Health Data Space framework for…The description risks blending MyHealth@EU primary-use exchange with the wider European Health Data Space framework for primary and secondary use. These have related but distinct governance, infrastructure, and implementation timelines. Suggested revision: Separate the current cross-border healthcare services, future EHDS primary-use obligations, and secondary-use arrangements. Explain how each example supports the architecture claim being made. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-261 discuss | in the document all mentions on GitHub record | ||
| PC-1038✎ edit📣 feedback | received | Core architects WHO agent, medium |
3.6.4 Cross-border health data flows §3.6.4 p.77-78 l.Lines 925-937 |
The GDHCN description correctly separates trust from personal content, but it may imply that the network alone establis…The GDHCN description correctly separates trust from personal content, but it may imply that the network alone establishes end-to-end trustworthiness. Document authenticity does not establish clinical accuracy, issuer competence, holder identity, current validity, or legal acceptability. Suggested revision: Clarify that GDHCN supports verification of issuer trust and document integrity. Relying parties must also evaluate document type, validity, subject binding, clinical meaning, revocation status, policy, and applicable law. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-076 discuss | in the document all mentions on GitHub record | ||
| PC-1039✎ edit📣 feedback | received | WHO Core architects agent, low |
3.6.4 Cross-border health data flows §3.6.4 p.77-78 l.Lines 925-937 |
GDHCN is described as a trust layer separate from clinical content. It is not made clear whether the document treats th…GDHCN is described as a trust layer separate from clinical content. It is not made clear whether the document treats this as foundational DPI, DPI-H, regional infrastructure, or an external trust network used by DPI-H. Suggested revision: Explicitly classify GDHCN as an external or cross-border trust network that DPI-H can use, and distinguish it from domestic foundational identity and trust infrastructure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-076 discuss | in the document all mentions on GitHub record | ||
| PC-1040✎ edit📣 feedback | received | Core architects agent |
3.6.4 Cross-border health data flows §3.6.4 p.78 l.Lines 939-950 |
The cross-border requirements mix SHOULD and SHALL without explaining whether they form a normative conformance profile…The cross-border requirements mix SHOULD and SHALL without explaining whether they form a normative conformance profile or general guidance. Suggested revision: Apply the document’s harmonised normative terminology and define the scope of conformance. Identify which requirements are essential for any cross-border exchange and which depend on the use case or legal arrangement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-077 discuss | in the document all mentions on GitHub record | ||
| PC-1041✎ edit📣 feedback | received | Metadata registries agent |
3.6.4 Cross-border health data flows §3.6.4 p.78 l.Lines 940-943 |
Terminology and language translation are required for receiving clinicians, but the section does not address countries …Terminology and language translation are required for receiving clinicians, but the section does not address countries with limited national terminology translations or terminology-service capacity. Suggested revision: Recommend phased use of internationally available translations, regional shared services, curated priority subsets, clearly marked untranslated content, and human interpretation safeguards where automated translation is insufficient. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | ||
| PC-1042✎ edit📣 feedback | received | Core architects agent |
3.6.4 Cross-border health data flows §3.6.4 p.78 l.Lines 944-950 |
Mutual recognition of identity, professional credentials, trust anchors, and signatures is treated as one trust-framewo…Mutual recognition of identity, professional credentials, trust anchors, and signatures is treated as one trust-framework requirement. These involve different authorities and assurance models. Suggested revision: Separate person identity, professional identity, organisational identity, issuer trust, document signatures, endpoint authentication, and authorisation. Define how each is recognised across jurisdictions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-076 discuss | in the document all mentions on GitHub record | ||
| PC-1043✎ edit📣 feedback | received | Core architects Clinical agent, medium |
3.6.4 Cross-border health data flows §3.6.4 p.78 l.Lines 947-950 |
The requirement for an explicit legal basis and consent is important, but it does not address emergency care, public-he…The requirement for an explicit legal basis and consent is important, but it does not address emergency care, public-health emergencies, displaced populations, children, persons lacking capacity, or people without recognised digital identity. Suggested revision: Add guidance for lawful exceptions, emergency access, guardianship and representation, vulnerable populations, alternative identification, minimum-necessary exchange, and post-event transparency or review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-077 discuss | in the document all mentions on GitHub record | ||
| PC-1044✎ edit📣 feedback | received | Core architects agent |
3.6.4 Cross-border health data flows §3.6.4 p.78 l.Lines 939-950 |
The requirements do not explicitly mention data minimisation, purpose limitation, provenance, traceability, security-in…The requirements do not explicitly mention data minimisation, purpose limitation, provenance, traceability, security-incident coordination, redress, or correction of cross-border data. Suggested revision: Add these requirements and define responsibility for notification, correction, dispute handling, audit access, and patient redress across jurisdictions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-077 discuss | in the document all mentions on GitHub record | ||
| PC-1045✎ edit📣 feedback | received | Core architects agent |
3.6.5 Conformance §3.6.5 p.78 l.Lines 953-959 |
The subsection is extremely brief relative to the complexity of the interoperability requirements. It states that requi…The subsection is extremely brief relative to the complexity of the interoperability requirements. It states that requirements should be testable but does not identify the minimum interoperability conformance artefacts. Suggested revision: List the required artefacts: implementation guides, profiles, capability statements, terminology packages, test cases, test data, validators, simulators, security test requirements, certification rules, and versioned conformance statements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1046✎ edit📣 feedback | received | Core architects agent |
3.6.5 Conformance §3.6.5 p.78 l.Lines 954-959 |
The section links conformance primarily to content, terminology, information models, and exchange behaviour. Organisati…The section links conformance primarily to content, terminology, information models, and exchange behaviour. Organisational, legal, workflow, security, resilience, and operational interoperability are harder to test but still require assessment. Suggested revision: Define a layered conformance model covering technical interface conformance, content and semantic conformance, security and trust, workflow behaviour, operational service levels, and governance readiness. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1047✎ edit📣 feedback | received | Core architects agent |
3.6.5 Conformance §3.6.5 p.78 l.Lines 954-959 |
Vendor claims are identified as a testing target, but there is no requirement for publication of test scope, supported …Vendor claims are identified as a testing target, but there is no requirement for publication of test scope, supported options, exceptions, versions, or expiry of certification. Suggested revision: Require a standard conformance statement identifying component, actor role, supported services, profiles, versions, options, test environment, results, limitations, certification authority, issue date, and validity period. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1048✎ edit📣 feedback | received | Core architects agent |
3.6.5 Conformance §3.6.5 p.78 l.Lines 954-959 |
The section does not address continuous conformance after procurement. Systems may become non-conformant following upgr…The section does not address continuous conformance after procurement. Systems may become non-conformant following upgrades, configuration changes, terminology updates, or national-profile changes. Suggested revision: Require regression testing and revalidation after material changes, periodic surveillance testing, monitoring of production interoperability errors, and defined triggers for suspension or renewal of conformance status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1049✎ edit📣 feedback | received | Core architects agent |
3.6.5 Conformance §3.6.5 p.78 l.Lines 954-959 |
Comprehensive conformance infrastructure may be difficult for lower-resource countries to operate independently.Comprehensive conformance infrastructure may be difficult for lower-resource countries to operate independently. Suggested revision: Recommend regional or shared test services, reusable open-source validators and simulators, mutual recognition of test results, competency development, and a risk-based testing sequence focused first on high-impact interfaces. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | ||
| PC-1050✎ edit📣 feedback | received | Core architects agent |
3.7.1 Purpose §3.7.1 p.78-79 l.Lines 964-980 |
The distinction between system conformance and architecture conformance is valuable. However, “conformance of the archi…The distinction between system conformance and architecture conformance is valuable. However, “conformance of the architecture” combines several different assessments: model validity, alignment with the reference architecture, coverage, traceability, and documentation of deviations. Suggested revision: Separate these into clearly defined assessment dimensions: model validity, reference alignment, capability coverage, relationship completeness, traceability, and documented deviation. Define the expected evidence and assessment method for each. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1051✎ edit📣 feedback | received | Core architects agent |
3.7.1 Purpose §3.7.1 p.79 l.Lines 965-980 |
The section suggests that the reference architecture can be used as a common benchmark regardless of whether a national…The section suggests that the reference architecture can be used as a common benchmark regardless of whether a national architecture was developed from it. This may be difficult where the national architecture uses different component boundaries, modelling languages, or terminology. Suggested revision: Define a formal mapping method that allows national elements expressed in other frameworks or modelling languages to be mapped to the reference architecture without requiring complete remodelling in ArchiMate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1052✎ edit📣 feedback | received | Core architects agent |
3.7.1 Purpose §3.7.1 p.79 l.Lines 970-980 |
Machine readability of elements and relationships makes automated checking possible, but it does not by itself make an …Machine readability of elements and relationships makes automated checking possible, but it does not by itself make an architecture testable. The document does not yet define machine-readable validation rules, mandatory properties, cardinalities, or acceptable relationship patterns. Suggested revision: Publish a formal architecture profile containing schemas, identifiers, permitted relationships, mandatory properties, validation rules, severity levels, and machine-readable test assertions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1053✎ edit📣 feedback | received | Editorial agent |
3.7.1 Purpose §3.7.1 p.79 l.Lines 975-980 |
The terms “adopts,” “adapts,” and “maps to” are introduced parenthetically before they are fully explained in Section 3…The terms “adopts,” “adapts,” and “maps to” are introduced parenthetically before they are fully explained in Section 3.7.5. Suggested revision: Add a brief definition here or move the terminology to Section 3.7.5 and cross-reference it from this paragraph. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1054✎ edit📣 feedback | received | Core architects agent |
3.7.1 Purpose §3.7.1 p.79 l.Lines 982-988 |
Outcome monitoring is presented as the third question alongside system and architecture conformance. Achieving a health…Outcome monitoring is presented as the third question alongside system and architecture conformance. Achieving a health outcome is influenced by policy, service delivery, workforce, financing, and social conditions, not only by architecture components. Suggested revision: Clarify that architecture contribution to outcomes should be assessed rather than attributing outcomes solely to architecture. Require a theory of change, contextual indicators, implementation measures, and evaluation of alternative explanations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-082 discuss | in the document all mentions on GitHub record | ||
| PC-1055✎ edit📣 feedback | received | Core architects agent |
3.7.1 Purpose §3.7.1 p.79 l.Lines 982-988 |
The section does not clearly distinguish conformance testing, interoperability testing, performance testing, security t…The section does not clearly distinguish conformance testing, interoperability testing, performance testing, security testing, clinical-safety assurance, operational acceptance, and impact evaluation. Suggested revision: Add a testing taxonomy showing the purpose, object under test, evidence, responsible body, and timing for each type of assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1056✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.79 l.Lines 991-997 |
The section describes the conformance model as a “small, self-contained extension” to the ArchiMate core. It is unclear…The section describes the conformance model as a “small, self-contained extension” to the ArchiMate core. It is unclear whether this extension remains fully conformant to ArchiMate or introduces project-specific modelling conventions. Suggested revision: State explicitly which elements and relationships are native ArchiMate constructs and which are DPI-H modelling conventions. Publish the conventions as a formal profile with examples and validation rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1057✎ edit📣 feedback | received | Core architects agent, medium |
3.7.2 The model §3.7.2 p.79-80 l.Table 3.7.1 |
The table mixes element types and relationship types in one list. This may be difficult for readers unfamiliar with Arc…The table mixes element types and relationship types in one list. This may be difficult for readers unfamiliar with ArchiMate and could obscure how the constructs form a conformance model. Suggested revision: Separate the table into elements and relationships, then provide a small worked example showing how components, functions, interactions, assignment, triggering, and services connect. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-1058✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.79-80 l.Table 3.7.1, “Application Interaction” |
Application Interaction is defined as collective behaviour performed by two or more components. Some conformance-releva…Application Interaction is defined as collective behaviour performed by two or more components. Some conformance-relevant exchanges may involve a user, device, external service, batch process, or organisational actor rather than two application components. Suggested revision: Clarify how human actors, devices, external services, and organisational roles are represented. Allow the interaction model to reference business actors, interfaces, technology services, or external participants where required. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1059✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.79-80 l.Table 3.7.1, “Application Function” |
Internal automated behaviour may not be externally observable and therefore may not be suitable as a direct conformance…Internal automated behaviour may not be externally observable and therefore may not be suitable as a direct conformance target. Different implementations can realise the same service through different internal functions. Suggested revision: State that conformance should normally be assessed against externally observable services and behaviour. Internal functions should be modelled only where needed for traceability, safety, or implementation planning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1060✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.80 l.Lines 1002-1011 |
Application Interface, Business Process, Business Role, Requirement, Constraint, and Assessment are deferred until part…Application Interface, Business Process, Business Role, Requirement, Constraint, and Assessment are deferred until particular views are adopted. Requirements and constraints are already essential to architecture conformance, regardless of whether UI testing is included. Suggested revision: Include Requirement, Constraint, and Assessment in the core conformance model. Treat Application Interface, Business Process, and Business Role as conditional extensions where relevant. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-1061✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.80 l.Lines 1008-1011 |
The evaluation verdict is left implicit, although the section aims to support machine-readable assessment. Without an e…The evaluation verdict is left implicit, although the section aims to support machine-readable assessment. Without an explicit result model, outcomes such as passed, failed, conditionally passed, not applicable, or not tested cannot be exchanged consistently. Suggested revision: Define an explicit assessment-result model covering status, date, assessor, scope, evidence, test environment, version, findings, exceptions, validity period, and remediation requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1062✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.80 l.Lines 1013-1020 |
Modelling both an abstract actor and a concrete system as Application Components creates ambiguity. Automated checks ma…Modelling both an abstract actor and a concrete system as Application Components creates ambiguity. Automated checks may not reliably distinguish a reference role from a deployed product. Suggested revision: Introduce a mandatory type or stereotype property distinguishing abstract actor roles, reference components, national logical components, concrete systems, and test simulators. Apply a consistent naming and identifier convention. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-1063✎ edit📣 feedback | received | Core architects agent, medium |
3.7.2 The model §3.7.2 p.80 l.Lines 1015-1020 |
“Actor” is defined as an abstract information-processing role, while other parts of the document use actor to include p…“Actor” is defined as an abstract information-processing role, while other parts of the document use actor to include people, organisations, and stakeholders. The same term therefore has different meanings. Suggested revision: Use application actor role or IHE actor role in this subsection, and distinguish it explicitly from human actors, organisational actors, and stakeholder elements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-1064✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.80 l.Lines 1017-1020 |
The document states that a concrete system realises an actor through a realisation relationship. The evidence required …The document states that a concrete system realises an actor through a realisation relationship. The evidence required to substantiate this assertion is not defined. Suggested revision: Require a conformance statement identifying the actor role, services, transactions, mandatory and optional capabilities, standard versions, implementation options, test evidence, and known limitations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1065✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.80-81 l.Lines 1022-1033 |
Offered and required services are clearly distinguished, but the directionality is described using ArchiMate relationsh…Offered and required services are clearly distinguished, but the directionality is described using ArchiMate relationships that may not correspond directly to how API clients, event publishers, subscribers, and asynchronous participants behave. Suggested revision: Add examples for request-response APIs, event publication and subscription, document exchange, batch transfer, and user-initiated workflows. Clarify how offered and required services are modelled for each pattern. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1066✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.80-81 l.Lines 1026-1033 |
The section equates the responder with the actor offering a service and the initiator with the actor requiring it. This…The section equates the responder with the actor offering a service and the initiator with the actor requiring it. This terminology fits request-response transactions but may be misleading for event-driven or peer-to-peer interaction. Suggested revision: Use provider and consumer as the general service relationship, and apply initiator and responder only to transaction patterns where those roles are meaningful. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1067✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.81 l.Lines 1035-1043 |
Mandatory or optional support is recorded as a property on the serving relationship or as a Constraint. Using two alter…Mandatory or optional support is recorded as a property on the serving relationship or as a Constraint. Using two alternative modelling methods may produce inconsistent national models and automated checks. Suggested revision: Select one normative representation for support obligation. Prefer a formal Constraint or defined relationship property with a controlled vocabulary and machine-readable validation rule. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1068✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.81 l.Lines 1035-1043 |
The discussion distinguishes required services from mandatory support, but does not address conditional requirements wh…The discussion distinguishes required services from mandatory support, but does not address conditional requirements whose applicability depends on a selected option, jurisdiction, use case, or maturity level. Suggested revision: Add a conditional status, with machine-readable applicability criteria and an obligation to document why a conditional requirement is or is not applicable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1069✎ edit📣 feedback | received | Editorial Core architects agent, medium |
3.7.2 The model §3.7.2 p.81 l.Lines 1035-1043 |
The explanation of two meanings of “required” is accurate but demonstrates that the terminology is inherently confusing.The explanation of two meanings of “required” is accurate but demonstrates that the terminology is inherently confusing. Suggested revision: Use consumed service rather than “required service” for direction, while retaining mandatory, conditional, recommended, and optional for obligation level. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1070✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.81 l.Lines 1045-1061 |
The distinction between interaction and transaction is useful, but “fully specified” is not defined. Transactions may s…The distinction between interaction and transaction is useful, but “fully specified” is not defined. Transactions may still leave options, profiles, security arrangements, error behaviour, or local constraints unresolved. Suggested revision: Define the minimum specification content for a transaction: participant roles, trigger, preconditions, payload, semantics, transport, security, response, errors, state changes, audit, options, and conformance tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1071✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.81 l.Lines 1054-1061 |
The section allows interactions not yet specified to transaction level, but does not explain whether such interactions …The section allows interactions not yet specified to transaction level, but does not explain whether such interactions can be treated as conformant or procured safely. Suggested revision: Define maturity states such as conceptual interaction, specified interaction, testable transaction, and certified profile. Restrict formal conformance claims to interactions with adequate normative specifications and tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1072✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.81 l.Lines 1063-1066 |
The statement that an interaction is not the unit of conformance is reasonable for actor-role certification, but end-to…The statement that an interaction is not the unit of conformance is reasonable for actor-role certification, but end-to-end interoperability also depends on the interaction between multiple tested systems. Component-level testing alone may not demonstrate successful exchange. Suggested revision: Add bilateral and multilateral interoperability testing, workflow testing, and end-to-end scenario testing in addition to actor-role conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1073✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.81-82 l.Figure 3.7.1 anchor: medium |
The figure illustrates one IHE document-exchange transaction. It may lead readers to assume that the conformance model …The figure illustrates one IHE document-exchange transaction. It may lead readers to assume that the conformance model is primarily document-centric or request-response based. Suggested revision: Add a second example using FHIR API or event-based exchange, demonstrating how the same model applies to synchronous and asynchronous patterns. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1074✎ edit📣 feedback | received | Editorial agent |
3.7.2 The model §3.7.2 p.81-82 l.Figure 3.7.1 anchor: medium |
The figure caption is lengthy and contains essential modelling rules that may be overlooked if readers treat it only as…The figure caption is lengthy and contains essential modelling rules that may be overlooked if readers treat it only as descriptive text. Suggested revision: Move the rules into the main narrative or a boxed modelling convention, and keep the caption focused on what the figure depicts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-1075✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.82 l.Lines 1077-1083 |
The text says that conformance is asserted about the service rather than the access channel. Channel-specific behaviour…The text says that conformance is asserted about the service rather than the access channel. Channel-specific behaviour, authentication, accessibility, usability, and protocol conformance may still be important. Suggested revision: Distinguish service-level conformance from channel or interface conformance. A component should demonstrate the core service behaviour and the requirements applicable to each supported access channel. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1076✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.82 l.Lines 1077-1083 |
A user-interface workflow and a machine-to-machine transaction are described as two ways of reaching the same service. …A user-interface workflow and a machine-to-machine transaction are described as two ways of reaching the same service. The UI may implement additional business validation, user permissions, or workflow logic not exercised through the API. Suggested revision: Require channel-specific test coverage and verify that core business rules, security, consent, provenance, and audit requirements are enforced consistently across all supported channels. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1077✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.82 l.Lines 1085-1092 |
Conformance is defined as correct realisation of services associated with a named actor role, but “correctly” is not ti…Conformance is defined as correct realisation of services associated with a named actor role, but “correctly” is not tied to measurable criteria. Suggested revision: Define correctness through normative requirements, applicable profiles, expected behaviour, test assertions, security requirements, terminology bindings, performance thresholds, and accepted evidence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1078✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.82-83 l.Lines 1094-1105 |
The system under test is evaluated one actor role at a time. A product may realise multiple roles whose combined behavi…The system under test is evaluated one actor role at a time. A product may realise multiple roles whose combined behaviour creates unexpected interactions or security risks. Suggested revision: Require both per-role tests and integrated multi-role tests where a single system claims several actors or where role combination affects behaviour, data separation, authorisation, or audit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1079✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.83 l.Lines 1099-1102 |
Simulator-based testing verifies one side of an interaction but may not reflect production behaviour, scale, timing, se…Simulator-based testing verifies one side of an interaction but may not reflect production behaviour, scale, timing, security configuration, or implementation variability. Suggested revision: Supplement simulator testing with peer interoperability testing, production-like security, representative data volumes, negative testing, failure scenarios, and operational acceptance tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1080✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.83 l.Lines 1103-1105 |
Optional services are tested only when a system declares support. This may permit suppliers to avoid testing important …Optional services are tested only when a system declares support. This may permit suppliers to avoid testing important recommended functions by not declaring them. Suggested revision: Require procurement specifications to identify which optional or recommended capabilities are mandatory for the national use case. Conformance statements must explicitly list unsupported optional capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1081✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.83 l.Figure 3.7.2 anchor: medium |
The figure introduces testing through a user interface but does not show how UI behaviour, accessibility, user authenti…The figure introduces testing through a user interface but does not show how UI behaviour, accessibility, user authentication, workflow, or human factors are assessed. Suggested revision: Add an accompanying note distinguishing UI-driven end-to-end transaction testing from usability, accessibility, workflow, and human-factors evaluation, which require separate methods. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1082✎ edit📣 feedback | received | Core architects agent |
3.7.2 The model §3.7.2 p.83 l.Figure 3.7.2 anchor: medium |
The testing arrangement may assume that countries can operate sophisticated simulators and test environments. This capa…The testing arrangement may assume that countries can operate sophisticated simulators and test environments. This capacity may not exist in lower-resource settings. Suggested revision: Provide reusable hosted or regional test services, downloadable simulators, reference data, documented test scripts, training, and the possibility of mutual recognition of accredited test results. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | ||
| PC-1083✎ edit📣 feedback | received | Core architects agent |
3.7.3 Alignment with IHE profiles §3.7.3 p.83-84 l.Lines 1118-1126 |
IHE is identified as the principal framework accommodated by the model. This may overemphasise IHE relative to FHIR imp…IHE is identified as the principal framework accommodated by the model. This may overemphasise IHE relative to FHIR implementation guides, SMART Guidelines, national profiles, OpenHIE workflows, DICOM conformance, and other domain standards. Suggested revision: Present IHE as a leading worked example rather than the principal universal framework. Explain how the model accommodates other profile and conformance ecosystems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-1084✎ edit📣 feedback | received | Core architects agent, medium |
3.7.3 Alignment with IHE profiles §3.7.3 p.83-84 l.Lines 1119-1126 |
The explanation assumes readers understand IHE actors, profiles, transactions, integration statements, and testing tool…The explanation assumes readers understand IHE actors, profiles, transactions, integration statements, and testing tools. This may not be appropriate for all technical teams or procurement readers. Suggested revision: Add a concise IHE primer or glossary box and identify which parts of IHE are directly reused by the architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-1085✎ edit📣 feedback | received | Core architects agent |
3.7.3 Alignment with IHE profiles §3.7.3 p.83-84 l.Lines 1121-1126 |
The architecture defers protocol details and testing to IHE where a matching transaction exists. It does not explain ho…The architecture defers protocol details and testing to IHE where a matching transaction exists. It does not explain how the architecture selects a specific IHE profile, version, option, national extension, or security environment. Suggested revision: Require a national profile-selection record specifying version, actors, options, content profile, transport, security, terminology bindings, national constraints, and applicable tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-083 discuss | in the document all mentions on GitHub record | ||
| PC-1086✎ edit📣 feedback | received | Core architects agent |
3.7.3 Alignment with IHE profiles §3.7.3 p.83-84 l.Lines 1121-1126 |
Deferring to external specifications creates a dependency on their lifecycle. Profiles may be revised, retired, replace…Deferring to external specifications creates a dependency on their lifecycle. Profiles may be revised, retired, replaced, or unsupported by current test tooling. Suggested revision: Establish a standards lifecycle policy covering profile selection, version pinning, updates, deprecation, replacement, compatibility, and continued availability of test artefacts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-083 discuss | in the document all mentions on GitHub record | ||
| PC-1087✎ edit📣 feedback | received | Core architects agent |
3.7.3 Alignment with IHE profiles §3.7.3 p.84 l.Lines 1127-1130 |
For human-initiated or non-IHE interactions, the text says the architecture will specify them “by other means” but does…For human-initiated or non-IHE interactions, the text says the architecture will specify them “by other means” but does not identify those means. Suggested revision: Define the alternative specification method and minimum artefacts required, such as workflow models, API specifications, user stories, security rules, acceptance criteria, and test cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1088✎ edit📣 feedback | received | Core architects agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84 l.Lines 1132-1146 |
The architecture is described as a map of what must be tested, but this assumes that all services, requirements, option…The architecture is described as a map of what must be tested, but this assumes that all services, requirements, options, interactions, and expected outcomes are modelled completely. Suggested revision: Add a test-readiness assessment that checks specification completeness before test planning begins. Identify unresolved requirements or interactions that cannot yet be tested. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-084 discuss | in the document all mentions on GitHub record | ||
| PC-1089✎ edit📣 feedback | received | Core architects agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84 l.Lines 1137-1141 |
“Standard components arrive tested” is too strong. A product may have passed a standard test in a different version, op…“Standard components arrive tested” is too strong. A product may have passed a standard test in a different version, option, configuration, jurisdiction, or deployment environment. Suggested revision: Replace with a sentence like: “Reusable standard conformance evidence may be available.” Require validation that the evidence matches the selected version, options, configuration, national profile, and deployment context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-1090✎ edit📣 feedback | received | Core architects Metadata registries agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84 l.Lines 1137-1141 |
Standard conformance testing may verify interface behaviour but not national terminology, information-model constraints…Standard conformance testing may verify interface behaviour but not national terminology, information-model constraints, security configuration, data quality, performance, or operational suitability. Suggested revision: Require country-specific supplementary testing even where external certification exists, focused on national profiles, terminology, security, performance, deployment configuration, and priority workflows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-1091✎ edit📣 feedback | received | Core architects agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84 l.Lines 1142-1146 |
Bespoke tests are assigned to the adopter, but the cost, ownership, maintenance, and reuse of those tests are not addre…Bespoke tests are assigned to the adopter, but the cost, ownership, maintenance, and reuse of those tests are not addressed. Suggested revision: Treat tests, reference data, simulators, and validators as governed national assets with named ownership, funding, versioning, open publication where possible, and reuse across procurements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | ||
| PC-1092✎ edit📣 feedback | received | Core architects agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84 l.Lines 1148-1151 |
Test planning is integrated into architecture work, which is a strong recommendation. However, the section does not lin…Test planning is integrated into architecture work, which is a strong recommendation. However, the section does not link testing to procurement stages, contractual acceptance, deployment gates, or ongoing operations. Suggested revision: Add test gates for market engagement, tender evaluation, pre-award demonstration, contractual acceptance, pre-production deployment, major upgrades, and periodic operational reassessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-260 discuss | in the document all mentions on GitHub record | ||
| PC-1093✎ edit📣 feedback | received | Core architects agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84 l.Lines 1153-1160 |
Requirements coverage, standards conformance, and capability completeness are presented as ratios. Simple percentages c…Requirements coverage, standards conformance, and capability completeness are presented as ratios. Simple percentages can conceal the failure of a small number of critical requirements and treat all requirements as equally important. Suggested revision: Weight or stratify measures by criticality. Report mandatory failures separately, prohibit overall pass results where critical requirements fail, and show coverage by safety, security, interoperability, and operational domain. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1094✎ edit📣 feedback | received | Core architects agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84 l.Lines 1153-1160 |
The denominator for standards conformance is “the total identified,” which can be manipulated by omitting applicable st…The denominator for standards conformance is “the total identified,” which can be manipulated by omitting applicable standards from the initial list. Suggested revision: Require independent or governance-approved determination of applicable standards and document the rationale for exclusions or non-applicability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1095✎ edit📣 feedback | received | Core architects agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84-85 l.Lines 1162-1169 |
Detecting a capability without a realising component is useful, but a model can appear complete even when the realising…Detecting a capability without a realising component is useful, but a model can appear complete even when the realising component is unavailable, non-conformant, poorly governed, or unused. Suggested revision: Distinguish model coverage, deployed coverage, conformant coverage, operational coverage, and effective-use coverage. Do not treat a model relationship alone as evidence that the capability exists in practice. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1096✎ edit📣 feedback | received | Core architects agent |
3.7.4 Planning testing from the architecture §3.7.4 p.84-85 l.Lines 1162-1169 |
“Completeness and consistency become properties that can be checked against the model itself” may overstate automated a…“Completeness and consistency become properties that can be checked against the model itself” may overstate automated assurance. Some semantic, organisational, legal, and governance issues require expert judgement. Suggested revision: State that structural completeness and selected consistency rules can be checked automatically, while semantic adequacy, governance suitability, and contextual fitness require multidisciplinary review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-1097✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85 l.Lines 1172-1182 |
A goal is said to be validated “in the same way as a component.” Component conformance and outcome achievement are fund…A goal is said to be validated “in the same way as a component.” Component conformance and outcome achievement are fundamentally different forms of evidence and should not be treated as equivalent. Suggested revision: Replace “in the same way” with: “using an analogous traceability pattern.” Clearly distinguish technical verification from programme evaluation and health-outcome assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-082 discuss | in the document all mentions on GitHub record | ||
| PC-1098✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85 l.Lines 1178-1182 |
Outcomes are described as measurable results that signal achievement of a goal, but many goals require multiple indicat…Outcomes are described as measurable results that signal achievement of a goal, but many goals require multiple indicators, baselines, target populations, time periods, and equity stratification. Suggested revision: Define outcome specifications with indicator, target, baseline, population, timeframe, data source, disaggregation, responsible authority, and interpretation limitations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-082 discuss | in the document all mentions on GitHub record | ||
| PC-1099✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85 l.Lines 1184-1192 |
The criterion-mechanism-verdict pattern is conceptually useful but overlooks causal analysis. Measuring an outcome does…The criterion-mechanism-verdict pattern is conceptually useful but overlooks causal analysis. Measuring an outcome does not show whether DPI-H caused or materially contributed to the result. Suggested revision: Add contribution analysis, theory-of-change validation, process evaluation, contextual factors, unintended consequences, and qualitative evidence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-082 discuss | in the document all mentions on GitHub record | ||
| PC-1100✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85 l.Lines 1184-1192 |
Modelling an indicator as an Application Function or Business Process may conflate the indicator definition with the me…Modelling an indicator as an Application Function or Business Process may conflate the indicator definition with the mechanism that computes or collects it. Suggested revision: Model the indicator or measure as a requirement, outcome measure, or assessment criterion, and model the calculation or data-collection process separately as behaviour. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-082 discuss | in the document all mentions on GitHub record | ||
| PC-1101✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85 l.Lines 1187-1192 |
Evaluation results remain implicit despite the section discussing repeated goal assessment and adoption measurement. Th…Evaluation results remain implicit despite the section discussing repeated goal assessment and adoption measurement. This prevents the architecture model from carrying historical evidence or comparison over time. Suggested revision: Use the ArchiMate Assessment element or a linked results model to record findings, dates, evidence, confidence, evaluator, status, and trends while avoiding unnecessary operational-data burden in the architecture model itself. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1102✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85-86 l.Lines 1194-1212 |
Adoption, adaptation, and mapping are all expressed using the same realisation relationship. This may make it difficult…Adoption, adaptation, and mapping are all expressed using the same realisation relationship. This may make it difficult to distinguish direct reuse, modified implementation, and looser correspondence mechanically. Suggested revision: Add a mandatory mapping-type property with controlled values such as adopted, adapted, mapped, combined, deferred, replaced, and excluded. Require rationale and evidence for each type. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1103✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85-86 l.Lines 1196-1200 |
Using realisation to express country-to-reference mapping implies that the national element fully implements the intent…Using realisation to express country-to-reference mapping implies that the national element fully implements the intent of the reference element. This may be too strong for partial, broader, narrower, or approximate mappings. Suggested revision: Use realisation only for full fulfilment. Define separate mapping relationships or properties for exact, partial, broader, narrower, alternative, and related correspondences. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1104✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85-86 l.Lines 1202-1212 |
The three approaches are presented as alternatives, but national architectures may use all three simultaneously across …The three approaches are presented as alternatives, but national architectures may use all three simultaneously across different areas. Suggested revision: State that adoption, adaptation, and mapping can coexist within one national architecture and should be recorded at element level. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1105✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.85-86 l.Lines 1202-1212 |
Adoption without modification is characterised as the strongest form of alignment. Direct adoption may not be the most …Adoption without modification is characterised as the strongest form of alignment. Direct adoption may not be the most appropriate or effective form where legal, linguistic, institutional, or operational conditions differ. Suggested revision: Replace “strongest” with “most direct.” Treat well-documented adaptation as equally valid where it preserves the reference intent and satisfies relevant requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1106✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.86 l.Lines 1214-1230 |
A reference element is treated as covered when at least one country element realises it. Binary coverage does not show …A reference element is treated as covered when at least one country element realises it. Binary coverage does not show partial functionality, geographic reach, population coverage, maturity, service quality, or actual use. Suggested revision: Introduce graded coverage measures including functional scope, population and geographic reach, operational status, conformance, data quality, governance maturity, and adoption. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1107✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.86 l.Lines 1215-1222 |
A single national system may realise several reference components. The document does not require logical separation, in…A single national system may realise several reference components. The document does not require logical separation, independent data export, distinct governance, or replacement boundaries within such a platform. Suggested revision: Require each realised component to remain separately identifiable through services, responsibilities, data ownership, conformance scope, portability, and lifecycle management, even when implemented in one platform. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-1108✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.86 l.Lines 1221-1222 |
An unrealised reference element is automatically treated as a gap. A country may intentionally meet the underlying capa…An unrealised reference element is automatically treated as a gap. A country may intentionally meet the underlying capability through an alternative design or determine that the capability is not currently applicable. Suggested revision: Classify uncovered elements as confirmed gap, alternative realisation, deferred, not applicable, or intentionally excluded. Require rationale, risk assessment, and approval for non-gap classifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1109✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.86 l.Lines 1224-1230 |
Coverage is defined as the proportion of reference elements realised. This gives equal weight to minor and critical ele…Coverage is defined as the proportion of reference elements realised. This gives equal weight to minor and critical elements and can be inflated by modelling many low-level elements. Suggested revision: Report coverage by layer, capability, component, criticality, and health goal. Avoid a single undifferentiated percentage as the principal adoption measure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1110✎ edit📣 feedback | received | Core architects agent |
3.7.5 Validating goals and adoption §3.7.5 p.86 l.Lines 1228-1230 |
The text allows Association or Specialisation for looser correspondences but does not define when each should be used o…The text allows Association or Specialisation for looser correspondences but does not define when each should be used or how it affects coverage. Suggested revision: Publish mapping rules and examples for realisation, specialisation, association, exact mapping, partial mapping, and alternative implementation. Define which relationships count toward each coverage measure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1111✎ edit📣 feedback | received | Core architects agent, medium |
3.7.6 Constructs and their counterparts §3.7.6 p.86 l.Lines 1233-1236 |
Application Service is described parenthetically as “capability,” although Section 3.1 defines capability and applicati…Application Service is described parenthetically as “capability,” although Section 3.1 defines capability and application service as distinct element types. This is internally inconsistent. Suggested revision: Remove “capability” from the parenthetical statement. State that the Application Service is the externally observable unit against which service behaviour can be assessed, while capability remains a higher-level ability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-040 discuss | in the document all mentions on GitHub record | ||
| PC-1112✎ edit📣 feedback | received | Core architects agent |
3.7.6 Constructs and their counterparts §3.7.6 p.86 l.Lines 1233-1236 |
The Application Component is described as the system in an actor role. Earlier sections also use Application Component …The Application Component is described as the system in an actor role. Earlier sections also use Application Component for logical DPI-H components. The same element type therefore represents a reference component, abstract actor role, and concrete system. Suggested revision: Introduce mandatory classifications or stereotypes for reference component, actor role, national logical component, concrete product, deployed instance, and simulator. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-1113✎ edit📣 feedback | received | Editorial Core architects agent, low |
3.7.6 Constructs and their counterparts §3.7.6 p.86-87 l.Table 3.7.2 |
The table is useful but assumes familiarity with both ArchiMate and IHE. The “Bound by” column does not explain whether…The table is useful but assumes familiarity with both ArchiMate and IHE. The “Bound by” column does not explain whether the relationship is a modelling rule, conformance assertion, or implementation dependency. Suggested revision: Rename the column to ArchiMate relationship or modelling rule and add a short plain-language explanation for each row. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-1114✎ edit📣 feedback | received | Core architects agent, medium |
3.7.6 Constructs and their counterparts §3.7.6 p.86-87 l.Table 3.7.2, “Support qualifier” |
The support qualifier is shown on the serving relationship, although offered services use realisation relationships. It…The support qualifier is shown on the serving relationship, although offered services use realisation relationships. It is unclear how mandatory or optional support is recorded consistently for both offered and consumed services. Suggested revision: Define a single support-obligation property applicable to the actor-service association regardless of relationship direction, with formal validation rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1115✎ edit📣 feedback | received | Core architects agent |
3.7.6 Constructs and their counterparts §3.7.6 p.86-87 l.Table 3.7.2, “Conformance” |
Conformance is represented as an assertion over services but has no formal element, relationship, result object, or evi…Conformance is represented as an assertion over services but has no formal element, relationship, result object, or evidence model. This weakens the stated machine-readable approach. Suggested revision: Add a formal conformance-claim and assessment model, even if maintained as a linked profile rather than native ArchiMate. Include scope, version, evidence, status, issuer, and validity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1116✎ edit📣 feedback | received | Core architects agent |
3.7.6 Constructs and their counterparts §3.7.6 p.87 l.Table 3.7.2, “Country-to-reference mapping” |
The table associates country-to-reference mapping only with Application Components. National goals, capabilities, servi…The table associates country-to-reference mapping only with Application Components. National goals, capabilities, services, data objects, outcomes, and requirements also need mapping. Suggested revision: Extend the mapping model to all relevant element types and define permitted cross-level mappings. Prevent a national component from being mapped directly to an unrelated reference capability without an explicit rationale. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1117✎ edit📣 feedback | received | Core architects agent |
3.7.1 Purpose §3.7 overall p.78-87 l.Entire section anchor: medium |
The section is conceptually rich but does not yet provide technical teams with a complete, executable conformance packa…The section is conceptually rich but does not yet provide technical teams with a complete, executable conformance package. It lacks published profiles, validation rules, test cases, reference data, simulators, result schemas, certification governance, and version-management procedures. Suggested revision: Commit to publishing a companion conformance package containing the machine-readable architecture profile, component profiles, implementation guides, validation rules, capability statements, test plans, test data, simulators, reporting schemas, governance process, and release schedule. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1118✎ edit📣 feedback | received | Core architects agent, medium |
3.7.1 Purpose §3.7 overall p.78-87 l.Entire section anchor: medium |
The level of modelling detail is high for the main guidance and may interrupt the architecture narrative, while still b…The level of modelling detail is high for the main guidance and may interrupt the architecture narrative, while still being insufficient for direct technical implementation. Suggested revision: Retain a concise explanation of the conformance approach in the main chapter and move detailed ArchiMate and IHE modelling conventions into a technical annex or separately maintained conformance specification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-039 discuss | in the document all mentions on GitHub record | ||
| PC-1119✎ edit📣 feedback | received | Core architects agent |
3.7.1 Purpose §3.7 overall p.78-87 l.Entire section anchor: medium |
The section does not address the cost and institutional capacity required to maintain profiles, test tools, certificati…The section does not address the cost and institutional capacity required to maintain profiles, test tools, certification, test data, and conformance services over time. Suggested revision: Add an operating and financing model for conformance infrastructure, covering ownership, recurrent funding, accreditation, supplier fees if used, equitable access, regional collaboration, and maintenance after standards updates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | ||
| PC-1120✎ edit📣 feedback | received | Core architects agent |
3.7.1 Purpose §3.7 overall p.78-87 l.Entire section anchor: medium |
The proposed approach may be difficult for countries without ArchiMate, FHIR, IHE, testing, or certification expertise.…The proposed approach may be difficult for countries without ArchiMate, FHIR, IHE, testing, or certification expertise. Without a proportional adoption model, conformance could become a barrier to implementation. Suggested revision: Provide progressive conformance levels, beginning with published specifications and basic validation, then interface testing, interoperable workflow testing, formal certification, and continuous operational conformance as national capacity grows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-246 discuss | in the document all mentions on GitHub record | ||
| PC-1121✎ edit📣 feedback | received | Core architects Clinical agent |
3.7.1 Purpose §3.7 overall p.78-87 l.Entire section anchor: medium |
Security, privacy, accessibility, performance, resilience, data quality, and clinical safety are mentioned elsewhere bu…Security, privacy, accessibility, performance, resilience, data quality, and clinical safety are mentioned elsewhere but are not integrated consistently into the conformance model. Suggested revision: Define cross-cutting conformance domains that apply to every relevant component and actor role, with risk-based requirements and test evidence for security, privacy, accessibility, performance, resilience, data quality, and clinical safety. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1122✎ edit📣 feedback | received | Core architects agent |
Implementing a National Digital Health Architecture §Chapter 4 introduction p.88 l.Lines 3-10 anchor: low |
The introduction clearly identifies the chapter as the bridge from reference architecture to implementation. However, i…The introduction clearly identifies the chapter as the bridge from reference architecture to implementation. However, it does not explicitly define the main implementation outputs that countries should produce, such as a baseline assessment, target architecture, roadmap, investment plan, governance model, and conformance plan. Suggested revision: Add a concise list of expected national outputs and show how the sections in Chapter 4 contribute to each output. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-091 discuss | in the document all mentions on GitHub record | ||
| PC-1123✎ edit📣 feedback | received | Core architects agent |
Implementing a National Digital Health Architecture §Chapter 4 introduction p.88 l.Lines 6-10 anchor: low |
The chapter claims to be explicit about who is accountable for implementation responsibilities, but the subsequent sect…The chapter claims to be explicit about who is accountable for implementation responsibilities, but the subsequent sections identify roles mainly in narrative form rather than through a complete responsibility model. Suggested revision: Add a responsibility-assignment matrix covering the Ministry of Health, national digital architect, DPI authorities, data-protection authority, procurement, finance, component owners, implementers, development partners, and subnational authorities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-108 discuss | in the document all mentions on GitHub record | ||
| PC-1124✎ edit📣 feedback | received | Editorial agent, medium |
Implementing a National Digital Health Architecture §Chapter 4 introduction p.88 l.Lines 3-10 anchor: low |
The chapter addresses ministries, architects, implementers, and development partners together. Their implementation nee…The chapter addresses ministries, architects, implementers, and development partners together. Their implementation needs differ substantially, which may make some sections too technical for one audience and insufficiently detailed for another. Suggested revision: Add audience markers within Chapter 4, identifying which subsections are decision guidance, architecture guidance, implementation guidance, or procurement guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-091 discuss | in the document all mentions on GitHub record | ||
| PC-1125✎ edit📣 feedback | received | Core architects agent |
4.1.1 No Country Starts from Zero §4.1.1 p.88 l.Lines 13-20 |
The section appropriately recognises that no country starts from zero. However, the legacy landscape is described mainl…The section appropriately recognises that no country starts from zero. However, the legacy landscape is described mainly in terms of systems and tools rather than also including contracts, data assets, standards, workforce, infrastructure, governance bodies, and operating processes. Suggested revision: Expand the legacy baseline to include systems, interfaces, data, identifiers, standards, contracts, licences, infrastructure, workforce capacity, governance arrangements, business processes, and current funding commitments. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1126✎ edit📣 feedback | received | Core architects agent, medium |
4.1.1 No Country Starts from Zero §4.1.1 p.88 l.Lines 13-20 |
The examples emphasise programme systems, national information systems, registries, and spreadsheets. Some settings rem…The examples emphasise programme systems, national information systems, registries, and spreadsheets. Some settings remain substantially paper-based or depend on hybrid paper-digital workflows. Suggested revision: Explicitly include paper records, manual registers, phone-based reporting, disconnected desktop applications, and informal data exchange as valid starting conditions that the architecture assessment must document. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1127✎ edit📣 feedback | received | Core architects agent |
4.1.1 No Country Starts from Zero §4.1.1 p.88 l.Lines 17-20 |
The four options of preserving, upgrading, integrating, or retiring existing investments are useful but incomplete. Cou…The four options of preserving, upgrading, integrating, or retiring existing investments are useful but incomplete. Countries may also need to consolidate duplicate systems, contain systems temporarily, replace only selected capabilities, or maintain them during a prolonged transition. Suggested revision: Introduce a standard disposition framework such as retain, remediate, integrate, consolidate, re-platform, replace, retire, or tolerate temporarily. Require rationale, cost, risk, dependencies, and target date for each decision. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1128✎ edit📣 feedback | received | Core architects agent |
4.1.1 No Country Starts from Zero §4.1.1 p.88 l.Lines 22-25 |
REDDHI is again described as a continuously maturing direction of travel. The chapter does not translate this into clea…REDDHI is again described as a continuously maturing direction of travel. The chapter does not translate this into clearly defined implementation stages or observable entry and exit conditions. Suggested revision: Define measurable REDDHI maturity states or milestones without presenting REDDHI as a one-time certification. Link each milestone to capabilities, governance, conformance, coverage, data quality, resilience, and sustainability indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | ||
| PC-1129✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.88-89 l.Lines 28-33 |
The importance of current-state assessment is correctly emphasised, but the document does not specify a standard assess…The importance of current-state assessment is correctly emphasised, but the document does not specify a standard assessment method or minimum evidence set. Different countries may therefore produce assessments that are not comparable or sufficiently rigorous. Suggested revision: Provide a reusable assessment template covering systems, capabilities, data, interfaces, governance, standards, security, infrastructure, cost, contracts, use, coverage, performance, and planned retirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | ||
| PC-1130✎ edit📣 feedback | received | Editorial agent, medium |
4.1.2 Assessing Where You Are §4.1.2 p.88-89 l.Lines 28-33 |
The statement that countries skipping assessment “tend to build on unstable foundations” is plausible but broad.The statement that countries skipping assessment “tend to build on unstable foundations” is plausible but broad. Suggested revision: Qualify it as a recognised implementation risk or provide evidence. Suggested wording: “Skipping this assessment increases the risk of duplicating existing capabilities, integrating with systems approaching retirement, or overlooking critical governance and data-quality weaknesses.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1131✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 34-38 |
The inventory asks whether each system aligns with a REDDHI component. This may bias the assessment toward the referenc…The inventory asks whether each system aligns with a REDDHI component. This may bias the assessment toward the reference component catalogue rather than first identifying national capabilities, workflows, and needs. Suggested revision: Begin with a capability and service inventory, then map existing systems to DPI-H reference components. Allow one system to realise several components and one component to be distributed across several systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1132✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 35-38 |
The inventory includes ownership and operation but not recurrent cost, contract conditions, licence obligations, suppli…The inventory includes ownership and operation but not recurrent cost, contract conditions, licence obligations, supplier dependency, hosting, support, or data-exit conditions. These are essential to sustainability decisions. Suggested revision: Require collection of total cost of ownership, funding source, contract term, licence model, hosting arrangement, support model, supplier concentration, data portability, source-code access where relevant, and exit or transition provisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | ||
| PC-1133✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 35-38 |
Population and geographic coverage are included, but the assessment does not explicitly require analysis of accessibili…Population and geographic coverage are included, but the assessment does not explicitly require analysis of accessibility, actual use, service quality, or excluded populations. Suggested revision: Add active use, user categories, digital accessibility, language coverage, connectivity constraints, gender and disability inclusion, populations without legal identity, and differences between nominal and effective coverage. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1134✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 39-42 |
The foundational-DPI assessment asks about identity, payments, and data exchange but omits potentially relevant capabil…The foundational-DPI assessment asks about identity, payments, and data exchange but omits potentially relevant capabilities such as trust services, digital signatures, organisational identity, geospatial infrastructure, civil registration, consent, notifications, and public-sector cloud. Suggested revision: Clarify that identity, payments, and exchange are the principal DPI-F areas considered, while countries should assess any additional shared national capabilities relevant to health. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1135✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 39-42 |
The assessment asks whether foundational DPI supports health use cases but does not require evaluation of real-world ac…The assessment asks whether foundational DPI supports health use cases but does not require evaluation of real-world accessibility, service reliability, assurance levels, cost, legal restrictions, or exclusion risks. Suggested revision: Add assessment of coverage, reliability, latency, service levels, security assurance, integration cost, legal basis, accessibility to public and private health providers, and effects on populations not covered by foundational identity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1136✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 43-47 |
Governance assessment focuses on whether legal frameworks, institutional homes, procurement alignment, and capacity exi…Governance assessment focuses on whether legal frameworks, institutional homes, procurement alignment, and capacity exist. It does not assess whether these arrangements function effectively in practice. Suggested revision: Review both formal and operational maturity, including decision records, enforcement capability, architecture exceptions, procurement compliance, incident handling, stakeholder participation, funding authority, and demonstrated stewardship. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1137✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 43-47 |
The section asks whether capacity exists “in government” but does not consider legitimate capacity distributed across u…The section asks whether capacity exists “in government” but does not consider legitimate capacity distributed across universities, standards bodies, public agencies, professional councils, local organisations, or regional institutions. Suggested revision: Assess national capacity across the wider public-interest ecosystem while defining which strategic responsibilities and controlling authority must remain accountable to government. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1138✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 48-53 |
Countries are advised to choose two or three priority health goals. The seven goals are broad, and selecting complete g…Countries are advised to choose two or three priority health goals. The seven goals are broad, and selecting complete goals may still produce programmes that are too large for an initial implementation. Suggested revision: Select bounded, high-value use cases within priority goals and document their users, workflows, information needs, expected outcomes, architectural dependencies, and scale pathway. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | ||
| PC-1139✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 48-53 |
Political support and a willing implementation community are used as selection criteria. This may deprioritise the need…Political support and a willing implementation community are used as selection criteria. This may deprioritise the needs of marginalised populations that lack political influence or organised institutional support. Suggested revision: Add disease burden, service inequity, affected population, public value, unmet need, feasibility, risk, and potential to strengthen shared infrastructure as selection criteria. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | ||
| PC-1140✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 48-53 |
The text prioritises use cases able to demonstrate tangible value quickly. This can encourage visible short-term projec…The text prioritises use cases able to demonstrate tangible value quickly. This can encourage visible short-term projects over less visible foundational governance, data-quality, and infrastructure work. Suggested revision: Require a balanced portfolio combining early-value use cases with foundational investments whose benefits may take longer to materialise. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | ||
| PC-1141✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 54-60 |
The national roadmap is described as a living document but lacks a minimum structure, governance process, update cadenc…The national roadmap is described as a living document but lacks a minimum structure, governance process, update cadence, and connection to budget and procurement cycles. Suggested revision: Define the roadmap’s minimum contents: baseline, target capabilities, transition states, dependencies, ownership, timeline, financing, procurement plan, risks, benefits, indicators, conformance requirements, and review schedule. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-091 discuss | in the document all mentions on GitHub record | ||
| PC-1142✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 54-60 |
The benefits case and logic model are described as strengthening the roadmap rather than being essential. Without them,…The benefits case and logic model are described as strengthening the roadmap rather than being essential. Without them, investments may not be traceable to expected public value. Suggested revision: Make a benefits case, cost model, and theory of change required outputs of the roadmap, proportionate to the scale of investment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-091 discuss | in the document all mentions on GitHub record | ||
| PC-1143✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 54-60 |
The section refers generally to recognised readiness and capability frameworks but does not identify preferred examples…The section refers generally to recognised readiness and capability frameworks but does not identify preferred examples or explain how they relate to REDDHI and the architecture model. Suggested revision: Reference a small set of suitable frameworks and provide a mapping showing which assessment dimensions they cover, where gaps remain, and how results feed into the national roadmap. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | ||
| PC-1144✎ edit📣 feedback | received | Core architects agent |
4.1.2 Assessing Where You Are §4.1.2 p.89 l.Lines 57-60 |
The logic model is expected to connect investment to capabilities and outcomes, but it does not explicitly include serv…The logic model is expected to connect investment to capabilities and outcomes, but it does not explicitly include services, operational adoption, assumptions, risks, or contextual factors. Suggested revision: Use a complete theory-of-change chain: investment, enabling conditions, components, services, adoption, capabilities, intermediate outcomes, health outcomes, assumptions, risks, and indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-091 discuss | in the document all mentions on GitHub record | ||
| PC-1145✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.89 l.Lines 64-68 |
The four entry points provide an accessible organising framework. However, countries may match several entry points sim…The four entry points provide an accessible organising framework. However, countries may match several entry points simultaneously across different regions, programmes, or components. Suggested revision: State that entry points are archetypes rather than mutually exclusive categories. Countries should assess the entry point separately by capability, domain, or region. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-092 discuss | in the document all mentions on GitHub record | ||
| PC-1146✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.89 l.Lines 64-68 |
The four entry points are primarily classified by existing digital infrastructure. They give less attention to governan…The four entry points are primarily classified by existing digital infrastructure. They give less attention to governance maturity, workforce capacity, legal readiness, fiscal space, decentralisation, connectivity, security, and conflict or emergency conditions. Suggested revision: Add these as dimensions that modify the recommended pathway, even where two countries appear to share the same infrastructure entry point. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-092 discuss | in the document all mentions on GitHub record | ||
| PC-1147✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.89-90 l.Lines 70-80 |
Entry point 1 recommends establishing governance and standards before major technology investment. This is sound, but c…Entry point 1 recommends establishing governance and standards before major technology investment. This is sound, but countries may still need urgent digital services while governance arrangements are being developed. Suggested revision: Allow controlled early implementations where essential, subject to minimum standards, explicit governance sponsorship, bounded scope, portability, published interfaces, and a transition plan into shared national infrastructure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | ||
| PC-1148✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.89-90 l.Lines 70-80 |
The recommendation to resist complex capabilities until foundations are stable may be interpreted as preventing countri…The recommendation to resist complex capabilities until foundations are stable may be interpreted as preventing countries from addressing urgent clinical, surveillance, or emergency needs through targeted solutions. Suggested revision: Clarify that urgent services may proceed in parallel, provided they do not create avoidable lock-in and are designed for later conformance, integration, or retirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | ||
| PC-1149✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.89-90 l.Lines 72-77 |
Donor-funded projects are identified as a risk to national coherence, but the section does not define how donors should…Donor-funded projects are identified as a risk to national coherence, but the section does not define how donors should be governed or aligned during the early phase. Suggested revision: Require donor and partner investments to use the national architecture, shared requirements, open interfaces, conformance criteria, joint governance, sustainability plan, and transparent exception process. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | ||
| PC-1150✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 81-90 |
Entry point 2 prioritises integration over replacement. This is pragmatic, but integration may preserve poor data quali…Entry point 2 prioritises integration over replacement. This is pragmatic, but integration may preserve poor data quality, unsafe systems, proprietary constraints, or unmanageable technical debt. Suggested revision: Make integration conditional on a structured assessment of safety, data quality, supportability, security, legal compliance, interface feasibility, cost, and expected remaining life. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1151✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 84-90 |
Deploying a Client Registry and shared APIs is presented as an example of reducing duplication immediately. Identity re…Deploying a Client Registry and shared APIs is presented as an example of reducing duplication immediately. Identity reconciliation can initially expose or amplify duplicate and conflicting records rather than immediately reduce them. Suggested revision: Add data-profiling, matching-quality assessment, manual adjudication, source remediation, merge governance, and monitoring as prerequisites for identity integration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-026 discuss | in the document all mentions on GitHub record | ||
| PC-1152✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 89-90 |
The phrase “an interoperability capability that standardises data exchange” is vague and may still be interpreted as pr…The phrase “an interoperability capability that standardises data exchange” is vague and may still be interpreted as procuring a mediator or integration platform. Suggested revision: Specify that the capability includes governed standards, profiles, terminology, endpoint registration, trust, interfaces, mappings, testing, monitoring, and mediation mechanisms selected for the context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | ||
| PC-1153✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 92-100 |
Entry point 3 focuses on API exposure and openness. Adding APIs to a proprietary or poorly structured platform is not s…Entry point 3 focuses on API exposure and openness. Adding APIs to a proprietary or poorly structured platform is not sufficient to achieve interoperability, maintainability, or supplier independence. Suggested revision: Require governed information models, semantic alignment, complete data export, interface rights, documentation, security, testability, configuration portability, and a credible supplier-exit path. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | ||
| PC-1154✎ edit📣 feedback | received | Core architects agent, medium |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 92-100 |
Negotiating with existing suppliers to expose standard APIs may involve additional licence costs, contract changes, or …Negotiating with existing suppliers to expose standard APIs may involve additional licence costs, contract changes, or legal constraints that are not addressed. Suggested revision: Add contract review, intellectual-property assessment, cost analysis, procurement leverage, regulatory options, and contingency planning where suppliers refuse or cannot comply. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | ||
| PC-1155✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 98-100 |
The “right to move” is a strong principle but is not defined in operational terms.The “right to move” is a strong principle but is not defined in operational terms. Suggested revision: Define minimum exit rights covering complete and timely export of data and metadata, configuration, audit history, documentation, interface specifications, encryption-key arrangements, migration support, and deletion or return of retained copies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-241 discuss | in the document all mentions on GitHub record | ||
| PC-1156✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 102-110 |
Entry point 4 combines scaling, semantic governance, last-mile coverage, financing, and architecture capacity. These ma…Entry point 4 combines scaling, semantic governance, last-mile coverage, financing, and architecture capacity. These may represent several distinct pathways rather than one maturity stage. Suggested revision: Separate scaling coverage, deepening functional capability, strengthening governance, and improving sustainability into independently assessable dimensions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-092 discuss | in the document all mentions on GitHub record | ||
| PC-1157✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 103-110 |
“Established shared infrastructure” and “strong governance” do not necessarily mean that marginalised regions, private …“Established shared infrastructure” and “strong governance” do not necessarily mean that marginalised regions, private providers, or community health organisations are connected or benefiting. Suggested revision: Require disaggregated assessment of effective coverage, service quality, affordability, inclusion, and use before classifying a country or domain as scaling and deepening. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-092 discuss | in the document all mentions on GitHub record | ||
| PC-1158✎ edit📣 feedback | received | Core architects agent |
4.2.1 Different Entry Points toward REDDHI §4.2.1 p.90 l.Lines 108-110 |
Domestically financed national infrastructure is treated as the desired sustainability state. Some countries may sustai…Domestically financed national infrastructure is treated as the desired sustainability state. Some countries may sustainably use regional shared services, pooled procurement, multilateral financing, or long-term partner support. Suggested revision: Define sustainability as predictable, accountable, and resilient financing under national governance, rather than requiring exclusively domestic financing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | ||
| PC-1159✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.90-91 l.Lines 113-122 |
The phases are described as overlapping and iterative, but their presentation remains substantially sequential. Countri…The phases are described as overlapping and iterative, but their presentation remains substantially sequential. Countries may interpret the phases as formal gates or fixed implementation order. Suggested revision: Present the phases as concurrent workstreams with maturity milestones and dependencies. Show governance, financing, capacity, security, evaluation, and change management running across all phases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | ||
| PC-1160✎ edit📣 feedback | received | Core architects agent, medium |
4.2.2 A Phased Implementation Approach §4.2.2 p.90-91 l.Lines 116-122 |
Indicative timeframes are introduced without a clear evidence basis and may create unrealistic expectations across coun…Indicative timeframes are introduced without a clear evidence basis and may create unrealistic expectations across countries with widely different scale and starting conditions. Suggested revision: Either provide the basis for the timeframes or describe them as illustrative only. Encourage countries to estimate duration from scope, readiness, procurement, data remediation, governance, and capacity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | ||
| PC-1161✎ edit📣 feedback | received | Core architects WHO agent, medium |
4.2.2 A Phased Implementation Approach §4.2.2 p.91 l.Lines 123-129 |
The relationship with the WHO Digital Implementation Investment Guide is useful but remains high level. Readers may str…The relationship with the WHO Digital Implementation Investment Guide is useful but remains high level. Readers may struggle to determine which artefact or decision belongs to the DIIG and which belongs to this architecture guidance. Suggested revision: Add a crosswalk between DIIG stages and DPI-H architecture activities, outputs, decision points, responsible roles, and investment artefacts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-095 discuss | in the document all mentions on GitHub record | ||
| PC-1162✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.91 l.Lines 130-145 |
Phase 1 includes assessment, governance, stakeholder engagement, use-case selection, procurement alignment, roadmap dev…Phase 1 includes assessment, governance, stakeholder engagement, use-case selection, procurement alignment, roadmap development, and financing. It does not explicitly include security, privacy, legal analysis, information architecture, data-quality assessment, or change readiness. Suggested revision: Add baseline legal, privacy, security, semantic, data-quality, infrastructure, change-readiness, and workforce assessments to Phase 1. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1163✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.91 l.Lines 130-145 |
Stakeholder engagement lists health programmes, finance, identity, and ICT ministries but does not explicitly include s…Stakeholder engagement lists health programmes, finance, identity, and ICT ministries but does not explicitly include subnational authorities, private providers, professional bodies, civil society, patients, data-protection authorities, standards bodies, or implementers. Suggested revision: Expand the stakeholder list and require context-specific stakeholder analysis covering decision authority, affected communities, data contributors, service operators, and groups at risk of exclusion. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1164✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.91 l.Lines 136-139 |
Priority health goals and use cases are selected before the document explicitly requires detailed capability, service, …Priority health goals and use cases are selected before the document explicitly requires detailed capability, service, data, workflow, and dependency modelling. Suggested revision: Require each selected use case to be modelled from outcome through workflow, actors, capabilities, services, information, DPI-H components, DPI-F dependencies, governance, and conformance requirements before implementation approval. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-1165✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.91 l.Lines 139-141 |
Procurement is aligned with open standards and conformance requirements, but Phase 1 does not require publication or av…Procurement is aligned with open standards and conformance requirements, but Phase 1 does not require publication or availability of the national profiles and test artefacts against which suppliers will be assessed. Suggested revision: Include national profile selection, implementation-guide development, test planning, reference data, validation tooling, and supplier conformance statements as Phase 1 or early Phase 2 outputs. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-260 discuss | in the document all mentions on GitHub record | ||
| PC-1166✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.91 l.Lines 142-145 |
Financing discussions begin early, which is a strength. However, the phase does not explicitly require estimates of rec…Financing discussions begin early, which is a strength. However, the phase does not explicitly require estimates of recurrent operating cost, workforce cost, semantic governance, conformance infrastructure, cybersecurity, support, and refresh or replacement. Suggested revision: Require a full lifecycle cost model rather than only implementation costing, including recurrent operations, governance, licences, connectivity, security, support, training, testing, migration, and eventual replacement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | ||
| PC-1167✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.91 l.Lines 146-147 |
The statement that Phase 1 investment is modest and returns are disproportionately large may not hold where national as…The statement that Phase 1 investment is modest and returns are disproportionately large may not hold where national assessment, legal reform, architecture development, and stakeholder coordination require substantial resources. Suggested revision: Qualify the claim. Suggested wording: “Although Phase 1 is usually less capital-intensive than deployment, it requires adequate specialist capacity and can substantially reduce downstream waste and implementation risk.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1168✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.91-92 l.Lines 148-161 |
Phase 2 combines core registries, the LHR, terminology services, standards alignment, and consolidation. This may be to…Phase 2 combines core registries, the LHR, terminology services, standards alignment, and consolidation. This may be too broad for a single phase and may encourage simultaneous implementation of several high-complexity components. Suggested revision: Require country-specific sequencing based on selected use cases, dependencies, governance readiness, data quality, architecture capacity, and investment constraints. Define minimum deliverables for each chosen component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | ||
| PC-1169✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 154-161 |
The foundational shared data layer includes the LHR as a Phase 2 component but not the LIMR. The role of minimum semant…The foundational shared data layer includes the LHR as a Phase 2 component but not the LIMR. The role of minimum semantic governance and information-model specifications during initial implementation remains unclear. Suggested revision: Require minimum governed data models, terminology bindings, versioning, and publication processes from the outset, even if a full LIMR platform is introduced later. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-1170✎ edit📣 feedback | received | Metadata registries agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 154-161 |
Deploying a “basic terminology service” may exceed the initial capacity of some settings, while other countries can beg…Deploying a “basic terminology service” may exceed the initial capacity of some settings, while other countries can begin with governed terminology packages and synchronised value sets rather than a live national service. Suggested revision: Allow maturity-appropriate implementation through curated code lists, versioned terminology packages, regional services, local mirrors, or a national runtime service, provided governance and migration paths are defined. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-1171✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 158-160 |
The Client Registry is described as a common first component. In some contexts, a facility registry, workforce registry…The Client Registry is described as a common first component. In some contexts, a facility registry, workforce registry, product master, terminology foundation, or surveillance use case may provide greater immediate value and face fewer privacy risks. Suggested revision: Present the Client Registry as a frequent but not default first component. Selection should follow use-case dependencies, risk, data availability, governance readiness, and expected shared value. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-026 discuss | in the document all mentions on GitHub record | ||
| PC-1172✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 162-166 |
Foundational-DPI integration emphasises national identity, while the implementation may also depend on trust services, …Foundational-DPI integration emphasises national identity, while the implementation may also depend on trust services, civil registration, organisational identity, geospatial references, payments, and exchange. Suggested revision: Require integration planning for all relevant foundational or cross-sector capabilities, prioritised according to the selected use cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1173✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 164-166 |
The interoperability capability is described as something to be “deployed” centrally or distributively. This wording ri…The interoperability capability is described as something to be “deployed” centrally or distributively. This wording risks recreating the idea that interoperability is a deployable component rather than a combination of standards, governance, services, and implementation mechanisms. Suggested revision: Replace with a sentence like: “Establish the interoperability capability by publishing specifications, governance and trust arrangements, implementing the necessary exchange mechanisms, and enabling conformant endpoints.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-073 discuss | in the document all mentions on GitHub record | ||
| PC-1174✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 167-169 |
Connecting two or three systems is used to demonstrate value, but the selection criteria for those systems are not give…Connecting two or three systems is used to demonstrate value, but the selection criteria for those systems are not given. Choosing only cooperative or technically mature systems may create an unrepresentative demonstration. Suggested revision: Select systems based on public value, representative complexity, readiness, dependency coverage, equity, data quality, and scale potential. Document why they are representative of later expansion. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-096 discuss | in the document all mentions on GitHub record | ||
| PC-1175✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 170-171 |
The phrase “not a pilot that would require reconstruction before it can scale” is directionally useful but may discoura…The phrase “not a pilot that would require reconstruction before it can scale” is directionally useful but may discourage safe experimentation and learning. Suggested revision: Distinguish disposable pilots from production-oriented pilots. Require bounded implementation that uses target standards and governance, tests assumptions, and can be scaled or deliberately retired based on evidence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-096 discuss | in the document all mentions on GitHub record | ||
| PC-1176✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 170-171 |
“Standards-conformant foundation” is not accompanied by minimum acceptance criteria for completion of Phase 2.“Standards-conformant foundation” is not accompanied by minimum acceptance criteria for completion of Phase 2. Suggested revision: Define exit criteria covering governance, authoritative ownership, conformance testing, data quality, security, service levels, actual use by priority programmes, support, financing, and documented scale readiness. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | ||
| PC-1177✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 173-184 |
Phase 3 combines additional system connection, SGI establishment, geographic expansion, legacy transition, and deployme…Phase 3 combines additional system connection, SGI establishment, geographic expansion, legacy transition, and deployment of business-service components. The combined scope may be unrealistic and difficult to govern. Suggested revision: Divide Phase 3 into capability workstreams with separate milestones for ecosystem connection, semantic governance, coverage expansion, legacy transition, and business-service development. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-093 discuss | in the document all mentions on GitHub record | ||
| PC-1178✎ edit📣 feedback | received | Core architects agent, medium |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 174-180 |
Geographic expansion mentions primary care, community health, offline, and low-connectivity settings, but it does not i…Geographic expansion mentions primary care, community health, offline, and low-connectivity settings, but it does not include accessibility, language, private providers, displaced populations, or cross-border communities. Suggested revision: Expand the last-mile criteria and require locally appropriate workflows, non-digital fallback, accessible interfaces, language support, assisted access, and inclusion of non-state providers where relevant. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-096 discuss | in the document all mentions on GitHub record | ||
| PC-1179✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 175-176 |
SGI is introduced in Phase 3, after foundational components are implemented in Phase 2. Semantic governance must begin …SGI is introduced in Phase 3, after foundational components are implemented in Phase 2. Semantic governance must begin before schemas, terminology, profiles, and data are implemented. Suggested revision: Establish minimum SGI in Phase 1 and Phase 2, including ownership, approval, versioning, publication, and change control. Develop advanced cross-asset capabilities progressively in Phase 3. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-1180✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 179-180 |
Legacy functions are transitioned when systems reach end of life. Some systems may remain in operation indefinitely des…Legacy functions are transitioned when systems reach end of life. Some systems may remain in operation indefinitely despite high cost, risk, or poor interoperability. Suggested revision: Use risk, cost, safety, supportability, data quality, security, and strategic fit alongside end-of-life status to prioritise transition. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1181✎ edit📣 feedback | received | Core architects agent, medium |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 181-183 |
Phase 3 lists decision support, HMIS and analytics, and public-health surveillance, but omits the Supplier Registry and…Phase 3 lists decision support, HMIS and analytics, and public-health surveillance, but omits the Supplier Registry and Benefits Package Registry from the business-services layer described in Section 3.5. Suggested revision: Clarify that the listed components are examples. Link business-service selection to the country’s priority goals and include all catalogue components where relevant. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-096 discuss | in the document all mentions on GitHub record | ||
| PC-1182✎ edit📣 feedback | received | Core architects Clinical agent, medium |
4.2.2 A Phased Implementation Approach §4.2.2 p.92 l.Lines 181-183 |
Advanced decision support and analytics may be prioritised before data quality, representativeness, workflow integratio…Advanced decision support and analytics may be prioritised before data quality, representativeness, workflow integration, and evaluation capacity are sufficient. Suggested revision: Require readiness criteria for each business-service capability, including data coverage and quality, governed models, evidence base, workflow readiness, human oversight, safety, monitoring, and operating capacity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-096 discuss | in the document all mentions on GitHub record | ||
| PC-1183✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.92-93 l.Lines 184-195 |
Phase 4 aims to transition from external funding to domestic financing. This may not be realistic or necessary in every…Phase 4 aims to transition from external funding to domestic financing. This may not be realistic or necessary in every setting, especially for regional services or long-term pooled financing. Suggested revision: Replace with a sentence like: “Transition toward predictable, diversified, and nationally accountable financing, with reduced dependence on short-term project funding.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | ||
| PC-1184✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
4.2.2 A Phased Implementation Approach §4.2.2 p.92-93 l.Lines 185-190 |
Cost recovery and shared-benefit arrangements are mentioned but no safeguards are provided against user fees, provider …Cost recovery and shared-benefit arrangements are mentioned but no safeguards are provided against user fees, provider exclusion, or inequitable access. Suggested revision: Require financing mechanisms to protect essential use, subsidise low-resource participants, ensure non-discriminatory access, and assess distributional impacts before introducing fees or contribution requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-114 discuss | in the document all mentions on GitHub record | ||
| PC-1185✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.93 l.Lines 191-193 |
Development partners are encouraged to support shared infrastructure, but the guidance does not define how programmes c…Development partners are encouraged to support shared infrastructure, but the guidance does not define how programmes can fund shared components when donor mandates require disease-specific attribution and results. Suggested revision: Provide cost-allocation, contribution-tracking, shared-results, pooled-funding, and attribution mechanisms that allow programme funders to demonstrate value while strengthening national infrastructure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | ||
| PC-1186✎ edit📣 feedback | received | Core architects agent |
4.2.2 A Phased Implementation Approach §4.2.2 p.93 l.Lines 194-195 |
Continuous architecture evolution is stated but no recurring architecture-management cycle is defined.Continuous architecture evolution is stated but no recurring architecture-management cycle is defined. Suggested revision: Require periodic architecture review, standards updates, portfolio rationalisation, benefits review, risk assessment, conformance reassessment, technology refresh, and roadmap revision. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-047 discuss | in the document all mentions on GitHub record | ||
| PC-1187✎ edit📣 feedback | received | Core architects agent, medium |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 198-200 |
“Legacy systems are not the enemy of DPI-H, unplanned legacy systems are” is memorable but imprecise. Many legacy syste…“Legacy systems are not the enemy of DPI-H, unplanned legacy systems are” is memorable but imprecise. Many legacy systems were planned appropriately for earlier requirements but have become unsupported or misaligned over time. Suggested revision: Replace with a sentence like: “Legacy systems should be assessed according to their current value, risk, supportability, interoperability, and strategic fit rather than their age alone.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1188✎ edit📣 feedback | received | Core architects Clinical agent |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 202-205 |
The legacy assessment asks whether a system aligns with REDDHI and can expose APIs, but does not require evaluation of …The legacy assessment asks whether a system aligns with REDDHI and can expose APIs, but does not require evaluation of clinical safety, cybersecurity, accessibility, data quality, performance, or ongoing support. Suggested revision: Add these assessment dimensions and require a documented disposition decision for every significant legacy system. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1189✎ edit📣 feedback | received | Core architects agent |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 207-211 |
“Integrate before you replace” is stated as an almost universal preference where data is difficult to recreate. Integra…“Integrate before you replace” is stated as an almost universal preference where data is difficult to recreate. Integration can extend the life of unsafe, unsupported, or prohibitively expensive systems. Suggested revision: Qualify the principle: preserve and migrate valuable data, but integrate the legacy application only where the risk, cost, remaining life, security, and supportability justify doing so. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1190✎ edit📣 feedback | received | Core architects agent |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 207-211 |
Exposing legacy data through standard APIs may not be technically feasible and can create a façade that does not resolv…Exposing legacy data through standard APIs may not be technically feasible and can create a façade that does not resolve inconsistent semantics or poor data quality. Suggested revision: Allow alternatives such as read-only extraction, scheduled bulk exchange, event capture, external adapters, data replication, document exchange, or staged migration. Require semantic mapping and quality assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1191✎ edit📣 feedback | received | Core architects agent |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 213-217 |
Natural transition points are useful, but procurement end dates may not align with clinical, operational, or data-migra…Natural transition points are useful, but procurement end dates may not align with clinical, operational, or data-migration readiness. Suggested revision: Require transition planning well before contract end, including target design, data migration, testing, workforce preparation, parallel operation where necessary, fallback, cutover, and decommissioning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1192✎ edit📣 feedback | received | Core architects agent |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 213-217 |
The section does not mention the cost of parallel operation, migration, data cleaning, contract termination, archival a…The section does not mention the cost of parallel operation, migration, data cleaning, contract termination, archival access, or decommissioning. Suggested revision: Include these costs in the roadmap and investment case. Require suppliers to provide transition assistance and complete data export under agreed terms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1193✎ edit📣 feedback | received | Core architects agent |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 219-223 |
Architectural conformance is proposed as a mandatory procurement requirement, but the reference architecture does not y…Architectural conformance is proposed as a mandatory procurement requirement, but the reference architecture does not yet provide a complete executable conformance package. Suggested revision: Make conformance mandatory only against published, versioned, testable national profiles. Until then, use evidence-based requirements covering open interfaces, data portability, standards alignment, and documented mappings. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-260 discuss | in the document all mentions on GitHub record | ||
| PC-1194✎ edit📣 feedback | received | Core architects agent |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 219-223 |
Strict conformance requirements may exclude smaller local suppliers that lack certification resources, even when their …Strict conformance requirements may exclude smaller local suppliers that lack certification resources, even when their solutions could meet country needs. Suggested revision: Provide transparent test tools, reusable profiles, pre-procurement support, proportionate evidence requirements, regional test services, and phased remediation so conformance promotes interoperability without unnecessarily reducing competition. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-260 discuss | in the document all mentions on GitHub record | ||
| PC-1195✎ edit📣 feedback | received | Core architects agent |
4.2.3 Navigating Legacy Systems §4.2.3 p.93 l.Lines 219-223 |
The section focuses on stopping new technical silos but does not address governance, financing, contractual, or data si…The section focuses on stopping new technical silos but does not address governance, financing, contractual, or data silos within otherwise standards-based systems. Suggested revision: Require shared governance, data stewardship, reference identifiers, semantic alignment, access arrangements, funding coordination, and lifecycle management in addition to interface conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-089 discuss | in the document all mentions on GitHub record | ||
| PC-1196✎ edit📣 feedback | received | Core architects agent |
4.2.4 The Role of the National Digital Architect §4.2.4 p.93-94 l.Lines 226-236 |
The national digital architect is positioned as an individual or small team with authority across programmes and minist…The national digital architect is positioned as an individual or small team with authority across programmes and ministries. In many countries, such authority cannot be exercised by a technical role without a formal legal or governance mandate. Suggested revision: Define the role as an accountable architecture function established through the national governance structure, with delegated authority, escalation routes, and support from procurement, finance, legal, security, and sector leadership. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | ||
| PC-1197✎ edit📣 feedback | received | Core architects agent, medium |
4.2.4 The Role of the National Digital Architect §4.2.4 p.93-94 l.Lines 227-236 |
The assertion that implementation fails mainly for lack of architectural accountability rather than technology may be d…The assertion that implementation fails mainly for lack of architectural accountability rather than technology may be directionally useful but is too broad. Suggested revision: Qualify the claim and recognise other major causes, including financing, leadership, workforce, adoption, procurement, legal barriers, infrastructure, data quality, and political economy. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1198✎ edit📣 feedback | received | Core architects agent |
4.2.4 The Role of the National Digital Architect §4.2.4 p.94 l.Lines 230-236 |
An individual architect may become a bottleneck or single point of institutional dependency, particularly where experti…An individual architect may become a bottleneck or single point of institutional dependency, particularly where expertise is scarce. Suggested revision: Establish a multidisciplinary national architecture office or function, with documented succession, peer review, delegated decision authority, knowledge management, and institutional continuity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | ||
| PC-1199✎ edit📣 feedback | received | Core architects agent |
4.2.4 The Role of the National Digital Architect §4.2.4 p.94 l.Lines 233-236 |
The role is empowered to “say no,” but the criteria, transparency, appeal, and accountability for rejecting investments…The role is empowered to “say no,” but the criteria, transparency, appeal, and accountability for rejecting investments are not specified. Suggested revision: Require published architecture principles, documented review criteria, written decisions, conflicts-of-interest controls, time-bound review, an exception process, and appeal or escalation to strategic governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | ||
| PC-1200✎ edit📣 feedback | received | Core architects agent |
4.2.4 The Role of the National Digital Architect §4.2.4 p.94 l.Lines 237-244 |
The role is intended to be enduring but no funding, career framework, institutional placement, or independence safeguar…The role is intended to be enduring but no funding, career framework, institutional placement, or independence safeguards are described. Suggested revision: Require a recurrent budget, defined seniority, professional development, succession planning, access to specialist support, and protection from project-based or supplier-dependent funding. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | ||
| PC-1201✎ edit📣 feedback | received | Core architects agent |
4.2.4 The Role of the National Digital Architect §4.2.4 p.94 l.Lines 237-244 |
The suggested institutional locations include the Ministry of Health, digital-health agency, or whole-of-government aut…The suggested institutional locations include the Ministry of Health, digital-health agency, or whole-of-government authority, but do not discuss the trade-offs among them. Suggested revision: Provide selection criteria covering legal mandate, proximity to health policy, authority across ministries, procurement influence, technical capacity, independence, continuity, and coordination with foundational-DPI authorities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | ||
| PC-1202✎ edit📣 feedback | received | Core architects agent, medium |
4.2.4 The Role of the National Digital Architect §4.2.4 p.94 l.Lines 241-244 |
Regional and global networks of national architects are mentioned without examples or evidence of how they support impl…Regional and global networks of national architects are mentioned without examples or evidence of how they support implementation. Suggested revision: Provide illustrative networks or collaboration models and explain their functions, such as peer review, shared profiles, training, reference models, or mutual support, while avoiding dependence on informal networks for formal national accountability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | ||
| PC-1203✎ edit📣 feedback | received | Core architects agent |
4.2.4 The Role of the National Digital Architect §4.2.4 p.94 l.Lines 226-244 |
The national digital architect role focuses on architecture standards and investment alignment but does not explicitly …The national digital architect role focuses on architecture standards and investment alignment but does not explicitly cover benefits, data architecture, security, service management, transition architecture, and architecture repositories. Suggested revision: Define the full architecture-function responsibilities and the multidisciplinary roles that support them, rather than placing all responsibilities on one individual. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-094 discuss | in the document all mentions on GitHub record | ||
| PC-1204✎ edit📣 feedback | received | Core architects agent |
4.3 Profiles and Specifications for Implementation §4.3 p.94 l.Lines 249-254 |
The section correctly explains that implementable architectures need profiles covering data structures, actors, transac…The section correctly explains that implementable architectures need profiles covering data structures, actors, transactions, and interfaces. However, it does not identify the complete set of implementation artefacts countries should produce. Suggested revision: Add a minimum implementation-package checklist covering logical models, implementation guides, terminology bindings, actor definitions, capability statements, API specifications, security profiles, workflow specifications, test cases, test data, deployment guidance, and versioning policies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-098 discuss | in the document all mentions on GitHub record | ||
| PC-1205✎ edit📣 feedback | received | Core architects agent, medium |
4.3 Profiles and Specifications for Implementation §4.3 p.94 l.Lines 249-254 |
The section provides high-level direction but does not contain enough operational detail for technical teams to create …The section provides high-level direction but does not contain enough operational detail for technical teams to create national profiles directly. Suggested revision: Retain the principles in the main guidance but provide a companion technical implementation guide containing templates, examples, modelling conventions, publication processes, and validation rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-098 discuss | in the document all mentions on GitHub record | ||
| PC-1206✎ edit📣 feedback | received | Core architects agent |
4.3 Profiles and Specifications for Implementation §4.3 p.94 l.Lines 249-254 |
The section suggests that profiles give practical form to the architecture, but it does not define the relationship amo…The section suggests that profiles give practical form to the architecture, but it does not define the relationship among a reference profile, national profile, implementation guide, vendor implementation, and conformance statement. Suggested revision: Define this hierarchy and show how requirements are progressively constrained from the global reference architecture to national specifications and tested product implementations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-098 discuss | in the document all mentions on GitHub record | ||
| PC-1207✎ edit📣 feedback | received | Core architects agent, medium |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.94-95 l.Lines 256-264 |
The statement that the most consequential implementation decision is what data to capture and how to structure it is im…The statement that the most consequential implementation decision is what data to capture and how to structure it is important, but it may understate the significance of purpose, workflow, users, governance, and expected outcomes. Suggested revision: Replace with a sentence like: “One of the most consequential implementation decisions is defining the information required to support agreed purposes and workflows, and how that information should be structured, coded, governed, and exchanged.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | ||
| PC-1208✎ edit📣 feedback | received | Core architects agent |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.94-95 l.Lines 256-264 |
The section recommends designing data structures first. Designing structures before analysing workflows, decisions, act…The section recommends designing data structures first. Designing structures before analysing workflows, decisions, actors, and information needs may produce technically coherent but operationally unsuitable models. Suggested revision: Use a sequence beginning with use cases, actors, workflows, decisions, and information requirements, followed by logical modelling, terminology binding, implementation profiling, and validation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-090 discuss | in the document all mentions on GitHub record | ||
| PC-1209✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.94-95 l.Lines 261-264 |
Semantic interoperability is described as depending on initial data-model decisions and governance through SGI. It also…Semantic interoperability is described as depending on initial data-model decisions and governance through SGI. It also depends on implementation guides, terminology versions, mappings, provenance, workflows, and conformance. Suggested revision: Expand the statement to recognise the full semantic-governance and implementation ecosystem rather than attributing semantic interoperability mainly to data models. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-1210✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.95 l.Lines 265-272 |
Countries are instructed to define minimum data models for every DPI-H component before implementation. This may be too…Countries are instructed to define minimum data models for every DPI-H component before implementation. This may be too demanding for countries adopting existing international or regional specifications with limited modelling capacity. Suggested revision: Allow countries to adopt suitable existing models and define only necessary national constraints, extensions, translations, and mappings, provided national governance and conformance are maintained. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1211✎ edit📣 feedback | received | Core architects agent |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.95 l.Lines 265-272 |
The “irreducible” minimum dataset is described conceptually, but the method for determining whether an element is truly…The “irreducible” minimum dataset is described conceptually, but the method for determining whether an element is truly mandatory is not defined. Suggested revision: Require every mandatory element to have a documented purpose, use case, responsible source, data-quality expectation, privacy justification, and conformance test. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-100 discuss | in the document all mentions on GitHub record | ||
| PC-1212✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.95 l.Lines 265-272 |
Mandatory national datasets may create barriers for people or facilities unable to provide every required attribute. Th…Mandatory national datasets may create barriers for people or facilities unable to provide every required attribute. This is especially relevant to identity, address, contact, nationality, and credential data. Suggested revision: Distinguish mandatory schema support from mandatory presence in every record. Define conditional, unknown, unavailable, provisional, and not-applicable states and ensure missing data does not automatically prevent essential service access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-100 discuss | in the document all mentions on GitHub record | ||
| PC-1213✎ edit📣 feedback | received | Metadata registries agent |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.95 l.Lines 265-272 |
The LIMR is described as the designated home for national data models. Earlier sections describe it as a progressive en…The LIMR is described as the designated home for national data models. Earlier sections describe it as a progressive enabler rather than part of the minimum foundation. Suggested revision: Clarify that governed models must exist from the outset, while they may initially be published through simpler repositories or implementation guides and later managed through a dedicated LIMR. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-1214✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.95 l.Lines 273-283 |
The minimum datasets for core registries are described only at a very high level. They do not state how organisation, s…The minimum datasets for core registries are described only at a very high level. They do not state how organisation, service, role, relationship, provenance, identifier, and historical-status information is handled consistently across components. Suggested revision: Define cross-component modelling patterns for identifiers, organisations, locations, roles, relationships, provenance, lifecycle status, effective periods, versioning, and audit metadata. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1215✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.95 l.Lines 273-283 |
The workforce example refers to a “licensed health worker,” which may exclude community health workers, traditional pra…The workforce example refers to a “licensed health worker,” which may exclude community health workers, traditional practitioners, volunteers, trainees, and other cadres without formal professional licensing. Suggested revision: Replace with “recognised health worker” and model professional registration, certification, employment authorisation, community accreditation, or other nationally applicable status separately. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1216✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
4.3.1 Design Data Structures and Data Models First §4.3.1 p.95 l.Lines 273-283 |
Versioning, validity periods, and content integrity are identified for terminology and LIMR metadata, but these propert…Versioning, validity periods, and content integrity are identified for terminology and LIMR metadata, but these properties are equally important for registry records, interfaces, profiles, and implementation guides. Suggested revision: Apply common lifecycle, validity, provenance, versioning, and integrity requirements across all governed architecture artefacts and authoritative records. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1217✎ edit📣 feedback | received | Core architects agent |
4.3.2 Actors and Roles: Defining Who Participates §4.3.2 p.95 l.Lines 285-291 |
The section combines human and system actors but does not provide a modelling rule distinguishing individuals, professi…The section combines human and system actors but does not provide a modelling rule distinguishing individuals, professional roles, organisations, devices, applications, and abstract interoperability roles. Suggested revision: Define an actor taxonomy and show how each actor type relates to authentication, authorisation, attribution, workflow, and conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-1218✎ edit📣 feedback | received | Core architects agent |
4.3.2 Actors and Roles: Defining Who Participates §4.3.2 p.95 l.Lines 285-291 |
The section implies that actor definitions are primarily needed for transactions and access control. They are also nece…The section implies that actor definitions are primarily needed for transactions and access control. They are also necessary for governance, accountability, consent, task assignment, safety, and audit. Suggested revision: Expand the purpose of actor modelling and require accountable ownership for each role and interaction. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-1219✎ edit📣 feedback | received | Core architects agent, medium |
4.3.2 Actors and Roles: Defining Who Participates §4.3.2 p.95 l.Lines 292-304 |
SMART Guidelines personas are presented as a worked example of actor modelling. The text may overstate the degree to wh…SMART Guidelines personas are presented as a worked example of actor modelling. The text may overstate the degree to which personas are directly represented as computable actor definitions in every corresponding implementation guide. Suggested revision: Verify the statement against current SMART Guidelines specifications and distinguish human personas, business roles, system actors, and FHIR actor representations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-1220✎ edit📣 feedback | received | Editorial agent |
4.3.2 Actors and Roles: Defining Who Participates §4.3.2 p.95 l.Lines 292-304 |
The phrase “depersonalised, context-free descriptions” may be confusing. Personas usually contain relevant role and con…The phrase “depersonalised, context-free descriptions” may be confusing. Personas usually contain relevant role and context characteristics while excluding identifying information. Suggested revision: Replace with a sentence like: “generic, non-identifying descriptions of the people and system roles involved in a workflow.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-1221✎ edit📣 feedback | received | Core architects agent, medium |
4.3.2 Actors and Roles: Defining Who Participates §4.3.2 p.95-96 l.Lines 298-304 |
Reusing common actor sets may improve consistency, but national roles and scopes of practice vary significantly. Over-s…Reusing common actor sets may improve consistency, but national roles and scopes of practice vary significantly. Over-standardisation could obscure local legal and professional distinctions. Suggested revision: Define reusable base roles that countries can specialise through governed national role models, while preserving mappings to the common reference roles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1222✎ edit📣 feedback | received | Core architects agent |
4.3.2 Actors and Roles: Defining Who Participates §4.3.2 p.95-96 l.Lines 298-304 |
The examples of registrant, verifying authority, and consuming system are insufficient for complex registry workflows i…The examples of registrant, verifying authority, and consuming system are insufficient for complex registry workflows involving source authorities, stewards, adjudicators, administrators, data subjects, auditors, and downstream services. Suggested revision: Provide a fuller minimum role set for each component and distinguish data provision, verification, approval, stewardship, consumption, oversight, and support roles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-258 discuss | in the document all mentions on GitHub record | ||
| PC-1223✎ edit📣 feedback | received | Core architects agent |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 306-323 |
Recommending FHIR as the primary exchange framework is reasonable for new health-data services, but the section may be …Recommending FHIR as the primary exchange framework is reasonable for new health-data services, but the section may be read as recommending FHIR for every DPI-H domain and interaction, including supply chain, payments, geospatial data, trust, and bulk analytics. Suggested revision: State that FHIR is the recommended primary framework for relevant health-information exchange, while other recognised standards may be more appropriate for imaging, supply chain, payments, geospatial data, analytics, and foundational DPI integration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-1224✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 308-313 |
FHIR is described as delivering the syntactic and structural layer of interoperability. FHIR also provides semantic str…FHIR is described as delivering the syntactic and structural layer of interoperability. FHIR also provides semantic structures and terminology-binding mechanisms, although shared interpretation depends on profiling and governance. Suggested revision: Revise to explain that FHIR provides a common exchange representation, structured resources, terminology bindings, and extensibility mechanisms, but does not guarantee semantic interoperability without shared profiles and governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-1225✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 313-321 |
The text presents FHIR profiles as representations derived from a technology-independent logical model. While this is a…The text presents FHIR profiles as representations derived from a technology-independent logical model. While this is a sound modelling approach, many FHIR profiles are authored directly from requirements without a separate formal logical model. Suggested revision: Present derivation from governed logical models as the preferred national approach rather than an inherent property of all FHIR profiling. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-1226✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 318-321 |
The statement that two valid FHIR systems can diverge in meaning is correct, but alignment to the same logical model al…The statement that two valid FHIR systems can diverge in meaning is correct, but alignment to the same logical model alone is not sufficient. Systems must also share terminology versions, invariants, extensions, workflow expectations, and exchange behaviour. Suggested revision: Expand the conditions for semantic interoperability and conformance accordingly. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-1227✎ edit📣 feedback | received | Core architects agent |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 321-323 |
FHIR’s alignment with web standards is said to make it accessible to a broad implementer ecosystem. Countries may still…FHIR’s alignment with web standards is said to make it accessible to a broad implementer ecosystem. Countries may still face substantial shortages of profiling, terminology, security, and implementation expertise. Suggested revision: Acknowledge the capacity requirement and recommend reusable implementation guides, reference implementations, regional expertise, training, hosted test services, and gradual adoption. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-1228✎ edit📣 feedback | received | Core architects agent |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 324-329 |
The profiles are expected to define resources, operations, search parameters, and transaction patterns, but they omit t…The profiles are expected to define resources, operations, search parameters, and transaction patterns, but they omit terminology packages, security, versioning, error responses, subscriptions, bulk exchange, and non-functional requirements. Suggested revision: Expand the national profile template to cover these areas and define expected capability statements and test cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-098 discuss | in the document all mentions on GitHub record | ||
| PC-1229✎ edit📣 feedback | received | Core architects agent |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 324-329 |
The text implies that suppliers and governments can use profiles to assess existing systems, but it does not describe h…The text implies that suppliers and governments can use profiles to assess existing systems, but it does not describe how non-FHIR systems may demonstrate equivalent capability during transition. Suggested revision: Allow documented mappings, adapters, or alternative conformant interfaces under time-bound transition arrangements, with tests demonstrating preservation of meaning and behaviour. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-099 discuss | in the document all mentions on GitHub record | ||
| PC-1230✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 330-337 |
The progressive approach is helpful, but aligning underlying data models directly to FHIR resource structures may creat…The progressive approach is helpful, but aligning underlying data models directly to FHIR resource structures may create technology dependency and conflict with the stated role of technology-independent logical models. Suggested revision: Recommend alignment to governed logical concepts and mappings to FHIR, rather than requiring internal data structures to mirror FHIR resources. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-265 discuss | in the document all mentions on GitHub record | ||
| PC-1231✎ edit📣 feedback | received | Core architects agent |
4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3.3 p.96 l.Lines 330-337 |
“Simpler exchange mechanisms” are not defined. Countries need to know which transitional methods are acceptable and how…“Simpler exchange mechanisms” are not defined. Countries need to know which transitional methods are acceptable and how they progress toward target conformance. Suggested revision: Provide examples such as versioned CSV packages, secure batch exchange, HL7 v2, CDA documents, offline bundles, or simplified APIs, with required mappings, governance, validation, and migration milestones. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-099 discuss | in the document all mentions on GitHub record | ||
| PC-1232✎ edit📣 feedback | received | Core architects WHO agent, medium |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.96-97 l.Lines 339-344 |
The list of foundational dependencies includes CRVS together with identity, payments, and national exchange, although C…The list of foundational dependencies includes CRVS together with identity, payments, and national exchange, although CRVS is not consistently classified elsewhere as one of the principal DPI-F categories. Suggested revision: Establish a consistent classification of foundational DPI, cross-sector authoritative systems, and DPI-H. Use the same classification throughout the guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-267 discuss | in the document all mentions on GitHub record | ||
| PC-1233✎ edit📣 feedback | received | Core architects agent |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 343-352 |
Requiring two categories of interface is useful, but the distinction between APIs foundational DPI provides to health a…Requiring two categories of interface is useful, but the distinction between APIs foundational DPI provides to health and APIs health provides to foundational DPI can oversimplify event-driven, federated, and bidirectional exchange. Suggested revision: Describe required information flows, services, events, responsibilities, and trust boundaries rather than classifying all integration as one-directional APIs. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-101 discuss | in the document all mentions on GitHub record | ||
| PC-1234✎ edit📣 feedback | received | Core architects agent |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 345-352 |
The examples assume that foundational systems expose modern APIs and that health systems can access them. Some countrie…The examples assume that foundational systems expose modern APIs and that health systems can access them. Some countries rely on batch files, messaging, manual processes, or restricted government networks. Suggested revision: Allow several governed integration patterns, including APIs, secure messaging, events, batch exchange, and transitional manual verification, with a documented progression path. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-099 discuss | in the document all mentions on GitHub record | ||
| PC-1235✎ edit📣 feedback | received | Core architects WHO agent, medium |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 347-348 |
Civil-registration events are described as triggering updates in the Client and Workforce Registries. A birth or death …Civil-registration events are described as triggering updates in the Client and Workforce Registries. A birth or death event may require verification, matching, legal finalisation, and domain-specific action rather than automatic record modification. Suggested revision: Require event validation, identity matching, effective-date management, provenance, confirmation, reconciliation, and exception handling before authoritative records are updated. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-101 discuss | in the document all mentions on GitHub record | ||
| PC-1236✎ edit📣 feedback | received | Core architects agent |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 353-361 |
The second API category suggests foundational-DPI authorities might consume patient-matching, facility, workforce, and …The second API category suggests foundational-DPI authorities might consume patient-matching, facility, workforce, and terminology APIs. Some of these uses may exceed their mandate or create unnecessary cross-sector access to sensitive health information. Suggested revision: Require purpose limitation, minimum necessary access, legal authority, documented use cases, and privacy-impact assessment before exposing health-sector services to foundational-DPI authorities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1237✎ edit📣 feedback | received | Core architects agent |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 354-356 |
Allowing foundational identity authorities to consume patient-matching APIs could increase surveillance or deterrence r…Allowing foundational identity authorities to consume patient-matching APIs could increase surveillance or deterrence risks for undocumented persons or people using sensitive services. Suggested revision: Make such integration optional and use-case-specific. Require separation of health identity from legal-identity enforcement, strong access controls, audit, transparency, and protection against denial of care. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1238✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 357-359 |
Payment systems are said to use workforce-registry credentials to confirm provider eligibility before releasing funds. …Payment systems are said to use workforce-registry credentials to confirm provider eligibility before releasing funds. Workforce credentials alone do not establish contractual eligibility, facility empanelment, entitlement, or claim validity. Suggested revision: Distinguish professional-authorisation verification from contracting, empanelment, benefit, and payment eligibility checks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-1239✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 359-361 |
The suggestion that systems outside health need access to health terminology APIs is too broad and may create unnecessa…The suggestion that systems outside health need access to health terminology APIs is too broad and may create unnecessary licensing, governance, and privacy concerns. Suggested revision: Limit access to authorised use cases requiring health-coded information and apply licensing, authentication, purpose, and minimum-data restrictions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1240✎ edit📣 feedback | received | Core architects agent |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 362-367 |
Health requirements are to be communicated to foundational-DPI authorities, but no joint governance or prioritisation m…Health requirements are to be communicated to foundational-DPI authorities, but no joint governance or prioritisation mechanism is defined. Suggested revision: Establish a cross-sector architecture forum, requirements process, service-level agreement, funding arrangement, conflict-resolution method, and roadmap for shared dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1241✎ edit📣 feedback | received | Core architects agent |
4.3.4 Integration Interfaces with Foundational DPI §4.3.4, Integration interfaces p.97 l.Lines 365-367 |
Interim capabilities are permitted where DPI-F is absent, but transition plans alone may not prevent permanent duplicat…Interim capabilities are permitted where DPI-F is absent, but transition plans alone may not prevent permanent duplication. Suggested revision: Require interoperability with future national services, modular replacement boundaries, time-bound review, cost comparison, and strategic-governance approval for any continued parallel capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-011 discuss | in the document all mentions on GitHub record | ||
| PC-1242✎ edit📣 feedback | received | Editorial agent |
4.3.4 Interoperability Implementation Pathways §4.3.4, implementation pathways p.97 l.Section heading, Lines 369 onward |
The document has two subsections numbered 4.3.4: “Integration Interfaces with Foundational DPI” and “Interoperability I…The document has two subsections numbered 4.3.4: “Integration Interfaces with Foundational DPI” and “Interoperability Implementation Pathways.” Suggested revision: Renumber the latter as 4.3.5 and update all subsequent subsection numbers and cross-references. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-097 discuss | in the document all mentions on GitHub record | ||
| PC-1243✎ edit📣 feedback | received | Core architects agent |
4.3.4 Interoperability Implementation Pathways §4.3.4, implementation pathways p.97-98 l.Lines 369-380 |
The section introduces centralised, federated, and hybrid models after Section 3.6 has already described a broader and …The section introduces centralised, federated, and hybrid models after Section 3.6 has already described a broader and more nuanced set of exchange patterns. The terminology is not fully aligned. Suggested revision: Consolidate the topology guidance or provide a cross-reference table showing how centralised, federated, distributed-access-point, gateway, direct, and publish-subscribe patterns relate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1244✎ edit📣 feedback | received | Editorial agent, medium |
4.3.4 Interoperability Implementation Pathways §4.3.4, implementation pathways p.97 l.Lines 369-374 |
“Logical decoupling of core functions” is a useful principle but is not defined for non-architect readers.“Logical decoupling of core functions” is a useful principle but is not defined for non-architect readers. Suggested revision: Explain that components should have clear responsibilities, independent data ownership, documented interfaces, replaceable implementations, and minimal hidden dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1245✎ edit📣 feedback | received | Core architects agent |
4.3.4 Interoperability Implementation Pathways §4.3.4, implementation pathways p.97-98 l.Lines 375-380 |
The section states that modularity allows incremental adoption but does not identify the minimum shared specifications …The section states that modularity allows incremental adoption but does not identify the minimum shared specifications needed to prevent independently adopted modules from becoming new silos. Suggested revision: Require common identifiers, terminology, models, interface contracts, security policies, event conventions, versioning, and conformance tests before independent deployment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1246✎ edit📣 feedback | received | Core architects agent |
4.3.4 Interoperability Implementation Pathways §4.3.4, implementation pathways p.98 l.Lines 381-390 |
Centralised models are associated with stronger public governance and accountability, while federated models are associ…Centralised models are associated with stronger public governance and accountability, while federated models are associated with autonomy. Public governance and accountability depend on institutional design, not only topology. Suggested revision: Present these as possible benefits rather than inherent properties and add the corresponding risks and prerequisites for each topology. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1247✎ edit📣 feedback | received | Core architects agent |
4.3.4 Interoperability Implementation Pathways §4.3.4, implementation pathways p.98 l.Lines 381-390 |
Federated systems require local infrastructure, skills, security, uptime, and conformance. They may be harder, not easi…Federated systems require local infrastructure, skills, security, uptime, and conformance. They may be harder, not easier, for under-resourced participants to operate. Suggested revision: Include participant capacity and equity in topology selection. Consider shared managed access points, regional services, or hybrid models where local operation is not sustainable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1248✎ edit📣 feedback | received | Core architects agent, medium |
4.3.4 Interoperability Implementation Pathways §4.3.4, implementation pathways p.98 l.Lines 388-390 |
“Master registries and policy enforcement” are presented as examples of centralised functions. Registries and policy en…“Master registries and policy enforcement” are presented as examples of centralised functions. Registries and policy enforcement may themselves be federated or distributed. Suggested revision: Describe them as functions often coordinated nationally, without prescribing physical centralisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1249✎ edit📣 feedback | received | Core architects agent |
4.3.4 Interoperability Implementation Pathways §4.3.4, implementation pathways p.98 l.Lines 391-396 |
The text refers to several large countries using a hybrid model but does not identify them or provide evidence. It also…The text refers to several large countries using a hybrid model but does not identify them or provide evidence. It also describes a centralised HIE and claims exchange without distinguishing logical from physical centralisation. Suggested revision: Identify the examples and sources, describe their actual topology and governance accurately, or remove the unsupported generalisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1250✎ edit📣 feedback | received | Core architects agent |
4.3.5 Minimum Conformance and Testing §4.3.5, minimum conformance p.98 l.Lines 398-407 |
The section recommends an interoperability test bed but cites a general European test-bed repository rather than a clea…The section recommends an interoperability test bed but cites a general European test-bed repository rather than a clearly identified health-specific implementation package. Suggested revision: Provide health-specific examples and clarify which test-bed capabilities are required for FHIR, IHE, terminology, security, performance, and national profiles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | ||
| PC-1251✎ edit📣 feedback | received | Core architects agent |
4.3.5 Minimum Conformance and Testing §4.3.5, minimum conformance p.98 l.Lines 398-407 |
Conformance certification is suggested as a procurement condition, but the certifying authority, accreditation model, v…Conformance certification is suggested as a procurement condition, but the certifying authority, accreditation model, validity period, appeals process, and treatment of product updates are not defined. Suggested revision: Define certification governance or describe certification as an optional national mechanism. At minimum, require transparent test evidence, scope, version, issuer, date, limitations, and retesting triggers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | ||
| PC-1252✎ edit📣 feedback | received | Core architects agent |
4.3.5 Minimum Conformance and Testing §4.3.5, minimum conformance p.98 l.Lines 400-404 |
Countries may lack the resources to create and operate national test beds. Requiring national adaptation of testing inf…Countries may lack the resources to create and operate national test beds. Requiring national adaptation of testing infrastructure could delay implementation. Suggested revision: Recommend shared regional services, hosted test environments, reusable validators, open test artefacts, and mutual recognition of accredited results. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | ||
| PC-1253✎ edit📣 feedback | received | Core architects agent |
4.3.5 Minimum Conformance and Testing §4.3.5, minimum conformance p.98 l.Lines 404-407 |
Mandatory certification may reduce competition or disproportionately burden smaller local suppliers.Mandatory certification may reduce competition or disproportionately burden smaller local suppliers. Suggested revision: Make tools and profiles freely accessible where possible, use proportionate fees, provide early supplier testing, recognise equivalent evidence, and focus certification on high-risk or high-impact capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-086 discuss | in the document all mentions on GitHub record | ||
| PC-1254✎ edit📣 feedback | received | Core architects agent |
4.3.5 Minimum Conformance and Testing §4.3.5, minimum conformance p.98 l.Lines 398-407 |
The subsection focuses on interoperability conformance and does not integrate privacy, security, resilience, accessibil…The subsection focuses on interoperability conformance and does not integrate privacy, security, resilience, accessibility, performance, data quality, or clinical-safety acceptance. Suggested revision: Add a multidomain minimum-conformance framework and cross-reference the broader testing taxonomy proposed for Section 3.7. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1255✎ edit📣 feedback | received | Core architects agent |
4.4 Measuring Progress and Impact §4.4 p.98-99 l.Lines 409-424 |
The section relies heavily on Section 3.7’s coverage measure, which counts realised reference elements. This is not suf…The section relies heavily on Section 3.7’s coverage measure, which counts realised reference elements. This is not sufficient to show whether deployed capabilities are operational, conformant, used, or effective. Suggested revision: Distinguish model coverage, deployed coverage, conformant coverage, operational coverage, effective-use coverage, and population or geographic reach. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | ||
| PC-1256✎ edit📣 feedback | received | Core architects agent |
4.4 Measuring Progress and Impact §4.4 p.98-99 l.Lines 418-424 anchor: medium |
Gaps identified through model mapping are to feed the roadmap, but no prioritisation method is provided.Gaps identified through model mapping are to feed the roadmap, but no prioritisation method is provided. Suggested revision: Prioritise gaps using health impact, dependency centrality, risk, equity, regulatory obligation, cost, existing maturity, implementation readiness, and expected reuse. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1257✎ edit📣 feedback | received | Core architects agent |
4.4.1 Assessing impact: Are goals being achieved? §4.4.1 p.99 l.Lines 427-434 |
Baseline measurement is correctly emphasised, but attribution of outcome changes “with confidence” may not be possible …Baseline measurement is correctly emphasised, but attribution of outcome changes “with confidence” may not be possible without an appropriate evaluation design and comparison. Suggested revision: Replace attribution language with contribution-oriented wording and recommend evaluation methods proportionate to the intervention, including comparison groups where feasible, interrupted time series, mixed methods, or contribution analysis. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-104 discuss | in the document all mentions on GitHub record | ||
| PC-1258✎ edit📣 feedback | received | Core architects agent, medium |
4.4.1 Assessing impact: Are goals being achieved? §4.4.1 p.99 l.Lines 431-434 |
Baseline data may be unavailable, poor quality, incomplete, or already influenced by earlier digital investments.Baseline data may be unavailable, poor quality, incomplete, or already influenced by earlier digital investments. Suggested revision: Require documentation of baseline limitations, data-quality assessment, retrospective reconstruction where feasible, and proxy indicators where direct measurement is unavailable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-104 discuss | in the document all mentions on GitHub record | ||
| PC-1259✎ edit📣 feedback | received | Core architects agent |
4.4.1 Assessing impact: Are goals being achieved? §4.4.1 p.99 l.Lines 435-438 |
Process evaluation is appropriately included but remains very general.Process evaluation is appropriately included but remains very general. Suggested revision: Define minimum process-evaluation dimensions: fidelity, adoption, reach, usability, workflow effects, burden, workarounds, unintended consequences, equity, cost, and implementation context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-104 discuss | in the document all mentions on GitHub record | ||
| PC-1260✎ edit📣 feedback | received | Core architects agent, medium |
4.4.1 Assessing impact: Are goals being achieved? §4.4.1 p.99 l.Lines 439-442 |
The text suggests that results can be compared and aggregated internationally because the architecture provides a canon…The text suggests that results can be compared and aggregated internationally because the architecture provides a canonical decomposition. Common architecture elements do not automatically make outcome measures comparable. Suggested revision: Require harmonised indicator definitions, denominators, data-quality rules, context metadata, coding, collection methods, and interpretation guidance before cross-country comparison. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-104 discuss | in the document all mentions on GitHub record | ||
| PC-1261✎ edit📣 feedback | received | Core architects agent, medium |
4.4.2 Tracking progress over time §4.4.2 p.99 l.Lines 445-459 |
The four progress dimensions are useful but omit security and resilience, actual adoption, service performance, semanti…The four progress dimensions are useful but omit security and resilience, actual adoption, service performance, semantic maturity, workforce capacity, and financial sustainability. Suggested revision: Expand the framework or add subdimensions covering these areas. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | ||
| PC-1262✎ edit📣 feedback | received | Core architects agent |
4.4.2 Tracking progress over time §4.4.2 p.99 l.Lines 447-449 |
Component coverage is described by functionality, geography, and population, but not by dependency integrity, authorita…Component coverage is described by functionality, geography, and population, but not by dependency integrity, authoritative governance, conformance, or reuse across programmes. Suggested revision: Add governance status, reuse, data quality, service performance, interoperability, resilience, and sustainable operation to REDDHI progress measures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-032 discuss | in the document all mentions on GitHub record | ||
| PC-1263✎ edit📣 feedback | received | Core architects agent |
4.4.2 Tracking progress over time §4.4.2 p.99 l.Lines 450-452 |
Standards conformance combines APIs, standards, terminology, and data models in one dimension. A system may meet one ar…Standards conformance combines APIs, standards, terminology, and data models in one dimension. A system may meet one area and fail another. Suggested revision: Report structural, semantic, behavioural, security, and interface conformance separately, with mandatory failures visible. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-080 discuss | in the document all mentions on GitHub record | ||
| PC-1264✎ edit📣 feedback | received | Core architects agent |
4.4.2 Tracking progress over time §4.4.2 p.99 l.Lines 453-455 |
Governance maturity is described broadly but not tied to the maturity-assessment dimensions requested in Section 3.4.7.Governance maturity is described broadly but not tied to the maturity-assessment dimensions requested in Section 3.4.7. Suggested revision: Define one consistent governance-maturity framework and use it in baseline assessment, roadmapping, annual measurement, and REDDHI monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-054 discuss | in the document all mentions on GitHub record | ||
| PC-1265✎ edit📣 feedback | received | Core architects agent, medium |
4.4.2 Tracking progress over time §4.4.2 p.99 l.Lines 456-459 |
Outcome linkage includes health outcomes, administrative burden, and resource allocation but does not include patient e…Outcome linkage includes health outcomes, administrative burden, and resource allocation but does not include patient experience, workforce experience, equity, trust, safety, or environmental sustainability. Suggested revision: Expand outcome monitoring and require disaggregation by relevant population, region, provider type, and digital-access characteristics. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-105 discuss | in the document all mentions on GitHub record | ||
| PC-1266✎ edit📣 feedback | received | Core architects agent |
4.4.2 Tracking progress over time §4.4.2 p.100 l.Lines 460-462 |
Annual or biannual assessment may be too infrequent for security, service performance, data quality, or implementation …Annual or biannual assessment may be too infrequent for security, service performance, data quality, or implementation risks and too frequent for some long-term health outcomes. Suggested revision: Define monitoring frequency by indicator type: continuous or monthly operational monitoring, quarterly implementation review, annual maturity assessment, and longer-term outcome evaluation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-104 discuss | in the document all mentions on GitHub record | ||
| PC-1267✎ edit📣 feedback | received | Core architects agent |
4.5 Roles, Skills, and Capacity §4.5 p.100 l.Lines 465-467 |
The section correctly states that architecture depends on people and institutions but does not distinguish permanent na…The section correctly states that architecture depends on people and institutions but does not distinguish permanent national capabilities from temporary project roles or external support. Suggested revision: Classify responsibilities as sovereign or accountable national functions, operational functions, specialist capabilities, and temporarily sourced support. Define which must remain institutionally owned. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-107 discuss | in the document all mentions on GitHub record | ||
| PC-1268✎ edit📣 feedback | received | Core architects agent, medium |
4.5.1 How to Use This Architecture §4.5.1 p.100 l.Lines 469-487 |
The audience descriptions repeat earlier guidance but do not provide concrete tasks or outputs for each actor.The audience descriptions repeat earlier guidance but do not provide concrete tasks or outputs for each actor. Suggested revision: Convert the list into an action matrix showing what each actor should decide, produce, review, approve, operate, or fund. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-108 discuss | in the document all mentions on GitHub record | ||
| PC-1269✎ edit📣 feedback | received | Editorial agent |
4.5.1 How to Use This Architecture §4.5.1 p.100 l.Lines 475-477 |
The text says architects can adopt, adapt, or map the architecture “as described in section 4.4,” although the detailed…The text says architects can adopt, adapt, or map the architecture “as described in section 4.4,” although the detailed approach is described primarily in Section 3.7.5. Suggested revision: Correct the cross-reference and check all related references throughout Chapter 4. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-081 discuss | in the document all mentions on GitHub record | ||
| PC-1270✎ edit📣 feedback | received | Core architects agent |
4.5.1 How to Use This Architecture §4.5.1 p.100 l.Lines 478-480 |
Implementers and suppliers are directed to data models, actors, profiles, and conformance criteria, but the document do…Implementers and suppliers are directed to data models, actors, profiles, and conformance criteria, but the document does not yet provide a fully published national implementation package. Suggested revision: State that these artefacts must be developed or adopted nationally before they can function as enforceable procurement specifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-260 discuss | in the document all mentions on GitHub record | ||
| PC-1271✎ edit📣 feedback | received | Core architects agent |
4.5.1 How to Use This Architecture §4.5.1 p.100 l.Lines 481-483 |
Development partners are asked to align with national priorities but are not given a mechanism for demonstrating or rep…Development partners are asked to align with national priorities but are not given a mechanism for demonstrating or reporting alignment. Suggested revision: Require partner investments to map to roadmap components and capabilities, identify shared-infrastructure contributions, document exceptions, and report sustainability and conformance commitments. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-113 discuss | in the document all mentions on GitHub record | ||
| PC-1272✎ edit📣 feedback | received | Core architects agent, medium |
4.5.1 How to Use This Architecture §4.5.1 p.100 l.Lines 488-491 |
The section says using the architecture is more about discipline than adopting every element. This is a strong summary …The section says using the architecture is more about discipline than adopting every element. This is a strong summary but should also refer to outcomes, accountability, and adaptability, not only vocabulary and standards. Suggested revision: Add explicit traceability to public value, accountable governance, evidence-based adaptation, and transparent deviation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-108 discuss | in the document all mentions on GitHub record | ||
| PC-1273✎ edit📣 feedback | received | Core architects agent |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 p.100-101 l.Lines 493-519 |
The role list is strong but omits service-management, product-management, procurement, commercial, legal, health-econom…The role list is strong but omits service-management, product-management, procurement, commercial, legal, health-economics, evaluation, accessibility, user-experience, clinical-safety, and cybersecurity-operations capabilities. Suggested revision: Add these capabilities or explain where they sit within broader roles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | ||
| PC-1274✎ edit📣 feedback | received | Core architects agent, medium |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 p.100-101 l.Lines 499-500 |
“Enterprise and solution architects” are grouped together even though their scope, accountability, and deliverables dif…“Enterprise and solution architects” are grouped together even though their scope, accountability, and deliverables differ. Suggested revision: Distinguish enterprise, domain, data, security, integration, and solution architecture responsibilities while allowing roles to be combined in smaller settings. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | ||
| PC-1275✎ edit📣 feedback | received | Core architects agent, low |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 p.101 l.Lines 501-503 |
“Information and FHIR modellers” centres one exchange standard and may underrepresent openEHR, imaging, supply-chain, s…“Information and FHIR modellers” centres one exchange standard and may underrepresent openEHR, imaging, supply-chain, statistical, and legacy standards. Suggested revision: Use “clinical and health-information modellers,” with FHIR profiling identified as one important specialism. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | ||
| PC-1276✎ edit📣 feedback | received | Metadata registries agent |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 p.101 l.Lines 504-506 |
Terminology specialists are said to operate semantic-governance processes. Semantic governance also requires clinicians…Terminology specialists are said to operate semantic-governance processes. Semantic governance also requires clinicians, data architects, modellers, analysts, programme experts, and decision authorities. Suggested revision: Describe semantic governance as multidisciplinary and distinguish terminology expertise from the wider governance function. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | ||
| PC-1277✎ edit📣 feedback | received | Core architects Clinical agent, medium |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 p.101 l.Lines 509-510 |
Security and privacy architects are included, but clinical safety, patient safety, and responsible AI assurance are not…Security and privacy architects are included, but clinical safety, patient safety, and responsible AI assurance are not assigned explicitly. Suggested revision: Add clinical-safety and digital-health assurance responsibilities, with multidisciplinary review for high-risk components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | ||
| PC-1278✎ edit📣 feedback | received | Core architects agent |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 p.101 l.Lines 511-512 |
Integration engineers are assigned data migration, but large-scale migration also requires data owners, clinical valida…Integration engineers are assigned data migration, but large-scale migration also requires data owners, clinical validation, privacy, archival, reconciliation, and operational acceptance. Suggested revision: Describe migration as a governed multidisciplinary workstream rather than an engineering task alone. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | ||
| PC-1279✎ edit📣 feedback | received | Core architects agent, medium |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §4.5.2 p.101 l.Lines 520-524 |
The text says not every role needs a dedicated post, which is pragmatic, but does not define the minimum capacity or wo…The text says not every role needs a dedicated post, which is pragmatic, but does not define the minimum capacity or workload needed for national implementation. Suggested revision: Provide indicative capability-team patterns for early, intermediate, and mature settings, including options for pooled or regional specialist capacity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-107 discuss | in the document all mentions on GitHub record | ||
| PC-1280✎ edit📣 feedback | received | Core architects agent, medium |
4.5.3 Building and Sustaining National Capacity §4.5.3 p.101 l.Lines 526-532 |
The NHS Digital Academy is cited as an example of national capacity building, but it represents a high-income setting w…The NHS Digital Academy is cited as an example of national capacity building, but it represents a high-income setting with substantial institutional resources. Suggested revision: Add examples from low- and middle-income settings, regional academies, university partnerships, standards communities, and train-the-trainer models. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-107 discuss | in the document all mentions on GitHub record | ||
| PC-1281✎ edit📣 feedback | received | Core architects agent |
4.5.3 Building and Sustaining National Capacity §4.5.3 p.101 l.Lines 526-532 |
Bringing capacity in-house is presented as the preferred trajectory. Some specialist capabilities may be more sustainab…Bringing capacity in-house is presented as the preferred trajectory. Some specialist capabilities may be more sustainably pooled regionally or maintained through long-term partnerships. Suggested revision: Define which capabilities require internal institutional ownership and which may be accessed through accountable external or regional arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-107 discuss | in the document all mentions on GitHub record | ||
| PC-1282✎ edit📣 feedback | received | Core architects agent |
4.5.3 Building and Sustaining National Capacity §4.5.3 p.101-102 l.Lines 534-538 |
Change management is acknowledged but treated briefly relative to its importance. The section does not address workflow…Change management is acknowledged but treated briefly relative to its importance. The section does not address workflow redesign, incentives, implementation support, adoption measurement, local champions, or resistance. Suggested revision: Add a structured change-management approach covering stakeholder analysis, co-design, workflow redesign, communications, training, support, incentives, feedback, adoption measurement, and continuous improvement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-109 discuss | in the document all mentions on GitHub record | ||
| PC-1283✎ edit📣 feedback | received | Core architects agent, medium |
4.5.3 Building and Sustaining National Capacity §4.5.3 p.101-102 l.Lines 534-538 |
Training and communication may not be sufficient where digital transformation increases workload, shifts power, or crea…Training and communication may not be sufficient where digital transformation increases workload, shifts power, or creates unfunded responsibilities for frontline staff. Suggested revision: Require workload and distributional-impact assessment, protected training time, implementation support, appropriate staffing, and mechanisms for addressing burdens transferred to facilities or health workers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-109 discuss | in the document all mentions on GitHub record | ||
| PC-1284✎ edit📣 feedback | received | Core architects agent |
4.6 Financing and Partnerships §4.6 p.102 l.Lines 542-545 |
The section correctly frames DPI-H as an enduring capability rather than a completed project. However, it does not expl…The section correctly frames DPI-H as an enduring capability rather than a completed project. However, it does not explicitly distinguish capital, recurrent, transition, refresh, and contingency costs. Suggested revision: Introduce a lifecycle-cost framework covering design, implementation, migration, operations, governance, support, licences, connectivity, security, training, testing, refresh, replacement, and decommissioning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | ||
| PC-1285✎ edit📣 feedback | received | Core architects Financial systems agent, low |
4.6.1 The Investment Case §4.6.1 p.102 l.Lines 547-553 |
The distinction between financing DPI-H and using DPI-H to improve health financing is valuable but may be difficult fo…The distinction between financing DPI-H and using DPI-H to improve health financing is valuable but may be difficult for non-specialist readers. Suggested revision: Add a short comparison table showing the purpose, costs, benefits, stakeholders, and indicators associated with each concept. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-037 discuss | in the document all mentions on GitHub record | ||
| PC-1286✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
4.6.1 The Investment Case §4.6.1 p.102 l.Lines 555-563 |
The Ministry of Finance value case focuses on budget execution, leakage, provider payment, and administrative efficienc…The Ministry of Finance value case focuses on budget execution, leakage, provider payment, and administrative efficiency. It gives less attention to care quality, equity, resilience, workforce productivity, public trust, and the cost of failing infrastructure. Suggested revision: Expand the value case and distinguish monetisable savings, avoided costs, service improvements, equity benefits, resilience, and wider public value. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-116 discuss | in the document all mentions on GitHub record | ||
| PC-1287✎ edit📣 feedback | received | Core architects agent |
4.6.1 The Investment Case §4.6.1 p.102 l.Lines 555-563 |
The claimed efficiency and fraud-reduction benefits are plausible but are not linked to evidence or quantified examples…The claimed efficiency and fraud-reduction benefits are plausible but are not linked to evidence or quantified examples in this section. Suggested revision: Add documented examples with context, baseline, implementation cost, measured outcomes, and limitations. Avoid assuming that digital infrastructure automatically produces savings. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-116 discuss | in the document all mentions on GitHub record | ||
| PC-1288✎ edit📣 feedback | received | Core architects agent |
4.6.1 The Investment Case §4.6.1 p.102 l.Lines 558-562 |
DPI-H is framed as capital investment, but many of its largest costs are recurrent, including staff, hosting, support, …DPI-H is framed as capital investment, but many of its largest costs are recurrent, including staff, hosting, support, governance, cybersecurity, terminology, testing, and change management. Suggested revision: Present DPI-H as infrastructure requiring both capital investment and protected recurrent operating expenditure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | ||
| PC-1289✎ edit📣 feedback | received | Core architects agent |
4.6.1 The Investment Case §4.6.1 p.102 l.Lines 560-563 |
Multi-year recurrent budget lines may be difficult in countries with annual appropriations, fiscal instability, or high…Multi-year recurrent budget lines may be difficult in countries with annual appropriations, fiscal instability, or high donor dependence. Suggested revision: Provide alternative arrangements such as medium-term expenditure frameworks, pooled funds, framework agreements, phased commitments, contingency reserves, and blended financing with transition conditions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | ||
| PC-1290✎ edit📣 feedback | received | Core architects agent |
4.6.2 Sustainability by Design §4.6.2 p.102 l.Lines 566-573 |
The five sustainability dimensions are relevant but omit workforce capability, supplier and market sustainability, envi…The five sustainability dimensions are relevant but omit workforce capability, supplier and market sustainability, environmental sustainability, security resilience, and adoption. Suggested revision: Add these dimensions or show how they are incorporated into the existing categories. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-111 discuss | in the document all mentions on GitHub record | ||
| PC-1291✎ edit📣 feedback | received | Core architects agent |
4.6.2 Sustainability by Design §4.6.2 p.102-103 l.Lines 566-576 |
The dimensions are presented as a list without a method for assessing sustainability or resolving trade-offs.The dimensions are presented as a list without a method for assessing sustainability or resolving trade-offs. Suggested revision: Provide a sustainability-assessment checklist with evidence, risks, responsible owners, target maturity, and mitigation actions for each dimension. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-111 discuss | in the document all mentions on GitHub record | ||
| PC-1292✎ edit📣 feedback | received | Core architects agent |
4.6.2 Sustainability by Design §4.6.2 p.103 l.Lines 574-576 |
Legal authority is correctly identified as essential, but the section does not address conflicting laws, regulatory gap…Legal authority is correctly identified as essential, but the section does not address conflicting laws, regulatory gaps, cross-border obligations, procurement restrictions, or the time required for legal reform. Suggested revision: Require early legal-gap analysis, transitional legal controls, regulatory coordination, and a roadmap for required legislation or regulation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-049 discuss | in the document all mentions on GitHub record | ||
| PC-1293✎ edit📣 feedback | received | Core architects agent |
4.6.3 Approaches to Financing §4.6.3 p.103 l.Lines 578-594 |
The financing options are useful but do not differentiate which costs or components are suitable for each mechanism.The financing options are useful but do not differentiate which costs or components are suitable for each mechanism. Suggested revision: Map financing instruments to capital investment, recurrent services, shared regional infrastructure, capacity development, innovation, emergency needs, and transition costs. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-115 discuss | in the document all mentions on GitHub record | ||
| PC-1294✎ edit📣 feedback | received | Core architects agent |
4.6.3 Approaches to Financing §4.6.3 p.103 l.Lines 579-583 |
Blended financing requires an explicit transition plan, but the document does not state what happens if domestic financ…Blended financing requires an explicit transition plan, but the document does not state what happens if domestic financing cannot increase as expected. Suggested revision: Require fiscal-risk scenarios, minimum service commitments, scope prioritisation, contingency financing, and an orderly reduction plan that protects essential services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | ||
| PC-1295✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
4.6.3 Approaches to Financing §4.6.3 p.103 l.Lines 584-585 |
Health-coverage schemes may contribute to shared services they use, but this could privilege insured populations or shi…Health-coverage schemes may contribute to shared services they use, but this could privilege insured populations or shift costs away from government responsibilities. Suggested revision: Require contributions to support shared national access without creating exclusive control or unequal service quality for uninsured populations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-114 discuss | in the document all mentions on GitHub record | ||
| PC-1296✎ edit📣 feedback | received | Core architects agent |
4.6.3 Approaches to Financing §4.6.3 p.103 l.Lines 586-588 |
Efficiency dividends are proposed as a financing source, but savings may be uncertain, accrue to another institution, o…Efficiency dividends are proposed as a financing source, but savings may be uncertain, accrue to another institution, or be absorbed into general budgets. Suggested revision: Require conservative benefit estimates, agreed benefit ownership, tracking, verification, and an approved mechanism for reinvestment before relying on savings to fund operations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-115 discuss | in the document all mentions on GitHub record | ||
| PC-1297✎ edit📣 feedback | received | Core architects agent |
4.6.3 Approaches to Financing §4.6.3 p.103 l.Lines 589-590 |
Private-sector arrangements are described mainly as hosting or application development. Other models, such as managed s…Private-sector arrangements are described mainly as hosting or application development. Other models, such as managed services or public-private partnerships, introduce risks related to lock-in, control, commercial incentives, continuity, and transparency. Suggested revision: Add safeguards covering competition, data and configuration portability, audit rights, service continuity, pricing transparency, security, supplier failure, subcontractors, and termination assistance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-117 discuss | in the document all mentions on GitHub record | ||
| PC-1298✎ edit📣 feedback | received | Core architects agent |
4.6.3 Approaches to Financing §4.6.3 p.103 l.Lines 589-590 |
Government ownership of “core registries and the data they hold” is presented as the relevant safeguard. Legal ownershi…Government ownership of “core registries and the data they hold” is presented as the relevant safeguard. Legal ownership may not be the only or best concept for personal data, and registries may be operated through federated arrangements. Suggested revision: Use the concepts of public accountability, stewardship, control, lawful processing, access, portability, and continuity rather than relying only on ownership. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-038 discuss | in the document all mentions on GitHub record | ||
| PC-1299✎ edit📣 feedback | received | Core architects agent |
4.6.3 Approaches to Financing §4.6.3 p.103 l.Lines 591-593 |
Pooling programme investment is encouraged but no mechanism is described for allocating governance rights, costs, benef…Pooling programme investment is encouraged but no mechanism is described for allocating governance rights, costs, benefits, and service priorities among contributing programmes. Suggested revision: Add pooled-funding governance covering contribution formulas, decision rights, service entitlements, cost transparency, dispute resolution, and protection of national priorities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-112 discuss | in the document all mentions on GitHub record | ||
| PC-1300✎ edit📣 feedback | received | Core architects agent |
4.6.3 Approaches to Financing §4.6.3 p.103 l.Lines 595-599 |
The value case relies on coverage, conformance, governance maturity, and outcome linkage but omits service performance,…The value case relies on coverage, conformance, governance maturity, and outcome linkage but omits service performance, user adoption, data quality, security, and cost efficiency. Suggested revision: Add a balanced investment scorecard covering public value, cost, reach, use, quality, conformance, resilience, security, governance, equity, and outcome contribution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-111 discuss | in the document all mentions on GitHub record | ||
| PC-1301✎ edit📣 feedback | received | Core architects agent, medium |
4.6.4 Partnerships §4.6.4 p.103 l.Lines 601-609 |
Partnerships across government and external organisations are appropriately emphasised, but the section does not distin…Partnerships across government and external organisations are appropriately emphasised, but the section does not distinguish strategic authority, implementation support, supplier roles, standards participation, and funding relationships. Suggested revision: Define partnership types and minimum agreements covering responsibilities, decision rights, funding, intellectual property, data access, sustainability, conformance, transparency, and exit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-113 discuss | in the document all mentions on GitHub record | ||
| PC-1302✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
4.6.4 Partnerships §4.6.4 p.103 l.Lines 601-604 |
Public financial management, identity, payments, and interoperability governance sit outside health, but the section do…Public financial management, identity, payments, and interoperability governance sit outside health, but the section does not explain how conflicting priorities or service-level expectations are resolved across ministries. Suggested revision: Establish joint governance, shared roadmaps, documented dependencies, service agreements, escalation, and cross-sector architecture review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-074 discuss | in the document all mentions on GitHub record | ||
| PC-1303✎ edit📣 feedback | received | Core architects agent |
4.6.4 Partnerships §4.6.4 p.103 l.Lines 605-609 |
Development partners are assigned responsibility for alignment, but national institutions also need the capacity and au…Development partners are assigned responsibility for alignment, but national institutions also need the capacity and authority to enforce alignment. Suggested revision: Require a national partner-coordination mechanism, architecture review, investment registration, shared reporting, exception approval, and consequences for non-aligned investments. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-113 discuss | in the document all mentions on GitHub record | ||
| PC-1304✎ edit📣 feedback | received | Core architects agent, medium |
4.6.4 Partnerships §4.6.4 p.103 l.Lines 605-609 |
Development partners may operate through global procurement, standard programmes, or contractual arrangements that cann…Development partners may operate through global procurement, standard programmes, or contractual arrangements that cannot be altered easily at country level. Suggested revision: Encourage alignment at both country and global partner levels, with common architecture clauses, reusable standards profiles, pooled procurement, and transparent management of unavoidable exceptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-113 discuss | in the document all mentions on GitHub record | ||
| PC-1305✎ edit📣 feedback | received | Core architects agent |
4.6.4 Partnerships §4.6.4 p.103 l.Lines 607-609 |
The national digital architect is again positioned as the main mechanism for coordinating partnerships. Partnership coo…The national digital architect is again positioned as the main mechanism for coordinating partnerships. Partnership coordination requires political, financial, legal, and programme authority beyond the architecture function. Suggested revision: Assign coordination to the strategic governance body, supported by the architecture function, finance, procurement, legal, and programme leadership. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-113 discuss | in the document all mentions on GitHub record | ||
| PC-1306✎ edit📣 feedback | received | Core architects agent |
4.3 Profiles and Specifications for Implementation §4.3-4.6 overall p.94-103 l.Sections 4.3-4.6 anchor: medium |
The implementation chapter gives limited attention to operational service management after deployment, including suppor…The implementation chapter gives limited attention to operational service management after deployment, including support desks, monitoring, capacity, problem management, maintenance windows, supplier escalation, and continuity exercises. Suggested revision: Add an operational-readiness section defining the minimum service-management capabilities required before national shared components enter production. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | ||
| PC-1307✎ edit📣 feedback | received | Core architects agent |
4.3 Profiles and Specifications for Implementation §4.3-4.6 overall p.94-103 l.Sections 4.3-4.6 anchor: medium |
Cybersecurity appears mainly through architecture principles and specialist roles but is not integrated into implementa…Cybersecurity appears mainly through architecture principles and specialist roles but is not integrated into implementation phases, financing, procurement, measurement, and operational readiness. Suggested revision: Integrate security-by-design activities, threat modelling, assurance, incident response, vulnerability management, recovery testing, and security financing throughout Chapter 4. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-1308✎ edit📣 feedback | received | Core architects agent |
4.3 Profiles and Specifications for Implementation §4.3-4.6 overall p.94-103 l.Sections 4.3-4.6 anchor: medium |
Accessibility, offline operation, language, digital literacy, assisted access, and non-digital alternatives are not con…Accessibility, offline operation, language, digital literacy, assisted access, and non-digital alternatives are not consistently carried from the design principles into the implementation, measurement, skills, and financing guidance. Suggested revision: Add an inclusion and accessibility workstream across assessment, profiling, procurement, testing, rollout, measurement, capacity, and financing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | ||
| PC-1309✎ edit📣 feedback | received | Core architects agent |
4.3 Profiles and Specifications for Implementation §4.3-4.6 overall p.94-103 l.Sections 4.3-4.6 anchor: medium |
The chapter does not provide a consolidated implementation deliverables matrix showing what countries should have at ea…The chapter does not provide a consolidated implementation deliverables matrix showing what countries should have at each stage. Suggested revision: Add a matrix covering baseline assessment, target architecture, governance, national profiles, implementation guides, test assets, transition plans, investment case, operating model, capacity plan, procurement package, and progress measures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-098 discuss | in the document all mentions on GitHub record | ||
| PC-1310✎ edit📣 feedback | received | Core architects agent, medium |
Future proofing the Architecture §Chapter 5 introduction p.104 l.Lines 2-9 anchor: low |
The chapter opens with a broad list of AI and emerging technologies, but the chapter itself focuses predominantly on AI…The chapter opens with a broad list of AI and emerging technologies, but the chapter itself focuses predominantly on AI. This creates a mismatch between the stated scope and the substantive coverage. Suggested revision: Either rename the chapter Future-proofing the Architecture for AI and Emerging Technologies and clarify the emphasis on AI, or add substantive treatment of the other technologies introduced, including their architectural dependencies and risks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1311✎ edit📣 feedback | received | Core architects agent, medium |
Future proofing the Architecture §Chapter 5 introduction p.104 l.Lines 2-9 anchor: low |
The opening list combines technologies with different architectural roles, including AI models, agents, remote monitori…The opening list combines technologies with different architectural roles, including AI models, agents, remote monitoring, wearables, genomics, edge computing, and verifiable credentials. Readers may not understand why these are grouped together. Suggested revision: Categorise them as analytical technologies, data-generating technologies, computing and deployment technologies, and trust or credential technologies. Explain the different implications of each category for DPI-H. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1312✎ edit📣 feedback | received | Core architects agent, medium |
Future proofing the Architecture §Chapter 5 introduction p.104 l.Lines 3-6 anchor: low |
The chapter states that machine learning is being applied across diagnosis, risk prediction, imaging, outbreak forecast…The chapter states that machine learning is being applied across diagnosis, risk prediction, imaging, outbreak forecasting, planning, and resource allocation. These claims are plausible but are not linked here to evidence of effectiveness, adoption, or limitations. Suggested revision: Add representative evidence or qualify the examples as areas of experimentation and adoption with varying levels of maturity and demonstrated effectiveness. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1313✎ edit📣 feedback | received | Editorial agent, medium |
Future proofing the Architecture §Chapter 5 introduction p.104 l.Lines 5-6 anchor: low |
The statement that large language and multimodal models are changing how clinical knowledge is summarised, retrieved, a…The statement that large language and multimodal models are changing how clinical knowledge is summarised, retrieved, and acted upon may imply established benefit without acknowledging variable reliability and adoption. Suggested revision: Replace with measured wording such as: “Large language and multimodal models are increasingly being explored for summarising, retrieving, and supporting the interpretation of clinical knowledge, although their reliability and appropriate use remain under evaluation.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1314✎ edit📣 feedback | received | Core architects agent |
Future proofing the Architecture §Chapter 5 introduction p.104 l.Lines 10-16 anchor: low |
The decision not to catalogue technologies is sensible, but the chapter does not define a reusable assessment method th…The decision not to catalogue technologies is sensible, but the chapter does not define a reusable assessment method that countries can apply to technologies not discussed explicitly. Suggested revision: Introduce a technology-assessment framework covering health need, evidence, data dependencies, interoperability, safety, equity, legal basis, human oversight, operational capacity, cost, environmental impact, supplier dependency, and exit options. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-129 discuss | in the document all mentions on GitHub record | ||
| PC-1315✎ edit📣 feedback | received | Core architects agent, medium |
Future proofing the Architecture §Chapter 5 introduction p.104 l.Lines 13-16 anchor: low |
The section notes that ministries need to know what to adopt and on what foundations, but it does not provide an adopti…The section notes that ministries need to know what to adopt and on what foundations, but it does not provide an adoption decision process or stage gates. Suggested revision: Add a staged process: define the problem; assess non-AI alternatives; establish evidence and data readiness; conduct risk and impact assessments; test in a controlled setting; evaluate; authorise limited deployment; monitor; and scale, modify, or retire. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-129 discuss | in the document all mentions on GitHub record | ||
| PC-1316✎ edit📣 feedback | received | Core architects agent, medium |
Future proofing the Architecture §Chapter 5 introduction p.104 l.Lines 17-24 anchor: low |
AI is said to span rule-based systems, statistical models, machine learning, and large language models. Some widely use…AI is said to span rule-based systems, statistical models, machine learning, and large language models. Some widely used definitions distinguish rule-based decision systems from AI or apply different legal classifications. Suggested revision: State that the guidance uses an intentionally broad functional definition and that countries should apply the definitions and risk classifications established in their own legal frameworks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-128 discuss | in the document all mentions on GitHub record | ||
| PC-1317✎ edit📣 feedback | received | Core architects agent, medium |
Future proofing the Architecture §Chapter 5 introduction p.104 l.Lines 17-24 anchor: low |
The legal examples focus on jurisdictions with emerging formal AI frameworks. Many countries do not yet have specific A…The legal examples focus on jurisdictions with emerging formal AI frameworks. Many countries do not yet have specific AI legislation and may need to govern AI through existing health, medical-device, data-protection, professional, and administrative law. Suggested revision: Explain how countries can use existing legal and regulatory mechanisms while dedicated AI governance matures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-128 discuss | in the document all mentions on GitHub record | ||
| PC-1318✎ edit📣 feedback | received | Core architects agent |
5.1 Emerging technologies and the foundations they depend on §5.1 p.104-105 l.Lines 26-31 |
The section correctly states that emerging technologies depend on trusted registries, terminology, information models, …The section correctly states that emerging technologies depend on trusted registries, terminology, information models, and interoperability. However, it may imply that countries should delay all AI use until the complete DPI-H foundation is mature. Suggested revision: Clarify that bounded AI use cases may proceed with fit-for-purpose local foundations and controls, while national scale and reuse require progressively stronger shared DPI-H capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | ||
| PC-1319✎ edit📣 feedback | received | Core architects agent |
5.1 Emerging technologies and the foundations they depend on §5.1 p.104-105 l.Lines 27-31 |
The chapter emphasises structured and governed data but does not mention model interoperability, standardised output re…The chapter emphasises structured and governed data but does not mention model interoperability, standardised output representation, model metadata, provenance, or integration of AI-generated results into EHR workflows. Suggested revision: Add requirements for standardised model inputs and outputs, provenance, confidence or uncertainty representation, workflow integration, version identification, and traceability of AI-supported recommendations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1320✎ edit📣 feedback | received | Core architects agent |
5.1 Emerging technologies and the foundations they depend on §5.1 p.105 l.Lines 30-31 |
The statement that weak infrastructure makes AI less likely to perform as intended is correct, but the implications var…The statement that weak infrastructure makes AI less likely to perform as intended is correct, but the implications vary depending on whether the AI uses local, device-generated, imaging, free-text, or national shared data. Suggested revision: Distinguish AI use cases by their data dependency and identify the minimum infrastructure required for each category. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | ||
| PC-1321✎ edit📣 feedback | received | Core architects agent |
5.1 Emerging technologies and the foundations they depend on §5.1 p.105 l.Lines 32-38 |
Consumer-facing technologies are placed outside the architecture when they do not use shared health-system data. They m…Consumer-facing technologies are placed outside the architecture when they do not use shared health-system data. They may still influence care, create health data, trigger referrals, or later connect to DPI-H. Suggested revision: Clarify that such technologies may initially sit outside DPI-H but should become subject to applicable interoperability, safety, privacy, provenance, and data-quality requirements when they contribute information to or influence the health system. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-271 discuss | in the document all mentions on GitHub record | ||
| PC-1322✎ edit📣 feedback | received | Core architects agent, medium |
5.1 Emerging technologies and the foundations they depend on §5.1 p.105 l.Lines 32-38 |
Consumer-facing applications are described as potentially valuable without shared infrastructure, but reliance on perso…Consumer-facing applications are described as potentially valuable without shared infrastructure, but reliance on personal devices and self-entered data can exclude people without connectivity, devices, literacy, or stable digital identity. Suggested revision: Add an equity qualification and require alternative access pathways, accessibility, affordability, language support, and assessment of digital exclusion. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-237 #11 | in the document all mentions on GitHub record | ||
| PC-1323✎ edit📣 feedback | received | Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.105 l.Lines 40-50 |
The section says a model “inherits and amplifies” weaknesses in fragmented or poorly coded data. Models may amplify som…The section says a model “inherits and amplifies” weaknesses in fragmented or poorly coded data. Models may amplify some weaknesses, mask others, or behave unpredictably; amplification is not automatic in every case. Suggested revision: Replace with a sentence like: “A model may reproduce, compound, or obscure weaknesses in the data, potentially at a scale that makes resulting errors difficult to detect and correct.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1324✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.105 l.Lines 42-50 |
The deterioration-risk example effectively illustrates incomplete longitudinal data, but it would benefit from evidence…The deterioration-risk example effectively illustrates incomplete longitudinal data, but it would benefit from evidence or explicit identification as a hypothetical example. Suggested revision: Label it as illustrative or support it with an appropriate real-world study demonstrating performance degradation caused by incomplete cross-provider data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1325✎ edit📣 feedback | received | Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.105 l.Lines 49-50 |
The trusted-data foundation is said to enable reliable, safe, and equitable model training, validation, and deployment.…The trusted-data foundation is said to enable reliable, safe, and equitable model training, validation, and deployment. Strong infrastructure is necessary but does not by itself ensure these outcomes. Suggested revision: Replace “is what allows” with “is an important enabling condition for.” Add representative data, suitable study design, independent evaluation, workflow readiness, governance, and ongoing oversight. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1326✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.105 l.Lines 51-69 |
The list identifies terminology, LIMR, Client Registry, interoperability, and governance as key AI enablers. It omits f…The list identifies terminology, LIMR, Client Registry, interoperability, and governance as key AI enablers. It omits facility and workforce registries, product data, data-quality services, provenance, secure research environments, model registries, and computing infrastructure. Suggested revision: Expand the list or explain that the examples are illustrative. Identify additional infrastructure according to AI use case, including authoritative workforce, facility, product, device, and organisational data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-119 discuss | in the document all mentions on GitHub record | ||
| PC-1327✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.105 l.Lines 53-56 |
The text says governed terminology improves the reliability with which models connect concepts. Terminology can improve…The text says governed terminology improves the reliability with which models connect concepts. Terminology can improve consistency, but model performance still depends on mapping quality, context, data capture, and representation. Suggested revision: Qualify the claim and include governed mappings, implementation context, version consistency, and validation of terminology use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1328✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.105 l.Lines 57-59 |
The LIMR is said to ensure that data is machine-processable rather than locked in free text. Clinical free text remains…The LIMR is said to ensure that data is machine-processable rather than locked in free text. Clinical free text remains valuable, and forcing all relevant information into structured models may produce burden or information loss. Suggested revision: State that the LIMR supports consistent structured data where appropriate, while governed use of documents and narrative text remains necessary. Include provenance and appropriate methods for extracting structured information from narrative content. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1329✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.105 l.Lines 60-61 |
The Client Registry is presented as enabling correct longitudinal linkage for AI. Identity errors and probabilistic mat…The Client Registry is presented as enabling correct longitudinal linkage for AI. Identity errors and probabilistic matching can produce unequal harms, particularly for people with incomplete, changing, or culturally diverse demographic information. Suggested revision: Require evaluation of linkage accuracy, false matches, missed matches, demographic performance differences, human review, correction pathways, and exclusion risks before using linked records for training or inference. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-124 discuss | in the document all mentions on GitHub record | ||
| PC-1330✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.105-106 l.Lines 62-65 |
The chapter refers to interoperability as being realised through “the information mediator and shared terminology,” alt…The chapter refers to interoperability as being realised through “the information mediator and shared terminology,” although Section 3.6 deliberately avoids treating an information mediator as a required single component. Suggested revision: Replace with wording consistent with Section 3.6: “realised through shared specifications, terminology, information models, trust arrangements, and appropriate exchange or mediation mechanisms.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-102 discuss | in the document all mentions on GitHub record | ||
| PC-1331✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.105-106 l.Lines 62-65 |
The text focuses on moving data to where models are developed and recommendations back to care. Central movement of ide…The text focuses on moving data to where models are developed and recommendations back to care. Central movement of identifiable data may not be necessary or appropriate. Suggested revision: Include privacy-preserving options such as federated analysis, secure data environments, distributed inference, local deployment, de-identification, and controlled access to minimum necessary data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-125 discuss | in the document all mentions on GitHub record | ||
| PC-1332✎ edit📣 feedback | received | Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 66-69 |
Governance, consent, and privacy are grouped together as supporting lawful AI use. Consent may not be the applicable le…Governance, consent, and privacy are grouped together as supporting lawful AI use. Consent may not be the applicable legal basis for all care, public-health, research, or administrative AI use. Suggested revision: Refer to lawful basis, purpose limitation, transparency, consent or preference where applicable, access control, oversight, and data-subject rights as distinct governance mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-1333✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 70-83 |
The section suggests that consistent terminology and information models reduce the burden on large models and thereby i…The section suggests that consistent terminology and information models reduce the burden on large models and thereby improve reliability. This is plausible but not sufficient to establish trustworthy performance. Suggested revision: Present this as an architectural advantage that must be empirically validated for each use case rather than a guaranteed improvement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1334✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 75-83 |
Drawing on authoritative registries is described as making outputs traceable to sources. Source traceability depends on…Drawing on authoritative registries is described as making outputs traceable to sources. Source traceability depends on preserved provenance through extraction, transformation, feature creation, model training, retrieval, and inference. Suggested revision: Require end-to-end data lineage and provenance, including source version, transformations, model version, prompt or configuration where relevant, retrieved sources, and output audit information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-247 discuss | in the document all mentions on GitHub record | ||
| PC-1335✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 75-83 |
Traceability is discussed mainly before acting on a model output. The guidance does not cover post-deployment auditabil…Traceability is discussed mainly before acting on a model output. The guidance does not cover post-deployment auditability, incident investigation, correction, model withdrawal, or notification of affected users. Suggested revision: Add requirements for post-market or post-deployment monitoring, incident reporting, corrective action, rollback, model suspension, user notification, and retention of evidence needed for investigation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1336✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 78-81 |
Resource allocation, eligibility, and care decisions are identified as contexts requiring audit. These are also high-im…Resource allocation, eligibility, and care decisions are identified as contexts requiring audit. These are also high-impact decisions that may require stronger restrictions than audit alone. Suggested revision: Require human accountability, contestability, explanation appropriate to the decision, bias assessment, documented decision authority, and prohibition or strict control of fully automated high-impact decisions where required by law or policy. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1337✎ edit📣 feedback | received | Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 84-101 |
The introduction of skills, agents, and MCP is highly technical and may date quickly. It may also distract from the mor…The introduction of skills, agents, and MCP is highly technical and may date quickly. It may also distract from the more durable architectural principle of separating probabilistic inference from deterministic governed services. Suggested revision: Lead with the durable principle and move specific terms such as skills, agents, and Model Context Protocol to an illustrative technology note or versioned online annex. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1338✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 84-101 |
The text recommends model calls to authoritative deterministic services but does not address authentication, authorisat…The text recommends model calls to authoritative deterministic services but does not address authentication, authorisation, transaction integrity, failure handling, service availability, or malicious tool invocation. Suggested revision: Add controls for service discovery, authentication, least-privilege access, input validation, output validation, audit, rate limits, safe failure, human confirmation for high-impact actions, and isolation of untrusted model-generated requests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-120 discuss | in the document all mentions on GitHub record | ||
| PC-1339✎ edit📣 feedback | received | Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 85-89 |
Deterministic services are described as producing the same result for the same input every time. Results may differ whe…Deterministic services are described as producing the same result for the same input every time. Results may differ when reference data, rules, time context, or service versions change. Suggested revision: Qualify the statement: “The same input evaluated against the same governed rule set, reference-data version, configuration, and time context should produce a reproducible result.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | ||
| PC-1340✎ edit📣 feedback | received | Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 91-95 |
“Skills” and “agents” do not have universally stable definitions, and different vendors use these terms differently.“Skills” and “agents” do not have universally stable definitions, and different vendors use these terms differently. Suggested revision: Define them as illustrative implementation concepts rather than normative architecture elements and avoid making the architecture dependent on vendor terminology. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1341✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 94-95 |
MCP is mentioned as an emerging shared-interface convention without explaining its maturity, security implications, gov…MCP is mentioned as an emerging shared-interface convention without explaining its maturity, security implications, governance, or suitability for health settings. Suggested revision: Present MCP only as an example of an emerging interface pattern. State that any adoption requires security review, standardisation assessment, health-sector profiling, access governance, and evidence of operational suitability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1342✎ edit📣 feedback | received | Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 96-101 |
Authoritative services are linked to registries, terminology, and LIMR, but deterministic rules may also depend on comp…Authoritative services are linked to registries, terminology, and LIMR, but deterministic rules may also depend on computable guidelines, benefit rules, policy versions, units, and jurisdictional context. Suggested revision: Include governed rule and guideline repositories, policy provenance, effective dates, jurisdiction, configuration, and terminology versions as dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | ||
| PC-1343✎ edit📣 feedback | received | Core architects agent |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 102-105 |
Machine-readable capability metadata is proposed as a future readiness criterion but no minimum metadata or conformance…Machine-readable capability metadata is proposed as a future readiness criterion but no minimum metadata or conformance method is defined. Suggested revision: Define a future-facing metadata profile covering purpose, interface, actor, inputs, outputs, semantics, security, version, dependencies, evidence, limitations, performance, and responsible authority. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1344✎ edit📣 feedback | received | Core architects agent, medium |
5.2 Why data foundations determine what AI can deliver §5.2 p.106 l.Lines 102-105 |
The phrase “as this practice matures” appropriately signals uncertainty, but machine-readable publication is not limite…The phrase “as this practice matures” appropriately signals uncertainty, but machine-readable publication is not limited to AI readiness and already supports general discoverability, conformance, and automation. Suggested revision: Reframe it as a broader architectural good practice whose AI-related value is one additional benefit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1345✎ edit📣 feedback | received | Core architects agent |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 107-111 |
The section separates operational and analytical AI uses but does not provide a clear risk or maturity classification t…The section separates operational and analytical AI uses but does not provide a clear risk or maturity classification that decision-makers can use to prioritise them. Suggested revision: Classify use cases by purpose, affected person, degree of autonomy, reversibility, evidence maturity, data dependency, consequence of error, and required oversight. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | ||
| PC-1346✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 108-110 |
The statement that credible near-term applications tend to be assistive is useful, but “assistive” is not defined. Syst…The statement that credible near-term applications tend to be assistive is useful, but “assistive” is not defined. Systems can still strongly influence human decisions while formally leaving the final decision to a person. Suggested revision: Define assistive use by the actual role of the system, level of automation, ability of users to understand and override outputs, time available for review, and consequences of disagreement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | ||
| PC-1347✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 112-116 |
Claims adjudication and fraud detection are identified as examples without discussing evidence quality, false positives…Claims adjudication and fraud detection are identified as examples without discussing evidence quality, false positives, appeal, or the impact on providers and beneficiaries. Suggested revision: Add requirements for accuracy, fairness, explainability, human review, appeal, monitoring, and protection against inappropriate denial or delay of legitimate claims. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-121 discuss | in the document all mentions on GitHub record | ||
| PC-1348✎ edit📣 feedback | received | Editorial agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 112-116 |
The statement that current use of large language models in claims adjudication remains limited is time-sensitive and ma…The statement that current use of large language models in claims adjudication remains limited is time-sensitive and may become outdated quickly. Suggested revision: Remove the time-sensitive assertion from the stable guidance or move it to a versioned online evidence annex. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1349✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 117-118 |
Supply-chain forecasting and anomaly detection require reliable historic demand, inventory, product, facility, and logi…Supply-chain forecasting and anomaly detection require reliable historic demand, inventory, product, facility, and logistics data, which may be weak in lower-resource settings. Suggested revision: State the minimum data-quality and coverage requirements and identify simpler statistical or rules-based alternatives where advanced models are not justified. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-121 discuss | in the document all mentions on GitHub record | ||
| PC-1350✎ edit📣 feedback | received | Metadata registries Supply chain agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 117-118 |
Product classification and mapping to reference catalogues can produce uncertain or context-dependent matches. The sect…Product classification and mapping to reference catalogues can produce uncertain or context-dependent matches. The section does not discuss confidence thresholds or human validation. Suggested revision: Require confidence scoring, provenance, review of ambiguous mappings, protection against silent substitution, and governed addition of previously unmapped products. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-121 discuss | in the document all mentions on GitHub record | ||
| PC-1351✎ edit📣 feedback | received | Clinical Core architects agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 119-122 |
Diagnostic support, image interpretation, and risk prediction are high-impact clinical uses. Human oversight alone is n…Diagnostic support, image interpretation, and risk prediction are high-impact clinical uses. Human oversight alone is not sufficient without clinical evaluation, regulatory review, workflow validation, and monitoring. Suggested revision: Add requirements for intended-use definition, clinical evidence, external validation, regulatory classification, safety case, representative evaluation, workflow integration, accountability, and post-deployment monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-121 discuss | in the document all mentions on GitHub record | ||
| PC-1352✎ edit📣 feedback | received | Clinical Core architects agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 119-122 |
Clinical AI functions are correctly positioned outside a single shared component, but the relationship with the Computa…Clinical AI functions are correctly positioned outside a single shared component, but the relationship with the Computable Decision Support Engine remains unclear. Readers may interpret AI models as part of the CDSE by default. Suggested revision: Clarify when an AI model, rule engine, knowledge service, or workflow support tool contributes to the CDSE logical capability and when it remains embedded within a point-of-care application. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | ||
| PC-1353✎ edit📣 feedback | received | Core architects agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 123-128 |
The settlement-pattern example usefully highlights limitations, but it does not cite evidence or discuss privacy, surve…The settlement-pattern example usefully highlights limitations, but it does not cite evidence or discuss privacy, surveillance, outdated imagery, seasonal movement, or informal settlements. Suggested revision: Add evidence and note the need for validation against local data, privacy safeguards, temporal currency, uncertainty, community consultation, and protection against exclusion caused by misclassification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-121 discuss | in the document all mentions on GitHub record | ||
| PC-1354✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 129-132 |
Extracting structured data from scanned documents is presented as enabling reuse, but extracted information may contain…Extracting structured data from scanned documents is presented as enabling reuse, but extracted information may contain transcription errors, missing context, uncertain terminology mappings, or incorrect patient linkage. Suggested revision: Require confidence assessment, source-document retention, provenance, human review according to risk, terminology validation, patient matching, and correction workflows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-121 discuss | in the document all mentions on GitHub record | ||
| PC-1355✎ edit📣 feedback | received | Core architects agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 129-132 |
Document extraction may be highly relevant to paper-heavy settings, but it also depends on image quality, language supp…Document extraction may be highly relevant to paper-heavy settings, but it also depends on image quality, language support, handwriting recognition, and local document formats. Suggested revision: Add contextual evaluation criteria and support local-language validation, representative document testing, and fallback manual processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-121 discuss | in the document all mentions on GitHub record | ||
| PC-1356✎ edit📣 feedback | received | Core architects agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 133-137 |
“Current good practice” is used without specifying the source or scope of the recommendation to start with assistive to…“Current good practice” is used without specifying the source or scope of the recommendation to start with assistive tools. Suggested revision: Reference an authoritative source or use: “A risk-based approach generally favours beginning with assistive use under accountable human oversight, particularly where consequences are significant.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | ||
| PC-1357✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.3 Where artificial intelligence can support the health system §5.3 p.107 l.Lines 133-137 |
Human review is recommended but the guidance does not address automation bias, review workload, alert fatigue, user com…Human review is recommended but the guidance does not address automation bias, review workload, alert fatigue, user competence, or situations where meaningful oversight is impossible. Suggested revision: Require human-factors evaluation, training, workload assessment, usable explanations, override mechanisms, monitoring of reliance, and evidence that oversight is meaningful rather than nominal. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-249 discuss | in the document all mentions on GitHub record | ||
| PC-1358✎ edit📣 feedback | received | Core architects agent |
5.4.1 What AI readiness means §5.4.1 p.107-108 l.Lines 140-146 |
AI readiness is organised into data, legal and policy, and institutional capacity. The framework omits technical infras…AI readiness is organised into data, legal and policy, and institutional capacity. The framework omits technical infrastructure, cybersecurity, procurement capability, clinical evidence, workforce readiness, financing, and change management. Suggested revision: Expand the readiness framework or define these as subdimensions of institutional capacity. Include computing, integration, security, evidence, operations, financing, procurement, and user readiness. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | ||
| PC-1359✎ edit📣 feedback | received | Core architects agent |
5.4.1 What AI readiness means §5.4.1 p.108 l.Lines 142-146 |
Country-level readiness may vary substantially by use case, institution, region, and population. A single country-level…Country-level readiness may vary substantially by use case, institution, region, and population. A single country-level readiness assessment may obscure important differences. Suggested revision: Assess readiness at national, organisational, use-case, data-source, and deployment-setting levels. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | ||
| PC-1360✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.4.1 What AI readiness means §5.4.1 p.108 l.Lines 147-152 |
The prerequisites mention data protection, safeguards, training-data quality, and model drift but omit intended use, cl…The prerequisites mention data protection, safeguards, training-data quality, and model drift but omit intended use, clinical evidence, accountability, incident response, auditability, explainability, cybersecurity, and supplier management. Suggested revision: Add these as explicit readiness and governance requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1361✎ edit📣 feedback | received | Core architects agent, medium |
5.4.1 What AI readiness means §5.4.1 p.108 l.Lines 147-152 |
“Input and output safeguards” is undefined and may refer to content filters, workflow rules, privacy controls, or clini…“Input and output safeguards” is undefined and may refer to content filters, workflow rules, privacy controls, or clinical validation. Suggested revision: Define the concept or replace it with specific safeguards appropriate to health systems, including input validation, prompt or instruction controls, output verification, policy enforcement, and safe handling of uncertainty. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1362✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.4.1 What AI readiness means §5.4.1 p.108 l.Lines 149-150 |
Model drift monitoring is mentioned, but models can also be affected by data drift, concept drift, workflow changes, so…Model drift monitoring is mentioned, but models can also be affected by data drift, concept drift, workflow changes, software updates, terminology changes, and changing clinical practice. Suggested revision: Require monitoring of model, data, concept, workflow, and outcome drift, with predefined thresholds and escalation or retraining procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1363✎ edit📣 feedback | received | Editorial agent |
5.4.1 What AI readiness means §5.4.1 p.108 l.Lines 150-152 |
The footnote numbering and references to WHO guidance and jurisdictional frameworks appear inconsistent, with superscri…The footnote numbering and references to WHO guidance and jurisdictional frameworks appear inconsistent, with superscript numbering not clearly aligned in the extracted text. Suggested revision: Verify and standardise all references, numbering, dates, document titles, and links before publication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-254 discuss | in the document all mentions on GitHub record | ||
| PC-1364✎ edit📣 feedback | received | Core architects agent |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.Lines 154-168 |
The section defines trustworthy AI through effectiveness, safety, transparency, accountability, fairness, and oversight…The section defines trustworthy AI through effectiveness, safety, transparency, accountability, fairness, and oversight. It does not distinguish trustworthiness as an evidenced property from public trust as a social response. Suggested revision: Clarify that trustworthiness must be demonstrated through evidence and governance, while trust should not be demanded from users or treated as a substitute for accountability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | ||
| PC-1365✎ edit📣 feedback | received | Core architects agent, medium |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.Lines 155-164 |
The questions proposed for decision-makers are valuable but do not include comparison with non-AI alternatives, represe…The questions proposed for decision-makers are valuable but do not include comparison with non-AI alternatives, representativeness, subgroup performance, cybersecurity, integration, cost, or the ability to stop using the product. Suggested revision: Expand the procurement and evaluation questions to cover these areas. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | ||
| PC-1366✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.Lines 165-168 |
“Evals” are introduced as a discipline but are not defined in a way that distinguishes technical model evaluation from …“Evals” are introduced as a discipline but are not defined in a way that distinguishes technical model evaluation from clinical validation, safety assurance, usability testing, or real-world monitoring. Suggested revision: Define a layered evaluation framework covering technical performance, clinical or operational validity, human factors, equity, security, workflow impact, prospective testing, and post-deployment monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | ||
| PC-1367✎ edit📣 feedback | received | Editorial agent |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.Lines 165-168 |
“Evals” is technology-sector jargon and may date quickly or be unclear to ministries and procurement teams.“Evals” is technology-sector jargon and may date quickly or be unclear to ministries and procurement teams. Suggested revision: Use “structured evaluation and testing” as the primary term, with “sometimes referred to as evals” in parentheses if necessary. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | ||
| PC-1368✎ edit📣 feedback | received | Core architects agent, medium |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.Lines 165-168 |
Repeated evaluation can be resource-intensive, especially for smaller health systems.Repeated evaluation can be resource-intensive, especially for smaller health systems. Suggested revision: Provide a risk-based approach, reusable evaluation protocols, shared regional evaluation capacity, independent evidence recognition, and prioritisation of high-impact uses. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | ||
| PC-1369✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.4.2 Trustworthy AI in a health setting §5.4.2 p.108 l.Lines 154-168 |
The section does not explicitly address procurement claims, documentation disclosure, access to training and validation…The section does not explicitly address procurement claims, documentation disclosure, access to training and validation information, or supplier responsibility for updates. Suggested revision: Require suppliers to provide intended use, model and data documentation, evaluation evidence, subgroup performance, known limitations, update policy, incident process, audit access, and exit arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-122 discuss | in the document all mentions on GitHub record | ||
| PC-1370✎ edit📣 feedback | received | Core architects agent |
5.4.3 Equity and safety §5.4.3 p.109 l.Lines 170-175 |
The equity discussion focuses primarily on unrepresentative training data. Inequity may also arise from deployment cont…The equity discussion focuses primarily on unrepresentative training data. Inequity may also arise from deployment context, access, workflow, language, disability, connectivity, user behaviour, and differential consequences of error. Suggested revision: Expand equity assessment across the full lifecycle, including problem selection, data, design, access, deployment, oversight, outcomes, redress, and withdrawal. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-124 discuss | in the document all mentions on GitHub record | ||
| PC-1371✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.4.3 Equity and safety §5.4.3 p.109 l.Lines 170-175 |
The section does not specify how fairness or subgroup safety should be measured or what happens when performance differ…The section does not specify how fairness or subgroup safety should be measured or what happens when performance differs across groups. Suggested revision: Require context-appropriate subgroup evaluation, uncertainty analysis, minimum safety thresholds, mitigation, restricted use where necessary, and ongoing disaggregated monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-124 discuss | in the document all mentions on GitHub record | ||
| PC-1372✎ edit📣 feedback | received | Clinical Core architects agent, medium |
5.4.3 Equity and safety §5.4.3 p.109 l.Lines 170-175 |
Safety is included in the heading but the paragraph focuses mostly on equity and data representativeness. Clinical safe…Safety is included in the heading but the paragraph focuses mostly on equity and data representativeness. Clinical safety engineering, hazard analysis, safe failure, and incident management are not discussed. Suggested revision: Add explicit safety requirements covering hazard identification, safety cases, failure modes, human oversight, downtime procedures, adverse-event reporting, and rollback. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1373✎ edit📣 feedback | received | Core architects agent, medium |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.Lines 177-185 |
The section correctly identifies volatile pricing and lock-in but does not include the complete lifecycle cost of data …The section correctly identifies volatile pricing and lock-in but does not include the complete lifecycle cost of data preparation, integration, evaluation, compute, monitoring, human review, retraining, security, and supplier transition. Suggested revision: Require an AI total-cost-of-ownership model covering all lifecycle activities and comparison with non-AI alternatives. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-126 discuss | in the document all mentions on GitHub record | ||
| PC-1374✎ edit📣 feedback | received | Core architects agent |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.Lines 179-182 |
Model substitutability is recommended, but different models may require different prompts, input formats, safety settin…Model substitutability is recommended, but different models may require different prompts, input formats, safety settings, evaluation thresholds, workflows, and infrastructure. Suggested revision: Require logical separation through stable application interfaces where feasible, while documenting model-specific dependencies, revalidation needs, and transition costs. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-127 discuss | in the document all mentions on GitHub record | ||
| PC-1375✎ edit📣 feedback | received | Core architects agent |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.Lines 182-185 |
“Sovereign models” may refer to national hosting, domestic ownership, regional operation, local training, data residenc…“Sovereign models” may refer to national hosting, domestic ownership, regional operation, local training, data residency, or governance. The term is not defined. Suggested revision: Define the intended sovereignty dimensions and avoid implying that domestic hosting alone ensures control, safety, affordability, or independence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-127 discuss | in the document all mentions on GitHub record | ||
| PC-1376✎ edit📣 feedback | received | Core architects agent |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.Lines 182-185 |
Nationally hosted models may be unrealistic or inefficient for many countries because of cost, specialist capacity, ene…Nationally hosted models may be unrealistic or inefficient for many countries because of cost, specialist capacity, energy, maintenance, and scale requirements. Suggested revision: Present national, regional, shared public, regulated commercial, and hybrid options, with a decision framework based on sensitivity, capability, cost, resilience, and strategic control. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-127 discuss | in the document all mentions on GitHub record | ||
| PC-1377✎ edit📣 feedback | received | Core architects agent |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.Lines 186-193 |
The section recognises vendor, donor, and political pressure, which is valuable, but it does not propose governance mec…The section recognises vendor, donor, and political pressure, which is valuable, but it does not propose governance mechanisms for resisting or evaluating such pressure. Suggested revision: Require independent needs assessment, transparent business cases, conflict-of-interest declarations, architecture review, evidence standards, public procurement criteria, and approval through accountable governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-126 discuss | in the document all mentions on GitHub record | ||
| PC-1378✎ edit📣 feedback | received | Core architects agent |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.Lines 189-193 |
“Foundations first” is a strong general principle but may be interpreted as a rigid sequence. Some bounded AI use cases…“Foundations first” is a strong general principle but may be interpreted as a rigid sequence. Some bounded AI use cases can help improve data quality or provide value while broader infrastructure matures. Suggested revision: Use: “foundations proportionate to the use case before scale.” Permit controlled experimentation where risks, dependencies, portability, and learning objectives are explicit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1379✎ edit📣 feedback | received | Core architects agent, medium |
5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.Lines 177-193 |
Environmental cost is not addressed despite discussion of model compute and sustainability.Environmental cost is not addressed despite discussion of model compute and sustainability. Suggested revision: Include energy use, carbon impact, water use where relevant, hardware requirements, data-centre dependencies, and proportionality of model size to the health use case. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-126 discuss | in the document all mentions on GitHub record | ||
| PC-1380✎ edit📣 feedback | received | Core architects agent |
5.5 Keeping the architecture open and adaptable §5.5 p.109-110 l.Lines 195-210 |
The section argues that strong infrastructure supports AI, genomics, remote monitoring, and decentralised identity, but…The section argues that strong infrastructure supports AI, genomics, remote monitoring, and decentralised identity, but only AI received detailed analysis. Suggested revision: Add short architectural considerations for the other named technology areas or explicitly state that they require separate future guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-129 discuss | in the document all mentions on GitHub record | ||
| PC-1381✎ edit📣 feedback | received | Editorial agent, medium |
5.5 Keeping the architecture open and adaptable §5.5 p.109-110 l.Lines 195-203 |
The statement that foundation strength determines whether technology compounds value or adds another silo is directiona…The statement that foundation strength determines whether technology compounds value or adds another silo is directionally correct but too binary. Technologies may deliver local value while remaining only partially integrated. Suggested revision: Use more measured wording that recognises a continuum of integration, reuse, sustainability, and system-wide value. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1382✎ edit📣 feedback | received | Core architects agent |
5.5 Keeping the architecture open and adaptable §5.5 p.109-110 l.Lines 204-210 |
Flexibility at interfaces is emphasised, but future adaptability also depends on data portability, modular procurement,…Flexibility at interfaces is emphasised, but future adaptability also depends on data portability, modular procurement, versioning, abstraction, governance, skills, and sustainable funding. Suggested revision: Expand the future-proofing requirements to include these dimensions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-129 discuss | in the document all mentions on GitHub record | ||
| PC-1383✎ edit📣 feedback | received | Core architects agent |
5.5 Keeping the architecture open and adaptable §5.5 p.109-110 l.Lines 204-210 |
Open interfaces alone do not ensure that future technologies can be connected safely or meaningfully.Open interfaces alone do not ensure that future technologies can be connected safely or meaningfully. Suggested revision: Require governed semantics, identity and trust, provenance, policy enforcement, conformance, observability, and controlled extension mechanisms in addition to interface flexibility. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-129 discuss | in the document all mentions on GitHub record | ||
| PC-1384✎ edit📣 feedback | received | Core architects agent |
5.5 Keeping the architecture open and adaptable §5.5 p.110 l.Lines 208-210 |
Ongoing stewardship and maintenance are recognised but not linked to explicit ownership, recurrent financing, release m…Ongoing stewardship and maintenance are recognised but not linked to explicit ownership, recurrent financing, release management, or architecture review. Suggested revision: Assign responsibility for continuous evolution and include it in the operating model, institutional mandate, budget, and performance measures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-129 discuss | in the document all mentions on GitHub record | ||
| PC-1385✎ edit📣 feedback | received | Core architects agent |
5.5 Keeping the architecture open and adaptable §5.5 p.110 l.Lines 211-217 |
The possibility that AI might eventually become a reusable DPI-H component is raised, but the criteria for making that …The possibility that AI might eventually become a reusable DPI-H component is raised, but the criteria for making that determination are not stated. Suggested revision: Apply the Section 3.5.1 component criteria and add AI-specific considerations such as evidence stability, explainability, model lifecycle, risk, shared utility, governance, vendor dependence, and reproducibility. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | ||
| PC-1386✎ edit📣 feedback | received | Core architects agent |
5.5 Keeping the architecture open and adaptable §5.5 p.110 l.Lines 211-217 |
“Aspects of AI” and “reusable shared components in their own right” are vague. AI might be represented as models, evalu…“Aspects of AI” and “reusable shared components in their own right” are vague. AI might be represented as models, evaluation infrastructure, knowledge services, model registries, secure computing, or shared interfaces. Suggested revision: Identify the possible reusable capabilities without proposing a single national AI platform. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | ||
| PC-1387✎ edit📣 feedback | received | Core architects agent |
5.5 Keeping the architecture open and adaptable §5.5 p.110 l.Lines 213-217 |
The decision to treat AI as cross-cutting is appropriate, but the document does not clarify whether a shared model regi…The decision to treat AI as cross-cutting is appropriate, but the document does not clarify whether a shared model registry, evaluation service, controlled computing environment, or AI governance function belongs within the present architecture. Suggested revision: State whether these are out of scope, optional implementation capabilities, or candidates for future architecture releases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-059 discuss | in the document all mentions on GitHub record | ||
| PC-1388✎ edit📣 feedback | received | Core architects agent, medium |
5.5 Keeping the architecture open and adaptable §5.5 p.110 l.Lines 218-222 |
The conclusion states that strong foundations allow safe and effective adoption “at scale.” Scaling should not be assum…The conclusion states that strong foundations allow safe and effective adoption “at scale.” Scaling should not be assumed to be the correct goal for every AI use case. Suggested revision: Replace with a sentence like: “safely, effectively, and at an appropriate scale, where evidence and public value justify broader adoption.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-248 discuss | in the document all mentions on GitHub record | ||
| PC-1389✎ edit📣 feedback | received | Core architects agent, medium |
5.1 Emerging technologies and the foundations they depend on §Chapter 5 overall p.104-110 l.Entire chapter anchor: medium |
The chapter relies mainly on illustrative use cases and high-level guidance. It contains few concrete country examples …The chapter relies mainly on illustrative use cases and high-level guidance. It contains few concrete country examples showing successful adoption, failure, measurable benefit, or implementation limitations. Suggested revision: Add short, sourced case studies representing different income levels and maturity contexts, including examples where AI was not adopted or was withdrawn because prerequisites were insufficient. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | ||
| PC-1390✎ edit📣 feedback | received | Core architects agent |
5.1 Emerging technologies and the foundations they depend on §Chapter 5 overall p.104-110 l.Entire chapter anchor: medium |
The chapter recognises lower-resource constraints but still assumes access to representative digital data, evaluation e…The chapter recognises lower-resource constraints but still assumes access to representative digital data, evaluation expertise, legal capacity, model monitoring, secure infrastructure, and supplier-management capability. Suggested revision: Add a low-resource adoption pathway based on bounded use cases, shared regional expertise, hosted evaluation services, simpler non-AI alternatives, minimum safeguards, and explicit conditions under which adoption should be deferred. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-123 discuss | in the document all mentions on GitHub record | ||
| PC-1391✎ edit📣 feedback | received | Core architects agent |
5.1 Emerging technologies and the foundations they depend on §Chapter 5 overall p.104-110 l.Entire chapter anchor: medium |
Chapter 5 is not sufficiently connected to the conformance model in Section 3.7. AI systems introduce model-specific ev…Chapter 5 is not sufficiently connected to the conformance model in Section 3.7. AI systems introduce model-specific evidence, versioning, performance, drift, human-factors, safety, and monitoring requirements. Suggested revision: Extend the conformance framework with AI-specific profiles and assessment evidence while distinguishing regulated product assurance from architecture conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1392✎ edit📣 feedback | received | Core architects Clinical agent, medium |
5.1 Emerging technologies and the foundations they depend on §Chapter 5 overall p.104-110 l.Entire chapter anchor: medium |
The chapter provides principles but not a practical national governance and deployment lifecycle for AI-enabled solutio…The chapter provides principles but not a practical national governance and deployment lifecycle for AI-enabled solutions. Suggested revision: Add an AI lifecycle covering need identification, alternatives analysis, risk classification, data readiness, procurement, evaluation, authorisation, deployment, monitoring, change control, incident response, revalidation, suspension, and retirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1393✎ edit📣 feedback | received | Core architects agent |
5.1 Emerging technologies and the foundations they depend on §Chapter 5 overall p.104-110 l.Entire chapter anchor: medium |
AI costs and commercial pressure are discussed, but financing guidance is not integrated with Chapter 4’s investment ca…AI costs and commercial pressure are discussed, but financing guidance is not integrated with Chapter 4’s investment case, procurement, partnerships, and recurrent-funding model. Suggested revision: Add cross-references and require AI proposals to demonstrate total cost, opportunity cost, financing sustainability, supplier-exit provisions, and compatibility with the national DPI-H roadmap. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1394✎ edit📣 feedback | received | Core architects agent, medium |
5.1 Emerging technologies and the foundations they depend on §Chapter 5 overall p.104-110 l.Entire chapter anchor: medium |
Several rapidly evolving terms, including large multimodal models, agents, skills, MCP, evals, and sovereign models, ma…Several rapidly evolving terms, including large multimodal models, agents, skills, MCP, evals, and sovereign models, may reduce the long-term stability and accessibility of the guidance. Suggested revision: Keep the stable document focused on durable architectural principles. Move rapidly evolving terminology and examples into a maintained online annex with version and publication date. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-118 discuss | in the document all mentions on GitHub record | ||
| PC-1395✎ edit📣 feedback | received | Core architects Clinical agent, low |
5.1 Emerging technologies and the foundations they depend on §Chapter 5 overall p.104-110 l.Entire chapter anchor: medium |
The chapter gives limited attention to medical-device regulation, clinical investigation, liability, professional accou…The chapter gives limited attention to medical-device regulation, clinical investigation, liability, professional accountability, intellectual property, cybersecurity threats specific to AI, and patient redress. Suggested revision: Add these topics at a level proportionate to the architecture guidance and identify where specialised regulatory or implementation guidance is required. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-250 discuss | in the document all mentions on GitHub record | ||
| PC-1396✎ edit📣 feedback | received | Editorial agent |
References §References p.111 l.Entire section anchor: medium |
The reference list is still marked “to be included before publication.” This prevents reviewers from systematically ver…The reference list is still marked “to be included before publication.” This prevents reviewers from systematically verifying the document’s evidence base, source quality, citation completeness, and consistency. Suggested revision: Complete the reference list before the next review round. Ensure that every in-text reference and footnote has a corresponding full bibliographic entry and that every listed reference is cited in the document. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1397✎ edit📣 feedback | received | WHO Editorial agent, medium |
References §References p.111 l.Entire section anchor: medium |
Many substantive claims rely on footnotes and embedded URLs, but the absence of a consolidated reference list makes it …Many substantive claims rely on footnotes and embedded URLs, but the absence of a consolidated reference list makes it difficult to assess whether the document relies appropriately on standards, peer-reviewed studies, implementation reports, policy documents, or vendor material. Suggested revision: Categorise references consistently and use authoritative primary sources wherever possible. Distinguish normative standards, technical guidance, peer-reviewed evidence, legislation, country documentation, and illustrative web resources. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1398✎ edit📣 feedback | received | Editorial agent |
References §References p.111 l.Entire section anchor: medium |
Citation formatting is inconsistent throughout the document. Some entries contain full bibliographic details, while oth…Citation formatting is inconsistent throughout the document. Some entries contain full bibliographic details, while others contain only a URL, organisation name, or informal title. Suggested revision: Apply one recognised citation style consistently to all references, including author or organisation, year, title, publisher, edition or version, persistent identifier or URL, and access date where required. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1399✎ edit📣 feedback | received | Editorial agent, medium |
References §References p.111 l.Entire section anchor: medium |
Several references and claims relate to evolving standards, national programmes, legislation, and AI governance. Withou…Several references and claims relate to evolving standards, national programmes, legislation, and AI governance. Without publication or effective dates, readers may apply outdated information. Suggested revision: Record publication date, version, status, effective date, and access date where relevant. For living standards and online resources, reference a specific release or archived version. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1400✎ edit📣 feedback | received | Core architects agent, medium |
References §References p.111 l.Entire section anchor: medium |
References to standards such as FHIR, ArchiMate, TOGAF, IHE profiles, OpenHIE specifications, SNOMED CT, and WHO SMART …References to standards such as FHIR, ArchiMate, TOGAF, IHE profiles, OpenHIE specifications, SNOMED CT, and WHO SMART Guidelines need exact version identification because implementation and conformance depend on version. Suggested revision: Cite the exact normative version or release used by the architecture and define a version-management policy for future updates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1401✎ edit📣 feedback | received | WHO agent, low |
References §References p.111 l.Entire section anchor: medium |
The document occasionally relies on secondary descriptions of technical or national implementations where authoritative…The document occasionally relies on secondary descriptions of technical or national implementations where authoritative primary documentation may be available. Suggested revision: Prefer official standards, legislation, national architecture documents, programme documentation, and peer-reviewed evaluations. Use secondary summaries only where primary evidence is unavailable and identify their limitations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1402✎ edit📣 feedback | received | Core architects WHO agent, medium |
References §References p.111 l.Entire section anchor: medium |
Country examples and broad benefit claims require evidence showing not only that a system exists, but also its scope, g…Country examples and broad benefit claims require evidence showing not only that a system exists, but also its scope, governance, implementation status, measured results, and limitations. Suggested revision: For each country claim, cite a source that supports the specific statement being made. Avoid using implementation existence as evidence of effectiveness or transferability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1403✎ edit📣 feedback | received | Editorial agent |
References §References p.111 l.Entire section anchor: medium |
Some URLs appear directly in the body and footnotes, producing visual clutter and reducing readability.Some URLs appear directly in the body and footnotes, producing visual clutter and reducing readability. Suggested revision: Use numbered references or concise footnotes in the narrative and place complete URLs in the consolidated reference list. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1404✎ edit📣 feedback | received | Core architects WHO agent, medium |
References §References p.111 l.Entire section anchor: medium |
The document does not appear to distinguish normative references, which define conformance requirements, from informati…The document does not appear to distinguish normative references, which define conformance requirements, from informative references, which provide background or examples. Suggested revision: Separate references into normative and informative categories, particularly for component specifications, standards profiles, and conformance requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1405✎ edit📣 feedback | received | WHO Core architects agent, medium |
References §References p.111 l.Entire section anchor: medium |
The evidence base should demonstrate applicability across low-, middle-, and high-income settings. The current distribu…The evidence base should demonstrate applicability across low-, middle-, and high-income settings. The current distributed citations make it difficult to assess geographic balance. Suggested revision: Review the reference set for geographic and income-level balance. Include implementation and evaluation evidence from low- and middle-income countries, not only global guidance and high-income national architectures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1406✎ edit📣 feedback | received | Core architects agent, low |
References §References p.111 l.Entire section anchor: medium |
The document makes detailed recommendations on privacy, security, consent, clinical safety, accessibility, procurement,…The document makes detailed recommendations on privacy, security, consent, clinical safety, accessibility, procurement, and AI but does not consistently identify authoritative sources for each domain. Suggested revision: Add relevant authoritative references for data protection, cybersecurity, accessibility, clinical safety, procurement, human rights, AI governance, and digital public-infrastructure safeguards. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1407✎ edit📣 feedback | received | Editorial agent, medium |
References §References p.111 l.Entire section anchor: medium |
Some cited online materials may be unstable, moved, or unavailable over the lifetime of the guidance.Some cited online materials may be unstable, moved, or unavailable over the lifetime of the guidance. Suggested revision: Prefer persistent identifiers, official repositories, archived publications, and DOI links. Maintain an accessible online bibliography with archived links where permitted. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1408✎ edit📣 feedback | received | Editorial agent |
References §References p.111 l.Entire section anchor: medium |
Trademark and standards-body names are formatted inconsistently, including varying use of registered-trademark symbols …Trademark and standards-body names are formatted inconsistently, including varying use of registered-trademark symbols for TOGAF, ArchiMate, FHIR, Open Group, and Archi. Suggested revision: Establish an editorial policy for first-use trademark acknowledgement and apply plain terminology consistently thereafter. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1409✎ edit📣 feedback | received | WHO Editorial agent, medium |
References §References p.111 l.Entire section anchor: medium |
The document references several figures adapted from external sources, but adaptation permissions, licences, and full s…The document references several figures adapted from external sources, but adaptation permissions, licences, and full source attribution are not consistently visible. Suggested revision: Include complete source, licence, adaptation statement, and permission status in each relevant figure caption and in the reference list. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-132 discuss | in the document all mentions on GitHub record | ||
| PC-1410✎ edit📣 feedback | received | Editorial agent |
A Appendix A §Appendix A p.112 l.Appendix title anchor: medium |
The appendix is introduced as “Appendix 1” and then “Appendix A,” creating inconsistent numbering.The appendix is introduced as “Appendix 1” and then “Appendix A,” creating inconsistent numbering. Suggested revision: Remove “Appendix 1” and use “Appendix A” consistently in the contents, heading, cross-references, and bookmarks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-254 discuss | in the document all mentions on GitHub record | ||
| PC-1411✎ edit📣 feedback | received | Editorial agent, medium |
A Appendix A §Appendix A p.112 l.Table A anchor: medium |
The stakeholder table lists stakeholder categories but does not explain how it should be used for architecture developm…The stakeholder table lists stakeholder categories but does not explain how it should be used for architecture development, consultation, governance, implementation, or impact assessment. Suggested revision: Add a brief introduction explaining that the table supports stakeholder identification, role assignment, engagement planning, governance representation, and assessment of affected groups. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1412✎ edit📣 feedback | received | Core architects agent |
A Appendix A §Appendix A p.112 l.Table A anchor: medium |
The table is primarily a list of stakeholders. It does not identify stakeholder interests, responsibilities, decision r…The table is primarily a list of stakeholders. It does not identify stakeholder interests, responsibilities, decision rights, data contributions, dependencies, risks, or expected value. Suggested revision: Expand the table with columns for role in DPI-H, main interests, data or services contributed, benefits, risks, governance participation, and required engagement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1413✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Individuals and Communities” anchor: medium |
Individuals, care recipients, caregivers, and families are included, but the table does not explicitly recognise margin…Individuals, care recipients, caregivers, and families are included, but the table does not explicitly recognise marginalised populations, people without legal identity, displaced populations, persons with disabilities, children, older people, linguistic minorities, or digitally excluded groups. Suggested revision: Add a note requiring country-specific identification of populations that may experience exclusion, disproportionate burden, surveillance risk, accessibility barriers, or reduced ability to exercise data rights. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1414✎ edit📣 feedback | received | Core architects agent, low |
A Appendix A §Appendix A p.112 l.Table A, “Individuals and Communities” anchor: medium |
“Individuals & care recipients” may place people mainly in the role of service recipients and underrepresent their role…“Individuals & care recipients” may place people mainly in the role of service recipients and underrepresent their roles as rights holders, data subjects, citizens, community members, caregivers, and contributors to governance. Suggested revision: Use: “Individuals, health-service users, data subjects, caregivers, families, and communities.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1415✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Health Workforce” anchor: medium |
The health-workforce category lists healthcare providers but does not distinguish regulated professionals, community he…The health-workforce category lists healthcare providers but does not distinguish regulated professionals, community health workers, public-health workers, laboratory and pharmacy staff, administrative workers, digital-health staff, and informal or traditional care providers where applicable. Suggested revision: Expand the category or reference the WHO health-worker classification while allowing countries to include nationally recognised cadres and non-clinical health-system roles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1416✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Health Facilities and Institutions” anchor: medium |
The table lists hospitals and primary healthcare institutions but omits laboratories, pharmacies, diagnostic centres, c…The table lists hospitals and primary healthcare institutions but omits laboratories, pharmacies, diagnostic centres, community sites, mobile services, emergency services, rehabilitation services, long-term care, logistics facilities, and virtual-care providers. Suggested revision: Expand the examples and align them with the broad facility scope defined in the Health Facility Registry component description. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1417✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Health Facilities and Institutions” anchor: medium |
Public, private, faith-based, non-governmental, military, humanitarian, and community-operated facilities may have diff…Public, private, faith-based, non-governmental, military, humanitarian, and community-operated facilities may have different governance, financing, and data obligations. The table does not distinguish these institutional contexts. Suggested revision: Add provider-sector and ownership distinctions and require stakeholder analysis to include non-state and humanitarian service providers where relevant. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1418✎ edit📣 feedback | received | Core architects agent, low |
A Appendix A §Appendix A p.112 l.Table A, “Health management personnel” anchor: medium |
“Health management personnel” is broad and overlaps with leadership, governance, facility administration, programme man…“Health management personnel” is broad and overlaps with leadership, governance, facility administration, programme management, and operational service management. Suggested revision: Clarify the category and include facility managers, programme managers, subnational health administrators, digital-health managers, and health-information managers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1419✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Leadership and Governance” anchor: medium |
The governance category includes health and finance ministries, public-health authorities, policymakers, regulators, an…The governance category includes health and finance ministries, public-health authorities, policymakers, regulators, and DPI-F agencies but omits data-protection authorities, civil-registration authorities, digital-government bodies, cybersecurity authorities, national archives, statistics offices, and local government. Suggested revision: Add these stakeholders where relevant to the national context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1420✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Leadership and Governance” anchor: medium |
“Other governmental agencies that own and govern DPI-F” assumes that foundational DPI is owned and governed by governme…“Other governmental agencies that own and govern DPI-F” assumes that foundational DPI is owned and governed by government agencies. Some countries use public corporations, regulated private operators, shared regional services, or public-private arrangements. Suggested revision: Replace with a sentence like: “Authorities and accountable operators responsible for foundational or cross-sector digital public infrastructure.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1421✎ edit📣 feedback | received | Financial systems agent |
A Appendix A §Appendix A p.112 l.Table A, “Health Financing Actors” anchor: medium |
The category lists purchasing agencies and health-coverage scheme managers but omits Ministries of Finance, treasury, p…The category lists purchasing agencies and health-coverage scheme managers but omits Ministries of Finance, treasury, public financial-management bodies, insurers, claims administrators, provider-payment bodies, social-security institutions, and patients making direct payments. Suggested revision: Expand the financing category and distinguish revenue-raising, pooling, purchasing, payment, claims, oversight, and beneficiary perspectives. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1422✎ edit📣 feedback | received | Supply chain agent |
A Appendix A §Appendix A p.112 l.Table A, “Supply Chain Actors” anchor: medium |
Procurement specialists, suppliers, warehouse staff, and logistics coordinators are listed, but regulators, manufacture…Procurement specialists, suppliers, warehouse staff, and logistics coordinators are listed, but regulators, manufacturers, importers, distributors, pharmacists, customs authorities, quality-control laboratories, and product-recall authorities are omitted. Suggested revision: Expand the category to reflect the full product and supply-chain lifecycle. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1423✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Academic, Research, and Training Bodies” anchor: medium |
The category combines research, education, and training institutions although their authority, data needs, governance r…The category combines research, education, and training institutions although their authority, data needs, governance roles, and responsibilities differ. Suggested revision: Separate research institutions, universities and training institutions, ethics bodies, and professional education or accreditation organisations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1424✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Support and Implementation Partners” anchor: medium |
Civil society, media, advocacy organisations, international agencies, and donors are grouped together as support and im…Civil society, media, advocacy organisations, international agencies, and donors are grouped together as support and implementation partners, although civil society and media may provide independent scrutiny rather than implementation support. Suggested revision: Separate civil society and public-interest oversight, media and advocacy, development partners and donors, and technical implementation partners. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1425✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendix A p.112 l.Table A, “Support and Implementation Partners” anchor: medium |
Technology suppliers, system integrators, standards organisations, open-source communities, telecommunications provider…Technology suppliers, system integrators, standards organisations, open-source communities, telecommunications providers, cloud providers, cybersecurity providers, and professional associations are not explicitly included. Suggested revision: Add these stakeholder categories and distinguish commercial suppliers from neutral standards, professional, and community organisations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-134 discuss | in the document all mentions on GitHub record | ||
| PC-1426✎ edit📣 feedback | received | Core architects agent |
A Appendix A §Appendix A p.112 l.Table A anchor: medium |
The table does not identify stakeholders responsible for operating shared components, maintaining standards, managing c…The table does not identify stakeholders responsible for operating shared components, maintaining standards, managing conformance, responding to incidents, or governing architecture changes. Suggested revision: Extend the stakeholder model to cover accountable authority, component operator, data steward, semantic steward, conformance authority, security authority, service manager, and architecture-review function. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1427✎ edit📣 feedback | received | Core architects agent |
A Appendix A §Appendix A p.112 l.Table A anchor: medium |
The table lists stakeholder organisations but does not require analysis of power differences, conflicts of interest, de…The table lists stakeholder organisations but does not require analysis of power differences, conflicts of interest, decision influence, or ability to participate. Suggested revision: Add a stakeholder-analysis method covering influence, impact, representation, conflicts, participation barriers, and measures needed to ensure meaningful involvement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1428✎ edit📣 feedback | received | Core architects agent |
A Appendix A §Appendix A p.112 l.Table A anchor: medium |
The stakeholder table does not show who funds shared infrastructure, who receives benefits, who bears operating costs, …The stakeholder table does not show who funds shared infrastructure, who receives benefits, who bears operating costs, or who may be asked to contribute. Suggested revision: Add financing roles or link Appendix A to the multistakeholder funding model proposed in Sections 3.4 and 4.6. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1429✎ edit📣 feedback | received | Editorial agent |
A Appendix A §Appendix A p.112 l.Table A anchor: medium |
The table contains inconsistent punctuation, capitalisation, ampersand use, and pluralisation, such as “Individuals & c…The table contains inconsistent punctuation, capitalisation, ampersand use, and pluralisation, such as “Individuals & care recipients,” “Healthcare Facilities,” and “Other Governmental agencies.” Suggested revision: Apply consistent sentence case, terminology, punctuation, and plural forms throughout the table. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-254 discuss | in the document all mentions on GitHub record | ||
| PC-1430✎ edit📣 feedback | received | Editorial agent, medium |
A Appendix A §Appendix A p.112 l.Table A anchor: medium |
The appendix does not indicate whether stakeholder categories are exhaustive or illustrative.The appendix does not indicate whether stakeholder categories are exhaustive or illustrative. Suggested revision: State that the list is illustrative and must be adapted through country-specific stakeholder mapping. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1431✎ edit📣 feedback | received | Editorial WHO agent, low |
B Appendix B §Appendix B p.113 l.Table B anchor: medium |
The appendix maps the seven goals to WHO building blocks but does not explain how the mapping should be used in plannin…The appendix maps the seven goals to WHO building blocks but does not explain how the mapping should be used in planning, assessment, investment, or reporting. Suggested revision: Add a short introduction explaining the purpose and limitations of the mapping and how it complements rather than replaces established health-system frameworks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1432✎ edit📣 feedback | received | Core architects agent, medium |
B Appendix B §Appendix B p.113 l.Table B anchor: medium |
Most goals are mapped to one primary WHO building block, although the goals are explicitly cross-cutting and depend on …Most goals are mapped to one primary WHO building block, although the goals are explicitly cross-cutting and depend on several building blocks. The simplified mapping understates these dependencies. Suggested revision: Use primary and secondary mappings or a many-to-many matrix showing the relative contribution of each WHO building block to every goal. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1433✎ edit📣 feedback | received | Core architects agent |
B Appendix B §Appendix B p.113 l.“Build trusted data foundations” row anchor: medium |
The goal is mapped only to health-information systems. Trusted data foundations also depend on leadership and governanc…The goal is mapped only to health-information systems. Trusted data foundations also depend on leadership and governance, workforce capability, financing, service delivery, and technologies. Suggested revision: Map it primarily to health-information systems and secondarily to leadership and governance, workforce, financing, and service delivery. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1434✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
B Appendix B §Appendix B p.113 l.“Support a capable, well-distributed health workforce” row anchor: medium |
The goal is mapped only to the health-workforce building block, but timely payment, education, deployment, regulation, …The goal is mapped only to the health-workforce building block, but timely payment, education, deployment, regulation, facilities, information, and service configuration also depend on financing, governance, and service delivery. Suggested revision: Add secondary mappings to health financing, leadership and governance, health-information systems, and service delivery. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1435✎ edit📣 feedback | received | Core architects Clinical agent, low |
B Appendix B §Appendix B p.113 l.“Ensure quality and continuity of care” row anchor: medium |
Mapping only to service delivery overlooks workforce, information systems, medicines and technologies, financing, and g…Mapping only to service delivery overlooks workforce, information systems, medicines and technologies, financing, and governance required for coordinated and safe care. Suggested revision: Add secondary mappings to health workforce, health-information systems, medical products and technologies, financing, and leadership and governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1436✎ edit📣 feedback | received | Core architects Clinical agent, medium |
B Appendix B §Appendix B p.113 l.“Establish trusted personal health records” row anchor: medium |
The row maps the goal to health-information systems and a proposed “People” focus. Personal health records also depend …The row maps the goal to health-information systems and a proposed “People” focus. Personal health records also depend on service delivery, governance, trust, legal rights, workforce use, and financing. Suggested revision: Add the relevant building blocks and explain the status and source of the proposed “People” dimension. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1437✎ edit📣 feedback | received | WHO agent, medium |
B Appendix B §Appendix B p.113 l.“Establish trusted personal health records” row anchor: medium |
The phrase “the ‘People’ focus proposed as a seventh block” is not sourced or explained, and readers may assume it is a…The phrase “the ‘People’ focus proposed as a seventh block” is not sourced or explained, and readers may assume it is an formally adopted WHO building block. Suggested revision: Cite the exact framework or proposal and clearly distinguish it from the established six WHO building blocks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1438✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
B Appendix B §Appendix B p.113 l.“Optimise supply chain management” row anchor: medium |
The goal is mapped only to medical products, vaccines, and technologies. Supply-chain performance also depends on finan…The goal is mapped only to medical products, vaccines, and technologies. Supply-chain performance also depends on financing, workforce, information, governance, procurement, service delivery, and infrastructure. Suggested revision: Add secondary mappings and show that product availability is a multi-building-block outcome. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1439✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
B Appendix B §Appendix B p.113 l.“Advance efficient and equitable health financing” row anchor: medium |
Mapping the goal only to health financing overlooks beneficiary identity, provider information, service delivery, workf…Mapping the goal only to health financing overlooks beneficiary identity, provider information, service delivery, workforce, medicines, data, public financial management, and governance. Suggested revision: Add secondary mappings to health-information systems, service delivery, workforce, medical products and technologies, and leadership and governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1440✎ edit📣 feedback | received | Core architects agent |
B Appendix B §Appendix B p.113 l.“Strengthen climate and epidemic resilience” row anchor: medium |
Labelling the goal simply “cross-cutting” does not show which health-system building blocks are required or how resilie…Labelling the goal simply “cross-cutting” does not show which health-system building blocks are required or how resilience extends the framework. Suggested revision: Map the goal across service delivery, workforce, information systems, medical products, financing, and leadership and governance, and explain the role of each. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1441✎ edit📣 feedback | received | Core architects agent |
B Appendix B §Appendix B p.113 l.“Leadership and governance” row anchor: medium |
Leadership and governance is shown as addressed as a principle rather than a goal. This presentation may understate tha…Leadership and governance is shown as addressed as a principle rather than a goal. This presentation may understate that leadership and governance are also capabilities and measurable health-system functions. Suggested revision: State that leadership and governance are cross-cutting prerequisites and implementation capabilities, even though they are not one of the seven outcome-oriented goals. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1442✎ edit📣 feedback | received | Core architects agent |
B Appendix B §Appendix B p.113 l.Table B anchor: medium |
The table maps goals to building blocks but does not map DPI-H components, capabilities, or stakeholder value to those …The table maps goals to building blocks but does not map DPI-H components, capabilities, or stakeholder value to those building blocks. Its contribution to the architecture methodology is therefore limited. Suggested revision: Consider extending the table or adding a companion matrix connecting goals, health-system building blocks, capabilities, and principal DPI-H components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1443✎ edit📣 feedback | received | Editorial agent |
B Appendix B §Appendix B p.113 l.Table B anchor: medium |
The table uses both British and American spelling conventions across the wider document, including “optimise” and “stan…The table uses both British and American spelling conventions across the wider document, including “optimise” and “standardized” in different sections. Suggested revision: Select a single English-language convention and apply it consistently throughout the document. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-283 discuss | in the document all mentions on GitHub record | ||
| PC-1444✎ edit📣 feedback | received | WHO agent, low |
B Appendix B §Appendix B p.113 l.Table B anchor: medium |
The appendix does not cite the authoritative WHO source for the six building blocks or the source supporting the propos…The appendix does not cite the authoritative WHO source for the six building blocks or the source supporting the proposed additional people-centred dimension. Suggested revision: Add full references and explain whether the mapping was developed by the authors or drawn from an existing WHO framework. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1445✎ edit📣 feedback | received | Core architects WHO agent, medium |
B Appendix B §Appendix B p.113 l.Table B anchor: medium |
The building-block framework is useful but may not fully represent decentralisation, community systems, private provide…The building-block framework is useful but may not fully represent decentralisation, community systems, private providers, digital governance, social determinants, emergency preparedness, and cross-sector DPI. Suggested revision: Acknowledge the limitations and position the mapping as a compatibility aid rather than a complete model of national health-system architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1446✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendices A-B overall p.112-113 l.Entire appendices anchor: medium |
Appendices A and B are much less developed than the detailed technical component appendices. This creates an imbalance …Appendices A and B are much less developed than the detailed technical component appendices. This creates an imbalance between institutional and technical guidance. Suggested revision: Expand the stakeholder and health-system mappings sufficiently to support governance, implementation, equity assessment, and investment planning, while keeping them concise and usable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1447✎ edit📣 feedback | received | Core architects agent |
A Appendix A §Appendices A-B overall p.112-113 l.Entire appendices anchor: medium |
Neither appendix provides a reusable country template or instructions for adaptation.Neither appendix provides a reusable country template or instructions for adaptation. Suggested revision: Publish editable stakeholder-mapping and goal-to-building-block templates with guidance on completing, validating, and approving them nationally. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1448✎ edit📣 feedback | received | Core architects agent, medium |
A Appendix A §Appendices A-B overall p.112-113 l.Entire appendices anchor: medium |
The appendices do not connect directly to the architecture repository, roadmap, governance model, or progress-measureme…The appendices do not connect directly to the architecture repository, roadmap, governance model, or progress-measurement framework. Suggested revision: Add cross-references showing how stakeholder analysis and health-system mappings inform architecture views, governance representation, implementation priorities, financing, and outcome evaluation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-133 discuss | in the document all mentions on GitHub record | ||
| PC-1449✎ edit📣 feedback | received | Core architects agent |
Metadata registries and foundational components §Appendix C introduction p.114 l.Lines 15-25 |
Appendix C lists the foundational components but does not provide a consolidated overview of their purpose, dependencie…Appendix C lists the foundational components but does not provide a consolidated overview of their purpose, dependencies, maturity, or relationship to the seven health goals before beginning the detailed specifications. Suggested revision: Add a summary matrix listing each component, architecture layer, purpose, principal services, governed data, main dependencies, relevant goals, implementation maturity, and related operational systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-193 discuss | in the document all mentions on GitHub record | ||
| PC-1450✎ edit📣 feedback | received | Core architects agent, medium |
Metadata registries and foundational components §Appendix C introduction p.114 l.Lines 18-25 |
The introductory list covers only the metadata registries and foundational components. The relationship to the business…The introductory list covers only the metadata registries and foundational components. The relationship to the business-services components presented later in Appendix C is not visible on this opening page. Suggested revision: Show both DPI-H layers in the Appendix C introduction and group all component descriptions consistently under the foundational shared data layer and business-services layer. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-193 discuss | in the document all mentions on GitHub record | ||
| PC-1451✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
Metadata registries and foundational components §Appendix C introduction p.114 l.Lines 18-25 |
The heading “Metadata registries and foundational components” continues to group entity registries, the LHR, Terminolog…The heading “Metadata registries and foundational components” continues to group entity registries, the LHR, Terminology Service, and LIMR under one category, although they manage different types of data and services. Suggested revision: Rename the group Foundational shared data and semantic components, with subcategories for authoritative entity registries, longitudinal health information, terminology, and information models. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-193 discuss | in the document all mentions on GitHub record | ||
| PC-1452✎ edit📣 feedback | received | Core architects agent |
Metadata registries and foundational components §Appendix C introduction p.114 l.Lines 18-25 |
Appendix C does not begin with a clear statement that these are logical architecture components rather than one-to-one …Appendix C does not begin with a clear statement that these are logical architecture components rather than one-to-one prescriptions for software products. Suggested revision: Add a prominent note that one platform may realise several logical components and one logical component may be distributed across several systems, provided its responsibilities and conformance boundaries remain explicit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-1453✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry p.115 l.Architecture placement anchor: medium |
The Client Registry is called the “single authoritative source” of health-specific identity. In federated arrangements,…The Client Registry is called the “single authoritative source” of health-specific identity. In federated arrangements, several legally authoritative source systems may contribute to a governed national identity-resolution capability. Suggested revision: Replace with authoritative national health-identity reference capability and clarify that it may be centralised, federated, or hybrid, with clearly assigned authority and reconciliation rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-1454✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry p.115 l.Architecture placement anchor: medium |
The statement that the Client Registry provides health-sector identity resolution where foundational identity does not …The statement that the Client Registry provides health-sector identity resolution where foundational identity does not exist is appropriate, but the transition relationship is not described. Suggested revision: Require a transition and interoperability plan showing how health identifiers, identity evidence, links, and assurance levels would integrate with future foundational identity services without excluding existing health-service users. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1455✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 1 p.115 l.Lines 47-53 |
The component combines identity records, health-identifier assignment, identifier cross-referencing, matching, and dedu…The component combines identity records, health-identifier assignment, identifier cross-referencing, matching, and deduplication. These capabilities may be distributed across a client registry, master patient index, identifier service, or identity-management platform. Suggested revision: Clarify that the Client Registry is a logical capability and may be realised through several coordinated services, provided authoritative responsibility, interfaces, conformance, and governance remain coherent. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-1456✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 1 p.115 l.Lines 47-53 |
The definition says that the registry maintains a unique, verifiable identity record for every person accessing health …The definition says that the registry maintains a unique, verifiable identity record for every person accessing health services. In practice, records may be provisional, incomplete, duplicated, unmatched, or held at different assurance levels. Suggested revision: Replace with wording that supports provisional registration, incomplete identity, uncertainty, multiple assurance levels, and later reconciliation without delaying essential care. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1457✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 1 p.115 l.Lines 51-53 |
“Canonical person record” may imply that one record represents an unquestionably correct identity. Identity resolution …“Canonical person record” may imply that one record represents an unquestionably correct identity. Identity resolution often involves uncertainty and competing source data. Suggested revision: Define the canonical record as the governed reference record selected for cross-system use, while preserving source provenance, conflicting evidence, matching confidence, and correction history. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1458✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 1 p.115 l.Lines 54-58 |
The statement that the Client Registry contains identity data rather than health data is conceptually useful, but ident…The statement that the Client Registry contains identity data rather than health data is conceptually useful, but identity and demographic attributes can themselves be sensitive health-related information in context. Suggested revision: Clarify that the registry does not contain clinical records, while its identity and demographic data remain sensitive personal data subject to health-sector privacy, security, and purpose restrictions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1459✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 1 p.115 l.Lines 59-64 |
Client Registry, MPI, and EMPI are presented as alternative terms. An MPI may be an index linking identifiers without m…Client Registry, MPI, and EMPI are presented as alternative terms. An MPI may be an index linking identifiers without maintaining all authoritative demographic attributes, while a Client Registry may have broader registration responsibilities. Suggested revision: Explain the functional overlap and differences rather than treating the terms as fully interchangeable. Allow countries to map existing arrangements by capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1460✎ edit📣 feedback | received | Core architects agent, medium |
Client Registry §Client Registry, 1 p.115 l.Lines 61-64 |
“Client” is preferred because it includes patients, carers, service users, and community members. A carer may also requ…“Client” is preferred because it includes patients, carers, service users, and community members. A carer may also require a distinct identity and relationship role rather than being represented as the subject of a health-service record. Suggested revision: Clarify that the registry identifies persons and represents their relevant roles and relationships separately. Consider whether Person Registry for Health is a clearer, less service-oriented term. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1461✎ edit📣 feedback | received | Core architects agent, low |
Client Registry §Client Registry, 2 p.115-116 l.Lines 67-72 |
The section links identity uncertainty to clinical risk, inflated public-health indicators, and unreliable programme me…The section links identity uncertainty to clinical risk, inflated public-health indicators, and unreliable programme measurement. These claims are credible but are not supported here by evidence. Suggested revision: Add appropriate evidence or describe the consequences as recognised risks rather than established outcomes in every context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1462✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 2 p.116 l.Lines 73-78 |
The discussion appropriately recognises migrants, refugees, children, and people using different names. It does not add…The discussion appropriately recognises migrants, refugees, children, and people using different names. It does not address the risk that linking records across sensitive services may expose people to stigma, legal enforcement, discrimination, or unwanted disclosure. Suggested revision: Require purpose-specific linkage rules, restricted matching across sensitive contexts, privacy-impact assessment, pseudonymised or segmented identifiers where appropriate, and governance approval for cross-programme linkage. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-138 discuss | in the document all mentions on GitHub record | ||
| PC-1463✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Client Registry §Client Registry, 2 p.116 l.Lines 73-78 |
The text says some children may be “denied services” without registry capability. Lack of formal registration should ne…The text says some children may be “denied services” without registry capability. Lack of formal registration should never be treated as justification for denial of essential health services. Suggested revision: State explicitly that the Client Registry must support care without foundational documentation and that registration or matching uncertainty must not become a barrier to essential service access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-139 discuss | in the document all mentions on GitHub record | ||
| PC-1464✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 2 p.116 l.Lines 79-84 |
The section says every connected system gains the ability to produce a longitudinal view when a Client Registry is avai…The section says every connected system gains the ability to produce a longitudinal view when a Client Registry is available. Identity linkage is necessary but not sufficient for a longitudinal view, which also requires exchange, data availability, semantic consistency, consent, provenance, and workflow integration. Suggested revision: Replace with a sentence like: “A Client Registry provides a necessary identity-linkage foundation for creating longitudinal views when the required exchange, data, governance, and semantic capabilities are also present.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1465✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 87-89 |
Support for incomplete demographic information is identified, but the core attributes do not explicitly include identit…Support for incomplete demographic information is identified, but the core attributes do not explicitly include identity assurance, provisional status, uncertainty, or source confidence. Suggested revision: Add explicit capabilities for provisional records, identity-assurance levels, confidence, verification status, unknown values, conflicting evidence, and review status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-139 discuss | in the document all mentions on GitHub record | ||
| PC-1466✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 90-93 |
Assignment of one nationally unique health identifier to every person may not be legally, politically, or technically a…Assignment of one nationally unique health identifier to every person may not be legally, politically, or technically appropriate in every country. Some countries use multiple sector-specific or regional identifiers linked through cross-references. Suggested revision: Describe the HUID as one implementation option. Define the required outcome as reliable cross-system person identification and linkage, which may use national, regional, federated, or multiple linked identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1467✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 90-93 |
The text requires the HUID to remain stable across demographic changes but does not address erroneous assignment, ident…The text requires the HUID to remain stable across demographic changes but does not address erroneous assignment, identifier compromise, duplicate assignment, identifier retirement, or reissuance. Suggested revision: Add lifecycle rules covering creation, activation, correction, replacement, retirement, compromise, duplicate resolution, and preservation of historical cross-references. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1468✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 94-97 |
Multi-identifier management is fundamental, but the requirement does not explicitly capture identifier assigning author…Multi-identifier management is fundamental, but the requirement does not explicitly capture identifier assigning authority, type, status, validity period, use, or confidence. Suggested revision: Require each identifier to include assigning authority, namespace or system, value, type, status, validity period, provenance, verification status, and restrictions on use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1469✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 98-101 |
Configurable probabilistic and deterministic matching is required, but no minimum performance, evaluation, explainabili…Configurable probabilistic and deterministic matching is required, but no minimum performance, evaluation, explainability, subgroup testing, or quality-monitoring expectations are stated. Suggested revision: Require context-specific thresholds for false matches and missed matches, representative evaluation, subgroup analysis, explainable match evidence, human adjudication, monitoring, and periodic recalibration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-143 discuss | in the document all mentions on GitHub record | ||
| PC-1470✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 98-101 |
Probabilistic matching may perform unequally for populations with variable spelling, naming conventions, uncertain birt…Probabilistic matching may perform unequally for populations with variable spelling, naming conventions, uncertain birth dates, shared addresses, or limited documentation. Suggested revision: Require localisation of matching rules, culturally appropriate name handling, language support, alternative attributes, subgroup testing, and accessible correction and redress processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-143 discuss | in the document all mentions on GitHub record | ||
| PC-1471✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 102-104 |
Identity verification against biometric services and foundational sources is included as a core attribute, but verifica…Identity verification against biometric services and foundational sources is included as a core attribute, but verification and identity resolution are different capabilities with different legal authority and assurance. Suggested revision: Separate identity resolution, verification, authentication, credential validation, and biometric matching. Define which are provided by the Client Registry and which are consumed from external services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-142 discuss | in the document all mentions on GitHub record | ||
| PC-1472✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 102-104 |
The biometric example may encourage deployment without adequate consideration of necessity, accuracy, exclusion, consen…The biometric example may encourage deployment without adequate consideration of necessity, accuracy, exclusion, consent, security, and legal basis. Suggested revision: Treat biometrics as an optional, high-risk mechanism requiring explicit legal authority, necessity and proportionality assessment, accuracy and equity testing, secure template governance, alternative access pathways, and impact assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-142 discuss | in the document all mentions on GitHub record | ||
| PC-1473✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 105-108 |
Household, spousal, and family relationships are included within the Client Registry. These relationships may be sensit…Household, spousal, and family relationships are included within the Client Registry. These relationships may be sensitive, contested, temporary, culturally variable, or maintained by other social or civil registries. Suggested revision: Make relationship management conditional and purpose-specific. Require relationship type, source, verification status, validity period, consent or legal basis, sensitivity classification, and correction process. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-141 discuss | in the document all mentions on GitHub record | ||
| PC-1474✎ edit📣 feedback | received | Core architects agent, medium |
Client Registry §Client Registry, 3 p.116 l.Lines 109-112 |
“Pseudo-anonymisation” should be written “pseudonymisation.” More importantly, pseudonymised data remains personal data…“Pseudo-anonymisation” should be written “pseudonymisation.” More importantly, pseudonymised data remains personal data where re-identification is possible. Suggested revision: Correct the terminology and state that pseudonymisation reduces direct identifiability but does not remove applicable data-protection obligations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-145 discuss | in the document all mentions on GitHub record | ||
| PC-1475✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 109-112 |
The right to be forgotten is included as a general registry capability. Health and legal-identity records may be subjec…The right to be forgotten is included as a general registry capability. Health and legal-identity records may be subject to statutory retention obligations and exceptions to erasure. Suggested revision: Replace with “support applicable rights to access, correction, restriction, objection, and erasure where legally applicable, while preserving records required for care, safety, audit, and statutory purposes.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-145 discuss | in the document all mentions on GitHub record | ||
| PC-1476✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 3 p.116 l.Lines 113-115 |
Standards-based APIs are required, but the core attributes mention only creation, query, cross-referencing, and subscri…Standards-based APIs are required, but the core attributes mention only creation, query, cross-referencing, and subscription. Merge, unlink, history, provenance, assurance, and relationship operations are also important. Suggested revision: Define the full service catalogue and actor roles in a versioned national implementation guide, including security, consent or legal-basis enforcement, error responses, and audit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1477✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.116-117 l.Lines 118-130 |
Foundational systems are described as authoritative for legal name, date of birth, sex, and nationality. In practice, a…Foundational systems are described as authoritative for legal name, date of birth, sex, and nationality. In practice, authority may be distributed, disputed, incomplete, or vary by attribute and jurisdiction. Suggested revision: Define authoritative sources at attribute level rather than assuming one foundational system is authoritative for all demographic attributes. Preserve provenance and conflict-resolution rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1478✎ edit📣 feedback | received | Editorial Core architects agent, medium |
Client Registry §Client Registry, 4 p.117 l.Lines 127-142 |
The three HUID models are attributed to WHO guidance, but the exact reference and terminology should be verified agains…The three HUID models are attributed to WHO guidance, but the exact reference and terminology should be verified against the cited source. Suggested revision: Cite the specific guidance, version, and section. State whether the three models are reproduced directly or adapted for this architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1479✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.117 l.Lines 131-134 |
Model A permits the HUID to be “derived from” the national identifier. Derivation can expose or make the national ident…Model A permits the HUID to be “derived from” the national identifier. Derivation can expose or make the national identifier predictable and may conflict with the later requirement for a non-intelligent identifier. Suggested revision: Prefer a random health identifier linked to, rather than derived from, foundational identifiers. If derivation is permitted, require a privacy and security justification and prohibit reversible or meaningful encoding. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1480✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.117 l.Lines 135-138 |
Model B describes an independent health identifier where foundational identity is absent, unreliable, or inaccessible. …Model B describes an independent health identifier where foundational identity is absent, unreliable, or inaccessible. It does not specify how identity assurance and duplicate risk are managed under limited evidence. Suggested revision: Require defined assurance levels, alternative evidence, provisional registration, matching review, duplicate monitoring, and later linkage without disrupting access to care. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1481✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.117 l.Lines 139-142 |
Model C links multiple local identifiers through an EMPI but does not address whether local identifiers remain authorit…Model C links multiple local identifiers through an EMPI but does not address whether local identifiers remain authoritative for local workflows or how corrections propagate. Suggested revision: Define identifier ownership, update propagation, conflict resolution, merge and unlink governance, source remediation, and continuity during transition. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1482✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.117 l.Lines 143-147 |
The text says the Client Registry does not duplicate foundational identity data, but Appendix C later makes several dem…The text says the Client Registry does not duplicate foundational identity data, but Appendix C later makes several demographic attributes mandatory in the Client Registry. Suggested revision: Clarify that the registry may retain the minimum demographic attributes required for health identity resolution, with provenance and synchronisation rules, rather than claiming that it does not duplicate any foundational data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1483✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.117 l.Lines 148-155 |
The privacy and access risks of linking health identity to civic systems are appropriately acknowledged, but the text f…The privacy and access risks of linking health identity to civic systems are appropriately acknowledged, but the text focuses mainly on deterrence from care. Risks also include surveillance, function creep, discrimination, and access by non-health authorities. Suggested revision: Expand the risk assessment and require purpose limitation, access separation, legal safeguards, transparency, audit, redress, and prohibition of unauthorised use for immigration, law enforcement, or other unrelated purposes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-138 discuss | in the document all mentions on GitHub record | ||
| PC-1484✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.117 l.Lines 148-155 |
The architecture leaves the linkage model to the country but does not specify the decision process or minimum evidence …The architecture leaves the linkage model to the country but does not specify the decision process or minimum evidence required. Suggested revision: Require a documented policy decision supported by legal analysis, privacy and human-rights impact assessment, equity assessment, threat modelling, stakeholder consultation, alternatives analysis, and governance approval. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-138 discuss | in the document all mentions on GitHub record | ||
| PC-1485✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
Client Registry §Client Registry, 4 p.117 l.Lines 158-164 |
The text says the Benefits Package Registry depends on the Client Registry to confirm scheme enrolment. The Client Regi…The text says the Benefits Package Registry depends on the Client Registry to confirm scheme enrolment. The Client Registry should identify persons, while enrolment or beneficiary status is normally managed elsewhere. Suggested revision: Revise to state that financing systems use the Client Registry to resolve person identity, while enrolment and eligibility are managed by the relevant beneficiary, scheme, or operational financing system. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1486✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Client Registry §Client Registry, 4 p.117 l.Lines 162-164 |
The Facility Registry is said to cross-reference the Client Registry to record facilities attended by a person. Attenda…The Facility Registry is said to cross-reference the Client Registry to record facilities attended by a person. Attendance history is clinical or encounter information and should not normally be held in the Facility Registry. Suggested revision: Remove this statement. Facility attendance should be represented in encounter, service-use, or LHR data referencing both the person and facility identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1487✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Client Registry §Client Registry, 4 p.117 l.Lines 163-164 |
Consent services are said to reference the Client Registry. This is appropriate for identity resolution, but consent ma…Consent services are said to reference the Client Registry. This is appropriate for identity resolution, but consent may also involve representatives, guardians, organisations, and anonymous or pseudonymous subjects. Suggested revision: Define how consent records identify data subjects, representatives, authority, relationship, assurance, and applicable identity context without forcing all use cases into one person identifier. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1488✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.117 l.Lines 165-168 |
The Client and Workforce Registries are described as architecturally parallel. Workforce identity additionally involves…The Client and Workforce Registries are described as architecturally parallel. Workforce identity additionally involves professional roles, credentials, licences, employment, and organisational affiliations. Suggested revision: Describe the shared identity-management patterns while making the distinct domain requirements and authoritative sources explicit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-136 discuss | in the document all mentions on GitHub record | ||
| PC-1489✎ edit📣 feedback | received | Metadata registries agent |
Client Registry §Client Registry, 4 p.117 l.Lines 169-174 |
The LIMR is described as holding the canonical Client Registry schema, while the Terminology Service supplies selected …The LIMR is described as holding the canonical Client Registry schema, while the Terminology Service supplies selected coded values. The relationship to FHIR profiles, implementation guides, identity standards, and matching configurations is not explained. Suggested revision: Add a traceability chain from logical model to national profile, terminology bindings, API specification, matching policy, validation artefacts, and deployed implementation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1490✎ edit📣 feedback | received | Metadata registries Core architects agent |
Client Registry §Client Registry, 4 p.117 l.Lines 172-174 |
Sex, gender, administrative territory, language, and relationship type are cited as coded attributes. These concepts ar…Sex, gender, administrative territory, language, and relationship type are cited as coded attributes. These concepts are legally, socially, clinically, and culturally sensitive and may not be represented adequately by one national value set. Suggested revision: Require purpose-specific definitions, inclusive and jurisdictionally appropriate value sets, separation of concepts, versioning, and governance involving affected communities and domain experts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1491✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 4 p.118 l.Lines 175-178 |
PKI is described as supporting biometric verification and identity credentials. PKI supports cryptographic trust but do…PKI is described as supporting biometric verification and identity credentials. PKI supports cryptographic trust but does not itself verify biometrics or establish identity correctness. Suggested revision: Clarify that PKI can verify credential signatures, issuer identity, and data integrity, while biometric matching and identity-proofing services provide separate functions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-142 discuss | in the document all mentions on GitHub record | ||
| PC-1492✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.118 l.Lines 181-185 |
The requirements are said to be consistent with and extend OpenHIE, WHO HUID, IHE PMIR, and PIX. These sources differ i…The requirements are said to be consistent with and extend OpenHIE, WHO HUID, IHE PMIR, and PIX. These sources differ in scope and may use different actors, versions, and data models. Suggested revision: Provide a traceability matrix showing the exact source, version, original requirement, adaptation, reason for change, and corresponding test method for each requirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1493✎ edit📣 feedback | received | Core architects agent, medium |
Client Registry §Client Registry, 5 p.118 l.Requirement table, Status column anchor: medium |
The table uses Required and Recommended, despite the main guidance stating that requirements use SHALL, SHOULD, and MAY.The table uses Required and Recommended, despite the main guidance stating that requirements use SHALL, SHOULD, and MAY. Suggested revision: Apply one normative convention consistently. Use SHALL, SHOULD, and MAY, with documented applicability and exceptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1494✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.118 l.Requirement 1 anchor: medium |
Requirement 1 mandates assignment of a HUID during creation of every new record. Some records may need provisional crea…Requirement 1 mandates assignment of a HUID during creation of every new record. Some records may need provisional creation before uniqueness is established, and not every country may use a national HUID. Suggested revision: Require assignment of a registry identifier or provisional identifier according to the national identifier model, with later reconciliation and no interruption of care. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1495✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.118 l.Requirement 1 anchor: medium |
Publishing every newly created person record to connected systems may expose unverified or duplicate data and unnecessa…Publishing every newly created person record to connected systems may expose unverified or duplicate data and unnecessarily distribute personal information. Suggested revision: Replace automatic publication with governed availability or event notification based on verification status, subscription, purpose, access rights, and minimum necessary data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-144 discuss | in the document all mentions on GitHub record | ||
| PC-1496✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.118 l.Requirement 2 anchor: medium |
The requirement says the registry shall capture HUID, foundational identifiers, and local identifiers at registration. …The requirement says the registry shall capture HUID, foundational identifiers, and local identifiers at registration. These identifiers may not be available at initial registration. Suggested revision: Require support for multiple identifier types when available rather than mandatory capture of each category during initial registration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1497✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
Client Registry §Client Registry, 5 p.118 l.Requirement 3 anchor: medium |
Configurable demographic schemas can support national needs but may also produce incompatible local extensions.Configurable demographic schemas can support national needs but may also produce incompatible local extensions. Suggested revision: Require extensions to follow governed extension rules, published definitions, terminology bindings, provenance, versioning, and conformance constraints. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1498✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
Client Registry §Client Registry, 5 p.118 l.Requirement 3 anchor: medium |
The requirement references the LIMR but makes this functionality only Recommended. If the LIMR is absent, the authorita…The requirement references the LIMR but makes this functionality only Recommended. If the LIMR is absent, the authoritative schema and extension governance mechanism remain undefined. Suggested revision: Require reference to a governed national schema repository or implementation guide. A dedicated LIMR platform may remain optional according to maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1499✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.118 l.Requirement 4 anchor: medium |
Inclusive registration is appropriately mandatory, but “alternative identity proofing methods” could still create high …Inclusive registration is appropriately mandatory, but “alternative identity proofing methods” could still create high burdens or expose vulnerable people. Suggested revision: Require low-barrier provisional registration, minimum necessary data, clear assurance levels, prohibition of service denial, alternative pathways, and review of discriminatory effects. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-139 discuss | in the document all mentions on GitHub record | ||
| PC-1500✎ edit📣 feedback | received | Core architects agent |
5.4.1 What AI readiness means §Client Registry, 5 p.119 l.Requirement 5 anchor: medium |
Demographic changes must be propagated to subscribed systems, but the requirement does not address verification, effect…Demographic changes must be propagated to subscribed systems, but the requirement does not address verification, effective dates, corrections, conflict, or whether consumers may reject changes. Suggested revision: Add update status, source authority, effective time, provenance, reason, verification state, subscription scope, conflict handling, acknowledgement, and reconciliation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-144 discuss | in the document all mentions on GitHub record | ||
| PC-1501✎ edit📣 feedback | received | Core architects agent |
5.4.1 What AI readiness means §Client Registry, 5 p.119 l.Requirement 6 anchor: medium |
Deactivation, suppression, and deletion are grouped together although they have different meanings and consequences. De…Deactivation, suppression, and deletion are grouped together although they have different meanings and consequences. Deletion may conflict with audit, safety, and legal-retention requirements. Suggested revision: Define each lifecycle action separately and require legal-basis, retention, audit, restoration, notification, and downstream-handling rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-144 discuss | in the document all mentions on GitHub record | ||
| PC-1502✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.119 l.Requirement 7 anchor: medium |
Returning the canonical record and “full cross-reference map” for any identifier query may expose unnecessary sensitive…Returning the canonical record and “full cross-reference map” for any identifier query may expose unnecessary sensitive identifiers to consuming systems. Suggested revision: Return only identifiers and attributes authorised and necessary for the requesting purpose. Apply field-level access control, masking, auditing, and purpose limitation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-145 discuss | in the document all mentions on GitHub record | ||
| PC-1503✎ edit📣 feedback | received | Core architects agent |
5.4.1 What AI readiness means §Client Registry, 5 p.119 l.Requirement 8 anchor: medium |
Demographic candidate searches can expose multiple people’s personal information to a user or system and may enable enu…Demographic candidate searches can expose multiple people’s personal information to a user or system and may enable enumeration attacks. Suggested revision: Require minimum search criteria, result limits, masking, rate limiting, role-based access, purpose controls, audit, and monitoring for misuse. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-143 discuss | in the document all mentions on GitHub record | ||
| PC-1504✎ edit📣 feedback | received | Core architects agent |
5.4.1 What AI readiness means §Client Registry, 5 p.119 l.Requirement 8 anchor: medium |
Ranked candidate results are required, but expected matching scores, thresholds, explanations, and reviewer actions are…Ranked candidate results are required, but expected matching scores, thresholds, explanations, and reviewer actions are not defined. Suggested revision: Define configurable thresholds, confidence representation, evidence displayed to authorised reviewers, no-match and uncertain-match handling, and test datasets representing the national population. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-143 discuss | in the document all mentions on GitHub record | ||
| PC-1505✎ edit📣 feedback | received | Core architects agent |
5.4.1 What AI readiness means §Client Registry, 5 p.119 l.Requirement 9 anchor: medium |
External verification returns an assurance level, but no common assurance framework is defined across foundational iden…External verification returns an assurance level, but no common assurance framework is defined across foundational identity, CRVS, biometrics, and local evidence. Suggested revision: Define a national identity-assurance model with evidence types, verification level, issuer trust, freshness, limitations, and appropriate uses. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1506✎ edit📣 feedback | received | Core architects Clinical agent |
5.4.1 What AI readiness means §Client Registry, 5 p.119 l.Requirement 10 anchor: medium |
The requirement elevates person linking and deduplication to mandatory but does not define acceptable matching quality …The requirement elevates person linking and deduplication to mandatory but does not define acceptable matching quality or minimum operational controls. Suggested revision: Add performance measures, representative evaluation, manual adjudication, merge protection, reversal, audit, monitoring, and clinical-risk assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-143 discuss | in the document all mentions on GitHub record | ||
| PC-1507✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.119 l.Requirement 10 anchor: medium |
“Merging combines them into one” may imply deletion or loss of the source records. Safe identity management generally p…“Merging combines them into one” may imply deletion or loss of the source records. Safe identity management generally preserves original records, identifiers, and provenance. Suggested revision: State that merging creates one active reference while preserving source records, historical identifiers, provenance, decisions, and reversibility. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-144 discuss | in the document all mentions on GitHub record | ||
| PC-1508✎ edit📣 feedback | received | Core architects agent |
5.4.1 What AI readiness means §Client Registry, 5 p.119 l.Requirement 11 anchor: medium |
Custom matching implementations are permitted without explicit independent validation or control over bias and safety.Custom matching implementations are permitted without explicit independent validation or control over bias and safety. Suggested revision: Require governance approval, documented features and weights, validation against representative data, subgroup analysis, versioning, change control, and monitoring before production use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-143 discuss | in the document all mentions on GitHub record | ||
| PC-1509✎ edit📣 feedback | received | Core architects Clinical agent |
5.4.1 What AI readiness means §Client Registry, 5 p.119-120 l.Requirement 12 anchor: medium |
Manual adjudication is Recommended, although uncertain matches can have significant clinical, privacy, and financial co…Manual adjudication is Recommended, although uncertain matches can have significant clinical, privacy, and financial consequences. Suggested revision: Make authorised adjudication mandatory where automated confidence is below the approved threshold or where the potential consequence is high. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-143 discuss | in the document all mentions on GitHub record | ||
| PC-1510✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.120 l.Requirement 13 anchor: medium |
Unlinking and merge reversal are only Recommended despite their importance in correcting identity errors with serious d…Unlinking and merge reversal are only Recommended despite their importance in correcting identity errors with serious downstream consequences. Suggested revision: Make reversal capability mandatory or require an equivalent corrective process that preserves full history and propagates corrections safely. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-144 discuss | in the document all mentions on GitHub record | ||
| PC-1511✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.120 l.Requirements 14-15 anchor: medium |
Family, household, and spousal relationships can be highly sensitive and may be unsafe in contexts involving domestic v…Family, household, and spousal relationships can be highly sensitive and may be unsafe in contexts involving domestic violence, stigma, migration, or contested relationships. Suggested revision: Make these capabilities conditional by national use case. Require restricted access, relationship provenance, validity, consent or legal basis, sensitivity classification, dispute handling, and safety review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-141 discuss | in the document all mentions on GitHub record | ||
| PC-1512✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
Client Registry §Client Registry, 5 p.120 l.Requirement 14 anchor: medium |
“Mother’s or guardian’s canonical record” may not support diverse family structures, unknown parentage, adoption, surro…“Mother’s or guardian’s canonical record” may not support diverse family structures, unknown parentage, adoption, surrogacy, or multiple guardians. Suggested revision: Use inclusive role-based relationships such as birth parent, legal parent, guardian, caregiver, or representative, with jurisdiction-specific value sets and validity periods. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-141 discuss | in the document all mentions on GitHub record | ||
| PC-1513✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.120 l.Requirement 16 anchor: medium |
Audit logging covers changes and access events but does not mention purpose, legal basis, query criteria, result disclo…Audit logging covers changes and access events but does not mention purpose, legal basis, query criteria, result disclosure, emergency access, or failed access attempts. Suggested revision: Define minimum audit events and fields, tamper evidence, retention, monitoring, access to logs, privacy safeguards, alerting, and incident investigation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-1514✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.120 l.Requirement 17 anchor: medium |
Role-based access control alone may be insufficient for a national Client Registry. Access may depend on organisation, …Role-based access control alone may be insufficient for a national Client Registry. Access may depend on organisation, purpose, relationship, location, assurance, consent, and emergency context. Suggested revision: Require policy-based controls that may combine role, attributes, purpose, organisation, assurance, consent or legal authority, and contextual conditions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-1515✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.120 l.Requirement 18 anchor: medium |
The requirement again uses “pseudo-anonymised.” In addition, generating pseudonymous identifiers within the Client Regi…The requirement again uses “pseudo-anonymised.” In addition, generating pseudonymous identifiers within the Client Registry may create a central linkability service whose misuse could enable broad surveillance. Suggested revision: Use “pseudonymised” and require strict separation, access controls, purpose-specific pseudonyms, authorised linkage processes, key governance, and re-identification safeguards. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-145 discuss | in the document all mentions on GitHub record | ||
| PC-1516✎ edit📣 feedback | received | Core architects agent, medium |
Client Registry §Client Registry, 5 p.120-121 l.Requirement 19 anchor: medium |
“Conformance with applicable data-protection legislation and principles” is too broad to serve as a testable requiremen…“Conformance with applicable data-protection legislation and principles” is too broad to serve as a testable requirement. Suggested revision: Break it into testable controls covering data minimisation, purpose specification, access, correction, retention, transparency, security, records of processing, impact assessment, and data-subject rights. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-145 discuss | in the document all mentions on GitHub record | ||
| PC-1517✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.121 l.Requirement 20 anchor: medium |
The requirement combines IHE PMIR, PIX, and FHIR Patient conventions without specifying versions, actors, transaction o…The requirement combines IHE PMIR, PIX, and FHIR Patient conventions without specifying versions, actors, transaction options, or national profiles. Suggested revision: Publish a national Client Registry implementation guide identifying selected profiles, versions, options, resources, identifier rules, operations, security, terminology, and conformance tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1518✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.121 l.Requirement 20 anchor: medium |
“Conformant with applicable IHE profiles and FHIR conventions” is not sufficiently precise or directly testable.“Conformant with applicable IHE profiles and FHIR conventions” is not sufficiently precise or directly testable. Suggested revision: Replace “conventions” with a specific normative profile and capability statement, accompanied by validation rules and actor-level tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1519✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.121 l.Requirement 21 anchor: medium |
Transaction monitoring is Recommended, although identity services are nationally critical and require operational obser…Transaction monitoring is Recommended, although identity services are nationally critical and require operational observability. Suggested revision: Make minimum monitoring mandatory, including volume, latency, failures, matching outcomes, unusual access, source system, destination, and service availability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | ||
| PC-1520✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Client Registry §Client Registry, 5 p.121 l.Requirement 22 anchor: medium |
The requirement refers to Shared Health Record ID synchronisation, while the document adopts Lifelong Health Record as …The requirement refers to Shared Health Record ID synchronisation, while the document adopts Lifelong Health Record as its preferred term. Suggested revision: Update the terminology and define whether synchronisation refers to identifiers, references, or actual identity records. Avoid duplicating person demographics in the LHR. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1521✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.121 l.Requirement 23 anchor: medium |
Comprehensive error handling is only Recommended despite its importance to safe identity workflows and integration.Comprehensive error handling is only Recommended despite its importance to safe identity workflows and integration. Suggested revision: Make essential error handling mandatory and define structured error codes, actionable responses, correlation identifiers, retry guidance, privacy-safe messages, and monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | ||
| PC-1522✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.121 l.Requirement 24 anchor: medium |
Subscription is Recommended without specifying event semantics, minimum payload, verification state, delivery guarantee…Subscription is Recommended without specifying event semantics, minimum payload, verification state, delivery guarantees, privacy, or correction events. Suggested revision: Publish an event specification covering event types, payload, identifiers, provenance, version, delivery, retry, deduplication, authorisation, audit, and handling of reversals. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-144 discuss | in the document all mentions on GitHub record | ||
| PC-1523✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.121 l.Requirement 25 anchor: medium |
“High availability and low latency” are mandatory but no measurable service levels or differentiated criticality are pr…“High availability and low latency” are mandatory but no measurable service levels or differentiated criticality are provided. Suggested revision: Define national performance and resilience profiles with availability, response time, throughput, recovery time, recovery point, dependency failure, degraded-mode operation, and monitoring requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | ||
| PC-1524✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 5 p.121 l.Requirement 25 anchor: medium |
Uniform low-latency expectations may not be realistic in remote or intermittently connected settings.Uniform low-latency expectations may not be realistic in remote or intermittently connected settings. Suggested revision: Define central and local service expectations, caching, asynchronous or offline workflows, timeouts, reconciliation, and safe fallback when live identity resolution is unavailable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | ||
| PC-1525✎ edit📣 feedback | received | Core architects agent, medium |
Client Registry §Client Registry, 6 p.122 l.Lines 196-200 |
The dataset is called a minimum dataset and is said to draw on WHO HUID, FHIR Patient, and IHE PMIR, but no field-level…The dataset is called a minimum dataset and is said to draw on WHO HUID, FHIR Patient, and IHE PMIR, but no field-level traceability is provided. Suggested revision: Add the source and rationale for each element, including whether it is required for identity resolution, communication, equity, reporting, or a particular national use case. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1526✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.Lines 196-200 |
The note says the data requirements are illustrative, while the table marks many fields Mandatory. This creates uncerta…The note says the data requirements are illustrative, while the table marks many fields Mandatory. This creates uncertainty over whether conformance requires every field or merely support for the field. Suggested revision: Distinguish schema support, conditional record requirement, and mandatory presence. Define applicability and permitted absent-data reasons. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1527✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“HUID” data element anchor: medium |
The HUID is mandatory, although earlier text permits several identity models and provisional registration.The HUID is mandatory, although earlier text permits several identity models and provisional registration. Suggested revision: Require a persistent registry identifier according to the country’s approved identity model, while allowing provisional identifiers and multiple linked identifier schemes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1528✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“First/given name” and “Family/surname” anchor: medium |
Requiring first and family names does not support mononymous people, cultures with different name structures, unknown n…Requiring first and family names does not support mononymous people, cultures with different name structures, unknown names, newborns, or persons using alternative names. Suggested revision: Use a flexible human-name structure supporting one or more names, use or type, local script, transliteration, period, preferred name, unknown values, and culturally appropriate formats. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1529✎ edit📣 feedback | received | Core architects agent, medium |
Client Registry §Client Registry, 6 p.122 l.“Date of birth” anchor: medium |
Full date or estimated date is mandatory, but no representation of precision, uncertainty, estimated status, or source …Full date or estimated date is mandatory, but no representation of precision, uncertainty, estimated status, or source is specified. Suggested revision: Represent date or age with precision, estimated indicator, source, confidence, and update history. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1530✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
Client Registry §Client Registry, 6 p.122 l.“Sex at birth” anchor: medium |
Sex at birth is mandatory for every national identity record, but its necessity depends on the identity-matching and ca…Sex at birth is mandatory for every national identity record, but its necessity depends on the identity-matching and care use case. It is sensitive, may be unknown or contested, and is distinct from administrative sex and clinical attributes. Suggested revision: Make it conditional where justified by defined purposes. Separate sex-related concepts clearly, permit unknown or undisclosed values, restrict access, and apply inclusive governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1531✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
Client Registry §Client Registry, 6 p.122 l.“Gender” anchor: medium |
“Gender identity” is included without defining the purpose, value set, confidentiality, update process, or distinction …“Gender identity” is included without defining the purpose, value set, confidentiality, update process, or distinction from administrative gender and clinically relevant sex characteristics. Suggested revision: Define each concept separately and collect only where necessary for a stated purpose, with appropriate privacy, terminology, access, and user-correction controls. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1532✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“Nationality/citizenship” anchor: medium |
Nationality is marked Mandatory despite the commitment to include refugees, stateless persons, undocumented migrants, a…Nationality is marked Mandatory despite the commitment to include refugees, stateless persons, undocumented migrants, and people without documentation. It may not be necessary for core health identity resolution. Suggested revision: Make nationality conditional or Recommended, support unknown, multiple, stateless, refugee, and not-disclosed states, and prohibit use as a condition for essential care. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1533✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“Current address” anchor: medium |
A physical address is Mandatory, but people may be homeless, displaced, nomadic, living in informal settlements, or una…A physical address is Mandatory, but people may be homeless, displaced, nomadic, living in informal settlements, or unable to provide a standard address. Suggested revision: Make address conditionally required where available. Support descriptive locations, landmarks, temporary addresses, contact locations, geocodes where appropriate, and no-fixed-address status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1534✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“Contact information” anchor: medium |
Telephone or email is Mandatory, which excludes people without personal devices, connectivity, literacy, or safe access…Telephone or email is Mandatory, which excludes people without personal devices, connectivity, literacy, or safe access to private communications. Suggested revision: Make contact information Recommended or conditional. Support trusted-contact details, preferred communication channel, communication restrictions, and absence without blocking registration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1535✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“Foundational identifiers” anchor: medium |
Foundational identifiers are Recommended and “where available and consented.” Consent may not be the only legal basis, …Foundational identifiers are Recommended and “where available and consented.” Consent may not be the only legal basis, and storing such identifiers increases linkage and breach risk. Suggested revision: Use “where legally authorised and necessary.” Require purpose limitation, restricted access, masking, verification status, and impact assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1536✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“Local/facility identifiers” anchor: medium |
Local identifiers are marked Mandatory, although a newly registered person may not yet possess any local identifier.Local identifiers are marked Mandatory, although a newly registered person may not yet possess any local identifier. Suggested revision: Require capability to store local identifiers when they exist, not mandatory presence in every person record. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-137 discuss | in the document all mentions on GitHub record | ||
| PC-1537✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“Mother’s/guardian’s name” anchor: medium |
Mother or guardian name is Mandatory for every person, not only newborns or dependent children. This is unnecessary and…Mother or guardian name is Mandatory for every person, not only newborns or dependent children. This is unnecessary and may be inappropriate for adults, people without known parents, diverse families, or sensitive circumstances. Suggested revision: Make this conditional for relevant child or dependent-person use cases and model it through governed person relationships rather than a mandatory free-text field. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-141 discuss | in the document all mentions on GitHub record | ||
| PC-1538✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122 l.“Household/family relationships” anchor: medium |
Household relationships are Recommended but highly sensitive and may change over time or be contested.Household relationships are Recommended but highly sensitive and may change over time or be contested. Suggested revision: Require purpose-specific collection, relationship provenance, effective periods, restricted access, safety review, and correction processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-141 discuss | in the document all mentions on GitHub record | ||
| PC-1539✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.122-123 l.“Photo” and “Biometric data” anchor: medium |
Photo is Recommended and biometrics Optional, but both introduce surveillance, breach, exclusion, spoofing, and misuse …Photo is Recommended and biometrics Optional, but both introduce surveillance, breach, exclusion, spoofing, and misuse risks. A photo is itself biometric-capable data. Suggested revision: Treat both as sensitive biometric or identity-verification data. Require legal authority, necessity, proportionality, security, retention limits, alternative pathways, and an impact assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-142 discuss | in the document all mentions on GitHub record | ||
| PC-1540✎ edit📣 feedback | received | Core architects agent, medium |
Client Registry §Client Registry, 6 p.123 l.“Record creation and update metadata” anchor: medium |
The metadata element includes dates and source user or system but omits effective period, verification status, source a…The metadata element includes dates and source user or system but omits effective period, verification status, source authority, reason for change, provenance, and record status. Suggested revision: Expand the lifecycle metadata and align it with the provenance and audit requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1541✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, 6 p.123 l.Notes 1-3 anchor: medium |
The biometric note appropriately requires privacy and equity assessment, but the same caution is not applied to mandato…The biometric note appropriately requires privacy and equity assessment, but the same caution is not applied to mandatory nationality, address, contact, sex-at-birth, family, and foundational-identifier data. Suggested revision: Apply data-minimisation and impact-assessment principles to the entire minimum dataset, not only biometrics. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-140 discuss | in the document all mentions on GitHub record | ||
| PC-1542✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, Governance p.123 l.Governance item 1 anchor: medium |
Multisector governance is required because the registry intersects with civil registration and social protection. Manda…Multisector governance is required because the registry intersects with civil registration and social protection. Mandatory participation from all sectors may not be necessary where they do not consume or contribute to the registry. Suggested revision: Require representation according to actual authority, dependency, and risk, while ensuring health, civil identity, data protection, affected communities, and relevant service operators are appropriately involved. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-138 discuss | in the document all mentions on GitHub record | ||
| PC-1543✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, Governance p.123 l.Governance item 1 anchor: medium |
The text says the Client Registry cannot be governed unilaterally by the Ministry of Health because its data is referen…The text says the Client Registry cannot be governed unilaterally by the Ministry of Health because its data is referenced across government. Cross-government reference should not automatically give other sectors governance rights over health-identity data. Suggested revision: Distinguish consultation and interoperability governance from decision authority over health-sector data and access. Preserve health-sector accountability and legal purpose boundaries. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-138 discuss | in the document all mentions on GitHub record | ||
| PC-1544✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, Governance p.123 l.Governance item 2 anchor: medium |
Linkage to foundational identity is correctly treated as a high-level policy decision, but the required assessment does…Linkage to foundational identity is correctly treated as a high-level policy decision, but the required assessment does not explicitly include human rights, security, service exclusion, or misuse by non-health authorities. Suggested revision: Add human-rights impact assessment, threat modelling, equity analysis, stakeholder consultation, misuse scenarios, independent oversight, and periodic review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-138 discuss | in the document all mentions on GitHub record | ||
| PC-1545✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Client Registry §Client Registry, Governance p.123 l.Governance item 3 anchor: medium |
The universal right to health registration is framed appropriately, but the guidance should distinguish registration fr…The universal right to health registration is framed appropriately, but the guidance should distinguish registration from entitlement to all services and ensure that failed matching does not delay care. Suggested revision: State that essential care must not depend on prior registration, possession of a foundational identifier, or successful real-time identity resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-139 discuss | in the document all mentions on GitHub record | ||
| PC-1546✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry, Governance p.123 l.Governance item 4 anchor: medium |
Merge and link decisions should be reviewable by the individual “where technically and legally feasible.” This qualific…Merge and link decisions should be reviewable by the individual “where technically and legally feasible.” This qualification may weaken practical redress. Suggested revision: Require a clear correction and review pathway with accessible support, representative or guardian mechanisms, response times, escalation, and protection against adverse consequences while disputes are resolved. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-144 discuss | in the document all mentions on GitHub record | ||
| PC-1547✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry overall p.115-123 l.Complete component description anchor: medium |
The component specifies many functions but does not provide a complete actor-and-transaction profile, security profile,…The component specifies many functions but does not provide a complete actor-and-transaction profile, security profile, matching-quality test set, or conformance test suite. Suggested revision: Publish a companion Client Registry implementation and conformance package containing actors, services, transactions, profiles, matching test datasets, privacy and security tests, performance requirements, and result-reporting templates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1548✎ edit📣 feedback | received | Core architects agent |
Client Registry §Client Registry overall p.115-123 l.Complete component description anchor: medium |
The specification assumes a relatively mature national ability to assign identifiers, govern sensitive demographics, op…The specification assumes a relatively mature national ability to assign identifiers, govern sensitive demographics, operate probabilistic matching, expose high-availability APIs, and coordinate multiple authorities. Suggested revision: Add progressive maturity levels, beginning with governed identifier cross-referencing and basic matching, then verified demographic services, eventing, advanced matching, and wider foundational-DPI integration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1549✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry p.124 l.Architecture placement anchor: medium |
The distinction among the Health Facility Registry, Master Facility List, and Common Geo-Registry is useful. However, d…The distinction among the Health Facility Registry, Master Facility List, and Common Geo-Registry is useful. However, describing the registry as “the technology” and the MFL as “the data” is too narrow. A registry is a governed capability comprising people, processes, data, technology, and services. Suggested revision: Replace with a sentence like: “The Health Facility Registry is the governed capability and supporting system through which facility records are created, validated, maintained, and published. The Master Facility List is an authoritative data product generated from that capability.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-146 discuss | in the document all mentions on GitHub record | ||
| PC-1550✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry p.124 l.Architecture placement anchor: medium |
The Common Geo-Registry is presented as a foundational component, although not every country classifies or implements g…The Common Geo-Registry is presented as a foundational component, although not every country classifies or implements geospatial reference data as foundational DPI. Suggested revision: Describe the CGR as a potential cross-sector authoritative geospatial capability. Where it does not exist, define how the Health Facility Registry can manage temporary reference data while remaining ready for later integration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1551✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 1 p.124 l.Lines 6-17 |
The intended scope includes clinical, logistics, community, outreach, temporary, mobile, and other public-health-releva…The intended scope includes clinical, logistics, community, outreach, temporary, mobile, and other public-health-relevant locations. This is broad and risks conflating facilities, service-delivery locations, organisations, sites, and temporary events. Suggested revision: Define a formal entity model distinguishing organisations, facilities, physical locations, service-delivery sites, mobile services, temporary sites, and events. Specify which entity types the registry governs directly. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-146 discuss | in the document all mentions on GitHub record | ||
| PC-1552✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 1 p.124 l.Lines 6-17 |
The phrase “all facilities…of direct relevance to the Ministry of Health’s mandate” may not cover decentralised systems…The phrase “all facilities…of direct relevance to the Ministry of Health’s mandate” may not cover decentralised systems in which subnational governments, regulators, defence authorities, or private bodies hold relevant authority. Suggested revision: Replace with “within the nationally defined scope of health-sector and public-health oversight,” allowing authority to be distributed according to the country’s legal and institutional arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-146 discuss | in the document all mentions on GitHub record | ||
| PC-1553✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 1 p.124 l.Lines 13-17 |
Maintaining one centrally governed record for every public, private, faith-based, and NGO facility may not be instituti…Maintaining one centrally governed record for every public, private, faith-based, and NGO facility may not be institutionally feasible in federal or decentralised settings. Suggested revision: Use “nationally governed authoritative reference arrangement” and allow centralised, federated, or hybrid implementation with clearly defined stewardship and reconciliation responsibilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-1554✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 1 p.124 l.Lines 18-23 |
The distinction between the registry and the MFL is helpful but may imply that a country cannot have an authoritative M…The distinction between the registry and the MFL is helpful but may imply that a country cannot have an authoritative MFL without the full technical registry described in Appendix C. Suggested revision: Clarify that countries may begin with a governed MFL and progressively establish stronger registry workflows, APIs, lifecycle management, validation, and interoperability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-146 discuss | in the document all mentions on GitHub record | ||
| PC-1555✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 1 p.124 l.Lines 24-35 |
The distinction among facility, building, location, and organisation is one of the section’s strongest features. Howeve…The distinction among facility, building, location, and organisation is one of the section’s strongest features. However, the component does not identify the logical model or standards used to represent these entities and relationships. Suggested revision: Add a conceptual entity-relationship model and map it to the selected national profiles, such as relevant FHIR and IHE mCSD resources and relationships. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-146 discuss | in the document all mentions on GitHub record | ||
| PC-1556✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 1 p.124 l.Lines 24-35 |
The text states that organisations appear in a separate organisational register, but no Organisation Registry is define…The text states that organisations appear in a separate organisational register, but no Organisation Registry is defined in the DPI-H component catalogue. Suggested revision: Identify the authoritative organisation source. Assess whether an Organisation Registry is required as DPI-F, DPI-H, or a shared government capability, and explain the interim arrangement where none exists. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-268 discuss | in the document all mentions on GitHub record | ||
| PC-1557✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 1 p.124 l.Lines 30-35 |
Temporary facilities are to receive distinct records, but the document does not describe when a temporary service shoul…Temporary facilities are to receive distinct records, but the document does not describe when a temporary service should be modelled as a facility, location, service event, or extension of an existing facility. Suggested revision: Add classification rules and examples based on operational responsibility, duration, location, services, reporting needs, and the requirement for independent identity and lifecycle history. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-146 discuss | in the document all mentions on GitHub record | ||
| PC-1558✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 1 p.125 l.Lines 36-43 |
The section correctly identifies temporal geography as a major challenge but does not state how historical boundary ver…The section correctly identifies temporal geography as a major challenge but does not state how historical boundary versions, facility assignments, and indicator recalculation should be represented technically. Suggested revision: Require persistent administrative-area identifiers, effective periods, versioned geometries, historical relationships, provenance, and defined rules for retrospective reporting and recalculation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1559✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 1 p.125 l.Lines 36-43 |
Maintaining precise historical geographic relationships may exceed the initial capacity of lower-resource settings.Maintaining precise historical geographic relationships may exceed the initial capacity of lower-resource settings. Suggested revision: Define maturity levels beginning with current administrative assignment and coordinates, followed by effective-period relationships, historical boundaries, and automated change propagation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1560✎ edit📣 feedback | received | Editorial Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 2 p.125 l.Lines 46-53 |
The examples of divergent facility identifiers and outdated operational status are credible, but several sentences are …The examples of divergent facility identifiers and outdated operational status are credible, but several sentences are grammatically awkward and do not cite evidence. Suggested revision: Edit for clarity and provide implementation evidence or label the examples as illustrative risks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1561✎ edit📣 feedback | received | Editorial agent |
Health Facility Registry §Health Facility Registry, 2 p.125 l.Lines 49-53 |
The sentence beginning “For example” contains inconsistent tense and agreement, including “may not always match” and “w…The sentence beginning “For example” contains inconsistent tense and agreement, including “may not always match” and “whose operational status have not been updated.” Suggested revision: Rewrite the paragraph using shorter, parallel examples and change “status have” to “status has.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-194 discuss | in the document all mentions on GitHub record | ||
| PC-1562✎ edit📣 feedback | received | Core architects agent, low |
Health Facility Registry §Health Facility Registry, 2 p.125 l.Lines 54-62 |
The section cites COVID-19 as demonstrating geolocated-facility-data gaps. The claim is relevant, but the source should…The section cites COVID-19 as demonstrating geolocated-facility-data gaps. The claim is relevant, but the source should support the specific stated consequences and not merely the existence of the WHO initiative. Suggested revision: Add an authoritative source documenting the identified planning and delivery problems and distinguish evidence from the motivation or objectives of the WHO initiative. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1563✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 2 p.125 l.Lines 63-74 |
The outcomes include workforce attribution, delivery routing, claims validation, coverage modelling, and surveillance. …The outcomes include workforce attribution, delivery routing, claims validation, coverage modelling, and surveillance. The relationship to the seven priority health goals is not shown explicitly. Suggested revision: Add a short mapping showing which registry services and data support each relevant health goal and what additional components are needed to realise the outcome. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1564✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 3 p.125 l.Lines 76-81 |
The scope includes “all facilities within the Ministry’s mandate” but still does not define the minimum inclusion crite…The scope includes “all facilities within the Ministry’s mandate” but still does not define the minimum inclusion criteria or whether non-service locations, virtual services, and administrative offices are included. Suggested revision: Publish nationally configurable inclusion rules and entity types, with explicit in-scope and out-of-scope examples. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-146 discuss | in the document all mentions on GitHub record | ||
| PC-1565✎ edit📣 feedback | received | Editorial agent |
Health Facility Registry §Health Facility Registry, 3 p.125-126 l.Lines 82-90 |
The term “multi-axial hierarchy” is technically meaningful but likely unfamiliar to many readers.The term “multi-axial hierarchy” is technically meaningful but likely unfamiliar to many readers. Suggested revision: Introduce it in plain language as “multiple concurrent hierarchies” and retain “multi-axial” as a technical term in parentheses. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-147 discuss | in the document all mentions on GitHub record | ||
| PC-1566✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 3 p.125-126 l.Lines 82-90 |
Administrative, operational, referral, and catchment relationships are all called hierarchies, although referral networ…Administrative, operational, referral, and catchment relationships are all called hierarchies, although referral networks and catchment relationships may be many-to-many networks rather than strict trees. Suggested revision: Model administrative and operational structures separately from referral networks and catchment relationships. Avoid requiring all relationships to form a hierarchy. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-147 discuss | in the document all mentions on GitHub record | ||
| PC-1567✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 91-93 |
Catchment areas are presented as facility attributes enabling equity analysis. Catchments may be overlapping, dynamic, …Catchment areas are presented as facility attributes enabling equity analysis. Catchments may be overlapping, dynamic, estimated, service-specific, seasonal, or affected by patient choice and transport. Suggested revision: Represent catchment definitions with method, service type, source, confidence, effective period, geometry or community list, and an indication of whether the catchment is administrative, modelled, or observed. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-147 discuss | in the document all mentions on GitHub record | ||
| PC-1568✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 94-99 |
Geographic coordinates and administrative linkages are combined in one core attribute. A facility location and its admi…Geographic coordinates and administrative linkages are combined in one core attribute. A facility location and its administrative assignment are related but distinct and may have different sources and update cycles. Suggested revision: Model coordinates, physical address, location geometry, administrative-area relationships, source, precision, verification status, and effective period separately. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1569✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 94-99 |
Requiring precise coordinates for every facility may be difficult or unsafe for sensitive locations, mobile services, s…Requiring precise coordinates for every facility may be difficult or unsafe for sensitive locations, mobile services, shelters, or facilities in conflict settings. Suggested revision: Allow precision and disclosure to vary by use case. Support restricted coordinates, approximate locations, moving locations, and security-based access controls. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1570✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 100-103 |
Facility status and service changes are included, but the component does not define the distinction among legal status,…Facility status and service changes are included, but the component does not define the distinction among legal status, operational status, accreditation status, temporary availability, and service-specific availability. Suggested revision: Define separate status dimensions, controlled values, effective periods, source authority, verification status, and rules governing public display. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1571✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 104-107 |
A configurable attribute schema is necessary, but uncontrolled national or subnational extensions could undermine inter…A configurable attribute schema is necessary, but uncontrolled national or subnational extensions could undermine interoperability. Suggested revision: Require governed extension rules, published definitions, terminology bindings, effective versions, compatibility policy, and conformance testing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1572✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 108-112 |
Multi-identifier support includes GLNs, supply-chain codes, and provider codes but does not require assigning authority…Multi-identifier support includes GLNs, supply-chain codes, and provider codes but does not require assigning authority, identifier status, effective period, or scope. Suggested revision: Apply the common identifier pattern proposed for the Client Registry, including system, authority, type, use, status, period, provenance, and verification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1573✎ edit📣 feedback | received | Editorial agent |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 113-123 |
“Standards-based access and interoperability” appears twice, once as an incomplete bullet and again as a full bullet.“Standards-based access and interoperability” appears twice, once as an incomplete bullet and again as a full bullet. Suggested revision: Remove the duplicate incomplete bullet and renumber or reformat the list consistently. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-194 discuss | in the document all mentions on GitHub record | ||
| PC-1574✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 114-120 |
Mobile facilities are described as being relocated through lifecycle updates. A genuinely mobile service may operate ac…Mobile facilities are described as being relocated through lifecycle updates. A genuinely mobile service may operate across routes and schedules rather than having one changing point location. Suggested revision: Support mobile-service routes, service areas, schedules, operating periods, host relationships, and encounter-level location provenance rather than repeatedly overwriting a single coordinate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1575✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 3 p.126 l.Lines 114-120 |
Retrospective preservation of services and populations served is required, but this information belongs partly in servi…Retrospective preservation of services and populations served is required, but this information belongs partly in service-delivery or encounter systems rather than the facility master record. Suggested revision: Keep the registry focused on facility identity, status, service capability, and location history. Reference operational systems for actual services delivered and populations served. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1576✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 4 p.126-127 l.Lines 127-153 |
The relationship with the Common Geo-Registry is well described, but the use of “would” throughout makes it unclear whe…The relationship with the Common Geo-Registry is well described, but the use of “would” throughout makes it unclear whether CGR integration is normative, recommended, or illustrative. Suggested revision: Apply explicit normative language and distinguish requirements where a nationally governed geospatial source exists from transitional arrangements where it does not. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1577✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 130-132 |
The CGR is assumed to provide historical administrative boundaries and query by date. Not all geospatial registries sup…The CGR is assumed to provide historical administrative boundaries and query by date. Not all geospatial registries support temporal versioning or event notification. Suggested revision: Treat temporal and notification services as target capabilities and require discovery of the actual services available from the national geospatial authority. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1578✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 134-143 |
Boundary changes trigger facility-linkage review, but the responsible authority, review timeframe, automatic versus man…Boundary changes trigger facility-linkage review, but the responsible authority, review timeframe, automatic versus manual update rules, and downstream notification are not specified. Suggested revision: Define the governance workflow, responsible stewards, change event, impact analysis, approval, effective date, propagation, and historical recalculation obligations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1579✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 144-147 |
The referential-integrity explanation implies that geographic data is maintained once and referenced everywhere. Derive…The referential-integrity explanation implies that geographic data is maintained once and referenced everywhere. Derived or operational geographic information may still be maintained locally for performance or offline use. Suggested revision: State that authoritative geographic definitions should be governed once, while controlled copies, caches, or derived datasets may be maintained with version and synchronisation controls. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1580✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 148-153 |
Where no CGR exists, the Health Facility Registry manages geographic reference data internally. The transition to a lat…Where no CGR exists, the Health Facility Registry manages geographic reference data internally. The transition to a later CGR could be complex if local identifiers and geometries diverge. Suggested revision: Require persistent local identifiers, provenance, export, versioning, mapping readiness, separation of facility and geography data, and a future reconciliation plan. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1581✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 156-160 |
The text identifies product, facility, and provider as the three supply-chain master-data pillars but conflates provide…The text identifies product, facility, and provider as the three supply-chain master-data pillars but conflates provider data with the Health Workforce Registry. Suppliers, organisations, contracts, and logistics locations are also needed. Suggested revision: Describe the relevant master-data domains more precisely and distinguish practitioner, facility, organisation, supplier, product, and location identities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-268 discuss | in the document all mentions on GitHub record | ||
| PC-1582✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 162-166 |
The section says mCSD permits joint querying of facility and workforce data. mCSD represents care services through orga…The section says mCSD permits joint querying of facility and workforce data. mCSD represents care services through organisations, locations, practitioners, practitioner roles, and healthcare services, not simply two separate registries. Suggested revision: Align the component model with the full mCSD entity structure and explain how queries are federated or coordinated across authoritative sources. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-162 discuss | in the document all mentions on GitHub record | ||
| PC-1583✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 167-171 |
Clinical records and consent records are expected to use canonical facility identifiers. This is appropriate, but histo…Clinical records and consent records are expected to use canonical facility identifiers. This is appropriate, but historical facility status and identifier changes must remain resolvable. Suggested revision: Require persistent identifiers, alias history, status, effective periods, and resolution of retired or merged facility identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1584✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 172-177 |
The Benefits Package Registry uses the Facility Registry for provider empanelment. Facility identity and capability sup…The Benefits Package Registry uses the Facility Registry for provider empanelment. Facility identity and capability support empanelment, but contractual participation and scheme status belong elsewhere. Suggested revision: State that the Facility Registry supplies authoritative facility identity and service attributes, while empanelment and contracting are managed by financing or contract-management systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1585✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 4 p.127 l.Lines 176-177 |
Financial systems are said to use the Facility Registry for payment routing. Facility identity does not necessarily ide…Financial systems are said to use the Facility Registry for payment routing. Facility identity does not necessarily identify the legal payee or banking destination. Suggested revision: Distinguish facility identity from organisation, contract, creditor, and payment-account information maintained by appropriate authoritative systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1586✎ edit📣 feedback | received | Metadata registries agent |
Health Facility Registry §Health Facility Registry, 4 p.128 l.Lines 178-180 |
Facility type, ownership, and service classifications use terminology services, but no international or national refere…Facility type, ownership, and service classifications use terminology services, but no international or national reference classifications are identified. Suggested revision: Identify appropriate reference vocabularies where available and require nationally governed value sets, mappings, and versioning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1587✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.128 l.Lines 183-189 |
The requirement sources are listed, but the appendix does not provide field-level traceability to OpenHIE, WHO, UNICEF,…The requirement sources are listed, but the appendix does not provide field-level traceability to OpenHIE, WHO, UNICEF, or GHFD guidance. Suggested revision: Add a traceability matrix showing the source, version, original status, DPI-H change, rationale, and test method for each requirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1588✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.128 l.Requirements table anchor: medium |
Requirement statuses again use Required and Recommended rather than the normative language promised in Section 3.5.2.Requirement statuses again use Required and Recommended rather than the normative language promised in Section 3.5.2. Suggested revision: Harmonise the terminology across all component specifications and define conditional applicability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1589✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.128 l.Requirement 1 anchor: medium |
Assigning a unique national facility identifier is required, but the identifier lifecycle, assigning authority, merger,…Assigning a unique national facility identifier is required, but the identifier lifecycle, assigning authority, merger, split, relocation, retirement, and reuse rules are not stated. Suggested revision: Publish an identifier policy covering creation, persistence, non-reuse, aliases, replacement, merger, split, retirement, and historical resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1590✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.128 l.Requirement 1 anchor: medium |
Requiring the full minimum dataset before creating a record may prevent provisional registration of temporary, remote, …Requiring the full minimum dataset before creating a record may prevent provisional registration of temporary, remote, emergency, or newly identified facilities. Suggested revision: Allow provisional records with minimum identity, location, status, source, and verification level, followed by time-bound completion and review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1591✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.128 l.Requirement 2 anchor: medium |
The requirement makes schema configurability mandatory but references LIMR governance only as Recommended. A configurab…The requirement makes schema configurability mandatory but references LIMR governance only as Recommended. A configurable schema without mandatory governance can cause divergence. Suggested revision: Require all schema changes to follow a governed national process. A dedicated LIMR platform may remain optional according to maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1592✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.128 l.Requirement 3 anchor: medium |
The minimum dataset requirement includes services, workforce by cadre, operating hours, and infrastructure attributes. …The minimum dataset requirement includes services, workforce by cadre, operating hours, and infrastructure attributes. These may not be consistently available or maintained in the foundational registry. Suggested revision: Separate mandatory signature data from optional or conditionally maintained service-readiness data and identify authoritative sources and update frequency. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1593✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.128 l.Requirement 3 anchor: medium |
Workforce numbers by cadre duplicate data that may be derived from the Health Workforce Registry and employment or depl…Workforce numbers by cadre duplicate data that may be derived from the Health Workforce Registry and employment or deployment systems. Suggested revision: Use references or derived views rather than maintaining duplicate workforce counts as authoritative facility master data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1594✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.128-129 l.Requirement 4 anchor: medium |
Facility status and service changes are mandatory, but no controlled status model, validation authority, propagation ti…Facility status and service changes are mandatory, but no controlled status model, validation authority, propagation timeframe, or notification requirements are included. Suggested revision: Define the status model, permissible transitions, source authority, effective dates, approval, audit, downstream propagation, and test cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1595✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.129 l.Requirement 5 anchor: medium |
Multi-identifier cross-referencing is mandatory but does not specify handling of duplicate, conflicting, reused, or ret…Multi-identifier cross-referencing is mandatory but does not specify handling of duplicate, conflicting, reused, or retired external codes. Suggested revision: Add identifier-status management, assigning authority, confidence, effective period, conflict resolution, and historical cross-reference retention. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1596✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.129 l.Requirement 6 anchor: medium |
The requirement describes administrative, operational, and referral or catchment structures as three “location hierarch…The requirement describes administrative, operational, and referral or catchment structures as three “location hierarchies.” Referral and catchment relationships may not be hierarchical. Suggested revision: Rename the capability Multiple organisational, geographic, referral, and catchment relationships, and use relationship types appropriate to each structure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-147 discuss | in the document all mentions on GitHub record | ||
| PC-1597✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.129 l.Requirement 6 anchor: medium |
Requiring all three relationship structures may be excessive where countries do not formally define referral networks o…Requiring all three relationship structures may be excessive where countries do not formally define referral networks or facility catchments. Suggested revision: Make each structure conditional based on national policy and selected use cases, while requiring support for multiple relationship types. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-147 discuss | in the document all mentions on GitHub record | ||
| PC-1598✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.129 l.Requirement 7 anchor: medium |
Start and end dates alone may not adequately represent uncertain, planned, retrospective, or disputed assignments.Start and end dates alone may not adequately represent uncertain, planned, retrospective, or disputed assignments. Suggested revision: Add status, source, approval, recorded date, effective period, confidence, and dispute or supersession handling. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1599✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.129 l.Requirement 8 anchor: medium |
Catchment management is Recommended but may require geospatial expertise and population data unavailable in many settin…Catchment management is Recommended but may require geospatial expertise and population data unavailable in many settings. Suggested revision: Provide progressive options using community lists, administrative approximations, service-area models, or polygons, each with source and confidence metadata. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-147 discuss | in the document all mentions on GitHub record | ||
| PC-1600✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.130 l.Requirement 9 anchor: low |
Coordinates must meet a “defined precision standard,” but no precision, accuracy, verification, datum, or coordinate-re…Coordinates must meet a “defined precision standard,” but no precision, accuracy, verification, datum, or coordinate-reference-system requirements are specified. Suggested revision: Define coordinate reference system, expected accuracy, precision, capture method, verification, quality status, source, and handling of restricted locations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1601✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.130 l.Requirement 10 anchor: medium |
Integration with a CGR is Recommended whenever one exists, but authoritative geospatial sources may not provide an API …Integration with a CGR is Recommended whenever one exists, but authoritative geospatial sources may not provide an API or notification service. Suggested revision: Make integration conditional on service availability and specify acceptable alternatives, including periodic synchronisation, governed imports, and manual reconciliation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-267 discuss | in the document all mentions on GitHub record | ||
| PC-1602✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.130 l.Requirement 11 anchor: medium |
Querying by geography, service type, and operational status is required through standards “such as mCSD,” but no specif…Querying by geography, service type, and operational status is required through standards “such as mCSD,” but no specific national profile, actors, or search semantics are defined. Suggested revision: Publish a national mCSD or equivalent implementation guide defining resources, profiles, search parameters, terminology, paging, history, security, and conformance tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | ||
| PC-1603✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.130 l.Requirement 12 anchor: medium |
Searching by any attribute may expose sensitive facilities, restricted locations, or operational details.Searching by any attribute may expose sensitive facilities, restricted locations, or operational details. Suggested revision: Apply attribute-level access policies, result filtering, rate limiting, masking, audit, and security classifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1604✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.130 l.Requirement 13 anchor: medium |
Public access to facility information is valuable but service descriptions and operating hours may be inaccurate, unava…Public access to facility information is valuable but service descriptions and operating hours may be inaccurate, unavailable, or unsafe to publish for sensitive facilities. Suggested revision: Define a public-data subset, publication approval, freshness indicators, update responsibility, accessibility and language requirements, and security exceptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1605✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.130 l.Requirement 13 anchor: medium |
Public facility data should be usable by people with disabilities, limited literacy, multiple languages, and low connec…Public facility data should be usable by people with disabilities, limited literacy, multiple languages, and low connectivity, not merely technically accessible. Suggested revision: Require accessible, multilingual, low-bandwidth formats and downloadable or offline-compatible facility directories where appropriate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1606✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.130 l.Requirement 14 anchor: medium |
Full version history is appropriately mandatory, but the requirement does not distinguish correction, supersession, eff…Full version history is appropriately mandatory, but the requirement does not distinguish correction, supersession, effective-time history, transaction-time history, or audit history. Suggested revision: Define the required temporal model and ensure historical queries can reproduce the facility state applicable at a specified date. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1607✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.131 l.Requirement 15 anchor: medium |
Audit logging covers authoring and imports but does not explicitly include queries, data disclosures, failed access, bu…Audit logging covers authoring and imports but does not explicitly include queries, data disclosures, failed access, bulk exports, API clients, or public-data publication. Suggested revision: Define complete audit coverage proportionate to sensitivity, including access, export, configuration, publication, and security events. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-1608✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 5 p.131 l.Requirement 16 anchor: medium |
Example roles such as Master Administrator, Data Curator, and Health Officer are implementation-specific and role-based…Example roles such as Master Administrator, Data Curator, and Health Officer are implementation-specific and role-based access alone may be insufficient. Suggested revision: Define minimum responsibilities rather than fixed role names and allow attribute, organisation, geography, purpose, and data-sensitivity controls. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-1609✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.131 l.Requirement 17 anchor: medium |
The registry must align with or serve as the source for the MFL. “Align with” could permit two independently maintained…The registry must align with or serve as the source for the MFL. “Align with” could permit two independently maintained authoritative datasets. Suggested revision: Require one governed authoritative arrangement. Any separate MFL publication should be derived from or formally synchronised with the registry under clear precedence rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-146 discuss | in the document all mentions on GitHub record | ||
| PC-1610✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.131 l.Requirement 18 anchor: medium |
Joint facility and workforce queries are required from the Facility Registry API, even though workforce data may be gov…Joint facility and workforce queries are required from the Facility Registry API, even though workforce data may be governed and served separately. Suggested revision: Treat joint discovery as a coordinated or federated service capability. Do not require the Facility Registry itself to hold or expose authoritative workforce records. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-162 discuss | in the document all mentions on GitHub record | ||
| PC-1611✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.131 l.Requirement 19 anchor: medium |
Bidirectional push and pull could allow downstream systems to overwrite authoritative facility data without clear sourc…Bidirectional push and pull could allow downstream systems to overwrite authoritative facility data without clear source and approval rules. Suggested revision: Define source systems, permitted directions, proposal-versus-authoritative update workflows, validation, conflict resolution, acknowledgement, and audit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-196 discuss | in the document all mentions on GitHub record | ||
| PC-1612✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.131 l.Requirement 20 anchor: medium |
Bulk import is mandatory but does not specify validation, duplicate detection, preview, rollback, provenance, error rep…Bulk import is mandatory but does not specify validation, duplicate detection, preview, rollback, provenance, error reporting, or approval before publication. Suggested revision: Add staged import, validation, matching, dry run, error report, approval, rollback, provenance, and duplicate-resolution requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-196 discuss | in the document all mentions on GitHub record | ||
| PC-1613✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.131 l.Requirement 21 anchor: medium |
Notifications are Recommended despite the operational importance of closures, relocations, identifier changes, and serv…Notifications are Recommended despite the operational importance of closures, relocations, identifier changes, and service availability changes. Suggested revision: Make critical lifecycle-event notification mandatory where subscribing systems depend on timely status, while allowing different delivery mechanisms according to maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1614✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 5 p.132 l.Requirement 22 anchor: medium |
High availability is mandatory but not measurable and may not be required equally for every function. Public search, au…High availability is mandatory but not measurable and may not be required equally for every function. Public search, authoring, and synchronous validation may have different criticality. Suggested revision: Define service classes and measurable availability, latency, recovery, offline access, and degraded-mode requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | ||
| PC-1615✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.132 l.Lines 202-208 anchor: medium |
Mandatory signature elements are expected before an active record can be published, but the publication states and mini…Mandatory signature elements are expected before an active record can be published, but the publication states and minimum completeness thresholds are not defined. Suggested revision: Define draft, provisional, verified, active, inactive, restricted, and retired states, including the validation and approval criteria for each. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-1616✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.132 l.“Facility unique identifier” anchor: medium |
The identifier is described as “non-intelligent,” which is appropriate, but identifier format, namespace, check digit, …The identifier is described as “non-intelligent,” which is appropriate, but identifier format, namespace, check digit, resolver, and governance are not defined. Suggested revision: Publish a national identifier policy and resolver approach without embedding mutable facility attributes in the identifier. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1617✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.132 l.“Facility name” anchor: medium |
Official and common names are included, but multilingual names, abbreviations, historical names, and local-script names…Official and common names are included, but multilingual names, abbreviations, historical names, and local-script names are not addressed. Suggested revision: Support multiple names with type, language, script, validity period, preferred-use context, and source. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1618✎ edit📣 feedback | received | Metadata registries Core architects Supply chain agent, medium |
Health Facility Registry §Health Facility Registry, 6 p.132 l.“Facility type” anchor: medium |
One field appears to combine service level, clinical type, and logistics type. A single facility may have several funct…One field appears to combine service level, clinical type, and logistics type. A single facility may have several functions that do not fit one classification. Suggested revision: Separate facility category, service-delivery level, logistics role, and service capabilities, using governed value sets and multiple classifications where necessary. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1619✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.132 l.“Facility ownership and managing authority” anchor: medium |
Legal owner and managing authority are included in one element, although ownership, operator, parent organisation, regu…Legal owner and managing authority are included in one element, although ownership, operator, parent organisation, regulator, and funder may differ. Suggested revision: Model these as relationships to authoritative organisation records, each with role and effective period. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1620✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.132 l.“Physical address” anchor: medium |
A conventional address may be unavailable in rural, informal, mobile, or emergency settings.A conventional address may be unavailable in rural, informal, mobile, or emergency settings. Suggested revision: Support structured address, free-text location description, landmarks, settlement or administrative references, geocode, and no-formal-address status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1621✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“Geographic coordinates” anchor: medium |
Publishing exact coordinates for all facilities may expose sensitive service locations or populations.Publishing exact coordinates for all facilities may expose sensitive service locations or populations. Suggested revision: Add coordinate sensitivity, public-versus-restricted precision, security classification, and approved disclosure rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1622✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“Administrative hierarchy linkage” anchor: medium |
The description lists health-administrative, supply-chain, and political hierarchies, while earlier text distinguishes …The description lists health-administrative, supply-chain, and political hierarchies, while earlier text distinguishes administrative, operational, and referral or catchment relationships. Suggested revision: Harmonise the relationship categories throughout the component and avoid treating supply-chain or referral networks as strict administrative hierarchies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-147 discuss | in the document all mentions on GitHub record | ||
| PC-1623✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“Catchment area population size” anchor: medium |
Population size is treated as a facility attribute, but it is a derived estimate dependent on census, projections, boun…Population size is treated as a facility attribute, but it is a derived estimate dependent on census, projections, boundaries, time, and methodology. Suggested revision: Store or reference the estimate with source, reference date, method, confidence, population definition, and version rather than treating it as stable master data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-147 discuss | in the document all mentions on GitHub record | ||
| PC-1624✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“Contact information” anchor: medium |
Contact information is Mandatory, although some remote, temporary, or mobile facilities may lack direct telephone or em…Contact information is Mandatory, although some remote, temporary, or mobile facilities may lack direct telephone or email contacts. Suggested revision: Make it conditional and support organisational, regional, radio, referral-network, or alternative contact mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1625✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“Common and mapped identifiers” anchor: medium |
All known external identifiers are marked Mandatory. Not every facility will have identifiers in all referenced schemes.All known external identifiers are marked Mandatory. Not every facility will have identifiers in all referenced schemes. Suggested revision: Require the capability to maintain available external identifiers, with at least the canonical national identifier mandatory. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1626✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“Type of services offered” anchor: medium |
Service availability is marked Recommended and may change more frequently than facility identity information. Without c…Service availability is marked Recommended and may change more frequently than facility identity information. Without clear update responsibility, published service directories may become unreliable. Suggested revision: Define the authoritative source, update frequency, verification method, effective period, temporary availability, and freshness indicator for services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1627✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“HRH numbers by cadre” anchor: medium |
Storing workforce counts in the Facility Registry duplicates or aggregates data held by workforce, HR, deployment, or s…Storing workforce counts in the Facility Registry duplicates or aggregates data held by workforce, HR, deployment, or scheduling systems and may become stale. Suggested revision: Treat this as a derived view or linked indicator rather than authoritative facility master data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1628✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“Infrastructure attributes” anchor: medium |
Electricity, water, sanitation, and connectivity are operationally important but may vary over time and require frequen…Electricity, water, sanitation, and connectivity are operationally important but may vary over time and require frequent assessment. Suggested revision: Record them as dated service-readiness observations or linked assessment data, not timeless facility attributes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1629✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, 6 p.133 l.“Opening and closing times” anchor: medium |
General hours do not capture emergency availability, seasonal schedules, temporary closures, appointment requirements, …General hours do not capture emergency availability, seasonal schedules, temporary closures, appointment requirements, or service-specific hours. Suggested revision: Use a structured availability model supporting service-specific schedules, exceptions, holidays, temporary changes, and effective periods. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-150 discuss | in the document all mentions on GitHub record | ||
| PC-1630✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, Governance p.134 l.Governance item 1 anchor: medium |
Multiple contributor authorities are recognised, but the document does not provide an attribute-level stewardship matri…Multiple contributor authorities are recognised, but the document does not provide an attribute-level stewardship matrix or conflict-resolution process. Suggested revision: Require a stewardship matrix identifying authoritative source, contributor, verifier, approver, update frequency, conflict rules, and service-level expectations for each data domain. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-151 discuss | in the document all mentions on GitHub record | ||
| PC-1631✎ edit📣 feedback | received | Editorial agent, medium |
Health Facility Registry §Health Facility Registry, Governance p.134 l.Governance item 1 anchor: medium |
The claim that faith-based or private facilities provide more than 30% of services in some countries needs a precise so…The claim that faith-based or private facilities provide more than 30% of services in some countries needs a precise source and context. Suggested revision: Cite the relevant source, countries, service definition, and reporting period, or use more general wording. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1632✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, Governance p.134 l.Governance item 2 anchor: medium |
Boundary changes require cross-institutional coordination, but governance is framed mainly around notification and retr…Boundary changes require cross-institutional coordination, but governance is framed mainly around notification and retrospective calculation. Legal authority, resource implications, and public communication are omitted. Suggested revision: Add decision authority, implementation date, funding, system-impact analysis, public communication, downstream acceptance, and dispute resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-151 discuss | in the document all mentions on GitHub record | ||
| PC-1633✎ edit📣 feedback | received | Core architects agent, medium |
Health Facility Registry §Health Facility Registry, Governance p.134 l.Governance item 3 anchor: medium |
The distinction between data owner and data custodian is introduced without definitions and may conflict with the termi…The distinction between data owner and data custodian is introduced without definitions and may conflict with the terminology used elsewhere in the document. Suggested revision: Use the consistent responsibility model recommended for Section 3.4, covering accountable authority, authoritative source, steward, custodian, operator, and contributor. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-151 discuss | in the document all mentions on GitHub record | ||
| PC-1634✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry, Governance p.134 l.Governance item 4 anchor: medium |
The registry is described as a public good and facility identity and location data should be publicly accessible. Some …The registry is described as a public good and facility identity and location data should be publicly accessible. Some facilities or services require restricted disclosure for safety, confidentiality, or security reasons. Suggested revision: Establish a presumption of public access to a defined subset, subject to documented and proportionate exceptions and differentiated location precision. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-148 discuss | in the document all mentions on GitHub record | ||
| PC-1635✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
Health Facility Registry §Health Facility Registry overall p.124-134 l.Complete component description anchor: medium |
The component has detailed requirements but lacks a complete implementation and conformance package, including entity p…The component has detailed requirements but lacks a complete implementation and conformance package, including entity profiles, workflow actors, event specifications, test data, geographic validation, and service-level tests. Suggested revision: Publish a companion package containing the logical model, mCSD or equivalent profiles, terminology, identifier rules, event model, bulk-import specification, geographic tests, security tests, and conformance suite. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1636✎ edit📣 feedback | received | Core architects agent |
Health Facility Registry §Health Facility Registry overall p.124-134 l.Complete component description anchor: medium |
The target component assumes advanced temporal geography, comprehensive private-sector participation, service directori…The target component assumes advanced temporal geography, comprehensive private-sector participation, service directories, notification, versioning, high availability, and joint workforce queries. Suggested revision: Define progressive maturity levels, beginning with a governed MFL and persistent identifiers, then APIs, lifecycle management, cross-references, temporal geography, service discovery, eventing, and coordinated multi-registry queries. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1637✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry p.135 l.Architecture placement anchor: medium |
The distinction among the Health Workforce Registry, HRIS, and Learning Management System is useful. However, the regis…The distinction among the Health Workforce Registry, HRIS, and Learning Management System is useful. However, the registry is described as holding the authoritative record of what a worker is “qualified and licensed to do,” although authority may be distributed among professional councils, employers, education institutions, and programme authorities. [draft-for-...idance.pdf | PDF] Suggested revision: Describe it as the authoritative national reference arrangement that consolidates or links identity, qualification, registration, licensing, and recognised-role information from the legally authoritative source for each attribute. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1638✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry p.135 l.Architecture placement anchor: medium |
The boundary with HRIS is not complete. Deployment, employment, facility affiliation, payroll eligibility, and employme…The boundary with HRIS is not complete. Deployment, employment, facility affiliation, payroll eligibility, and employment status are later included in the registry, although these may be operational HRIS responsibilities. [draft-for-...idance.pdf | PDF] Suggested revision: Distinguish stable workforce identity and professional-authorisation data from dynamic employment, payroll, scheduling, attendance, and deployment data. Where dynamic attributes are referenced, identify the authoritative operational source. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1639✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry p.135 l.Architecture placement anchor: medium |
“Who a health worker is and what they are qualified and licensed to do” does not cover community health workers or othe…“Who a health worker is and what they are qualified and licensed to do” does not cover community health workers or other recognised cadres who may not hold formal qualifications or licences. [draft-for-...idance.pdf | PDF] Suggested revision: Use: “who a health worker is and what roles, qualifications, registrations, licences, certifications, or other nationally recognised authorisations they hold.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1640✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 1 p.135 l.Lines 229-235 |
The definition covers licensed professionals and, where nationally defined, community health workers. It does not clear…The definition covers licensed professionals and, where nationally defined, community health workers. It does not clearly address trainees, volunteers, temporary workers, traditional practitioners, foreign workers, emergency responders, or administrative and support staff. [draft-for-...idance.pdf | PDF] Suggested revision: Define configurable inclusion criteria and workforce categories based on the national workforce framework. Support different verification, registration, and authorisation models for different cadres. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1641✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 1 p.135 l.Lines 229-235 |
The component is described as maintaining one standardised record for every worker. In federal or profession-regulated …The component is described as maintaining one standardised record for every worker. In federal or profession-regulated systems, several authoritative registries may remain legally independent. [draft-for-...idance.pdf | PDF] Suggested revision: Define a nationally governed workforce reference capability that may be centralised, federated, or hybrid, with clear source authority, matching, conflict-resolution, and publication rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-270 discuss | in the document all mentions on GitHub record | ||
| PC-1642✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 1 p.135 l.Lines 237-242 |
Identity and credentials are presented as two interlocking categories, but the component later includes employment, dep…Identity and credentials are presented as two interlocking categories, but the component later includes employment, deployment, CPD, activity status, and exit reasons. The two-category framing no longer reflects the full specification. [draft-for-...idance.pdf | PDF] Suggested revision: Use at least four categories: person identity; professional registration and authorisation; qualifications and development; and employment, deployment, or affiliation references. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1643✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 1 p.135 l.Lines 237-242 |
The wording says worker identity “may cross-reference” foundational identity. The role of foundational identity should …The wording says worker identity “may cross-reference” foundational identity. The role of foundational identity should remain optional and purpose-specific rather than becoming the sole basis for workforce registration. [draft-for-...idance.pdf | PDF] Suggested revision: State that the registry may link to foundational identity where legally authorised and useful, while supporting workers who lack, cannot access, or should not be required to disclose such identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-155 discuss | in the document all mentions on GitHub record | ||
| PC-1644✎ edit📣 feedback | received | WHO Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 1 p.135 l.Lines 243-248 |
The statement that the registry is a data source for 12 of 29 NHWA indicators should identify the exact indicators and …The statement that the registry is a data source for 12 of 29 NHWA indicators should identify the exact indicators and supporting source. [draft-for-...idance.pdf | PDF] Suggested revision: Add a traceability table mapping registry data elements to the relevant NHWA indicators and identifying additional data sources needed for each calculation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1645✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 1 p.135 l.Lines 243-248 |
The relationship to the “capable, well-distributed workforce” goal is clear, but the component also contributes to care…The relationship to the “capable, well-distributed workforce” goal is clear, but the component also contributes to care quality, financing, resilience, and data foundations. [draft-for-...idance.pdf | PDF] Suggested revision: Add a concise mapping from workforce-registry capabilities to all relevant priority health goals, including the additional systems required to realise each outcome. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1646✎ edit📣 feedback | received | Editorial agent, medium |
Health Workforce Registry §Health Workforce Registry, 2 p.135-136 l.Lines 251-256 |
The discussion identifies fragmented council, employer, facility, and paper records as a common problem. The claims are…The discussion identifies fragmented council, employer, facility, and paper records as a common problem. The claims are plausible but presented without supporting sources. [draft-for-...idance.pdf | PDF] Suggested revision: Add implementation evidence or label the paragraph as an illustrative description of recognised workforce-data risks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1647✎ edit📣 feedback | received | Editorial agent |
Health Workforce Registry §Health Workforce Registry, 2 p.136 l.Lines 257-265 |
The paragraph contains long sentences combining patient assurance, fraud prevention, workforce planning, and pandemic d…The paragraph contains long sentences combining patient assurance, fraud prevention, workforce planning, and pandemic disruption. This reduces readability. [draft-for-...idance.pdf | PDF] Suggested revision: Divide the paragraph into separate patient-safety, financial-accountability, workforce-planning, and resilience benefits. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1648✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Health Workforce Registry §Health Workforce Registry, 2 p.136 l.Lines 257-260 |
Verifying professional registration does not by itself establish current competence, scope for a specific task, employe…Verifying professional registration does not by itself establish current competence, scope for a specific task, employer authorisation, facility privileges, or fitness to practise. [draft-for-...idance.pdf | PDF] Suggested revision: Clarify the limits of registry verification and identify additional checks required for employment, privileging, prescribing, contracting, or clinical-task authorisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1649✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
Health Workforce Registry §Health Workforce Registry, 2 p.136 l.Lines 258-260 |
The component is suggested as a means of detecting payroll and claims fraud. Identity and credential verification can s…The component is suggested as a means of detecting payroll and claims fraud. Identity and credential verification can support controls, but fraud detection requires additional employment, service, contract, attendance, and payment data. [draft-for-...idance.pdf | PDF] Suggested revision: Use measured wording: “supports payroll and claims controls by enabling identity, licence, role, and affiliation verification.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1650✎ edit📣 feedback | received | Editorial agent, medium |
Health Workforce Registry §Health Workforce Registry, 2 p.136 l.Lines 261-265 |
The WHO statement about workforce shortages causing essential-service disruptions should cite the exact NHWA or emergen…The WHO statement about workforce shortages causing essential-service disruptions should cite the exact NHWA or emergency-monitoring source and specify its scope. [draft-for-...idance.pdf | PDF] Suggested revision: Add the exact source, reporting period, countries or regions covered, and limitations of the finding. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1651✎ edit📣 feedback | received | Editorial agent, medium |
Health Workforce Registry §Health Workforce Registry, 2 p.136 l.Lines 266-268 |
The registry is said to provide the enabling conditions for a safe and accountable workforce at scale. It is one enabli…The registry is said to provide the enabling conditions for a safe and accountable workforce at scale. It is one enabling condition, but safety also depends on supervision, competence, working conditions, service governance, and professional regulation. [draft-for-...idance.pdf | PDF] Suggested revision: Replace with a sentence like: “provides an important identity and credential foundation for workforce safety, planning, and accountability.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1652✎ edit📣 feedback | received | Metadata registries WHO agent |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 271-275 |
The WHO workforce classification is presented as the full scope for identity-record management. Countries may classify …The WHO workforce classification is presented as the full scope for identity-record management. Countries may classify cadres differently and may need to include emerging digital-health, public-health, or community roles. [draft-for-...idance.pdf | PDF] Suggested revision: Support national classifications mapped to an international reference classification and permit governed additions for nationally recognised roles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-1653✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 276-279 |
A nationally unique health-worker identifier is assumed. Some countries may maintain profession-specific identifiers or…A nationally unique health-worker identifier is assumed. Some countries may maintain profession-specific identifiers or federated identifiers linked through cross-references. [draft-for-...idance.pdf | PDF] Suggested revision: Define the required outcome as persistent and resolvable workforce identity. Permit one national identifier, multiple linked professional identifiers, or a federated identifier arrangement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-155 discuss | in the document all mentions on GitHub record | ||
| PC-1654✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 276-279 |
The identifier lifecycle does not address erroneous assignment, compromise, duplicate identifiers, merger of duplicate …The identifier lifecycle does not address erroneous assignment, compromise, duplicate identifiers, merger of duplicate records, retirement, or historical resolution. [draft-for-...idance.pdf | PDF] Suggested revision: Add identifier lifecycle requirements consistent with the Client and Facility Registry recommendations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1655✎ edit📣 feedback | received | Metadata registries WHO agent |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 280-283 |
ISCO-08 and the WHO health-worker classification support international reporting, but they may not be sufficiently gran…ISCO-08 and the WHO health-worker classification support international reporting, but they may not be sufficiently granular for licensing, service discovery, prescribing rights, or workforce deployment. [draft-for-...idance.pdf | PDF] Suggested revision: Maintain national occupation and role classifications with governed mappings to ISCO-08 and WHO classifications, including mapping purpose, equivalence, validity, and version. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-1656✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 284-287 |
The registry stores registration and licensing status, but the legally authoritative source may remain the professional…The registry stores registration and licensing status, but the legally authoritative source may remain the professional council or regulator. The specification does not distinguish source data from a consolidated reference copy. [draft-for-...idance.pdf | PDF] Suggested revision: Identify the authoritative source for each profession and attribute. Record source, verification, update time, effective period, and any replication or caching arrangement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-154 discuss | in the document all mentions on GitHub record | ||
| PC-1657✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 284-287 |
Licence status values are limited to active, expired, suspended, and revoked. Other states may include pending, provisi…Licence status values are limited to active, expired, suspended, and revoked. Other states may include pending, provisional, restricted, conditional, inactive, surrendered, retired, or unknown. [draft-for-...idance.pdf | PDF] Suggested revision: Use a governed national value set and represent status reason, restrictions, scope, jurisdiction, effective period, and verification time separately. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1658✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 288-291 |
Qualifications and CPD are included together although the authoritative sources, verification methods, and update cycle…Qualifications and CPD are included together although the authoritative sources, verification methods, and update cycles differ. [draft-for-...idance.pdf | PDF] Suggested revision: Separate formal qualifications, recognised certifications, CPD activities, CPD compliance, competencies, and scope-of-practice authorisations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1659✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 288-291 |
Requiring qualification records may disadvantage workers whose credentials are incomplete, foreign, historically paper-…Requiring qualification records may disadvantage workers whose credentials are incomplete, foreign, historically paper-based, or issued by institutions that no longer exist. [draft-for-...idance.pdf | PDF] Suggested revision: Support provisional and unverified qualifications, foreign-credential recognition, alternative evidence, verification status, dispute handling, and later completion. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1660✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 292-294 |
Primary employer and facility affiliation are dynamic operational relationships and may be governed through HRIS, deplo…Primary employer and facility affiliation are dynamic operational relationships and may be governed through HRIS, deployment systems, contracts, or practitioner-role directories rather than the registry itself. [draft-for-...idance.pdf | PDF] Suggested revision: Treat them as authoritative references or synchronised relationships from the responsible operational source, with effective periods and provenance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-1661✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 292-294 |
Workers may have multiple concurrent employers, facilities, remote roles, temporary deployments, locum work, community …Workers may have multiple concurrent employers, facilities, remote roles, temporary deployments, locum work, community assignments, or no current affiliation. [draft-for-...idance.pdf | PDF] Suggested revision: Replace the primary-versus-secondary model with multiple typed affiliations carrying role, organisation, location, status, effective period, source, and workload where appropriate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-1662✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 295-297 |
A real-time verification service is expected without defining data freshness, response content, liability, assurance, o…A real-time verification service is expected without defining data freshness, response content, liability, assurance, or the action a consuming system may safely take. [draft-for-...idance.pdf | PDF] Suggested revision: Define the verification profile, response status, source, last-updated time, assurance, restrictions, expiry, permitted use, failure behaviour, and audit requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1663✎ edit📣 feedback | received | Core architects WHO agent, medium |
Health Workforce Registry §Health Workforce Registry, 3 p.136 l.Lines 298-300 |
Supporting standard NHWA analytics directly within the registry may turn an authoritative reference component into an a…Supporting standard NHWA analytics directly within the registry may turn an authoritative reference component into an analytical reporting platform. [draft-for-...idance.pdf | PDF] Suggested revision: Require standardised data export or analytical services, while allowing detailed NHWA calculations and dashboards to be performed by HMIS or workforce-analytics applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1664✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 4 p.136-137 l.Lines 304-312 |
The relationship among the Workforce Registry, Facility Registry, and mCSD is useful, but mCSD also depends on organisa…The relationship among the Workforce Registry, Facility Registry, and mCSD is useful, but mCSD also depends on organisations, practitioner roles, healthcare services, endpoints, and locations. [draft-for-...idance.pdf | PDF] Suggested revision: Align the component boundaries with the full mCSD model and explain where each entity is governed and how joint discovery is provided. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-162 discuss | in the document all mentions on GitHub record | ||
| PC-1665✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 4 p.137 l.Lines 308-312 |
The claim that a worker record without a facility affiliation has limited operational value is too strong. Regulators, …The claim that a worker record without a facility affiliation has limited operational value is too strong. Regulators, educators, unemployed workers, independent professionals, and community workers may legitimately lack a current facility affiliation. [draft-for-...idance.pdf | PDF] Suggested revision: State that current affiliations add operational value where applicable, but are not prerequisites for a valid workforce record. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-1666✎ edit📣 feedback | received | Metadata registries agent |
Health Workforce Registry §Health Workforce Registry, 4 p.137 l.Lines 313-317 |
Occupation codes, qualifications, and specialisations are assigned to the Terminology Service, while the LIMR governs s…Occupation codes, qualifications, and specialisations are assigned to the Terminology Service, while the LIMR governs structure. The specification does not identify how competing profession-specific or national classifications are reconciled. [draft-for-...idance.pdf | PDF] Suggested revision: Require governed value sets, mappings, edition and version management, and domain-authority approval for workforce classifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-1667✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Health Workforce Registry §Health Workforce Registry, 4 p.137 l.Lines 320-329 |
Clinical systems verifying prescribing authority need more than registration and affiliation. Prescribing rights may de…Clinical systems verifying prescribing authority need more than registration and affiliation. Prescribing rights may depend on profession, specialty, jurisdiction, medicine class, supervision, local privileges, and current restrictions. [draft-for-...idance.pdf | PDF] Suggested revision: Distinguish professional licence verification from task-specific or facility-specific authorisation. Define additional authoritative sources and policy checks. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1668✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
Health Workforce Registry §Health Workforce Registry, 4 p.137 l.Lines 323-326 |
Claims and payroll systems are positioned as consumers of the registry for eligibility. Registry data supports identity…Claims and payroll systems are positioned as consumers of the registry for eligibility. Registry data supports identity and professional-status checks but does not replace employment, contract, attendance, or payment rules. [draft-for-...idance.pdf | PDF] Suggested revision: Clarify that the registry contributes reference data to a broader eligibility or validation process executed by operational systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1669✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 4 p.137 l.Lines 328-329 |
LMS platforms are described as updating qualification records. Training completion does not automatically become a reco…LMS platforms are described as updating qualification records. Training completion does not automatically become a recognised professional qualification or licence condition. [draft-for-...idance.pdf | PDF] Suggested revision: Require validation and approval by the responsible qualification, accreditation, or licensing authority before LMS information changes authoritative credential status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1670✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 4 p.137 l.Lines 331-338 |
The relationship with foundational identity mirrors the Client Registry, but health workers may have stronger legal-ide…The relationship with foundational identity mirrors the Client Registry, but health workers may have stronger legal-identity requirements for licensing, employment, controlled prescribing, or payment. [draft-for-...idance.pdf | PDF] Suggested revision: Define profession- and use-case-specific identity-assurance requirements rather than assuming one uniform linkage model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-155 discuss | in the document all mentions on GitHub record | ||
| PC-1671✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 4 p.137 l.Lines 335-338 |
Professional councils are identified as primary upstream sources, but no precedence rule is provided where council, emp…Professional councils are identified as primary upstream sources, but no precedence rule is provided where council, employer, education, and government records conflict. [draft-for-...idance.pdf | PDF] Suggested revision: Create an attribute-level authority and reconciliation matrix, with escalation, correction, and dispute-handling procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-154 discuss | in the document all mentions on GitHub record | ||
| PC-1672✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.137 l.Lines 341-347 |
The text claims alignment with OpenHIE requirements and identifies several extensions, but no requirement-level traceab…The text claims alignment with OpenHIE requirements and identifies several extensions, but no requirement-level traceability matrix is provided. [draft-for-...idance.pdf | PDF] Suggested revision: Add source requirement, version, original status, DPI-H status, adaptation rationale, and test-method columns. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1673✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.138-141 l.Requirements table anchor: medium |
Requirement statuses again use Required and Recommended rather than the normative SHALL, SHOULD, and MAY terminology st…Requirement statuses again use Required and Recommended rather than the normative SHALL, SHOULD, and MAY terminology stated in Section 3.5.2. [draft-for-...idance.pdf | PDF] Suggested revision: Harmonise requirement terminology and define conditional applicability across all component specifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1674✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.138 l.Requirement 1 anchor: medium |
The requirement mandates assignment of a unique worker identifier at registration, even where identity, qualification, …The requirement mandates assignment of a unique worker identifier at registration, even where identity, qualification, or professional status remains provisional or disputed. [draft-for-...idance.pdf | PDF] Suggested revision: Allow provisional registry identifiers and status, followed by verification and reconciliation before authoritative professional claims are published. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-155 discuss | in the document all mentions on GitHub record | ||
| PC-1675✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.138 l.Requirement 2 anchor: medium |
The registry must retain updates from source systems but does not define whether all submitted updates become authorita…The registry must retain updates from source systems but does not define whether all submitted updates become authoritative immediately. [draft-for-...idance.pdf | PDF] Suggested revision: Require source validation, precedence, approval, effective date, provenance, conflict detection, acceptance or rejection, and acknowledgement before publication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-196 discuss | in the document all mentions on GitHub record | ||
| PC-1676✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.138 l.Requirement 3 anchor: medium |
Schema configurability is mandatory, but reference to the LIMR does not itself prevent incompatible local extensions. […Schema configurability is mandatory, but reference to the LIMR does not itself prevent incompatible local extensions. [draft-for-...idance.pdf | PDF] Suggested revision: Require a governed national extension process, published profiles, terminology bindings, compatibility rules, and conformance testing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1677✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.138 l.Requirement 4 anchor: medium |
Bulk import is only Recommended despite the likelihood that initial national onboarding will depend on data from counci…Bulk import is only Recommended despite the likelihood that initial national onboarding will depend on data from councils, employers, and education institutions. [draft-for-...idance.pdf | PDF] Suggested revision: Make bulk onboarding or an equivalent migration mechanism mandatory for initial and periodic synchronisation, with validation, matching, preview, approval, rollback, and error reporting. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-196 discuss | in the document all mentions on GitHub record | ||
| PC-1678✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.138 l.Requirement 5 anchor: medium |
Querying by any known identifier and returning the canonical record and cross-reference map could disclose national IDs…Querying by any known identifier and returning the canonical record and cross-reference map could disclose national IDs, registration numbers, employee identifiers, or other sensitive identifiers unnecessarily. [draft-for-...idance.pdf | PDF] Suggested revision: Return only authorised and purpose-necessary fields. Apply field-level access, masking, purpose controls, audit, and restrictions on bulk or enumeration queries. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-145 discuss | in the document all mentions on GitHub record | ||
| PC-1679✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.138 l.Requirement 6 anchor: medium |
Joint care-services queries are assigned to the Workforce Registry, although relevant information may remain distribute…Joint care-services queries are assigned to the Workforce Registry, although relevant information may remain distributed across organisation, facility, service, and practitioner-role sources. [draft-for-...idance.pdf | PDF] Suggested revision: Define a federated or coordinated care-services discovery capability rather than requiring one registry to hold every entity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-162 discuss | in the document all mentions on GitHub record | ||
| PC-1680✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.138 l.Requirement 7 anchor: medium |
Ranked attribute search may expose personal and professional data and enable enumeration of the workforce. [draft-for-.…Ranked attribute search may expose personal and professional data and enable enumeration of the workforce. [draft-for-...idance.pdf | PDF] Suggested revision: Define separate public and restricted search profiles, minimum query criteria, result limits, masking, rate limits, audit, and monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-145 discuss | in the document all mentions on GitHub record | ||
| PC-1681✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.138-139 l.Requirement 8 anchor: medium |
Real-time or near-real-time verification is mandatory, but the terms are undefined and no maximum data age or response …Real-time or near-real-time verification is mandatory, but the terms are undefined and no maximum data age or response time is stated. [draft-for-...idance.pdf | PDF] Suggested revision: Define measurable freshness, update-latency, response-time, availability, and failure-mode requirements by verification use case. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1682✎ edit📣 feedback | received | Core architects Clinical agent |
Health Workforce Registry §Health Workforce Registry, 5 p.138-139 l.Requirement 8 anchor: medium |
A synchronous verification dependency could block care or service delivery during outages or poor connectivity. [draft-…A synchronous verification dependency could block care or service delivery during outages or poor connectivity. [draft-for-...idance.pdf | PDF] Suggested revision: Provide signed or cached verification, validity periods, offline credentials, emergency fallback, later reconciliation, and risk-based handling when live verification is unavailable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1683✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.139 l.Requirement 9 anchor: medium |
The licence record captures status, issuing body, and expiry but not scope, profession, specialty, jurisdiction, restri…The licence record captures status, issuing body, and expiry but not scope, profession, specialty, jurisdiction, restrictions, conditions, or reason for status. [draft-for-...idance.pdf | PDF] Suggested revision: Expand the licence model and link every status to effective period, source authority, verification, restrictions, and relevant professional role. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1684✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.139 l.Requirement 9 anchor: medium |
Licence changes are to be propagated “without delay,” which is not measurable and may be unrealistic across distributed…Licence changes are to be propagated “without delay,” which is not measurable and may be unrealistic across distributed regulators. [draft-for-...idance.pdf | PDF] Suggested revision: Define risk-based maximum propagation times, event acknowledgement, failed-delivery handling, monitoring, and escalation for suspension or revocation events. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1685✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.139 l.Requirement 10 anchor: medium |
Licence-expiry notifications to workers, employers, and systems may disclose employment or professional information wit…Licence-expiry notifications to workers, employers, and systems may disclose employment or professional information without ensuring the recipient remains authorised. [draft-for-...idance.pdf | PDF] Suggested revision: Verify recipient authority, use minimum necessary content, support preferred contact methods, log disclosure, and distinguish reminders from formal regulatory notifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1686✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.139 l.Requirement 11 anchor: medium |
Qualification details are mandatory, but no verification, issuer identity, authenticity, recognition, or equivalence re…Qualification details are mandatory, but no verification, issuer identity, authenticity, recognition, or equivalence requirements are included. [draft-for-...idance.pdf | PDF] Suggested revision: Require qualification status, issuer, verification method, recognition authority, country, subject, level, effective date, and supporting credential where permitted. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1687✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.139 l.Requirement 12 anchor: medium |
Recording individual CPD activities may duplicate an LMS, professional portfolio, or regulator system and create a larg…Recording individual CPD activities may duplicate an LMS, professional portfolio, or regulator system and create a large operational dataset in the registry. [draft-for-...idance.pdf | PDF] Suggested revision: Store or expose authoritative CPD compliance status and relevant summaries, while detailed learning activities remain in the responsible operational system unless nationally required. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1688✎ edit📣 feedback | received | Core architects WHO agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.139 l.Requirement 13 anchor: medium |
Generating NHWA reports directly within the registry may mix master-data stewardship with analytical reporting. [draft-…Generating NHWA reports directly within the registry may mix master-data stewardship with analytical reporting. [draft-for-...idance.pdf | PDF] Suggested revision: Require standard data services or extracts supporting NHWA reporting. Permit analytics to be performed in a governed workforce-analytics or HMIS environment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1689✎ edit📣 feedback | received | WHO Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.139 l.Requirement 13 anchor: medium |
The requirement says the registry supports NHWA “core indicators” but does not identify which indicators can be produce…The requirement says the registry supports NHWA “core indicators” but does not identify which indicators can be produced solely from registry data and which require education, finance, migration, or population data. [draft-for-...idance.pdf | PDF] Suggested revision: Add an indicator mapping with numerator, denominator, additional source, data-quality rule, and reporting limitation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1690✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.139 l.Requirement 14 anchor: medium |
Custom reports and exports may expose identifiable workforce data, particularly in small geographic or professional gro…Custom reports and exports may expose identifiable workforce data, particularly in small geographic or professional groups. [draft-for-...idance.pdf | PDF] Suggested revision: Require role-based and purpose-based access, aggregation thresholds, disclosure control, export approval, audit, and secure research or analytical environments. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1691✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.139-140 l.Requirement 15 anchor: medium |
Staffing ratios require denominators such as population, service volume, facility capacity, or full-time equivalents. T…Staffing ratios require denominators such as population, service volume, facility capacity, or full-time equivalents. The registry alone cannot produce all these measures accurately. [draft-for-...idance.pdf | PDF] Suggested revision: State the external data dependencies and distinguish headcount, full-time equivalent, contracted hours, actual activity, and service-capacity measures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1692✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 16 anchor: medium |
The API requirement references mCSD or the older CSD profile without specifying versions, actors, resource constraints,…The API requirement references mCSD or the older CSD profile without specifying versions, actors, resource constraints, security, or national extensions. [draft-for-...idance.pdf | PDF] Suggested revision: Select and publish a national profile with exact versions, actors, resources, search parameters, terminology, security, history, and tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-162 discuss | in the document all mentions on GitHub record | ||
| PC-1693✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 17 anchor: medium |
“Request care services updates” is ambiguous. It could mean polling source systems, requesting correction, retrieving d…“Request care services updates” is ambiguous. It could mean polling source systems, requesting correction, retrieving deltas, or initiating workflow. [draft-for-...idance.pdf | PDF] Suggested revision: Define separate operations for synchronisation, source-data request, correction proposal, event subscription, and authoritative update. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-162 discuss | in the document all mentions on GitHub record | ||
| PC-1694✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 17 anchor: medium |
Requiring the registry to request updates does not establish a duty on professional councils or employers to provide ti…Requiring the registry to request updates does not establish a duty on professional councils or employers to provide timely data. [draft-for-...idance.pdf | PDF] Suggested revision: Add governance agreements, source obligations, update frequency, service levels, data-quality responsibilities, and escalation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1695✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 18 anchor: medium |
“Upstream federation” is used for sending updates to other national or regional systems. The direction and authority of…“Upstream federation” is used for sending updates to other national or regional systems. The direction and authority of those systems are not necessarily upstream. [draft-for-...idance.pdf | PDF] Suggested revision: Rename the capability Federated and regional data exchange and define source authority, permitted data, direction, conflict handling, and cross-border governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-162 discuss | in the document all mentions on GitHub record | ||
| PC-1696✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 18 anchor: medium |
Cross-border workforce monitoring may involve sensitive personal, employment, migration, licence, and disciplinary data…Cross-border workforce monitoring may involve sensitive personal, employment, migration, licence, and disciplinary data. [draft-for-...idance.pdf | PDF] Suggested revision: Require legal basis, purpose limitation, minimum dataset, professional and individual rights, security, correction, retention, and cross-jurisdiction accountability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1697✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 19 anchor: medium |
Role-based access control is required, but workforce data access may also depend on organisation, profession, geography…Role-based access control is required, but workforce data access may also depend on organisation, profession, geography, purpose, worker consent or legal basis, and attribute sensitivity. [draft-for-...idance.pdf | PDF] Suggested revision: Use policy-based access controls and define public, employer, regulator, worker-self-service, analytical, and administrative access profiles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1698✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 20 anchor: medium |
Audit and version history are combined in one requirement although they serve different purposes. [draft-for-...idance.…Audit and version history are combined in one requirement although they serve different purposes. [draft-for-...idance.pdf | PDF] Suggested revision: Define record-history requirements separately from security and access audit requirements, including retention, integrity, review, and authorised access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1699✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 20 anchor: medium |
The requirement does not explicitly record worker-submitted corrections, disputed status, regulator decisions, or tempo…The requirement does not explicitly record worker-submitted corrections, disputed status, regulator decisions, or temporary protections while disputes are investigated. [draft-for-...idance.pdf | PDF] Suggested revision: Add correction and dispute events, status, evidence, decision maker, resolution time, appeal, and notification to affected consumers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1700✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.140 l.Requirement 21 anchor: medium |
Subscription is Recommended, although licence suspension, revocation, and material affiliation changes may require imme…Subscription is Recommended, although licence suspension, revocation, and material affiliation changes may require immediate notification to safety-critical consumers. [draft-for-...idance.pdf | PDF] Suggested revision: Make critical status notifications mandatory for authorised subscribers, with defined event semantics, delivery, acknowledgement, retry, audit, and correction handling. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1701✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 5 p.141 l.Requirement 22 anchor: medium |
High availability and low latency are mandatory but not quantified and may differ by use case. [draft-for-...idance.pdf…High availability and low latency are mandatory but not quantified and may differ by use case. [draft-for-...idance.pdf | PDF] Suggested revision: Define service classes for public lookup, routine query, safety-critical credential verification, administration, and bulk reporting, with measurable targets. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1702✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
Health Workforce Registry §Health Workforce Registry, 5 p.141 l.Requirement 22 anchor: medium |
Live prescribing-authority and claims checks may fail in low-connectivity settings. [draft-for-...idance.pdf | PDF]Live prescribing-authority and claims checks may fail in low-connectivity settings. [draft-for-...idance.pdf | PDF] Suggested revision: Support signed credentials, verified cached status, validity periods, offline lists, degraded operation, and later reconciliation according to risk. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | ||
| PC-1703✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.141 l.Lines 360-366 anchor: medium |
The minimum dataset is said to support identity, credential verification, and workforce analytics, but the field-level …The minimum dataset is said to support identity, credential verification, and workforce analytics, but the field-level necessity and source for each element are not documented. [draft-for-...idance.pdf | PDF] Suggested revision: Add purpose, authoritative source, applicability condition, privacy classification, verification requirement, and relevant indicator or workflow for each data element. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-1704✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.141 l.Lines 360-366 anchor: medium |
The table says mandatory elements must be present before an active record can be published. This may exclude legitimate…The table says mandatory elements must be present before an active record can be published. This may exclude legitimate workers with incomplete historical credentials or delayed source verification. [draft-for-...idance.pdf | PDF] Suggested revision: Define provisional, pending verification, active, restricted, inactive, suspended, retired, and archived publication states with appropriate limitations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1705✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.141 l.“Unique health worker identifier” anchor: medium |
The data model assumes one national identifier as mandatory. This conflicts with potential federated or profession-spec…The data model assumes one national identifier as mandatory. This conflicts with potential federated or profession-specific identifier models. [draft-for-...idance.pdf | PDF] Suggested revision: Require at least one persistent authoritative registry identifier and support multiple linked identifiers under the national identity model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1706✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.141 l.“Full name” anchor: medium |
First and family names do not accommodate all naming traditions, mononyms, multiple scripts, name changes, professional…First and family names do not accommodate all naming traditions, mononyms, multiple scripts, name changes, professional names, or incomplete identities. [draft-for-...idance.pdf | PDF] Suggested revision: Use a flexible multilingual human-name model with type, use, script, period, preferred name, and unknown values. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1707✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.141 l.“Date of birth” anchor: medium |
Full date of birth is Mandatory, although it may not be necessary for public or routine professional lookup and increas…Full date of birth is Mandatory, although it may not be necessary for public or routine professional lookup and increases re-identification risk. [draft-for-...idance.pdf | PDF] Suggested revision: Retain it only where required for identity resolution or legal registration, restrict access, and support estimated or partially known dates with precision metadata. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-1708✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.141 l.“Sex at birth” anchor: medium |
Sex at birth is Mandatory without explaining its necessity for workforce identity, licensing, or planning. This conflic…Sex at birth is Mandatory without explaining its necessity for workforce identity, licensing, or planning. This conflicts with data minimisation. [draft-for-...idance.pdf | PDF] Suggested revision: Remove it from the universal mandatory set unless a specific lawful workforce purpose is demonstrated. If collected, define the concept, access, values, correction, and permitted use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-1709✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.141 l.“Nationality/citizenship” anchor: medium |
Nationality is Mandatory and may create risks for refugees, stateless persons, migrants, or workers in cross-border set…Nationality is Mandatory and may create risks for refugees, stateless persons, migrants, or workers in cross-border settings. It may not be required for core professional identity. [draft-for-...idance.pdf | PDF] Suggested revision: Make nationality conditional or Recommended, support multiple, stateless, unknown, and undisclosed states, and separate nationality from legal work authorisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-1710✎ edit📣 feedback | received | Core architects WHO agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.141-142 l.“Place of birth” anchor: medium |
Place of birth is Recommended for migration statistics, but collecting it within a workforce registry can create discri…Place of birth is Recommended for migration statistics, but collecting it within a workforce registry can create discrimination or surveillance risks. [draft-for-...idance.pdf | PDF] Suggested revision: Collect only where necessary for approved NHWA reporting, restrict access, separate it from employment decisions, and consider use of aggregated or alternative migration indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-1711✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Physical address” anchor: medium |
A current residential address is Mandatory, although it is highly sensitive and not necessarily required for profession…A current residential address is Mandatory, although it is highly sensitive and not necessarily required for professional verification or national workforce planning. [draft-for-...idance.pdf | PDF] Suggested revision: Make residential address conditional. Prefer professional contact or administrative-area information where sufficient, with strong access restrictions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-1712✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Contact information” anchor: medium |
Personal phone and email are Mandatory without distinguishing professional and private contact channels or defining dis…Personal phone and email are Mandatory without distinguishing professional and private contact channels or defining disclosure rules. [draft-for-...idance.pdf | PDF] Suggested revision: Separate professional and personal contact details, require preferred-use and confidentiality indicators, and make public disclosure opt-in or legally governed. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-1713✎ edit📣 feedback | received | Metadata registries agent |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Occupation/cadre code” anchor: medium |
A single occupation code may not capture multiple roles, specialties, employment functions, scopes of practice, or conc…A single occupation code may not capture multiple roles, specialties, employment functions, scopes of practice, or concurrent cadres. [draft-for-...idance.pdf | PDF] Suggested revision: Support multiple typed classifications with source, scheme, version, effective period, primary-use context, and mapping to international classifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1714✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Specialisation” anchor: medium |
Specialisation is Recommended but not linked to an authoritative certification or professional-body source. [draft-for-…Specialisation is Recommended but not linked to an authoritative certification or professional-body source. [draft-for-...idance.pdf | PDF] Suggested revision: Record specialisation, credential or recognition status, issuing authority, jurisdiction, effective period, and verification status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1715✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Professional registration number” anchor: medium |
A registration number is Mandatory, but community health workers, support personnel, trainees, and unregulated cadres m…A registration number is Mandatory, but community health workers, support personnel, trainees, and unregulated cadres may not have one. [draft-for-...idance.pdf | PDF] Suggested revision: Make it conditional on the worker category and national regulatory framework. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1716✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Licensing body” and “Licence status” anchor: medium |
Licensing information is Mandatory for every worker, which excludes unlicensed but nationally recognised cadres. [draft…Licensing information is Mandatory for every worker, which excludes unlicensed but nationally recognised cadres. [draft-for-...idance.pdf | PDF] Suggested revision: Make licence fields mandatory only for roles subject to professional licensing and use alternative authorisation or accreditation fields for other cadres. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1717✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Licence expiry date” anchor: medium |
Some registrations or licences may be indefinite, renewed through continuing status, or not use a fixed expiry date. [d…Some registrations or licences may be indefinite, renewed through continuing status, or not use a fixed expiry date. [draft-for-...idance.pdf | PDF] Suggested revision: Support no-expiry, unknown, pending, conditional, and effective-period representations according to the issuing authority’s rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1718✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Qualification details” anchor: medium |
Qualification details are Mandatory, but the table does not support multiple qualifications, foreign recognition, quali…Qualification details are Mandatory, but the table does not support multiple qualifications, foreign recognition, qualification level, verification, or incomplete historical records. [draft-for-...idance.pdf | PDF] Suggested revision: Model qualifications as repeatable records with type, level, field, institution, country, award date, verification, recognition, evidence, and status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-1719✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Employment status” anchor: medium |
Employment status and type are Mandatory although these are dynamic HR attributes and may not be authoritative in the r…Employment status and type are Mandatory although these are dynamic HR attributes and may not be authoritative in the registry. [draft-for-...idance.pdf | PDF] Suggested revision: Make them linked or synchronised operational attributes with source, effective period, update frequency, and confidence. Do not block publication of a professional record where employment is unknown. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1720✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Contract type” anchor: medium |
Full-time or part-time classification alone is insufficient for FTE calculations. Contracted hours, standard full-time …Full-time or part-time classification alone is insufficient for FTE calculations. Contracted hours, standard full-time hours, multiple contracts, and actual activity are needed. [draft-for-...idance.pdf | PDF] Suggested revision: Add contracted hours or FTE fraction, reference period, employer, standard hours, effective period, and multiple concurrent contracts where this data is in scope. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1721✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.142 l.“Activity level” anchor: medium |
“Practising,” “professionally active,” and “licensed to practise” are layered stock concepts rather than simply one act…“Practising,” “professionally active,” and “licensed to practise” are layered stock concepts rather than simply one activity-status field. A worker may fit several categories simultaneously. [draft-for-...idance.pdf | PDF] Suggested revision: Represent these as derived classifications based on explicit underlying attributes and NHWA rules rather than one mutually exclusive status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1722✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.143 l.“Type of exit” anchor: medium |
Exit reason can be sensitive and is described using broad voluntary and involuntary categories. Some reasons, such as d…Exit reason can be sensitive and is described using broad voluntary and involuntary categories. Some reasons, such as dismissal, incapacity, death, or revocation, require restricted access and precise authority. [draft-for-...idance.pdf | PDF] Suggested revision: Make the field conditional, use controlled values, record source and effective date, restrict access, and distinguish workforce-flow reporting from disciplinary or medical information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-1723✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.143 l.“Primary employer/facility affiliation” anchor: medium |
A primary affiliation is Mandatory, although independent, unemployed, retired, locum, remote, temporary, or community w…A primary affiliation is Mandatory, although independent, unemployed, retired, locum, remote, temporary, or community workers may not have one. [draft-for-...idance.pdf | PDF] Suggested revision: Make affiliation repeatable and conditional. Support no-current-affiliation and non-facility organisational roles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-1724✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.143 l.“Secondary facility affiliations” anchor: medium |
Labeling affiliations as primary and secondary may not represent workers with multiple equal roles or rotating assignme…Labeling affiliations as primary and secondary may not represent workers with multiple equal roles or rotating assignments. [draft-for-...idance.pdf | PDF] Suggested revision: Model affiliations by type, role, organisation, facility, effective period, workload, and source rather than fixed primary or secondary labels. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-1725✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.143 l.“CPD status” anchor: medium |
The element includes activities, accrued credits, and compliance status, potentially duplicating detailed LMS or regula…The element includes activities, accrued credits, and compliance status, potentially duplicating detailed LMS or regulatory data. [draft-for-...idance.pdf | PDF] Suggested revision: Keep authoritative compliance and summary information in the registry and reference detailed learning records from their source. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-1726✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, 6 p.143 l.“Foundational identifier” anchor: medium |
The field is Recommended “where available and consented,” but consent may not be the appropriate basis for statutory pr…The field is Recommended “where available and consented,” but consent may not be the appropriate basis for statutory professional registration, and storing national IDs creates linkage risk. [draft-for-...idance.pdf | PDF] Suggested revision: Use “where legally authorised and necessary,” with restricted access, masking, verification status, purpose limitation, and impact assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-155 discuss | in the document all mentions on GitHub record | ||
| PC-1727✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry §Health Workforce Registry, 6 p.143 l.“Record creation and update metadata” anchor: medium |
Creation and last-update dates are insufficient for distributed source governance and temporal workforce data. [draft-f…Creation and last-update dates are insufficient for distributed source governance and temporal workforce data. [draft-for-...idance.pdf | PDF] Suggested revision: Include source authority, recorded time, effective period, verification, status, reason for change, author, provenance, and supersession. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1728✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, Governance p.143 l.Governance item 1 anchor: medium |
Multiple authoritative institutions are recognised, but the governance text does not define how their decisions are coo…Multiple authoritative institutions are recognised, but the governance text does not define how their decisions are coordinated or which source prevails for each attribute. [draft-for-...idance.pdf | PDF] Suggested revision: Add an attribute-level authority matrix, data-sharing agreements, service levels, conflict resolution, joint change control, and escalation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-154 discuss | in the document all mentions on GitHub record | ||
| PC-1729✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Health Workforce Registry §Health Workforce Registry, Governance p.143 l.Governance item 2 anchor: medium |
Licence-update latency is rightly highlighted as a patient-safety concern, but no minimum timing or assurance level is …Licence-update latency is rightly highlighted as a patient-safety concern, but no minimum timing or assurance level is proposed. [draft-for-...idance.pdf | PDF] Suggested revision: Require countries to establish risk-based maximum propagation times, monitoring, acknowledgement, incident handling, and safety fallback for critical regulatory changes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-159 discuss | in the document all mentions on GitHub record | ||
| PC-1730✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, Governance p.143 l.Governance item 2 anchor: medium |
The governance text addresses incorrect active status but not incorrect suspension, expiry, or revocation, which can un…The governance text addresses incorrect active status but not incorrect suspension, expiry, or revocation, which can unfairly prevent a worker from practising. [draft-for-...idance.pdf | PDF] Suggested revision: Treat false-positive and false-negative status errors as safety and rights issues. Require rapid correction, appeal, notification, and remediation in both directions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1731✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, Governance p.143 l.Governance item 3 anchor: medium |
Worker review and correction are appropriately required, but the process is not defined, and no protection is provided …Worker review and correction are appropriately required, but the process is not defined, and no protection is provided while disputed information affects employment or practice. [draft-for-...idance.pdf | PDF] Suggested revision: Define self-service or assisted access, correction evidence, response times, appeal, independent review, temporary dispute status, and notification to systems that received incorrect data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1732✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, Governance p.143-144 l.Governance item 4 anchor: medium |
Community health-worker governance is acknowledged, but similar alternative governance is also needed for trainees, vol…Community health-worker governance is acknowledged, but similar alternative governance is also needed for trainees, volunteers, temporary workers, traditional practitioners, and other non-regulated cadres. [draft-for-...idance.pdf | PDF] Suggested revision: Expand the governance requirement to all worker categories that lack a traditional professional regulator. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-1733✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry, Governance p.143-144 l.Governance section anchor: medium |
The governance section does not identify which workforce data should be public, restricted to employers or regulators, …The governance section does not identify which workforce data should be public, restricted to employers or regulators, visible to the worker, or available only for approved analytics. [draft-for-...idance.pdf | PDF] Suggested revision: Define public and restricted data subsets, disclosure purposes, access profiles, aggregation thresholds, audit, and worker transparency. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-1734✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry §Health Workforce Registry overall p.135-144 l.Complete component description anchor: medium |
The component provides detailed requirements but lacks a complete actor, profile, event, identity-assurance, credential…The component provides detailed requirements but lacks a complete actor, profile, event, identity-assurance, credential-verification, and conformance package. [draft-for-...idance.pdf | PDF] Suggested revision: Publish a companion implementation guide covering mCSD or equivalent profiles, actor roles, identifier policy, licence and qualification models, event notifications, security, test data, service levels, and conformance tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1735✎ edit📣 feedback | received | Core architects WHO agent |
Health Workforce Registry §Health Workforce Registry overall p.135-144 l.Complete component description anchor: medium |
The target specification assumes comprehensive licensing data, verified qualifications, employment links, NHWA reports,…The target specification assumes comprehensive licensing data, verified qualifications, employment links, NHWA reports, high-availability APIs, and frequent source updates. This may exceed the initial capacity of many countries. [draft-for-...idance.pdf | PDF] Suggested revision: Define maturity levels beginning with a governed workforce list and identifiers, then professional registration and licensing, facility affiliations, eventing, qualifications, NHWA-supporting data, and advanced verification services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1736✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Product Registry §Product Registry p.145 l.Architecture placement anchor: medium |
The Product Registry is described as cross-sectorally reusable and therefore foundational DPI-H. However, its scope is …The Product Registry is described as cross-sectorally reusable and therefore foundational DPI-H. However, its scope is limited to health products, and the corresponding cross-sector authorities may include medicines regulators, customs, procurement authorities, and general trade-item registries. Suggested revision: Describe it as a health-product reference capability that may build on cross-sector product, business, customs, and trade-identifier infrastructure. Clarify which health-specific attributes justify its classification as DPI-H. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1737✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry p.145 l.Architecture placement anchor: medium |
The distinction between the Product Registry and Product Catalogue Management Tool is useful, but the placement states …The distinction between the Product Registry and Product Catalogue Management Tool is useful, but the placement states that countries should implement the registry first. Some countries may already have operational catalogues or regulatory product databases that can be adapted as the authoritative registry. Suggested revision: Replace the fixed sequence with a capability-based assessment. Countries should identify and strengthen an existing authoritative source where suitable rather than necessarily deploying a new registry first. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-165 discuss | in the document all mentions on GitHub record | ||
| PC-1738✎ edit📣 feedback | received | Editorial agent, medium |
Product Registry §Product Registry p.145 l.Architecture placement anchor: medium |
The Product Catalogue Management Tool is capitalised as though it were a defined component, but it is not included in t…The Product Catalogue Management Tool is capitalised as though it were a defined component, but it is not included in the DPI-H component catalogue and is later treated as a generic functional application. Suggested revision: Use lower case unless defining a formal logical component, or add the term to the glossary with a clear boundary and accepted synonyms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-194 discuss | in the document all mentions on GitHub record | ||
| PC-1739✎ edit📣 feedback | received | Core architects Supply chain agent, medium |
Product Registry §Product Registry p.145 l.Architecture placement anchor: medium |
The registry is classified as a foundational component because of cross-sector reuse. Cross-sector reuse is not consist…The registry is classified as a foundational component because of cross-sector reuse. Cross-sector reuse is not consistently required of other foundational DPI-H components, such as the LHR or Terminology Service. Suggested revision: State that cross-programme reuse within health is the minimum DPI-H criterion, while cross-sector reuse is an additional characteristic for some components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1740✎ edit📣 feedback | received | Supply chain Metadata registries agent, medium |
Product Registry §Product Registry, 1 p.145 l.Lines 382-387 |
The scope includes medicines, vaccines, devices, diagnostics, and health commodities. These product classes use substan…The scope includes medicines, vaccines, devices, diagnostics, and health commodities. These product classes use substantially different regulatory, identification, packaging, clinical, and lifecycle models. Suggested revision: Define a common product-identity core and domain-specific extensions for medicinal products, devices, diagnostics, vaccines, and other commodities. Avoid one undifferentiated record model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1741✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 1 p.145 l.Lines 382-387 |
The phrase “recognised for use within the national health system” is ambiguous. Recognition may mean regulatory authori…The phrase “recognised for use within the national health system” is ambiguous. Recognition may mean regulatory authorisation, formulary inclusion, procurement eligibility, emergency approval, donation acceptance, or programme use. Suggested revision: Represent these as separate statuses and relationships, each with an authoritative source, scope, jurisdiction, and effective period. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1742✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 1 p.145 l.Lines 382-387 |
The registry is described as the common reference for supply-chain, clinical, and regulatory systems. The medicines or …The registry is described as the common reference for supply-chain, clinical, and regulatory systems. The medicines or medical-device regulator may already hold the legally authoritative market-authorisation register. Suggested revision: Clarify whether the Product Registry is the regulatory source, a national master-data hub, or a federated reference view linking several authoritative sources. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1743✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 1 p.145 l.Lines 388-392 |
The registry is said to contain only stable core attributes, but the examples later include storage requirements, shelf…The registry is said to contain only stable core attributes, but the examples later include storage requirements, shelf life, regulatory details, origin, and volumetrics, which can change by item, packaging level, market, and manufacturer. Suggested revision: Separate stable product identity from versioned item, packaging, regulatory, and logistics attributes. Define update authority and lifecycle for each category. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1744✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 1 p.145 l.Lines 388-392 |
“Minimum sufficient set” is used without criteria for determining whether an attribute belongs in the registry or in ca…“Minimum sufficient set” is used without criteria for determining whether an attribute belongs in the registry or in catalogue, regulatory, clinical, or procurement systems. Suggested revision: Define placement criteria based on authority, stability, reuse, lifecycle, domain specificity, and whether the attribute is essential to unambiguous identification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1745✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 1 p.145 l.Lines 393-400 |
The process correctly treats product master-data management as an ongoing programme, but it does not explicitly include…The process correctly treats product master-data management as an ongoing programme, but it does not explicitly include source onboarding, data cleansing, deduplication, identifier assignment, governance, or transition from local catalogues. Suggested revision: Add a staged implementation method covering source inventory, data profiling, canonical modelling, identifier policy, matching, cleansing, source onboarding, publication, synchronisation, and retirement of duplicate lists. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-165 discuss | in the document all mentions on GitHub record | ||
| PC-1746✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 1 p.145 l.Lines 393-400 |
The WHO product-catalogue handbook is used as the implementation frame, but countries may have different starting point…The WHO product-catalogue handbook is used as the implementation frame, but countries may have different starting points across medicines, vaccines, devices, and commodities. Suggested revision: Allow separate maturity pathways by product domain while maintaining common identifier, provenance, lifecycle, and governance patterns. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1747✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 2 p.145-146 l.Lines 403-410 |
The description of fragmented local product lists and inconsistent codes is credible, but the causal claims about forec…The description of fragmented local product lists and inconsistent codes is credible, but the causal claims about forecasting, diversion detection, and shortage signals should be supported by evidence or qualified. Suggested revision: Cite implementation evidence or describe these as common risks that the registry can help mitigate rather than outcomes guaranteed by deployment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1748✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 2 p.146 l.Lines 411-417 |
The text says all supply-chain systems draw from the same product master once the registry exists. Adoption, synchronis…The text says all supply-chain systems draw from the same product master once the registry exists. Adoption, synchronisation, contractual enforcement, and legacy-system constraints may prevent this in practice. Suggested revision: Replace with a sentence like: “Conformant supply-chain systems should progressively reference or synchronise with the governed product master.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1749✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 2 p.146 l.Lines 411-417 |
The section links the registry primarily to supply-chain outcomes but does not show its contribution to care quality, f…The section links the registry primarily to supply-chain outcomes but does not show its contribution to care quality, financing, public health, trusted data, or resilience. Suggested revision: Add a concise mapping to the relevant health goals and identify the other components required to realise each outcome. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1750✎ edit📣 feedback | received | Supply chain Metadata registries agent, medium |
Product Registry §Product Registry, 3 p.146 l.Lines 420-422 |
Product identity is described at generic and branded item or pack levels, but the relationship among ingredient, clinic…Product identity is described at generic and branded item or pack levels, but the relationship among ingredient, clinical drug, medicinal product, trade item, package, batch, and serialised unit is not defined. Suggested revision: Add a product-level model distinguishing generic clinical concept, regulated product, manufactured item, packaging level, batch or lot, and serialised instance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1751✎ edit📣 feedback | received | Supply chain Metadata registries agent, medium |
Product Registry §Product Registry, 3 p.146 l.Lines 423-425 |
Identifier management mentions GTINs and national codes but does not include identifier authority, scope, status, repla…Identifier management mentions GTINs and national codes but does not include identifier authority, scope, status, replacement, check-digit validation, or effective period. Suggested revision: Apply a common identifier model with assigning authority, namespace, product level, status, period, provenance, and historical cross-reference. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-269 discuss | in the document all mentions on GitHub record | ||
| PC-1752✎ edit📣 feedback | received | Metadata registries Supply chain agent |
Product Registry §Product Registry, 3 p.146 l.Lines 426-428 |
UNSPSC, GPC, and ATC serve different purposes and classify different aspects of products. Treating them as interchangea…UNSPSC, GPC, and ATC serve different purposes and classify different aspects of products. Treating them as interchangeable product classifications risks inappropriate mappings. Suggested revision: Identify the intended purpose and product level for each classification. Require context-specific mappings with equivalence, version, provenance, and limitations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-167 discuss | in the document all mentions on GitHub record | ||
| PC-1753✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 3 p.146 l.Lines 429-432 |
Packaging hierarchy management is essential but assumes a simple unit, inner pack, case, and pallet hierarchy. Real pac…Packaging hierarchy management is essential but assumes a simple unit, inner pack, case, and pallet hierarchy. Real packaging can contain variable, nested, jurisdiction-specific, and non-linear relationships. Suggested revision: Model repeatable packaging relationships, contained quantity, unit, conversion, GTIN, dimensions, status, and effective period without assuming a fixed four-level hierarchy. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1754✎ edit📣 feedback | received | Metadata registries Supply chain agent |
Product Registry §Product Registry, 3 p.146 l.Lines 429-432 |
Unit-of-measure handling is required but no standard such as UCUM is identified, and count units may differ from admini…Unit-of-measure handling is required but no standard such as UCUM is identified, and count units may differ from administration, dispensing, procurement, and packaging units. Suggested revision: Define governed units and conversion rules, distinguish relevant unit contexts, and reference suitable standards such as UCUM where applicable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1755✎ edit📣 feedback | received | Supply chain Clinical agent, medium |
Product Registry §Product Registry, 3 p.146 l.Lines 433-435 |
Generic-to-item mapping is said to support therapeutic substitution and equivalence determination. Product identity map…Generic-to-item mapping is said to support therapeutic substitution and equivalence determination. Product identity mapping alone does not establish clinical or regulatory interchangeability. Suggested revision: State that the registry can link items to a generic or reference product concept, while therapeutic equivalence and substitution rules require separate authoritative clinical or regulatory governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1756✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 3 p.146 l.Lines 436-438 |
Full version history and lifecycle states are required, but the distinction among product version, packaging version, r…Full version history and lifecycle states are required, but the distinction among product version, packaging version, regulatory status, item status, and publication status is not made. Suggested revision: Define separate lifecycle dimensions and the effect of each status on ordering, dispensing, reporting, and historical records. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-168 discuss | in the document all mentions on GitHub record | ||
| PC-1757✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 3 p.146 l.Lines 439-441 |
Governance workflow is included, but the required roles and authority differ across regulator, manufacturer, procuremen…Governance workflow is included, but the required roles and authority differ across regulator, manufacturer, procurement body, catalogue steward, pharmacy, and national data authority. Suggested revision: Define role and decision-right patterns for submission, validation, regulatory verification, clinical review, approval, publication, correction, and retirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-168 discuss | in the document all mentions on GitHub record | ||
| PC-1758✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 3 p.146 l.Lines 442-444 |
External sources include manufacturers, GDSN, and regulators but not WHO prequalification sources, national procurement…External sources include manufacturers, GDSN, and regulators but not WHO prequalification sources, national procurement systems, device registries, donor catalogues, or international product databases. Suggested revision: Present sources as illustrative and require source-authority assessment, precedence, verification, provenance, licensing, and reconciliation for every onboarded source. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1759✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 4 p.146-147 l.Lines 447-453 |
The Product Catalogue Management Tool is described as downstream from the registry, but operational catalogues may add …The Product Catalogue Management Tool is described as downstream from the registry, but operational catalogues may add attributes and curate product records before the national master is established. Suggested revision: Allow bidirectional governance workflows for proposing product additions or corrections, while preserving the Product Registry as the authoritative identity reference once records are approved. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-165 discuss | in the document all mentions on GitHub record | ||
| PC-1760✎ edit📣 feedback | received | Supply chain Clinical agent, medium |
Product Registry §Product Registry, 4 p.146-147 l.Lines 448-451 |
The list of catalogue attributes includes adverse-event linkage and drug interactions. These may belong to pharmacovigi…The list of catalogue attributes includes adverse-event linkage and drug interactions. These may belong to pharmacovigilance, clinical knowledge, regulatory, or decision-support systems rather than one catalogue tool. Suggested revision: Refine the catalogue scope and identify authoritative sources for each enriched attribute rather than implying one tool originates all information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1761✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Product Registry §Product Registry, 4 p.147 l.Lines 454-460 |
Several operational systems are expected to consume registry data, but no synchronisation, caching, offline distributio…Several operational systems are expected to consume registry data, but no synchronisation, caching, offline distribution, or version-pinning approach is defined. Suggested revision: Provide patterns for live API access, subscriptions, downloadable packages, local mirrors, offline bundles, and version-pinned records, with integrity and update controls. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-1762✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 4 p.147 l.Lines 458-460 |
Cold-chain and transport systems may require facility-specific or shipment-specific handling data not appropriate for t…Cold-chain and transport systems may require facility-specific or shipment-specific handling data not appropriate for the national product master. Suggested revision: Distinguish product-level storage requirements from batch, shipment, or local operational conditions managed by transaction systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1763✎ edit📣 feedback | received | Metadata registries Supply chain agent |
Product Registry §Product Registry, 4 p.147 l.Lines 461-464 |
The Terminology Service is said to manage ATC, UNSPSC, GPC, dosage form, route, and units. Some of these classification…The Terminology Service is said to manage ATC, UNSPSC, GPC, dosage form, route, and units. Some of these classifications or reference datasets may have licensing, distribution, or governance conditions and may not be suitable for direct terminology-server representation without profiling. Suggested revision: Document the authoritative source, version, licence, representation, mapping, and national governance approach for every classification and value set. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-167 discuss | in the document all mentions on GitHub record | ||
| PC-1764✎ edit📣 feedback | received | Metadata registries Supply chain agent |
Product Registry §Product Registry, 4 p.147 l.Lines 463-464 |
The LIMR defines data elements and bindings, but no relationship is described between a logical product model and stand…The LIMR defines data elements and bindings, but no relationship is described between a logical product model and standards such as FHIR Medication, MedicationKnowledge, medicinal-product definitions, device models, or GS1 data structures. Suggested revision: Publish traceability from the logical product model to selected implementation standards and define which artefact is authoritative at each level. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1765✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 4 p.147 l.Lines 465-470 |
The registry is positioned as the foundation for batch and serial traceability. This is correct as a dependency, but th…The registry is positioned as the foundation for batch and serial traceability. This is correct as a dependency, but the registry itself should not necessarily manage every batch, serial number, movement, and custody event. Suggested revision: State explicitly that batch, serial, shipment, and custody events are managed in operational traceability systems referencing the registry’s product identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1766✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Product Registry §Product Registry, 4 p.147 l.Lines 470-472 |
Product, facility, and supplier are called the three master-data pillars. The model omits organisations, manufacturers,…Product, facility, and supplier are called the three master-data pillars. The model omits organisations, manufacturers, regulatory authorities, locations, contracts, and logistics service providers as distinct domains. Suggested revision: Reframe these as three important master-data domains rather than an exhaustive set, and identify the organisation and legal-entity source. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-268 discuss | in the document all mentions on GitHub record | ||
| PC-1767✎ edit📣 feedback | received | Core architects Supply chain agent, medium |
Product Registry §Product Registry, 5 p.147 l.Lines 475-478 |
Requirements are described as Required and Recommended, again conflicting with the SHALL, SHOULD, and MAY convention st…Requirements are described as Required and Recommended, again conflicting with the SHALL, SHOULD, and MAY convention stated in the main document. Suggested revision: Harmonise normative terminology and define conditional applicability for product classes and country maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1768✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.147 l.Lines 475-478 |
The requirements cover all medicines, vaccines, devices, diagnostics, and commodities without indicating which requirem…The requirements cover all medicines, vaccines, devices, diagnostics, and commodities without indicating which requirements apply only to particular product classes. Suggested revision: Add an applicability column identifying universal, medicinal-product, vaccine, device, diagnostic, commodity, packaging, or advanced-maturity requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-063 discuss | in the document all mentions on GitHub record | ||
| PC-1769✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.147 l.Requirement 1 anchor: medium |
Product-image and supporting-document storage is made part of the core product-data requirement. Images and documents m…Product-image and supporting-document storage is made part of the core product-data requirement. Images and documents may be large, licensed, sensitive, or better managed in document repositories. Suggested revision: Make document and image support conditional. Permit governed references to external authoritative document repositories rather than requiring storage within the registry. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1770✎ edit📣 feedback | received | Supply chain agent, medium |
Product Registry §Product Registry, 5 p.147 l.Requirement 1 anchor: medium |
Product information is not required to support multilingual labels, accessible formats, patient-facing descriptions, or…Product information is not required to support multilingual labels, accessible formats, patient-facing descriptions, or low-bandwidth distribution. Suggested revision: Add multilingual designations and accessible publication where the registry supports public, clinical, or dispensing use, while distinguishing professional and patient-facing content. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-1771✎ edit📣 feedback | received | Metadata registries Supply chain agent |
Product Registry §Product Registry, 5 p.147 l.Requirement 2 anchor: medium |
UNSPSC is described parenthetically as covering pharmaceuticals and GPC as covering medical devices. Both are broader c…UNSPSC is described parenthetically as covering pharmaceuticals and GPC as covering medical devices. Both are broader classifications with different commercial purposes; ATC classifies medicines therapeutically rather than identifying products. Suggested revision: Correct the descriptions and state the intended use of each scheme. Avoid suggesting they are interchangeable product identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-167 discuss | in the document all mentions on GitHub record | ||
| PC-1772✎ edit📣 feedback | received | Metadata registries Supply chain agent |
Product Registry §Product Registry, 5 p.147 l.Requirement 2 anchor: medium |
WHODrug is included as a classification source without acknowledging its licensing, scope, or relationship to national …WHODrug is included as a classification source without acknowledging its licensing, scope, or relationship to national regulatory product data and IDMP. Suggested revision: Document licensing and governance conditions and clarify whether it is a terminology, dictionary, mapping source, or authoritative national product-identification source. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-167 discuss | in the document all mentions on GitHub record | ||
| PC-1773✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.147-148 l.Requirement 3 anchor: medium |
Packaging hierarchy is mandatory, but no rules are given for validating quantity conversions, circular relationships, d…Packaging hierarchy is mandatory, but no rules are given for validating quantity conversions, circular relationships, duplicate GTINs, inactive packages, or unit consistency. Suggested revision: Add integrity constraints, unit validation, hierarchy checks, identifier validation, lifecycle rules, and test cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1774✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.148 l.Requirement 4 anchor: medium |
The requirement says generic-to-item mapping supports brand-agnostic procurement. Procurement equivalence may require q…The requirement says generic-to-item mapping supports brand-agnostic procurement. Procurement equivalence may require quality, regulatory, formulation, strength, dosage form, route, packaging, and policy checks beyond a generic relationship. Suggested revision: Describe the registry relationship as an input to procurement equivalence assessment, not proof of interchangeability or procurement suitability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1775✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.148 l.Requirement 5 anchor: medium |
Product-history requirements record change, date, and user but omit source authority, effective date, approval, reason,…Product-history requirements record change, date, and user but omit source authority, effective date, approval, reason, previous value, publication status, and downstream impact. Suggested revision: Expand version and provenance metadata and require impact assessment for changes affecting identifiers, packaging, units, status, or mappings. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-168 discuss | in the document all mentions on GitHub record | ||
| PC-1776✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.148 l.Requirement 6 anchor: medium |
Assigning and managing GTINs may exceed the authority of a national health Product Registry. GTINs are normally issued …Assigning and managing GTINs may exceed the authority of a national health Product Registry. GTINs are normally issued under GS1 rules by authorised organisations. Suggested revision: State that the registry records and validates externally assigned identifiers and assigns national identifiers only under the appropriate national authority and governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1777✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.148 l.Requirement 7 anchor: medium |
Linking national identifiers to global identifiers is described as straightforward equivalence. National and global ide…Linking national identifiers to global identifiers is described as straightforward equivalence. National and global identifiers may represent different product or packaging levels. Suggested revision: Require level-aware mappings, mapping type, purpose, equivalence, validity, evidence, and human review of ambiguous relationships. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1778✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Product Registry §Product Registry, 5 p.148 l.Requirement 8 anchor: medium |
Role-based access is appropriate for authoring, but manufacturer submissions and automated source integrations also req…Role-based access is appropriate for authoring, but manufacturer submissions and automated source integrations also require organisational trust, digital signatures, delegated authority, and data segregation. Suggested revision: Add organisation and credential verification, attribute-based permissions, submission provenance, digital-signature support where appropriate, and separation of submitter and approver roles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1779✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.148 l.Requirement 9 anchor: medium |
Governance workflows require designated approvers but do not account for different approval authorities across regulato…Governance workflows require designated approvers but do not account for different approval authorities across regulatory, clinical, logistics, and master-data attributes. Suggested revision: Use attribute- and product-class-specific approval workflows with clear source authority and escalation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1780✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.148 l.Requirement 10 anchor: medium |
Activation, deactivation, deprecation, and retirement are required, but the effect of each status on existing stock, hi…Activation, deactivation, deprecation, and retirement are required, but the effect of each status on existing stock, historic records, procurement, dispensing, and substitutions is not specified. Suggested revision: Define lifecycle semantics and consumer obligations. Prohibit deletion of identifiers needed to interpret historical transactions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-168 discuss | in the document all mentions on GitHub record | ||
| PC-1781✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.148-149 l.Requirement 11 anchor: medium |
Bulk import is only Recommended, although initial onboarding and synchronisation with regulators, donors, manufacturers…Bulk import is only Recommended, although initial onboarding and synchronisation with regulators, donors, manufacturers, and procurement systems will commonly require it. Suggested revision: Make bulk onboarding or an equivalent migration capability mandatory, with validation, matching, dry run, approval, rollback, and detailed error reporting. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1782✎ edit📣 feedback | received | Supply chain agent, medium |
Product Registry §Product Registry, 5 p.149 l.Requirement 12 anchor: medium |
GDSN, WHODrug, and IDMP are listed as external sources, but access and national adoption vary significantly.GDSN, WHODrug, and IDMP are listed as external sources, but access and national adoption vary significantly. Suggested revision: Make each integration conditional and require a country-specific source strategy identifying authority, licensing, availability, mapping, and fallback. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1783✎ edit📣 feedback | received | Supply chain Metadata registries agent, medium |
Product Registry §Product Registry, 5 p.149 l.Requirement 12 anchor: medium |
“National IDMP implementations” may be unfamiliar and may not exist outside regulated medicinal-product environments.“National IDMP implementations” may be unfamiliar and may not exist outside regulated medicinal-product environments. Suggested revision: Define IDMP and scope it to applicable medicinal-product use cases rather than the entire health-product registry. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-167 discuss | in the document all mentions on GitHub record | ||
| PC-1784✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Product Registry §Product Registry, 5 p.149 l.Requirement 13 anchor: medium |
Machine-readable APIs are required but no national profile, resource model, event specification, bulk-export format, or…Machine-readable APIs are required but no national profile, resource model, event specification, bulk-export format, or security requirements are identified. Suggested revision: Publish a national Product Registry implementation guide covering query, history, package relationships, classification, search, events, bulk access, security, and conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-169 discuss | in the document all mentions on GitHub record | ||
| PC-1785✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Product Registry §Product Registry, 5 p.149 l.Requirement 13 anchor: medium |
Requiring all downstream systems to retrieve data through APIs may not work in low-connectivity settings or with legacy…Requiring all downstream systems to retrieve data through APIs may not work in low-connectivity settings or with legacy platforms. Suggested revision: Support live APIs, synchronised local caches, downloadable packages, secure files, and offline bundles with version and integrity control. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-1786✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Product Registry §Product Registry, 5 p.149 l.Requirement 14 anchor: medium |
Audit logging covers authoring, publication, access control, and imports but not queries, bulk exports, external-source…Audit logging covers authoring, publication, access control, and imports but not queries, bulk exports, external-source synchronisation, failed validation, mapping changes, or access to licensed content. Suggested revision: Define a complete audit profile proportionate to data sensitivity and licensing obligations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-168 discuss | in the document all mentions on GitHub record | ||
| PC-1787✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 5 p.149 l.Requirement 15 anchor: medium |
Subscriptions are Recommended, although product recalls, regulatory withdrawal, identifier replacement, and safety-rela…Subscriptions are Recommended, although product recalls, regulatory withdrawal, identifier replacement, and safety-related status changes may require urgent notifications. Suggested revision: Make critical status-event notification mandatory for authorised subscribers and define priority, delivery, acknowledgement, correction, and escalation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-169 discuss | in the document all mentions on GitHub record | ||
| PC-1788✎ edit📣 feedback | received | Supply chain Core architects agent |
Product Registry §Product Registry, 5 p.149 l.Requirement 16 anchor: medium |
High availability is mandatory but no measurable service classes are defined. Not every catalogue query has the same cr…High availability is mandatory but no measurable service classes are defined. Not every catalogue query has the same criticality as dispensing or recall validation. Suggested revision: Define service classes with availability, response time, recovery, offline access, update freshness, and degraded-mode requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-169 discuss | in the document all mentions on GitHub record | ||
| PC-1789✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.149 l.Lines 484-487 anchor: medium |
Data elements are said to be mandatory for interoperability, but field-level applicability varies by product class and …Data elements are said to be mandatory for interoperability, but field-level applicability varies by product class and product-identification level. Suggested revision: Add columns for product class, product level, source authority, applicability, verification, and maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1790✎ edit📣 feedback | received | Metadata registries Supply chain agent, medium |
Product Registry §Product Registry, 6 p.150 l.“Generic product identifier” anchor: medium |
A universal generic-product identifier is assumed without identifying the governing terminology or model. ATC codes do …A universal generic-product identifier is assumed without identifying the governing terminology or model. ATC codes do not uniquely identify a clinical product with ingredient, strength, form, and route. Suggested revision: Define or adopt a governed clinical-product model and identifier scheme, with mappings to relevant terminologies and regulated products. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1791✎ edit📣 feedback | received | Supply chain Metadata registries agent, low |
Product Registry §Product Registry, 6 p.150 l.“Generic product description” anchor: medium |
Human-readable descriptions may vary by language, naming rules, and level of specificity.Human-readable descriptions may vary by language, naming rules, and level of specificity. Suggested revision: Generate descriptions from governed structured attributes where possible and support multiple languages, synonyms, and naming conventions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1792✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Item identifier GTIN” anchor: medium |
GTIN is marked Mandatory for every product item. Some locally manufactured, donated, compounded, emergency, or unpackag…GTIN is marked Mandatory for every product item. Some locally manufactured, donated, compounded, emergency, or unpackaged products may not have a GTIN. Suggested revision: Require a canonical item identifier and record GTIN where assigned. Support national or temporary identifiers with provenance and later mapping. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1793✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Brand name” anchor: medium |
Brand name is Mandatory, although generic, unbranded, compounded, bulk, or programme commodities may not have one.Brand name is Mandatory, although generic, unbranded, compounded, bulk, or programme commodities may not have one. Suggested revision: Make brand name conditional and support generic or non-proprietary items explicitly. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1794✎ edit📣 feedback | received | Supply chain Metadata registries agent, medium |
Product Registry §Product Registry, 6 p.150 l.“Unit of measure” anchor: medium |
One base unit may not represent procurement, package, dispensing, administration, stock, and dose units.One base unit may not represent procurement, package, dispensing, administration, stock, and dose units. Suggested revision: Model multiple unit contexts and governed conversion relationships, with standard codes and validation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1795✎ edit📣 feedback | received | Metadata registries Supply chain agent, medium |
Product Registry §Product Registry, 6 p.150 l.“Product classification” anchor: medium |
Classification is Mandatory but no individual scheme is universally applicable to every product class.Classification is Mandatory but no individual scheme is universally applicable to every product class. Suggested revision: Require at least one approved classification appropriate to the product type and use case, with scheme, version, and mapping metadata. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1796✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Dosage form,” “Strength,” and “Route” anchor: medium |
These elements are Mandatory for all health products, but they are not applicable to many devices, diagnostics, supplie…These elements are Mandatory for all health products, but they are not applicable to many devices, diagnostics, supplies, or non-medicinal commodities. Suggested revision: Make them conditional for medicinal products and applicable product classes. Define alternative device and diagnostic attributes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1797✎ edit📣 feedback | received | Supply chain Metadata registries agent, medium |
Product Registry §Product Registry, 6 p.150 l.“Strength” anchor: medium |
Strength is presented as one quantity, but medicinal products may have numerator and denominator, concentration, multip…Strength is presented as one quantity, but medicinal products may have numerator and denominator, concentration, multiple ingredients, presentation strength, and ingredient-specific units. Suggested revision: Use a structured strength model supporting multiple ingredients, numerator and denominator, unit, basis of strength, and presentation context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1798✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Manufacturer name” anchor: medium |
Manufacturer is stored as a name rather than linked to an authoritative organisation record. Products may also involve …Manufacturer is stored as a name rather than linked to an authoritative organisation record. Products may also involve marketing-authorisation holders, legal manufacturers, contract manufacturers, and packagers. Suggested revision: Represent typed relationships to authoritative organisation identifiers with effective periods and jurisdictions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1799✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Country of origin” anchor: medium |
Country of origin is Mandatory but may vary by batch, manufacturing stage, component, or packaging location and may not…Country of origin is Mandatory but may vary by batch, manufacturing stage, component, or packaging location and may not be a stable product-master attribute. Suggested revision: Define the exact meaning and make it conditional. Store batch- or shipment-specific origin in operational traceability systems where appropriate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1800✎ edit📣 feedback | received | Supply chain Metadata registries agent, medium |
Product Registry §Product Registry, 6 p.150 l.“Route of administration” anchor: medium |
A medicinal product may support several approved routes, each subject to national authorisation and terminology.A medicinal product may support several approved routes, each subject to national authorisation and terminology. Suggested revision: Make route repeatable, versioned, tied to the regulated product and jurisdiction, and governed through appropriate value sets. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1801✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Shelf life from production” anchor: medium |
Shelf life is Mandatory across all product types and may vary by packaging, storage condition, formulation, market, or …Shelf life is Mandatory across all product types and may vary by packaging, storage condition, formulation, market, or regulatory authorisation. Suggested revision: Make it product-class- and item-specific, with conditions, unit, source, effective period, and jurisdiction. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1802✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Storage requirements” anchor: medium |
Storage requirements are represented mainly as temperature and humidity, but may also include light, orientation, steri…Storage requirements are represented mainly as temperature and humidity, but may also include light, orientation, sterility, hazardous-material handling, vibration, security, and post-opening conditions. Suggested revision: Use a structured, extensible condition model and distinguish product-master conditions from shipment or local operational requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1803✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Volumetrics” anchor: medium |
Dimensions and weight are Mandatory but differ by packaging level and may not be available for every item.Dimensions and weight are Mandatory but differ by packaging level and may not be available for every item. Suggested revision: Record them per packaging level where available and required for logistics; do not make them universally mandatory for initial publication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1804✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Packaging hierarchy level” anchor: medium |
The field description does not explicitly require parent-child package relationships, status, effective date, or valida…The field description does not explicitly require parent-child package relationships, status, effective date, or validation of conversion factors. Suggested revision: Add these properties and publish hierarchy-integrity rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1805✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.150 l.“Generic product to item mapping” anchor: medium |
The mapping is mandatory and is said to support substitution and equivalence. Some devices, diagnostics, and unique pro…The mapping is mandatory and is said to support substitution and equivalence. Some devices, diagnostics, and unique products have no meaningful generic-to-item relationship. Suggested revision: Make the relationship conditional and distinguish identity grouping from therapeutic, functional, procurement, or regulatory equivalence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1806✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.151 l.“Brand mappings” anchor: medium |
Brand mappings are Recommended but overlap with the mandatory generic-to-item mapping and brand field.Brand mappings are Recommended but overlap with the mandatory generic-to-item mapping and brand field. Suggested revision: Consolidate these relationships into one structured product-concept and item relationship model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-166 discuss | in the document all mentions on GitHub record | ||
| PC-1807✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, 6 p.151 l.“Item registration details” anchor: medium |
Regulatory registration is only Recommended, although the registry is described as containing products recognised for n…Regulatory registration is only Recommended, although the registry is described as containing products recognised for national use. Suggested revision: Make regulatory status mandatory where regulation applies, while supporting exempt, emergency, donated, investigational, unregulated, or pending categories. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1808✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, Governance p.151 l.Governance item 1 anchor: medium |
Timely alignment with the regulator is required, but no maximum update latency, data-sharing method, conflict rule, or …Timely alignment with the regulator is required, but no maximum update latency, data-sharing method, conflict rule, or incident process is specified. Suggested revision: Define source authority, service levels, events, acknowledgement, reconciliation, escalation, and urgent propagation for recalls, suspensions, and withdrawals. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1809✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, Governance p.151 l.Governance item 2 anchor: medium |
The governance framework must decide precedence where GDSN or manufacturer data conflicts with national regulatory data…The governance framework must decide precedence where GDSN or manufacturer data conflicts with national regulatory data. Regulatory authority should generally govern national authorisation, while manufacturers may govern selected item and packaging attributes. Suggested revision: Define precedence at attribute level rather than selecting one source for the entire record. Preserve provenance and unresolved conflicts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-164 #22 | in the document all mentions on GitHub record | ||
| PC-1810✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry, Governance p.151 l.Governance item 3 anchor: medium |
Registry and catalogue lifecycle coordination is mentioned, but the impact on procurement, warehouse, prescribing, disp…Registry and catalogue lifecycle coordination is mentioned, but the impact on procurement, warehouse, prescribing, dispensing, claims, and traceability systems is not included. Suggested revision: Require dependency and impact analysis across all registered consumers before major identifier, status, package, or classification changes are published. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-168 discuss | in the document all mentions on GitHub record | ||
| PC-1811✎ edit📣 feedback | received | Editorial Supply chain agent, medium |
Product Registry §Product Registry comparison p.151-154 l.Comparison table anchor: medium |
The comparison usefully separates the registry from catalogue management but is very long and repeats previous material.The comparison usefully separates the registry from catalogue management but is very long and repeats previous material. Suggested revision: Retain a concise boundary table in Appendix C and move detailed operational examples to a separate implementation guide. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1812✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry comparison p.151-154 l.“What it holds” row anchor: medium |
The registry column includes regulatory, storage, volumetric, shelf-life, and clinical attributes that are not always s…The registry column includes regulatory, storage, volumetric, shelf-life, and clinical attributes that are not always stable core identity data. This weakens the proposed boundary with the catalogue. Suggested revision: Reassess each attribute against authority, stability, reuse, and product level. Separate identity-core, regulatory, logistics, and clinical-enrichment datasets. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1813✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry comparison p.152 l.“Data stability” row anchor: medium |
Registry attributes are classified as stable and catalogue attributes as dynamic. Regulatory status, packaging, manufac…Registry attributes are classified as stable and catalogue attributes as dynamic. Regulatory status, packaging, manufacturer, and product authorisation can change materially, while some formulary or clinical attributes may remain stable for long periods. Suggested revision: Use relative update frequency and governance authority rather than a stable-versus-dynamic binary distinction. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1814✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Product Registry §Product Registry comparison p.152 l.“Number of instances” row anchor: medium |
The table states that there should be one Product Registry per country. This conflicts with the architecture’s support …The table states that there should be one Product Registry per country. This conflicts with the architecture’s support for federated and hybrid implementations and with distributed regulatory authority. Suggested revision: Replace with “one nationally governed authoritative product-reference arrangement,” which may be realised through one or more coordinated systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-051 discuss | in the document all mentions on GitHub record | ||
| PC-1815✎ edit📣 feedback | received | Supply chain agent, medium |
Product Registry §Product Registry comparison p.152-153 l.“What it does not do” row anchor: medium |
Pricing, formulary status, substitution rules, and clinical indications are excluded from the registry, but earlier man…Pricing, formulary status, substitution rules, and clinical indications are excluded from the registry, but earlier mandatory and core attributes already include some clinical and regulatory enrichment. Suggested revision: Harmonise the boundary across the architecture placement, requirements, data table, and comparison table. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-163 discuss | in the document all mentions on GitHub record | ||
| PC-1816✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry comparison p.153 l.“Governance” row anchor: medium |
A single national steward is proposed, but product governance is often distributed across regulators, procurement autho…A single national steward is proposed, but product governance is often distributed across regulators, procurement authorities, formulary committees, device agencies, and standards bodies. Suggested revision: Define one accountable coordinating authority with distributed attribute-level stewardship and formal decision rights. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-051 discuss | in the document all mentions on GitHub record | ||
| PC-1817✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry comparison p.153 l.“Relationship” row anchor: medium |
The table says a product cannot be published in any catalogue before a Product Registry record exists. This may be impr…The table says a product cannot be published in any catalogue before a Product Registry record exists. This may be impractical during emergency procurement, local compounding, donations, or initial migration. Suggested revision: Allow provisional product records and controlled temporary catalogue entries, with time-bound verification, restricted use, and later reconciliation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-168 discuss | in the document all mentions on GitHub record | ||
| PC-1818✎ edit📣 feedback | received | Supply chain agent, medium |
Product Registry §Product Registry comparison p.153 l.“Primary users” row anchor: medium |
The registry users include many operational systems, but patients, public-health agencies, customs authorities, regulat…The registry users include many operational systems, but patients, public-health agencies, customs authorities, regulators, and researchers are not represented. Suggested revision: Expand or qualify the list and define distinct access profiles appropriate to each user group. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-169 discuss | in the document all mentions on GitHub record | ||
| PC-1819✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry comparison p.153 l.“Risk if absent” row anchor: medium |
The consequences are stated categorically without acknowledging that countries may achieve product-data consistency thr…The consequences are stated categorically without acknowledging that countries may achieve product-data consistency through existing regulatory registers, shared catalogues, or regional services. Suggested revision: State that these risks arise when no effective authoritative product-reference arrangement exists, regardless of the technology or component name used. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-051 discuss | in the document all mentions on GitHub record | ||
| PC-1820✎ edit📣 feedback | received | Metadata registries Supply chain agent, medium |
Product Registry §Product Registry comparison p.154 l.“Relevant standards” row anchor: medium |
The standards list mixes identifiers, classifications, dictionaries, clinical terminologies, exchange resources, and mo…The standards list mixes identifiers, classifications, dictionaries, clinical terminologies, exchange resources, and model lists. Their roles and interoperability relationships are not explained. Suggested revision: Categorise the standards by purpose and identify which are normative, optional, licensed, product-class-specific, or used only for mapping. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-167 discuss | in the document all mentions on GitHub record | ||
| PC-1821✎ edit📣 feedback | received | Supply chain Metadata registries agent, medium |
Product Registry §Product Registry overall p.145-154 l.Complete component description anchor: medium |
The component lacks a complete implementation and conformance package covering product levels, identifier validation, p…The component lacks a complete implementation and conformance package covering product levels, identifier validation, packaging relationships, classification mappings, status transitions, source precedence, and critical-event notification. Suggested revision: Publish product-class-aware logical models, national profiles, terminology and identifier rules, validation constraints, test datasets, event specifications, security requirements, and conformance tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1822✎ edit📣 feedback | received | Supply chain agent |
Product Registry §Product Registry overall p.145-154 l.Complete component description anchor: medium |
The specification assumes access to GTIN, GDSN, WHODrug, IDMP, detailed packaging hierarchies, verified regulator data,…The specification assumes access to GTIN, GDSN, WHODrug, IDMP, detailed packaging hierarchies, verified regulator data, and high-availability APIs. These conditions will not hold in every country or for every product class. Suggested revision: Define progressive maturity levels beginning with governed product lists and national identifiers, then standard classifications, packaging and global identifiers, regulator integration, eventing, and advanced traceability support. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1823✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record p.155 l.Architecture placement anchor: medium |
The LHR is placed in the foundational shared data layer alongside authoritative registries. Unlike the registries, howe…The LHR is placed in the foundational shared data layer alongside authoritative registries. Unlike the registries, however, it contains or provides access to person-level clinical information generated through operational care processes. Its inclusion in the same layer requires stronger justification. Suggested revision: Explain that the LHR is included because it provides a reusable longitudinal health-information capability across programmes, not because it is a metadata registry. Visually distinguish it from authoritative entity registries within the foundational layer. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1824✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record p.155 l.Architecture placement anchor: medium |
The component name may imply that one national system stores every person’s complete health record throughout life. Thi…The component name may imply that one national system stores every person’s complete health record throughout life. This conflicts with the permitted centralised, federated, and hybrid implementation models. Suggested revision: Define the LHR as a governed capability providing longitudinal access to relevant health information, whether through consolidated storage, federated retrieval, document indexing, or a hybrid arrangement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1825✎ edit📣 feedback | received | Clinical Metadata registries agent, low |
Lifelong Health Record §Lifelong Health Record p.155 l.Architecture placement anchor: medium |
The relationship among Lifelong Health Record, Shared Health Record, longitudinal health record, electronic health reco…The relationship among Lifelong Health Record, Shared Health Record, longitudinal health record, electronic health record, and patient summary is not clearly standardised. These terms have different meanings across countries and architectures. Suggested revision: Provide a terminology comparison clarifying the preferred term, accepted synonyms, narrower or broader concepts, and concepts that should not be treated as equivalent. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1826✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record p.155 l.Architecture placement anchor: medium |
The distinction between the LHR and facility-level EMR or EHR systems is directionally clear but insufficient for platf…The distinction between the LHR and facility-level EMR or EHR systems is directionally clear but insufficient for platforms that combine local clinical workflows with regional or national longitudinal records. Suggested revision: State that classification applies to the logical capability rather than the entire software product. One platform may realise both operational EHR functionality and LHR services, provided their responsibilities, data ownership, interfaces, and conformance boundaries remain separable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1827✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 1 p.155 l.Purpose and scope anchor: medium |
The component aims to provide access to health information across a person’s lifetime, but the scope of information con…The component aims to provide access to health information across a person’s lifetime, but the scope of information considered appropriate for national or shared longitudinal access is not clearly bounded. Suggested revision: Define nationally configurable inclusion criteria based on care continuity, public value, sensitivity, legal authority, clinical relevance, retention requirements, and selected priority use cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1828✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 1 p.155 l.Purpose and scope anchor: medium |
A comprehensive lifelong record may be unrealistic where routine health information remains paper-based, fragmented, in…A comprehensive lifelong record may be unrealistic where routine health information remains paper-based, fragmented, inconsistently coded, or unavailable electronically. Suggested revision: Define progressive LHR maturity levels beginning with selected documents or summary datasets, followed by priority structured data domains and broader longitudinal access as readiness improves. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1829✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 1 p.155-156 l.Purpose and scope anchor: medium |
The description may imply that the LHR is the authoritative source of all clinical data. In many implementations, sourc…The description may imply that the LHR is the authoritative source of all clinical data. In many implementations, source clinical systems remain authoritative and the LHR maintains copies, summaries, references, or indexed access. Suggested revision: Distinguish source clinical records, contributed copies, derived summaries, document indexes, and federated references. Require provenance and source authority to be retained for every item. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1830✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 1 p.155-156 l.Purpose and scope anchor: medium |
The component appears to cover record storage, exchange, patient access, aggregation, consent enforcement, and possibly…The component appears to cover record storage, exchange, patient access, aggregation, consent enforcement, and possibly analytics. Combining all these responsibilities can create an overly broad national platform. Suggested revision: Separate the logical services of record contribution, discovery, retrieval, longitudinal assembly, patient access, consent or policy enforcement, and secondary-use export. Clarify which are core LHR responsibilities and which are provided by other components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1831✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 1 p.156 l.Purpose and scope anchor: medium |
A lifelong record can increase the consequences of unauthorised access by making sensitive information from many provid…A lifelong record can increase the consequences of unauthorised access by making sensitive information from many providers and life stages accessible through one capability. Suggested revision: Require privacy and security architecture proportionate to aggregation risk, including segmentation, purpose-based access, sensitive-data handling, least privilege, strong audit, breach containment, and differentiated access to specific data categories. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1832✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 1 p.156 l.Purpose and scope anchor: medium |
The LHR’s value may be framed primarily through digital access by individuals and providers. People without digital ide…The LHR’s value may be framed primarily through digital access by individuals and providers. People without digital identity, devices, literacy, connectivity, or stable residence may be excluded. Suggested revision: Require assisted access, authorised representatives, accessible formats, non-digital alternatives, multilingual support, low-bandwidth channels, and processes for people without foundational digital identity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | ||
| PC-1833✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 2 p.156 l.Rationale and expected outcomes anchor: medium |
The section associates longitudinal records with better continuity, reduced duplication, safer care, and stronger patie…The section associates longitudinal records with better continuity, reduced duplication, safer care, and stronger patient control. These benefits depend on content completeness, data quality, workflow integration, and actual use. Suggested revision: Qualify the claims and cite implementation evidence. State the enabling conditions required for the LHR to contribute to each expected outcome. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1834✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 2 p.156 l.Rationale and expected outcomes anchor: medium |
The LHR is strongly associated with trusted personal records and continuity of care, but its contribution to financing,…The LHR is strongly associated with trusted personal records and continuity of care, but its contribution to financing, surveillance, supply chain, workforce, and resilience is less direct. Suggested revision: Provide a goal mapping that distinguishes direct contribution, indirect contribution, and no material contribution, together with the other components required for each use case. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-135 discuss | in the document all mentions on GitHub record | ||
| PC-1835✎ edit📣 feedback | received | Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, 2 p.156 l.Rationale and expected outcomes anchor: medium |
Reducing repeated diagnostic tests is presented as an expected benefit. Clinicians may still repeat tests because infor…Reducing repeated diagnostic tests is presented as an expected benefit. Clinicians may still repeat tests because information is outdated, clinically unsuitable, inaccessible, uncertain, or obtained under different quality conditions. Suggested revision: Use measured wording and require provenance, timing, method, quality, and clinical-context information so receiving professionals can assess whether previous results are reusable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1836✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 2 p.156 l.Rationale and expected outcomes anchor: medium |
The component may be described as enabling a “complete” patient history. No national longitudinal record is likely to b…The component may be described as enabling a “complete” patient history. No national longitudinal record is likely to be complete, particularly during transition or where providers remain unconnected. Suggested revision: Use “available longitudinal health information” and require visible completeness, coverage, source, and freshness indicators so users do not mistake an incomplete record for a complete history. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1837✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.156-157 l.Core attributes anchor: medium |
Person-centred longitudinal organisation is fundamental, but the record may also need episode, condition, programme, fa…Person-centred longitudinal organisation is fundamental, but the record may also need episode, condition, programme, family, maternal-child, and population contexts. Suggested revision: Retain the person as the principal subject while allowing additional clinically relevant relationships and contexts through governed models and privacy controls. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1838✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 3 p.156-157 l.Core attributes anchor: medium |
Identity linkage depends on the Client Registry, but the specification does not describe how records are handled when i…Identity linkage depends on the Client Registry, but the specification does not describe how records are handled when identity is provisional, uncertain, duplicated, merged, or later corrected. Suggested revision: Add workflows for provisional identity, uncertain matching, record quarantine, merge and unlink events, identity correction, downstream propagation, and preservation of clinical provenance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1839✎ edit📣 feedback | received | Clinical Metadata registries agent, medium |
Lifelong Health Record §Lifelong Health Record, 3 p.157 l.Core attributes anchor: medium |
The LHR is expected to contain information from several sources, but the minimum semantic requirements for accepting, s…The LHR is expected to contain information from several sources, but the minimum semantic requirements for accepting, storing, and exposing data are not clearly separated. Suggested revision: Define acceptance levels for native conformant structured data, transformed structured data, standard documents, legacy documents, and unstructured content. Preserve source format and transformation provenance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1840✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.157 l.Core attributes anchor: medium |
Requiring structured data for all content may create unrealistic implementation burdens and lead to loss of clinically …Requiring structured data for all content may create unrealistic implementation burdens and lead to loss of clinically important narrative information. Suggested revision: Support a coexistence model covering structured resources, clinical documents, images or links, and narrative text, with progressive structuring of priority information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1841✎ edit📣 feedback | received | Metadata registries Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.157 l.Core attributes anchor: medium |
The specification depends on the LIMR and Terminology Service but does not define how profile versions, terminology edi…The specification depends on the LIMR and Terminology Service but does not define how profile versions, terminology editions, retired codes, and locally extended concepts are preserved over a person’s lifetime. Suggested revision: Require each data item to retain the applicable model, profile, terminology system, version, code, mapping, and validation status used when it was created or transformed. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1842✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.157 l.Core attributes anchor: medium |
Clinical provenance is essential but may be underspecified. Provenance requires more than author, facility, and date.Clinical provenance is essential but may be underspecified. Provenance requires more than author, facility, and date. Suggested revision: Include source system, responsible organisation, contributor, encounter, creation and recorded time, transformation, signature or attestation, verification status, model version, terminology version, and correction history. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1843✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.157 l.Core attributes anchor: medium |
A record may contain corrected, amended, entered-in-error, preliminary, final, or retracted information. Treating all i…A record may contain corrected, amended, entered-in-error, preliminary, final, or retracted information. Treating all information as equally current or valid could create clinical risk. Suggested revision: Require lifecycle and verification status for every clinical information item, with rules for supersession, correction, amendment, retraction, and display of historical content. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1844✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 3 p.157-158 l.Core attributes anchor: medium |
Consent management may be treated as the primary mechanism governing access. In healthcare, processing may also rely on…Consent management may be treated as the primary mechanism governing access. In healthcare, processing may also rely on treatment, statutory public-health duties, legal obligations, vital interests, or other lawful bases. Suggested revision: Refer to access and use policy based on applicable lawful basis, purpose, consent or preference where relevant, professional role, organisation, relationship, and emergency context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-1845✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.157-158 l.Core attributes anchor: medium |
A single consent status cannot adequately represent different data categories, purposes, recipients, time periods, juri…A single consent status cannot adequately represent different data categories, purposes, recipients, time periods, jurisdictions, and withdrawal conditions. Suggested revision: Use granular, versioned consent or policy records with purpose, data category, recipient, action, scope, validity, source, representative authority, and applicable exceptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-1846✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 3 p.158 l.Core attributes anchor: medium |
Sensitive information such as mental-health, reproductive-health, genetic, substance-use, sexual-health, adolescent, an…Sensitive information such as mental-health, reproductive-health, genetic, substance-use, sexual-health, adolescent, and safeguarding records may require additional restrictions. Suggested revision: Require configurable data segmentation and sensitivity labelling, with jurisdiction-specific policy, break-glass controls, audit, notification, and safeguards against fragmented or unsafe care. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-1847✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.158 l.Core attributes anchor: medium |
Emergency access may be necessary where consent or normal authorisation cannot be obtained, but the conditions and safe…Emergency access may be necessary where consent or normal authorisation cannot be obtained, but the conditions and safeguards are not clearly described. Suggested revision: Define emergency access criteria, minimum necessary disclosure, justification, enhanced audit, retrospective review, notification where appropriate, and sanctions for misuse. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-1848✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.158 l.Core attributes anchor: medium |
The LHR is expected to support data contributed by public and private providers, but source onboarding, data-quality ob…The LHR is expected to support data contributed by public and private providers, but source onboarding, data-quality obligations, certification, and liability are not defined. Suggested revision: Require contributor agreements covering identity, conformance, data quality, provenance, update obligations, corrections, security, service levels, and responsibility for inaccurate information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-038 discuss | in the document all mentions on GitHub record | ||
| PC-1849✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 3 p.158 l.Core attributes anchor: medium |
Search and retrieval are core services, but the specification does not define minimum search parameters, result complet…Search and retrieval are core services, but the specification does not define minimum search parameters, result completeness, pagination, history, or behaviour when data sources are unavailable. Suggested revision: Publish a national retrieval profile defining query types, identifiers, date and content filters, paging, history, timeout, partial results, source availability, error handling, and conformance tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-176 discuss | in the document all mentions on GitHub record | ||
| PC-1850✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 3 p.158 l.Core attributes anchor: medium |
Subscription and notification are important for care continuity, but event scope may become excessive if every clinical…Subscription and notification are important for care continuity, but event scope may become excessive if every clinical update is broadcast nationally. Suggested revision: Define governed event types, subscriptions, purpose, recipient eligibility, minimum payload, sensitivity, delivery, acknowledgement, retry, expiry, and correction or retraction handling. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-176 discuss | in the document all mentions on GitHub record | ||
| PC-1851✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 3 p.158 l.Core attributes anchor: medium |
The specification gives limited attention to clinical-data reconciliation when multiple sources report conflicting medi…The specification gives limited attention to clinical-data reconciliation when multiple sources report conflicting medications, allergies, diagnoses, or observations. Suggested revision: Distinguish source data from reconciled or curated views. Define responsibility, workflow, provenance, status, and display rules for reconciliation without overwriting original contributions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1852✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.158-159 l.Relationship to other systems anchor: medium |
The LHR’s relationship with facility EHRs and EMRs may imply that all local records should be replicated nationally. Th…The LHR’s relationship with facility EHRs and EMRs may imply that all local records should be replicated nationally. This could create excessive centralisation, cost, and privacy risk. Suggested revision: State that countries should select contribution and retrieval patterns by use case, including summaries, documents, event-based contributions, federated retrieval, or targeted structured datasets. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1853✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.158-159 l.Relationship to other systems anchor: medium |
The Client Registry is a necessary dependency, but the LHR also depends on facility, workforce, terminology, model, tru…The Client Registry is a necessary dependency, but the LHR also depends on facility, workforce, terminology, model, trust, and consent or policy capabilities. Suggested revision: Add a dependency diagram identifying required and optional dependencies for each LHR implementation pattern. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1854✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.159 l.Relationship to other systems |
Facility and workforce identifiers provide provenance, but organisation, device, laboratory, pharmacy, payer, and sourc…Facility and workforce identifiers provide provenance, but organisation, device, laboratory, pharmacy, payer, and source-system identities may also be required. Suggested revision: Include all relevant provenance actors using authoritative identifiers and clearly identify the source for organisation records, which remains a gap in the component catalogue. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1855✎ edit📣 feedback | received | Metadata registries Clinical agent |
Lifelong Health Record §Lifelong Health Record, 4 p.159 l.Relationship to other systems anchor: medium |
The relationship to the Terminology Service and LIMR is described at a high level but not connected to implementation g…The relationship to the Terminology Service and LIMR is described at a high level but not connected to implementation guides, validators, transformation specifications, and release management. Suggested revision: Add an artefact chain showing logical model, terminology binding, implementation profile, validation package, transformation specification, deployed version, and conformance evidence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1856✎ edit📣 feedback | received | Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.159 l.Relationship to other systems |
The LHR may be treated as the primary source for patient-facing digital wallets. A wallet may hold selected copies or c…The LHR may be treated as the primary source for patient-facing digital wallets. A wallet may hold selected copies or credentials rather than provide access to the full longitudinal record. Suggested revision: Describe wallets, portals, mobile applications, printed summaries, and assisted channels as possible access mechanisms that consume defined LHR services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | ||
| PC-1857✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.159 l.Relationship to other systems anchor: medium |
Patient access is beneficial, but the specification does not clearly address proxy access, guardianship, minors, loss o…Patient access is beneficial, but the specification does not clearly address proxy access, guardianship, minors, loss of capacity, deceased persons, shared devices, or domestic-safety risks. Suggested revision: Define representative and delegated access, age and capacity transitions, relationship verification, revocation, shared-device protection, safe communication, and access to records of deceased persons. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | ||
| PC-1858✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.159 l.Relationship to other systems |
The relationship with public-health surveillance and HMIS may encourage direct reuse of identifiable LHR data for secon…The relationship with public-health surveillance and HMIS may encourage direct reuse of identifiable LHR data for secondary purposes. Suggested revision: Require purpose-specific data minimisation, aggregation or de-identification where appropriate, legal authority, approved access, provenance, disclosure control, and separation of care and secondary-use environments. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-252 discuss | in the document all mentions on GitHub record | ||
| PC-1859✎ edit📣 feedback | received | Clinical Financial systems agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.159 l.Relationship to other systems anchor: low |
The LHR may support claims or financing processes, but clinical information should not be exposed broadly to payment sy…The LHR may support claims or financing processes, but clinical information should not be exposed broadly to payment systems when limited coded or administrative evidence is sufficient. Suggested revision: Define purpose-specific financing datasets and interfaces using minimum necessary information. Prevent general claims systems from accessing the full clinical record. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | ||
| PC-1860✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.159-160 l.Implementation patterns anchor: medium |
Centralised, federated, and hybrid models are recognised, but their relative prerequisites, risks, and operational resp…Centralised, federated, and hybrid models are recognised, but their relative prerequisites, risks, and operational responsibilities are not compared systematically. Suggested revision: Add a decision table covering governance, connectivity, source maturity, latency, availability, consent enforcement, data consistency, privacy, cost, local capacity, and disaster recovery. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1861✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.159-160 l.Implementation patterns anchor: medium |
Federated retrieval is sometimes presented as reducing centralisation risk, but it requires source systems to remain av…Federated retrieval is sometimes presented as reducing centralisation risk, but it requires source systems to remain available, conformant, discoverable, and responsive. Suggested revision: Require local availability assessment, caching strategy, source service levels, timeout and partial-result handling, fallback summaries, and continuity arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1862✎ edit📣 feedback | received | Clinical Core architects agent, low |
Lifelong Health Record §Lifelong Health Record, 4 p.159-160 l.Implementation patterns anchor: medium |
Centralised storage can simplify enforcement and availability but increases concentration risk. The specification does …Centralised storage can simplify enforcement and availability but increases concentration risk. The specification does not define architectural controls for limiting the consequences of compromise. Suggested revision: Require data segmentation, encryption, key governance, privileged-access controls, monitoring, compartmentalisation, backup isolation, recovery testing, and breach-containment design. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1863✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 4 p.159-160 l.Implementation patterns anchor: medium |
Hybrid architectures can become operationally unclear if the same information exists in source, shared, cached, and sum…Hybrid architectures can become operationally unclear if the same information exists in source, shared, cached, and summarised forms. Suggested revision: Define source-of-truth rules, copy status, synchronisation, conflict handling, freshness, correction propagation, retention, and deletion or withdrawal behaviour for each data category. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-170 discuss | in the document all mentions on GitHub record | ||
| PC-1864✎ edit📣 feedback | received | Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.160-163 l.Requirements table |
Requirement statuses use Required and Recommended instead of the SHALL, SHOULD, and MAY convention stated in Section 3.…Requirement statuses use Required and Recommended instead of the SHALL, SHOULD, and MAY convention stated in Section 3.5.2. Suggested revision: Harmonise the normative terminology and define universal, conditional, maturity-dependent, and use-case-specific applicability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1865✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.160-163 l.Requirements table |
The requirements do not clearly distinguish obligations for record sources, the LHR service, consuming applications, id…The requirements do not clearly distinguish obligations for record sources, the LHR service, consuming applications, identity services, terminology services, and consent or policy services. Suggested revision: Add an actor or responsible-component column and express every requirement from the perspective of the party that must implement it. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-063 discuss | in the document all mentions on GitHub record | ||
| PC-1866✎ edit📣 feedback | received | Clinical Core architects agent |
Lifelong Health Record §Lifelong Health Record, 5 p.160 l.Record contribution requirement |
Accepting health information from connected systems is required, but the minimum validation to be performed before acce…Accepting health information from connected systems is required, but the minimum validation to be performed before acceptance is not specified. Suggested revision: Require identity, schema, profile, terminology, provenance, authorisation, duplicate, integrity, and security validation, with clear handling of accepted, rejected, quarantined, or conditionally accepted submissions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1867✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 5 p.160 l.Record contribution requirement anchor: medium |
Rejecting non-conformant data may result in clinically important information being unavailable, particularly during tra…Rejecting non-conformant data may result in clinically important information being unavailable, particularly during transition. Suggested revision: Permit quarantined or clearly labelled legacy content where legally and clinically appropriate, while preventing it from being mistaken for fully conformant structured data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1868✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 5 p.160 l.Record retrieval requirement |
Retrieval requirements do not state whether responses must be complete, current, verified, or accompanied by source-ava…Retrieval requirements do not state whether responses must be complete, current, verified, or accompanied by source-availability information. Suggested revision: Require responses to indicate sources queried, sources unavailable, time range, freshness, validation status, omissions, and whether results are complete or partial. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-176 discuss | in the document all mentions on GitHub record | ||
| PC-1869✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 5 p.160 l.Longitudinal assembly requirement |
Chronological assembly alone does not create a clinically coherent longitudinal record. Duplicate, overlapping, contrad…Chronological assembly alone does not create a clinically coherent longitudinal record. Duplicate, overlapping, contradicted, corrected, and differently coded entries require interpretation. Suggested revision: Separate chronological aggregation from clinical reconciliation and derived summary generation. Preserve all source provenance and label algorithmically derived views clearly. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1870✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 5 p.160-161 l.Record correction requirement anchor: medium |
The specification should distinguish correction of factual patient or demographic errors from amendment of a clinician’…The specification should distinguish correction of factual patient or demographic errors from amendment of a clinician’s professional assessment or historical documentation. Suggested revision: Define correction, amendment, annotation, challenge, retraction, and entered-in-error workflows, including decision authority, provenance, notification, and preservation of the original record. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1871✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.161 l.Deletion or erasure requirement anchor: medium |
Deletion may conflict with clinical safety, legal retention, professional accountability, public-health obligations, an…Deletion may conflict with clinical safety, legal retention, professional accountability, public-health obligations, and audit integrity. Suggested revision: Support legally appropriate erasure, restriction, masking, withdrawal from future sharing, and retention exceptions. Do not require physical deletion where law or safety requires continued retention. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1872✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.161 l.Consent and access requirement |
Role-based access control alone is insufficient for a national longitudinal record.Role-based access control alone is insufficient for a national longitudinal record. Suggested revision: Require policy-based access combining role, organisation, relationship, purpose, data sensitivity, lawful basis, consent or preference, assurance, location, and emergency context. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-1873✎ edit📣 feedback | received | Clinical Core architects agent |
Lifelong Health Record §Lifelong Health Record, 5 p.161 l.Break-glass requirement |
Emergency access is not fully testable without defined triggers, permitted data scope, user warnings, documentation, re…Emergency access is not fully testable without defined triggers, permitted data scope, user warnings, documentation, review, and notification. Suggested revision: Publish a national emergency-access profile with positive, negative, misuse, audit, review, and revocation test cases. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-1874✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.161 l.Patient access requirement |
Digital patient access may be mandatory without sufficiently supporting people who cannot authenticate through national…Digital patient access may be mandatory without sufficiently supporting people who cannot authenticate through national digital identity or use online channels. Suggested revision: Require assisted and alternative access supported by suitable identity verification, accessibility, language, representatives, and non-digital record formats. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | ||
| PC-1875✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.161-162 l.Audit requirement |
Audit logging should cover viewing, searching, export, contribution, correction, disclosure, policy evaluation, emergen…Audit logging should cover viewing, searching, export, contribution, correction, disclosure, policy evaluation, emergency access, failed access, and administrative activity. Suggested revision: Define a complete audit-event model, tamper protection, retention, monitoring, patient transparency, investigation access, and privacy controls for the audit logs themselves. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-1876✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.162 l.Subscription and notification requirement |
Notifications can reveal that a person received care or that a sensitive record exists even when the payload omits clin…Notifications can reveal that a person received care or that a sensitive record exists even when the payload omits clinical details. Suggested revision: Treat event metadata as protected information. Apply purpose-specific subscriptions, sensitivity controls, minimum payload, authorisation, and audit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-176 discuss | in the document all mentions on GitHub record | ||
| PC-1877✎ edit📣 feedback | received | Clinical Core architects agent, low |
Lifelong Health Record §Lifelong Health Record, 5 p.162 l.Secondary-use requirement |
Support for analytics, research, planning, or surveillance may be described as a standard LHR function without sufficie…Support for analytics, research, planning, or surveillance may be described as a standard LHR function without sufficient separation from direct-care access. Suggested revision: Require separate access environments, approved datasets, disclosure controls, data minimisation, governance approval, transparency, audit, and re-identification safeguards. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-252 discuss | in the document all mentions on GitHub record | ||
| PC-1878✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.162 l.Availability requirement |
High availability and low latency are required but not quantified and may differ among emergency summary retrieval, ful…High availability and low latency are required but not quantified and may differ among emergency summary retrieval, full-history retrieval, patient access, contribution, and analytics. Suggested revision: Define measurable service classes with availability, latency, throughput, recovery time, recovery point, partial outage, dependency failure, and degraded operation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-103 discuss | in the document all mentions on GitHub record | ||
| PC-1879✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.162 l.Offline requirement |
Offline support may be only Recommended even though the architecture aims to work in low-connectivity settings.Offline support may be only Recommended even though the architecture aims to work in low-connectivity settings. Suggested revision: Make safe offline or degraded operation mandatory where the national implementation includes intermittently connected settings. Define cached dataset scope, validity, encryption, synchronisation, conflict, and audit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-175 discuss | in the document all mentions on GitHub record | ||
| PC-1880✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.162-163 l.Standards requirement anchor: medium |
FHIR, openEHR, IHE, IPS, and other standards may be listed without a clear statement of how they coexist or which is no…FHIR, openEHR, IHE, IPS, and other standards may be listed without a clear statement of how they coexist or which is normative for each exchange pattern. Suggested revision: Publish a standards architecture identifying the role, selected version, national profile, transformation, coexistence, and conformance expectations for each standard. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | ||
| PC-1881✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, 5 p.163 l.Standards requirement anchor: low |
Supporting both FHIR and openEHR does not by itself ensure equivalence between FHIR profiles and openEHR archetypes or …Supporting both FHIR and openEHR does not by itself ensure equivalence between FHIR profiles and openEHR archetypes or templates. Suggested revision: Require explicit model traceability and governed transformations, including information-loss analysis, terminology alignment, validation, and version management. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | ||
| PC-1882✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 5 p.163 l.Patient-summary requirement anchor: medium |
The International Patient Summary may be treated as the minimum LHR dataset. IPS is a specific cross-border and unsched…The International Patient Summary may be treated as the minimum LHR dataset. IPS is a specific cross-border and unscheduled-care summary and does not define the complete longitudinal record. Suggested revision: Present IPS as one priority summary use case and exchange artefact rather than the universal minimum content model for the LHR. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-264 discuss | in the document all mentions on GitHub record | ||
| PC-1883✎ edit📣 feedback | received | Clinical Metadata registries agent, medium |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Minimum dataset anchor: low |
The minimum dataset appears to combine administrative, clinical, provenance, consent, and audit elements without clearl…The minimum dataset appears to combine administrative, clinical, provenance, consent, and audit elements without clearly distinguishing record-level, encounter-level, document-level, and element-level metadata. Suggested revision: Restructure the dataset by information level and define cardinality, applicability, source, terminology, validation, sensitivity, and provenance for every element. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1884✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Minimum dataset anchor: low |
Making broad clinical domains mandatory before an active LHR record can exist may exclude people who have received only…Making broad clinical domains mandatory before an active LHR record can exist may exclude people who have received only limited services or whose historical data is unavailable. Suggested revision: Require the ability to represent the domains, not mandatory presence of data from every domain. Allow an LHR to exist with limited content and display its current coverage visibly. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1885✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Person identifier anchor: low |
A single HUID may be mandatory even though the Client Registry permits multiple identity models and provisional identit…A single HUID may be mandatory even though the Client Registry permits multiple identity models and provisional identities. Suggested revision: Require a resolved person reference according to the national identity model, supporting provisional and multiple linked identifiers where necessary. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1886✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Demographics anchor: low |
Repeating demographic attributes in the LHR can create inconsistency with the Client Registry.Repeating demographic attributes in the LHR can create inconsistency with the Client Registry. Suggested revision: Store a stable person reference and only the demographic snapshot needed to interpret the clinical record, with source and effective date. Use the Client Registry for current authoritative demographics. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1887✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Allergies and adverse reactions anchor: low |
Allergy data requires distinction among allergy, intolerance, adverse event, risk, verification, criticality, clinical …Allergy data requires distinction among allergy, intolerance, adverse event, risk, verification, criticality, clinical status, causative agent, and manifestation. Suggested revision: Use a governed structured model and terminology bindings, preserving source, verification, uncertainty, and correction history. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1888✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Medication information anchor: low |
Medication lists may combine prescribed, dispensed, administered, reported, historical, and current medications. Treati…Medication lists may combine prescribed, dispensed, administered, reported, historical, and current medications. Treating these as one list can be unsafe. Suggested revision: Represent medication events and statements separately and define reconciliation status, source, timing, dosage, product identifiers, and current-use determination. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1889✎ edit📣 feedback | received | Clinical Metadata registries agent, medium |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Diagnoses and problems anchor: low |
Diagnoses, encounter reasons, symptoms, conditions, problem-list entries, and billing codes may have different meanings…Diagnoses, encounter reasons, symptoms, conditions, problem-list entries, and billing codes may have different meanings and confidence. Suggested revision: Model the clinical context, status, verification, role, onset, resolution, source, and coding purpose rather than storing undifferentiated diagnosis codes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1890✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Laboratory and diagnostic results anchor: low |
Results require units, reference ranges, method, device or laboratory, specimen, status, interpretation, and correction…Results require units, reference ranges, method, device or laboratory, specimen, status, interpretation, and correction handling in addition to value and code. Suggested revision: Define a complete result model and require unit and terminology validation, provenance, preliminary or final status, and amended-result notification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1891✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Immunisation data anchor: low |
Immunisation information may come from a dedicated immunisation registry, local systems, patient-held records, or the L…Immunisation information may come from a dedicated immunisation registry, local systems, patient-held records, or the LHR. The authoritative relationship is not defined. Suggested revision: Define source authority, contribution and reconciliation rules, product and batch references, status, dose sequence, and handling of historical or self-reported vaccinations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-177 discuss | in the document all mentions on GitHub record | ||
| PC-1892✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Procedures and encounters anchor: low |
Procedure and encounter records require clear distinction among planned, performed, cancelled, entered-in-error, and hi…Procedure and encounter records require clear distinction among planned, performed, cancelled, entered-in-error, and historical events. Suggested revision: Add lifecycle, participants, facility, organisation, time, reason, outcome, provenance, and status requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1893✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Care plans and referrals anchor: low |
Care-plan and referral workflows are operational and often managed in point-of-care applications. The LHR should not ne…Care-plan and referral workflows are operational and often managed in point-of-care applications. The LHR should not necessarily become the workflow engine. Suggested revision: Store or expose relevant care-plan and referral information while keeping task assignment, scheduling, acceptance, and workflow execution within operational systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-177 discuss | in the document all mentions on GitHub record | ||
| PC-1894✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Clinical documents anchor: low |
Documents may be included without requirements for document identity, type, author, custodian, status, language, confid…Documents may be included without requirements for document identity, type, author, custodian, status, language, confidentiality, signature, format, and replacement relationships. Suggested revision: Define a national clinical-document profile and document-sharing conventions, including metadata, integrity, versioning, supersession, and rendering requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-173 discuss | in the document all mentions on GitHub record | ||
| PC-1895✎ edit📣 feedback | received | Clinical agent |
Lifelong Health Record §Lifelong Health Record, 6 p.163-165 l.Provenance metadata anchor: medium |
Provenance may be specified only as source system, facility, professional, and date, which is insufficient for transfor…Provenance may be specified only as source system, facility, professional, and date, which is insufficient for transformed or derived data. Suggested revision: Include original source, contributor, recorder, transformer, transformation specification, software version, validation status, derivation, signature, and custody history. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-1896✎ edit📣 feedback | received | Clinical Core architects agent |
Lifelong Health Record §Lifelong Health Record, Governance p.165 l.Governance item 1 |
National stewardship is required, but clinical-data responsibility remains distributed among contributing providers and…National stewardship is required, but clinical-data responsibility remains distributed among contributing providers and professionals. Suggested revision: Define accountability for the LHR service, source-data accuracy, model governance, access policy, patient rights, corrections, security, service management, and downstream use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-038 discuss | in the document all mentions on GitHub record | ||
| PC-1897✎ edit📣 feedback | received | Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, Governance p.165 l.Governance item 2 |
Patient control is emphasised, but the limits of control under treatment, public-health, legal-retention, safeguarding,…Patient control is emphasised, but the limits of control under treatment, public-health, legal-retention, safeguarding, and emergency obligations are not clearly explained. Suggested revision: Provide transparent, jurisdiction-specific rules distinguishing individual choice, statutory processing, professional obligations, and legally permitted exceptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-234 discuss | in the document all mentions on GitHub record | ||
| PC-1898✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, Governance p.165 l.Governance item 3 |
Individuals should be able to identify who accessed their record, but raw technical audit logs may be confusing, incomp…Individuals should be able to identify who accessed their record, but raw technical audit logs may be confusing, incomplete, or reveal protected information about professionals and investigations. Suggested revision: Provide understandable access-history views with date, organisation, purpose, action, and support for challenge, subject to proportionate security and legal exceptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-172 discuss | in the document all mentions on GitHub record | ||
| PC-1899✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record, Governance p.165 l.Governance item 4 |
Contributor obligations are not fully connected to enforcement, certification, funding, or sanctions.Contributor obligations are not fully connected to enforcement, certification, funding, or sanctions. Suggested revision: Require contributor agreements, conformance onboarding, data-quality monitoring, correction service levels, incident obligations, suspension criteria, and remediation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-038 discuss | in the document all mentions on GitHub record | ||
| PC-1900✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, Governance p.165 l.Governance section |
The operating cost of national longitudinal storage, high availability, long retention, cybersecurity, consent, audit, …The operating cost of national longitudinal storage, high availability, long retention, cybersecurity, consent, audit, support, and migration is not addressed within the component governance. Suggested revision: Require a lifecycle operating and financing model covering storage growth, retrieval, connectivity, security, support, terminology, conformance, archive, migration, and disaster recovery. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | ||
| PC-1901✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record overall p.155-165 l.Complete component description anchor: medium |
The component lacks a complete implementation and conformance package covering contribution, retrieval, documents, stru…The component lacks a complete implementation and conformance package covering contribution, retrieval, documents, structured data, identity events, consent or policy enforcement, provenance, partial results, offline operation, and correction. Suggested revision: Publish a companion LHR implementation guide containing actors, use cases, information models, terminology bindings, APIs, document profiles, events, security, test data, simulators, service levels, and end-to-end conformance scenarios. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1902✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Lifelong Health Record §Lifelong Health Record overall p.155-165 l.Complete component description anchor: medium |
The target specification assumes mature digital capture, reliable identity resolution, standards-based source systems, …The target specification assumes mature digital capture, reliable identity resolution, standards-based source systems, terminology services, policy enforcement, national exchange, and sustainable high-availability operation. Suggested revision: Define progressive maturity levels starting with priority summaries and documents, then structured domains, multiple contributors, patient access, eventing, federated retrieval, advanced policy enforcement, and broader longitudinal coverage. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1903✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, architecture placement p.166 l.Architecture placement anchor: medium |
The Terminology Service is presented as a foundational component, but the description sometimes conflates the runtime t…The Terminology Service is presented as a foundational component, but the description sometimes conflates the runtime terminology service with the wider terminology-governance function. A service cannot itself determine national terminology policy. Suggested revision: Distinguish terminology governance, terminology content repositories, authoring and publication tools, and runtime terminology services. Explain that these may be implemented through one or several platforms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-1904✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 1 p.166 l.Purpose and scope anchor: medium |
The component may be interpreted as a single national server containing every terminology required by the health system…The component may be interpreted as a single national server containing every terminology required by the health system. Some terminologies are maintained internationally, regionally, by specialist authorities, or under licensing restrictions. Suggested revision: Define it as a nationally governed terminology capability that may host, federate, mirror, or provide controlled access to terminology assets from multiple authoritative sources. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-1905✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 1 p.166 l.Purpose and scope anchor: medium |
The scope should distinguish code systems, value sets, concept maps, naming systems, identifier systems, classification…The scope should distinguish code systems, value sets, concept maps, naming systems, identifier systems, classifications, ontologies, and reference sets. These artefacts have different lifecycle and validation requirements. Suggested revision: Add a terminology-artefact taxonomy and define the services and governance applicable to each artefact type. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1906✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 1 p.166-167 l.Purpose and scope anchor: medium |
A live national terminology service may not be feasible initially in settings with limited connectivity or specialist c…A live national terminology service may not be feasible initially in settings with limited connectivity or specialist capacity. Suggested revision: Permit progressive implementation using governed spreadsheets, versioned packages, downloadable expansions, regional services, local mirrors, and eventually a full runtime service. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1907✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 2 p.167 l.Rationale anchor: medium |
The text may imply that using national terminology services guarantees semantic interoperability. Shared codes do not g…The text may imply that using national terminology services guarantees semantic interoperability. Shared codes do not guarantee consistent use, context, modelling, mappings, or workflow interpretation. Suggested revision: State that terminology services are one enabling capability within the broader semantic-governance and information-model framework. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-1908✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 3 p.167 l.Core attributes anchor: medium |
Authoring, validation, publication, distribution, mapping, expansion, subsumption, translation, and lookup are potentia…Authoring, validation, publication, distribution, mapping, expansion, subsumption, translation, and lookup are potentially combined as one service without identifying which are mandatory at each maturity level. Suggested revision: Separate governance and authoring capabilities from publication and runtime services. Classify capabilities as baseline, conditional, or advanced. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-1909✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 3 p.167 l.Core attributes anchor: medium |
Mapping is included, but mapping relationships can represent exact, broader, narrower, related, inexact, or use-case-sp…Mapping is included, but mapping relationships can represent exact, broader, narrower, related, inexact, or use-case-specific correspondence. Suggested revision: Require mapping purpose, equivalence, source and target versions, author, validation status, evidence, limitations, effective period, and review date. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | ||
| PC-1910✎ edit📣 feedback | received | Metadata registries Clinical agent |
Terminology Service §Terminology Service, 3 p.167-168 l.Core attributes anchor: medium |
Multilingual support is important but should not imply that automatically translated labels are suitable for clinical u…Multilingual support is important but should not imply that automatically translated labels are suitable for clinical use without review. Suggested revision: Require language, locale, preferred and acceptable terms, review status, translation source, and clinical validation. Clearly label machine-generated or provisional translations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-1911✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 3 p.168 l.Core attributes anchor: medium |
Runtime validation is described, but no behaviour is defined for inactive codes, retired value-set members, unknown sys…Runtime validation is described, but no behaviour is defined for inactive codes, retired value-set members, unknown systems, version mismatch, or locally extended codes. Suggested revision: Publish validation rules and structured outcomes covering valid, invalid, inactive, deprecated, unknown, version-mismatched, and locally permitted concepts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1912✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 3 p.168 l.Core attributes anchor: medium |
Dependency and impact analysis are not sufficiently explicit, although terminology changes can affect profiles, data mo…Dependency and impact analysis are not sufficiently explicit, although terminology changes can affect profiles, data models, decision logic, measures, and historical data. Suggested revision: Make dependency management and impact analysis mandatory for changes to widely used concepts, value sets, mappings, and editions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1913✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 4 p.168 l.Relationship to other components |
The relationship with the LIMR is described as bidirectional, but release coordination and responsibility for broken bi…The relationship with the LIMR is described as bidirectional, but release coordination and responsibility for broken bindings are not defined. Suggested revision: Require coordinated release planning, compatibility assessment, dependency tracking, notification, and rollback or remediation procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1914✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 4 p.168 l.Relationship to other components anchor: medium |
Operational systems may be expected to call the Terminology Service synchronously for every validation or user interact…Operational systems may be expected to call the Terminology Service synchronously for every validation or user interaction. This creates availability and latency risks. Suggested revision: Support live calls, validated caches, local mirrors, embedded value-set expansions, and offline packages under controlled version and integrity management. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-1915✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 4 p.168-169 l.Relationship to external standards anchor: medium |
SNOMED CT, ICD-11, LOINC, ATC, UCUM, and other assets differ in purpose, governance, licensing, and national adoption r…SNOMED CT, ICD-11, LOINC, ATC, UCUM, and other assets differ in purpose, governance, licensing, and national adoption requirements. Suggested revision: Add a standards table identifying purpose, authority, licensing, national extension requirements, translation needs, and appropriate use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-067 discuss | in the document all mentions on GitHub record | ||
| PC-1916✎ edit📣 feedback | received | Editorial Metadata registries agent, low |
Terminology Service §Terminology Service, 5 p.169-171 l.Requirements table |
Requirement statuses use Required and Recommended rather than the stated SHALL, SHOULD, and MAY convention.Requirement statuses use Required and Recommended rather than the stated SHALL, SHOULD, and MAY convention. Suggested revision: Harmonise normative terminology and add applicability by maturity, terminology type, licensing, and national use case. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1917✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 5 p.169 l.Import requirement |
Importing external terminology content without validation can introduce invalid versions, licence violations, duplicate…Importing external terminology content without validation can introduce invalid versions, licence violations, duplicate systems, or compromised packages. Suggested revision: Require source authentication, licence verification, integrity checks, namespace validation, staging, quality review, approval, and rollback before publication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1918✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 5 p.169 l.Version requirement |
Versioning is required but does not distinguish code-system version, value-set version, expansion parameters, mapping v…Versioning is required but does not distinguish code-system version, value-set version, expansion parameters, mapping version, package version, and publication status. Suggested revision: Define version semantics for each artefact type and require reproducible historical resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1919✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 5 p.169-170 l.Mapping requirement |
Automated mappings may be used in analytics or clinical exchange despite uncertain equivalence.Automated mappings may be used in analytics or clinical exchange despite uncertain equivalence. Suggested revision: Require human review proportionate to clinical risk, mapping confidence, intended-use restrictions, provenance, and monitoring of mapping-related errors. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | ||
| PC-1920✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 5 p.170 l.API requirement anchor: medium |
FHIR terminology operations may be referenced without specifying the FHIR release, supported operations, parameters, ca…FHIR terminology operations may be referenced without specifying the FHIR release, supported operations, parameters, capability statement, or national constraints. Suggested revision: Publish a national terminology implementation guide defining supported resources, operations, versions, parameters, security, paging, error handling, and tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-087 discuss | in the document all mentions on GitHub record | ||
| PC-1921✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 5 p.170 l.Subscription requirement |
Notification of terminology updates is only Recommended, although dependent systems need timely awareness of critical c…Notification of terminology updates is only Recommended, although dependent systems need timely awareness of critical changes. Suggested revision: Make release and deprecation notifications mandatory for registered consumers, using maturity-appropriate delivery mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1922✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 5 p.170-171 l.Availability requirement |
High availability is required without distinguishing authoring, publication, validation, lookup, and bulk-distribution …High availability is required without distinguishing authoring, publication, validation, lookup, and bulk-distribution services. Suggested revision: Define separate service classes and permit local caches or packages where continuous national connectivity is unavailable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-1923✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, 6 p.171 l.Minimum metadata anchor: low |
Minimum metadata should include more than title, identifier, version, and publisher.Minimum metadata should include more than title, identifier, version, and publisher. Suggested revision: Include canonical identifier, artefact type, jurisdiction, language, status, effective date, licence, source, owner, steward, dependencies, history, review date, and permitted-use information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1924✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, governance p.171 l.Governance section |
The governance section may not clearly identify who approves national extensions, translations, value sets, and mapping…The governance section may not clearly identify who approves national extensions, translations, value sets, and mappings when multiple professional or programme authorities are involved. Suggested revision: Define decision rights, domain-authority roles, public review, conflict resolution, publication authority, appeals, and emergency change procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-1925✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service overall p.166-171 l.Complete component anchor: medium |
The target specification assumes specialised terminology staff, licensing, authoring tools, runtime APIs, mapping gover…The target specification assumes specialised terminology staff, licensing, authoring tools, runtime APIs, mapping governance, and continuous service operation. Suggested revision: Define progressive maturity from governed code lists and packages to national authoring, mapping, runtime validation, federated terminology access, and advanced impact analysis. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1926✎ edit📣 feedback | received | Metadata registries Core architects agent |
Logical Information Model Repository §LIMR, architecture placement p.172 l.Architecture placement anchor: medium |
The LIMR is presented as a distinct DPI-H component although no direct OpenHIE equivalent exists and international cons…The LIMR is presented as a distinct DPI-H component although no direct OpenHIE equivalent exists and international consensus on its precise scope is limited. Suggested revision: Identify it as a proposed shared capability in this architecture and distinguish mature established practices from novel architectural consolidation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-180 discuss | in the document all mentions on GitHub record | ||
| PC-1927✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, architecture placement p.172 l.Architecture placement anchor: low |
“Logical Information Model Repository” may be interpreted as storing only technology-neutral logical models, while the …“Logical Information Model Repository” may be interpreted as storing only technology-neutral logical models, while the specification also includes profiles, schemas, templates, mappings, and implementation artefacts. Suggested revision: Define whether the repository governs logical models only or a linked ecosystem of logical and implementation artefacts. Consider a broader name if necessary. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-180 discuss | in the document all mentions on GitHub record | ||
| PC-1928✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 1 p.172 l.Purpose and scope anchor: medium |
The document implies that one governed logical model can serve FHIR, openEHR, forms, analytics, and other representatio…The document implies that one governed logical model can serve FHIR, openEHR, forms, analytics, and other representations. Transformation among these formalisms is not always lossless or automatic. Suggested revision: Require explicit traceability and mapping among artefacts, including transformation rules, information-loss analysis, validation, and model-specific governance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1929✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 1 p.172 l.Purpose and scope anchor: medium |
Establishing a national logical-model repository may be unrealistic for countries without established modelling methods…Establishing a national logical-model repository may be unrealistic for countries without established modelling methods or specialist teams. Suggested revision: Permit adoption of international or regional models with limited national constraints and publication through simpler repositories before a full LIMR capability is established. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-1930✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 2 p.172-173 l.Rationale anchor: medium |
The section may characterise local variation as inherently undesirable. National and local variation may be clinically,…The section may characterise local variation as inherently undesirable. National and local variation may be clinically, legally, or operationally necessary. Suggested revision: Focus on unmanaged and undocumented variation. Require governed extensions, constraints, mappings, and conformance rather than uniformity for its own sake. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1931✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 3 p.173 l.Core attributes anchor: medium |
Model authoring, review, publication, validation, transformation, distribution, and runtime use are combined without es…Model authoring, review, publication, validation, transformation, distribution, and runtime use are combined without establishing maturity or responsibility. Suggested revision: Separate authoring governance, publication and distribution, implementation-artifact generation, and runtime validation capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1932✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 3 p.173 l.Core attributes anchor: medium |
Model dependency, specialisation, inheritance, constraint, replacement, and deprecation relationships require formal re…Model dependency, specialisation, inheritance, constraint, replacement, and deprecation relationships require formal representation. Suggested revision: Introduce a dependency model and require impact analysis before publication of changes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1933✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 3 p.173 l.Core attributes anchor: medium |
The repository may store models without executable validation artefacts, limiting procurement and conformance value.The repository may store models without executable validation artefacts, limiting procurement and conformance value. Suggested revision: Require generation or publication of machine-readable schemas, profiles, invariants, terminology bindings, examples, and validation packages where technically feasible. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | ||
| PC-1934✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 3 p.173-174 l.Core attributes anchor: medium |
Reuse may be measured by copying model fragments rather than referencing and governing reusable components.Reuse may be measured by copying model fragments rather than referencing and governing reusable components. Suggested revision: Define reusable model components, identifiers, dependency rules, specialisation mechanisms, and prevention of unmanaged duplication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | ||
| PC-1935✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 4 p.174 l.Relationship to Terminology Service anchor: medium |
Terminology bindings require strength, purpose, version, and allowed extension behaviour, not merely a value-set refere…Terminology bindings require strength, purpose, version, and allowed extension behaviour, not merely a value-set reference. Suggested revision: Model required, extensible, preferred, or example bindings, with terminology version, context, jurisdiction, and exceptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | ||
| PC-1936✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 4 p.174 l.Relationship to implementations anchor: medium |
The relationship from logical model to national FHIR profile or openEHR template may be described but not made machine-…The relationship from logical model to national FHIR profile or openEHR template may be described but not made machine-readable. Suggested revision: Require persistent identifiers and traceability links among requirement, logical element, implementation element, terminology binding, test assertion, and deployed version. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-195 discuss | in the document all mentions on GitHub record | ||
| PC-1937✎ edit📣 feedback | received | Metadata registries Editorial agent, medium |
Logical Information Model Repository §LIMR, 5 p.174-176 l.Requirements table anchor: medium |
Requirement statuses remain inconsistent with the main normative convention.Requirement statuses remain inconsistent with the main normative convention. Suggested revision: Apply SHALL, SHOULD, and MAY consistently and identify baseline, conditional, and advanced requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1938✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 5 p.174 l.Model metadata requirement anchor: medium |
Model metadata should include governance and implementation information, not only technical identifiers.Model metadata should include governance and implementation information, not only technical identifiers. Suggested revision: Include purpose, scope, status, owner, steward, clinical reviewer, jurisdiction, language, licence, version, dependencies, effective date, review date, and implementation mappings. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | ||
| PC-1939✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 5 p.174-175 l.Versioning requirement anchor: medium |
The specification may not define backward compatibility, semantic versioning, migration, or support periods.The specification may not define backward compatibility, semantic versioning, migration, or support periods. Suggested revision: Publish lifecycle rules covering draft, trial, active, deprecated, retired, superseded, compatibility, migration guidance, and support periods. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1940✎ edit📣 feedback | received | Metadata registries Clinical agent |
Logical Information Model Repository §LIMR, 5 p.175 l.Validation requirement anchor: medium |
Structural validation alone does not establish clinical validity, usability, implementability, or semantic appropriaten…Structural validation alone does not establish clinical validity, usability, implementability, or semantic appropriateness. Suggested revision: Require clinical, technical, semantic, privacy, safety, and implementation review proportionate to the model’s use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1941✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 5 p.175 l.Local extension requirement anchor: medium |
Allowing local extensions without a feedback or convergence mechanism could perpetuate semantic fragmentation.Allowing local extensions without a feedback or convergence mechanism could perpetuate semantic fragmentation. Suggested revision: Require registration, rationale, namespace, owner, mapping, compatibility, review, and a process for proposing broader national adoption. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-262 discuss | in the document all mentions on GitHub record | ||
| PC-1942✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 5 p.175 l.Publication requirement anchor: medium |
Publication through APIs alone may be insufficient for low-connectivity or low-capacity implementers.Publication through APIs alone may be insufficient for low-connectivity or low-capacity implementers. Suggested revision: Support APIs, downloadable packages, human-readable documentation, examples, offline bundles, and accessible browsing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-1943✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 5 p.175-176 l.Impact analysis requirement anchor: medium |
Impact analysis may be Recommended although model changes can affect clinical systems, analytics, decision support, and…Impact analysis may be Recommended although model changes can affect clinical systems, analytics, decision support, and historical interpretation. Suggested revision: Make impact analysis mandatory for changes to published models used by production systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1944✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR, 5 p.176 l.Notification requirement anchor: medium |
Consumers require notification of changes, deprecations, and security or safety corrections.Consumers require notification of changes, deprecations, and security or safety corrections. Suggested revision: Make release and deprecation notifications mandatory for registered consumers, with acknowledgement for critical changes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-180 discuss | in the document all mentions on GitHub record | ||
| PC-1945✎ edit📣 feedback | received | Editorial Metadata registries agent, medium |
Logical Information Model Repository §LIMR, 6 p.176 l.Minimum dataset anchor: medium |
“Minimum dataset” is not the appropriate term for model-repository metadata and may be confused with clinical minimum d…“Minimum dataset” is not the appropriate term for model-repository metadata and may be confused with clinical minimum datasets. Suggested revision: Rename it Minimum metadata for governed information-model artefacts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-1946✎ edit📣 feedback | received | Metadata registries Clinical agent |
Logical Information Model Repository §LIMR, governance p.176 l.Governance section anchor: medium |
The governance model should avoid allowing a central modelling team to determine clinical meaning without domain partic…The governance model should avoid allowing a central modelling team to determine clinical meaning without domain participation. Suggested revision: Require multidisciplinary domain review involving clinicians, programmes, terminology specialists, implementers, analysts, privacy and safety experts, and affected users where relevant. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-180 discuss | in the document all mentions on GitHub record | ||
| PC-1947✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §LIMR overall p.172-176 l.Complete component |
The specification risks making a sophisticated repository platform a prerequisite for semantic governance.The specification risks making a sophisticated repository platform a prerequisite for semantic governance. Suggested revision: State explicitly that governance, identifiers, versioning, approval, and publication are required from the outset, while tooling can mature progressively. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-180 discuss | in the document all mentions on GitHub record | ||
| PC-1948✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Computable Decision Support Engine §CDSE, architecture placement p.177 l.Architecture placement |
The CDSE is presented as one shared national application component, although decision support may be embedded locally, …The CDSE is presented as one shared national application component, although decision support may be embedded locally, invoked remotely, distributed, or split between knowledge and execution services. Suggested revision: Define it as a logical decision-support capability that may be realised through governed knowledge artefacts, execution services, and application-integrated workflow components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1949✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, architecture placement p.177 l.Architecture placement |
Governed computable clinical knowledge and runtime execution are potentially conflated. These have different governance…Governed computable clinical knowledge and runtime execution are potentially conflated. These have different governance, safety, licensing, and deployment requirements. Suggested revision: Separate computable knowledge management from rule or model execution, while showing how they interact. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1950✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 1 p.177 l.Purpose and scope anchor: medium |
The component may imply that clinical guidance can be translated straightforwardly into deterministic rules. Guidance o…The component may imply that clinical guidance can be translated straightforwardly into deterministic rules. Guidance often contains uncertainty, judgement, exceptions, and contextual conditions. Suggested revision: State that only suitable recommendations should be made computable and that clinical interpretation, limitations, and human judgement must be preserved. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-1951✎ edit📣 feedback | received | Clinical Core architects agent, medium |
Computable Decision Support Engine §CDSE, 1 p.177 l.Purpose and scope anchor: medium |
National central execution may be unsuitable where latency, connectivity, privacy, or workflow constraints require loca…National central execution may be unsuitable where latency, connectivity, privacy, or workflow constraints require local operation. Suggested revision: Support central, local, federated, offline, and hybrid patterns with controlled knowledge synchronisation and versioning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1952✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 2 p.177-178 l.Rationale anchor: medium |
Expected improvements in quality and adherence should not be assumed without evidence of usability, workflow fit, alert…Expected improvements in quality and adherence should not be assumed without evidence of usability, workflow fit, alert burden, and clinical effectiveness. Suggested revision: Qualify outcome claims and require evaluation in the intended clinical setting before scale. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1953✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 3 p.178 l.Core attributes anchor: medium |
The component requires decision logic but may not require a formal intended-use statement.The component requires decision logic but may not require a formal intended-use statement. Suggested revision: Require intended users, population, setting, trigger, required inputs, outputs, limitations, contraindications, evidence, and level of human oversight for every artefact. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1954✎ edit📣 feedback | received | Clinical Metadata registries agent, medium |
Computable Decision Support Engine §CDSE, 3 p.178 l.Core attributes anchor: medium |
Decision logic depends on specific model and terminology versions, but these dependencies may not be explicitly bound a…Decision logic depends on specific model and terminology versions, but these dependencies may not be explicitly bound and preserved. Suggested revision: Require version-pinned dependencies on terminology, data models, guideline sources, value sets, and external services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1955✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 3 p.178 l.Core attributes anchor: medium |
The component needs clear representation of evidence source, guideline authority, publication date, jurisdiction, revie…The component needs clear representation of evidence source, guideline authority, publication date, jurisdiction, review date, and clinical owner. Suggested revision: Add complete knowledge-artefact metadata and governance status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1956✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 3 p.178 l.Core attributes anchor: medium |
Explainability may be treated as a generic output rather than defined according to user and risk.Explainability may be treated as a generic output rather than defined according to user and risk. Suggested revision: Require traceable reasons, relevant input data, rule or model version, source recommendation, uncertainty, and actionable next steps appropriate to the user. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-1957✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 3 p.178-179 l.Core attributes anchor: medium |
Alert fatigue, automation bias, overreliance, missing data, and inappropriate use outside the intended context are not …Alert fatigue, automation bias, overreliance, missing data, and inappropriate use outside the intended context are not sufficiently addressed. Suggested revision: Require human-factors testing, alert governance, override capture, missing-data handling, contraindication logic, and monitoring of user response and harm. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-1958✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 4 p.179 l.Relationship to LHR |
The CDSE may be expected to query the complete LHR, creating excessive access and privacy exposure.The CDSE may be expected to query the complete LHR, creating excessive access and privacy exposure. Suggested revision: Require minimum necessary, purpose-specific input datasets and avoid unrestricted access to the full longitudinal record. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1959✎ edit📣 feedback | received | Clinical Metadata registries agent, medium |
Computable Decision Support Engine §CDSE, 4 p.179 l.Relationship to TS and LIMR anchor: medium |
Semantic dependencies are central but the release order and compatibility consequences are not defined.Semantic dependencies are central but the release order and compatibility consequences are not defined. Suggested revision: Require coordinated dependency management, pre-release regression testing, compatibility declarations, and safe rollback. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1960✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 4 p.179 l.Relationship to point-of-care systems anchor: medium |
Workflow integration remains the responsibility of point-of-care applications, but the boundary is not sufficiently exp…Workflow integration remains the responsibility of point-of-care applications, but the boundary is not sufficiently explicit. Suggested revision: State that the CDSE exposes governed decision services or artefacts, while local applications manage presentation, workflow, user interaction, and final accountable action. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1961✎ edit📣 feedback | received | Clinical Core architects agent |
Computable Decision Support Engine §CDSE, 5 p.179-181 l.Requirements table |
The requirements do not clearly distinguish deterministic rules, statistical models, and AI-based decision support.The requirements do not clearly distinguish deterministic rules, statistical models, and AI-based decision support. Suggested revision: Define separate requirement profiles according to logic type, autonomy, risk, evidence, evaluation, explainability, and monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-1962✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 5 p.179 l.Rule execution requirement anchor: medium |
Reproducibility requires the same input, rule set, configuration, reference data, and time context, not merely the same…Reproducibility requires the same input, rule set, configuration, reference data, and time context, not merely the same rule identifier. Suggested revision: Require recording of every dependency needed to reproduce an execution result. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1963✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 5 p.180 l.Testing requirement anchor: medium |
Unit testing alone is insufficient for clinical decision support.Unit testing alone is insufficient for clinical decision support. Suggested revision: Require unit, integration, terminology, boundary, negative, regression, workflow, usability, clinical-validation, and post-deployment tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-1964✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 5 p.180 l.Override requirement |
Capturing overrides without context can create punitive surveillance or misinterpret appropriate professional judgement.Capturing overrides without context can create punitive surveillance or misinterpret appropriate professional judgement. Suggested revision: Record override reason proportionately, protect professional confidentiality, analyse patterns responsibly, and avoid treating every override as non-compliance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-1965✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 5 p.180 l.Update requirement |
Updating guidance may change clinical recommendations abruptly across the country.Updating guidance may change clinical recommendations abruptly across the country. Suggested revision: Require staged release, impact analysis, communication, training, compatibility testing, rollback, and monitoring following updates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1966✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, 5 p.180-181 l.Availability requirement |
Care should not fail solely because a remote decision-support service is unavailable.Care should not fail solely because a remote decision-support service is unavailable. Suggested revision: Require safe failure, local fallback, cached guidance where appropriate, clear unavailability indicators, and continuation of care without unsupported automation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-1967✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE, governance p.181 l.Governance section anchor: medium |
Clinical accountability among guideline authority, knowledge author, software operator, local implementer, and treating…Clinical accountability among guideline authority, knowledge author, software operator, local implementer, and treating professional is not sufficiently allocated. Suggested revision: Add a responsibility model and require safety cases, approval authority, incident handling, correction, and withdrawal processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-1968✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §CDSE overall p.177-181 l.Complete component |
The component needs a complete computable-guidance conformance package.The component needs a complete computable-guidance conformance package. Suggested revision: Publish knowledge-artefact profiles, execution-service interfaces, test cases, reference patients, expected outputs, safety requirements, dependency metadata, and monitoring standards. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-085 discuss | in the document all mentions on GitHub record | ||
| PC-1969✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, architecture placement p.182 l.Architecture placement anchor: medium |
Supplier identity may already be governed by national business, tax, procurement, customs, or legal-entity registries. …Supplier identity may already be governed by national business, tax, procurement, customs, or legal-entity registries. A separate health Supplier Registry could duplicate foundational data. Suggested revision: Define it as a health-sector qualification and reference layer built on authoritative cross-sector organisation and supplier identities where available. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1970✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 1 p.182 l.Purpose and scope anchor: medium |
Supplier identity, regulatory authorisation, product relationships, contracts, sanctions, performance, and procurement …Supplier identity, regulatory authorisation, product relationships, contracts, sanctions, performance, and procurement eligibility are different domains. Suggested revision: Limit the registry to authoritative supplier identity and health-sector qualification references. Keep contracts, transactions, bids, performance, and payments in operational systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1971✎ edit📣 feedback | received | Core architects Supply chain agent, medium |
Supplier Registry §Supplier Registry, 1 p.182 l.Purpose and scope anchor: medium |
The catalogue lacks a general Organisation Registry, although suppliers, manufacturers, distributors, laboratories, pro…The catalogue lacks a general Organisation Registry, although suppliers, manufacturers, distributors, laboratories, providers, and payees are organisations. Suggested revision: Address the missing organisation-identity capability and avoid creating separate duplicated organisation records in multiple health registries. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-268 discuss | in the document all mentions on GitHub record | ||
| PC-1972✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 2 p.182 l.Rationale anchor: medium |
Claims that the registry reduces counterfeit products, corruption, and procurement leakage require qualification.Claims that the registry reduces counterfeit products, corruption, and procurement leakage require qualification. Suggested revision: State that it supports controls through verified identity and qualification information but does not by itself prevent fraud or corruption. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1973✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 3 p.182-183 l.Core attributes anchor: medium |
Supplier identifiers require legal-entity authority, tax or business identifier, health-sector identifier, status, and …Supplier identifiers require legal-entity authority, tax or business identifier, health-sector identifier, status, and cross-references. Suggested revision: Apply a common organisation-identifier model with source, type, jurisdiction, status, and effective period. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-268 discuss | in the document all mentions on GitHub record | ||
| PC-1974✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 3 p.183 l.Core attributes anchor: medium |
A supplier may be a consortium, public agency, charity, donor, individual trader, foreign entity, or local manufacturer.A supplier may be a consortium, public agency, charity, donor, individual trader, foreign entity, or local manufacturer. Suggested revision: Support diverse legal and organisational forms, including provisional or foreign suppliers under controlled qualification processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1975✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 3 p.183 l.Core attributes anchor: medium |
Product-supplier relationships do not necessarily establish regulatory authorisation, manufacturer status, or current a…Product-supplier relationships do not necessarily establish regulatory authorisation, manufacturer status, or current ability to supply. Suggested revision: Model typed relationships such as manufacturer, authorisation holder, importer, distributor, wholesaler, service agent, and approved supplier, with source and validity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1976✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 3 p.183 l.Core attributes anchor: medium |
Beneficial ownership and sanctions information may be sensitive, legally restricted, or maintained by other authorities.Beneficial ownership and sanctions information may be sensitive, legally restricted, or maintained by other authorities. Suggested revision: Reference the authoritative source and expose only legally permitted information under differentiated access controls. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-192 discuss | in the document all mentions on GitHub record | ||
| PC-1977✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 4 p.183 l.Relationship to Product Registry anchor: medium |
The Product Registry identifies products, but approved supply relationships may depend on jurisdiction, programme, proc…The Product Registry identifies products, but approved supply relationships may depend on jurisdiction, programme, procurement framework, and contract. Suggested revision: Keep reference relationships in the registry and operational eligibility and contracting in procurement systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1978✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Supplier Registry §Supplier Registry, 4 p.183 l.Relationship to Facility Registry anchor: medium |
Some suppliers also operate regulated facilities, warehouses, or laboratories. Duplicating locations and organisation i…Some suppliers also operate regulated facilities, warehouses, or laboratories. Duplicating locations and organisation identities could create inconsistency. Suggested revision: Use authoritative organisation and location references rather than maintaining duplicate facility information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1979✎ edit📣 feedback | received | Supply chain agent, medium |
Supplier Registry §Supplier Registry, 5 p.183-185 l.Requirements table anchor: medium |
The normative terminology remains inconsistent and applicability to public, private, domestic, and foreign suppliers is…The normative terminology remains inconsistent and applicability to public, private, domestic, and foreign suppliers is unclear. Suggested revision: Harmonise requirement status and add supplier-type and maturity applicability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-1980✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 5 p.184 l.Registration requirement anchor: medium |
Mandatory completion of all qualification data before creation may block emergency or temporary suppliers.Mandatory completion of all qualification data before creation may block emergency or temporary suppliers. Suggested revision: Support provisional, pending verification, approved, restricted, suspended, and retired statuses with appropriate usage limits. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1981✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 5 p.184 l.Verification requirement anchor: medium |
The registry should not independently revalidate legal-entity data already governed by business or tax authorities.The registry should not independently revalidate legal-entity data already governed by business or tax authorities. Suggested revision: Verify through authoritative services or evidence and retain source, assurance, and freshness. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1982✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 5 p.184 l.Performance requirement anchor: medium |
Supplier-performance scoring is operational, context-sensitive, and potentially contested. It may not belong in the aut…Supplier-performance scoring is operational, context-sensitive, and potentially contested. It may not belong in the authoritative identity registry. Suggested revision: Keep detailed performance evaluation in procurement or contract systems. If summaries are exposed, require methodology, period, evidence, appeal, and restricted access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-192 discuss | in the document all mentions on GitHub record | ||
| PC-1983✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 5 p.184 l.Sanctions requirement anchor: medium |
Incorrect sanctions or exclusion status can cause significant financial and reputational harm.Incorrect sanctions or exclusion status can cause significant financial and reputational harm. Suggested revision: Require authoritative source, effective period, reason, legal basis, rapid correction, appeal, and notification of resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1984✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 5 p.184-185 l.Public access requirement anchor: medium |
Public transparency must be balanced against confidential commercial, personal, security, and investigatory information.Public transparency must be balanced against confidential commercial, personal, security, and investigatory information. Suggested revision: Define a public supplier subset and restricted regulatory and procurement views. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-192 discuss | in the document all mentions on GitHub record | ||
| PC-1985✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 5 p.185 l.Notification requirement anchor: medium |
Suspension, sanction, licence expiry, or recall-related events may require timely notification.Suspension, sanction, licence expiry, or recall-related events may require timely notification. Suggested revision: Make critical status-event notification mandatory for authorised consumers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1986✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, 6 p.185 l.Minimum dataset anchor: medium |
Personal addresses, bank details, ownership, and contact data should not be universally exposed or necessarily held wit…Personal addresses, bank details, ownership, and contact data should not be universally exposed or necessarily held within the registry. Suggested revision: Apply data minimisation, link to authoritative financial and business systems, and define public and restricted fields. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-192 discuss | in the document all mentions on GitHub record | ||
| PC-1987✎ edit📣 feedback | received | Supply chain agent |
Supplier Registry §Supplier Registry, governance p.185 l.Governance section anchor: medium |
Governance spans procurement, regulation, business registration, tax, customs, and health. Decision authority is not al…Governance spans procurement, regulation, business registration, tax, customs, and health. Decision authority is not allocated by attribute. Suggested revision: Add an attribute-level authority and stewardship matrix with conflict resolution and service levels. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1988✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
Supplier Registry §Supplier Registry overall p.182-185 l.Complete component anchor: medium |
The component requires stronger justification as a separate DPI-H component rather than a health-sector view over found…The component requires stronger justification as a separate DPI-H component rather than a health-sector view over foundational business and procurement data. Suggested revision: Include a component-assessment matrix and permit countries to realise the capability through mapped cross-sector registries and procurement services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-191 discuss | in the document all mentions on GitHub record | ||
| PC-1989✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, architecture placement p.186 l.Architecture placement |
The component is a useful distinction, but its boundary with scheme administration, beneficiary enrolment, contracts, t…The component is a useful distinction, but its boundary with scheme administration, beneficiary enrolment, contracts, tariffs, prior authorisation, claims rules, and clinical policy remains complex. Suggested revision: Define it as the authoritative publication capability for benefit definitions and related reference rules, excluding operational eligibility, contracting, authorisation, adjudication, and payment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-1990✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 1 p.186 l.Purpose and scope |
“What is covered, for whom, and under which conditions” may imply that the registry makes individual eligibility determ…“What is covered, for whom, and under which conditions” may imply that the registry makes individual eligibility determinations. Suggested revision: Clarify that it publishes general entitlement and coverage definitions, while operational systems determine person-specific eligibility using current enrolment and contextual data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-1991✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 1 p.186 l.Purpose and scope anchor: medium |
Countries may have multiple fragmented public, private, employer, donor, and programme packages with different legal au…Countries may have multiple fragmented public, private, employer, donor, and programme packages with different legal authority. Suggested revision: Support multiple scheme authorities and federated publication while providing common identifiers, terminology, provenance, and comparison structures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | ||
| PC-1992✎ edit📣 feedback | received | Financial systems agent, medium |
Benefits Package Registry §Benefits Package Registry, 2 p.186 l.Rationale anchor: medium |
Improved transparency and reduced claims disputes are plausible but depend on comprehensible rules, operational alignme…Improved transparency and reduced claims disputes are plausible but depend on comprehensible rules, operational alignment, and public access. Suggested revision: Qualify the claims and identify the conditions needed to realise them. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-1993✎ edit📣 feedback | received | Financial systems Metadata registries agent, low |
Benefits Package Registry §Benefits Package Registry, 3 p.186-187 l.Core attributes anchor: medium |
Benefits may be represented by service, condition, procedure, product, provider type, age, sex, geography, frequency, s…Benefits may be represented by service, condition, procedure, product, provider type, age, sex, geography, frequency, setting, or programme. Suggested revision: Define a structured rule model and terminology bindings without assuming that all benefit logic can be reduced to one code list. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | ||
| PC-1994✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 3 p.187 l.Core attributes anchor: medium |
Machine-readable benefit rules may still contain ambiguity, discretionary criteria, clinical judgement, and legal inter…Machine-readable benefit rules may still contain ambiguity, discretionary criteria, clinical judgement, and legal interpretation. Suggested revision: Distinguish computable rules, human-interpreted policy, guidance, exceptions, and supporting legal text. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | ||
| PC-1995✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 3 p.187 l.Core attributes anchor: medium |
Coverage conditions can encode discriminatory or inequitable restrictions even when technically precise.Coverage conditions can encode discriminatory or inequitable restrictions even when technically precise. Suggested revision: Require equity, human-rights, legal, clinical, and financial review before publication of material benefit rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | ||
| PC-1996✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
Benefits Package Registry §Benefits Package Registry, 4 p.187 l.Relationship to Client Registry |
The Client Registry should resolve person identity, not store scheme enrolment or entitlement.The Client Registry should resolve person identity, not store scheme enrolment or entitlement. Suggested revision: State that beneficiary or enrolment systems provide scheme membership while the Client Registry supports identity resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-1997✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 4 p.187 l.Relationship to Facility and Workforce Registries |
Facility and workforce registries support provider identity and qualification, but empanelment and contracting are oper…Facility and workforce registries support provider identity and qualification, but empanelment and contracting are operational financing relationships. Suggested revision: Keep empanelment and contract status in financing or contract-management systems, referencing authoritative facility and workforce identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-1998✎ edit📣 feedback | received | Financial systems Supply chain Metadata registries agent, medium |
Benefits Package Registry §Benefits Package Registry, 4 p.187 l.Relationship to Product Registry |
Benefit definitions for medicines and devices require product-level, generic-level, formulary-level, and package-level …Benefit definitions for medicines and devices require product-level, generic-level, formulary-level, and package-level distinctions. Suggested revision: Define which product concept level is used and how substitutions, exclusions, and product updates affect benefit rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | ||
| PC-1999✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 5 p.187-189 l.Requirements table |
Requirements need explicit actor responsibility and applicability to scheme type.Requirements need explicit actor responsibility and applicability to scheme type. Suggested revision: Add responsible authority, scheme category, legal status, maturity, and test method. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | ||
| PC-2000✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 5 p.188 l.Versioning requirement |
Benefit rules must be evaluated using the version effective on the date of service or decision, not merely the current …Benefit rules must be evaluated using the version effective on the date of service or decision, not merely the current version. Suggested revision: Require effective-dated, immutable historical versions and reproducible evaluation against past rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | ||
| PC-2001✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 5 p.188 l.Rule execution requirement anchor: medium |
Executing individual benefit decisions could transform the registry into an eligibility or adjudication engine.Executing individual benefit decisions could transform the registry into an eligibility or adjudication engine. Suggested revision: Limit the registry to reference publication and testable rule artefacts. Permit execution through operational systems or a separate governed rule service. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2002✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 5 p.188 l.Public-access requirement |
Legal or technical benefit rules may be machine-readable but incomprehensible to the public.Legal or technical benefit rules may be machine-readable but incomprehensible to the public. Suggested revision: Require clear-language, multilingual, accessible explanations alongside official and machine-readable forms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | ||
| PC-2003✎ edit📣 feedback | received | Financial systems Metadata registries agent, medium |
Benefits Package Registry §Benefits Package Registry, 5 p.188 l.Search requirement anchor: medium |
Search by code alone will not support patients or providers unfamiliar with formal terminology.Search by code alone will not support patients or providers unfamiliar with formal terminology. Suggested revision: Support plain-language search, synonyms, categories, exclusions, examples, and explanation of uncertainty or scheme-specific conditions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | ||
| PC-2004✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 5 p.188-189 l.Notification requirement |
Changes to benefit packages can materially affect care, claims, contracts, and patient expectations.Changes to benefit packages can materially affect care, claims, contracts, and patient expectations. Suggested revision: Make material-change notification mandatory with effective date, impacted schemes, services, products, providers, and transition arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | ||
| PC-2005✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 6 p.189 l.Minimum dataset anchor: low |
The dataset should distinguish package, scheme, benefit item, exclusion, limitation, condition, cost-sharing, authorisa…The dataset should distinguish package, scheme, benefit item, exclusion, limitation, condition, cost-sharing, authorisation, jurisdiction, and legal authority. Suggested revision: Restructure the model and define cardinalities, terminology, effective periods, status, and provenance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | ||
| PC-2006✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, 6 p.189 l.Cost-sharing fields anchor: low |
Cost-sharing information may require exemptions, caps, household rules, income categories, currency, indexation, and sp…Cost-sharing information may require exemptions, caps, household rules, income categories, currency, indexation, and special populations. Suggested revision: Add structured conditions and clear explanations, with equity review and historical versioning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | ||
| PC-2007✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry, governance p.189 l.Governance section |
Governance may be distributed among ministries, insurers, schemes, purchasers, regulators, and courts.Governance may be distributed among ministries, insurers, schemes, purchasers, regulators, and courts. Suggested revision: Define who has legal authority to publish, amend, interpret, and withdraw each package, with dispute and correction procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-190 discuss | in the document all mentions on GitHub record | ||
| PC-2008✎ edit📣 feedback | received | Financial systems agent |
Benefits Package Registry §Benefits Package Registry overall p.186-189 l.Complete component anchor: medium |
The component needs rule-testing, historical evaluation, terminology, publication, and consumer-explanation conformance.The component needs rule-testing, historical evaluation, terminology, publication, and consumer-explanation conformance. Suggested revision: Publish a companion benefit-definition model, test cases, example beneficiaries and services, expected outcomes, version rules, and API specification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-189 discuss | in the document all mentions on GitHub record | ||
| PC-2009✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, architecture placement p.190 l.Architecture placement |
HMIS commonly denotes the broader people, processes, governance, data, and technologies supporting management informati…HMIS commonly denotes the broader people, processes, governance, data, and technologies supporting management information, not one application component. Suggested revision: Rename the logical component Aggregate Health Information and Indicator Service, or clarify that it represents only the reusable digital services within the wider HMIS. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | ||
| PC-2010✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, architecture placement p.190 l.Architecture placement |
The component is placed in the business-services DPI-H layer, but some HMIS implementations are programme-specific oper…The component is placed in the business-services DPI-H layer, but some HMIS implementations are programme-specific operational reporting systems. Suggested revision: Define which shared capabilities qualify as DPI-H and which programme dashboards, workflows, and reports remain operational applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | ||
| PC-2011✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 1 p.190 l.Purpose and scope anchor: medium |
Aggregate reporting, indicator calculation, data collection, dashboards, analytics, and planning may be combined into o…Aggregate reporting, indicator calculation, data collection, dashboards, analytics, and planning may be combined into one very broad component. Suggested revision: Separate shared indicator and aggregate-data services from collection tools, dashboards, analytics platforms, and programme workflows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-033 discuss | in the document all mentions on GitHub record | ||
| PC-2012✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 1 p.190 l.Purpose and scope anchor: medium |
Routine aggregate reporting may still rely on paper forms, spreadsheets, SMS, or offline applications.Routine aggregate reporting may still rely on paper forms, spreadsheets, SMS, or offline applications. Suggested revision: Support several contribution channels and define a progressive path toward more structured and automated reporting. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | ||
| PC-2013✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 2 p.190 l.Rationale |
Claims that shared HMIS reduces reporting burden depend on indicator harmonisation, workflow redesign, data reuse, and …Claims that shared HMIS reduces reporting burden depend on indicator harmonisation, workflow redesign, data reuse, and programme agreement. Suggested revision: Qualify the claim and require measurement of actual reporting burden and duplicate data entry. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-2014✎ edit📣 feedback | received | Metadata registries agent, medium |
Health Management Information System §HMIS, 3 p.190-191 l.Core attributes |
Indicator definitions are central but may lack formal numerator, denominator, inclusion, exclusion, period, disaggregat…Indicator definitions are central but may lack formal numerator, denominator, inclusion, exclusion, period, disaggregation, source, and calculation metadata. Suggested revision: Require a governed indicator metadata model and link it to the Terminology Service, LIMR, and source-data specifications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-183 discuss | in the document all mentions on GitHub record | ||
| PC-2015✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 3 p.191 l.Core attributes |
Data validation may focus on completeness and range checks while missing consistency, plausibility, timeliness, duplica…Data validation may focus on completeness and range checks while missing consistency, plausibility, timeliness, duplicate reporting, and source reconciliation. Suggested revision: Define validation rules by indicator and data source, with transparent quality flags and remediation workflow. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-183 discuss | in the document all mentions on GitHub record | ||
| PC-2016✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 3 p.191 l.Core attributes |
Automatic aggregation from clinical systems may not be feasible where source data is incomplete or non-standardised.Automatic aggregation from clinical systems may not be feasible where source data is incomplete or non-standardised. Suggested revision: Allow mixed manual and automated reporting with provenance, source type, quality status, and gradual automation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | ||
| PC-2017✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 4 p.191 l.Relationship to registries anchor: medium |
Facility, workforce, product, and geography references are required, but changes in master data can alter historical in…Facility, workforce, product, and geography references are required, but changes in master data can alter historical indicator interpretation. Suggested revision: Require versioned identifiers, historical resolution, effective dates, and reproducible reporting against the reference-data state applicable to the reporting period. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-183 discuss | in the document all mentions on GitHub record | ||
| PC-2018✎ edit📣 feedback | received | Core architects agent |
Health Management Information System §HMIS, 4 p.191 l.Relationship to LHR |
Deriving aggregate indicators from person-level records can create re-identification risks, especially in small populat…Deriving aggregate indicators from person-level records can create re-identification risks, especially in small populations. Suggested revision: Apply purpose-specific access, aggregation thresholds, suppression, privacy-preserving analytics, secure environments, and audit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-184 discuss | in the document all mentions on GitHub record | ||
| PC-2019✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 5 p.191-193 l.Requirements table |
Requirements do not identify the difference between aggregate-data receipt, indicator calculation, analytics, and publi…Requirements do not identify the difference between aggregate-data receipt, indicator calculation, analytics, and publication responsibilities. Suggested revision: Add actor responsibility and separate service profiles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | ||
| PC-2020✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 5 p.192 l.Data-submission requirement |
Submission formats may be standards-based without handling corrections, revisions, late reports, duplicate submissions,…Submission formats may be standards-based without handling corrections, revisions, late reports, duplicate submissions, and partial reporting. Suggested revision: Define reporting status, version, period, source, correction, replacement, acknowledgement, and reconciliation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | ||
| PC-2021✎ edit📣 feedback | received | Metadata registries agent, medium |
Health Management Information System §HMIS, 5 p.192 l.Indicator calculation requirement |
Calculations must be reproducible and versioned.Calculations must be reproducible and versioned. Suggested revision: Require version-pinned indicator definitions, reference data, source data, transformation, software, and expected test results. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-183 discuss | in the document all mentions on GitHub record | ||
| PC-2022✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 5 p.192 l.Dashboard requirement anchor: medium |
Mandatory dashboards may unnecessarily prescribe presentation functionality within the shared component.Mandatory dashboards may unnecessarily prescribe presentation functionality within the shared component. Suggested revision: Require data and analytical services. Treat dashboards as configurable consuming applications unless a shared national dashboard is explicitly in scope. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | ||
| PC-2023✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 5 p.192 l.Disaggregation requirement anchor: medium |
Disaggregation can improve equity monitoring but also increase privacy risk and produce unstable estimates for small gr…Disaggregation can improve equity monitoring but also increase privacy risk and produce unstable estimates for small groups. Suggested revision: Require approved disaggregation dimensions, minimum cell sizes, uncertainty information, suppression, and interpretation guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-184 discuss | in the document all mentions on GitHub record | ||
| PC-2024✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 5 p.192-193 l.Offline requirement |
Offline reporting should be a core requirement in countries with intermittent connectivity.Offline reporting should be a core requirement in countries with intermittent connectivity. Suggested revision: Make store-and-forward, delayed synchronisation, duplicate handling, and reconciliation mandatory where relevant. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | ||
| PC-2025✎ edit📣 feedback | received | Core architects agent, medium |
Health Management Information System §HMIS, 5 p.193 l.Publication requirement |
Open publication can create misinterpretation, reputational harm, or identification of small facilities and communities.Open publication can create misinterpretation, reputational harm, or identification of small facilities and communities. Suggested revision: Define public, restricted, and internal datasets, quality thresholds, disclosure control, explanatory metadata, and correction processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-184 discuss | in the document all mentions on GitHub record | ||
| PC-2026✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
Health Management Information System §HMIS, 6 p.193 l.Minimum dataset anchor: low |
The HMIS minimum dataset should concern aggregate observations and indicator metadata, not a universal list of individu…The HMIS minimum dataset should concern aggregate observations and indicator metadata, not a universal list of individual clinical fields. Suggested revision: Structure it around reporting unit, period, indicator or data element, value, dimensions, source, status, quality, version, and provenance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | ||
| PC-2027✎ edit📣 feedback | received | Core architects WHO agent, medium |
Health Management Information System §HMIS, governance p.193 l.Governance section |
Programme reporting requirements can proliferate despite a shared platform.Programme reporting requirements can proliferate despite a shared platform. Suggested revision: Require national indicator governance, rationalisation, change control, sunset criteria, burden assessment, and partner alignment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-183 discuss | in the document all mentions on GitHub record | ||
| PC-2028✎ edit📣 feedback | received | Core architects agent |
Health Management Information System §HMIS overall p.190-193 l.Complete component |
The component requires a clearer boundary to justify its classification as shared DPI-H rather than a broad operational…The component requires a clearer boundary to justify its classification as shared DPI-H rather than a broad operational platform. Suggested revision: Limit the DPI-H component to reusable aggregate-data, indicator-definition, validation, and publication services and map other HMIS functions to operational applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | ||
| PC-2029✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, architecture placement p.194 l.Architecture placement anchor: low |
“Public Health Surveillance Platform” is extremely broad and may include case reporting, event-based surveillance, labo…“Public Health Surveillance Platform” is extremely broad and may include case reporting, event-based surveillance, laboratories, contact management, analytics, alerts, response coordination, and emergency operations. Suggested revision: Define the shared surveillance capabilities included in DPI-H and separate them from disease-specific and emergency-response operational applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2030✎ edit📣 feedback | received | Core architects agent |
Public Health Surveillance Platform §PHSP, architecture placement p.194 l.Architecture placement |
No direct OpenHIE component equivalent is identified, increasing the need for evidence that the full platform qualifies…No direct OpenHIE component equivalent is identified, increasing the need for evidence that the full platform qualifies as shared DPI-H. Suggested revision: Apply the component-selection criteria explicitly and distinguish established public-health capabilities from novel architectural grouping. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2031✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 1 p.194 l.Purpose and scope anchor: medium |
Surveillance, monitoring, intelligence, outbreak management, and response may be used interchangeably although they rep…Surveillance, monitoring, intelligence, outbreak management, and response may be used interchangeably although they represent different functions. Suggested revision: Define the terms and scope boundaries clearly. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2032✎ edit📣 feedback | received | Core architects WHO agent, low |
Public Health Surveillance Platform §PHSP, 1 p.194 l.Purpose and scope |
National surveillance may rely on indicator-based, case-based, laboratory, event-based, syndromic, community, environme…National surveillance may rely on indicator-based, case-based, laboratory, event-based, syndromic, community, environmental, and cross-border data at different maturity levels. Suggested revision: Present a modular capability model and allow progressive implementation according to national priorities and obligations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2033✎ edit📣 feedback | received | Core architects agent, low |
Public Health Surveillance Platform §PHSP, 2 p.194 l.Rationale anchor: medium |
Faster detection and response are plausible benefits but depend on reporting coverage, laboratory capacity, workforce, …Faster detection and response are plausible benefits but depend on reporting coverage, laboratory capacity, workforce, governance, and operational response. Suggested revision: Qualify outcome claims and identify the non-digital conditions required. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-280 discuss | in the document all mentions on GitHub record | ||
| PC-2034✎ edit📣 feedback | received | Metadata registries agent, medium |
Public Health Surveillance Platform §PHSP, 3 p.194-195 l.Core attributes anchor: medium |
Case definitions and reporting forms require governed models and terminology, but different diseases and emergencies ma…Case definitions and reporting forms require governed models and terminology, but different diseases and emergencies may require rapid local adaptation. Suggested revision: Support versioned case definitions, emergency extensions, effective dates, rapid review, publication, and later harmonisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2035✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 3 p.195 l.Core attributes anchor: medium |
Surveillance can involve identifiable, sensitive, geospatial, travel, contact, genomic, occupational, and social data.Surveillance can involve identifiable, sensitive, geospatial, travel, contact, genomic, occupational, and social data. Suggested revision: Require purpose limitation, legal authority, data minimisation, sensitivity classification, access segmentation, disclosure controls, retention, and public accountability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2036✎ edit📣 feedback | received | Core architects WHO agent, medium |
Public Health Surveillance Platform §PHSP, 3 p.195 l.Core attributes anchor: low |
Public-health surveillance can stigmatise communities or be repurposed for immigration, policing, or political control.Public-health surveillance can stigmatise communities or be repurposed for immigration, policing, or political control. Suggested revision: Require human-rights impact assessment, community safeguards, controlled cross-sector disclosure, anti-discrimination measures, oversight, and redress. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2037✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 3 p.195 l.Core attributes |
Laboratory results are central to surveillance, but the component boundary with laboratory information systems and nati…Laboratory results are central to surveillance, but the component boundary with laboratory information systems and national laboratory networks is unclear. Suggested revision: Keep laboratory workflows in operational systems and define standard result, specimen, test, organism, and notification interfaces to surveillance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2038✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 3 p.195 l.Core attributes |
Contact-tracing and case-management workflows are operational, high-volume, and event-specific.Contact-tracing and case-management workflows are operational, high-volume, and event-specific. Suggested revision: Treat them as consuming applications unless a reusable cross-hazard workflow capability is clearly justified and bounded. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2039✎ edit📣 feedback | received | Metadata registries agent, low |
Public Health Surveillance Platform §PHSP, 3 p.195 l.Core attributes |
Climate and environmental surveillance is included but lacks stable common models, terminology, data authority, and int…Climate and environmental surveillance is included but lacks stable common models, terminology, data authority, and integration standards. Suggested revision: Define it as an emerging capability, identify interim data standards and authoritative sources, and avoid presenting it as fully standardised. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2040✎ edit📣 feedback | received | Core architects agent |
Public Health Surveillance Platform §PHSP, 4 p.195-196 l.Relationship to Client Registry |
Linking surveillance cases to national identity may not always be necessary and could increase deterrence and misuse ri…Linking surveillance cases to national identity may not always be necessary and could increase deterrence and misuse risks. Suggested revision: Use minimum necessary identity, pseudonymous or programme-specific identifiers where suitable, and require explicit justification for national identity linkage. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2041✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 4 p.196 l.Relationship to Facility and Workforce Registries anchor: medium |
Facility and reporter references are important, but workforce identity should not automatically expose individual profe…Facility and reporter references are important, but workforce identity should not automatically expose individual professional information beyond surveillance needs. Suggested revision: Apply minimum necessary attributes and differentiated access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2042✎ edit📣 feedback | received | Core architects Clinical WHO agent, medium |
Public Health Surveillance Platform §PHSP, 4 p.196 l.Relationship to LHR |
Direct access to longitudinal records may exceed surveillance necessity.Direct access to longitudinal records may exceed surveillance necessity. Suggested revision: Define bounded, legally authorised surveillance datasets and avoid unrestricted LHR access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2043✎ edit📣 feedback | received | Core architects WHO agent, medium |
Public Health Surveillance Platform §PHSP, 4 p.196 l.Relationship to HMIS |
The boundary between aggregate surveillance, routine HMIS reporting, and case-based surveillance is not sufficiently ex…The boundary between aggregate surveillance, routine HMIS reporting, and case-based surveillance is not sufficiently explicit. Suggested revision: Define when data is managed as routine aggregate reporting, line-listed surveillance, case records, laboratory events, or outbreak-response information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-182 discuss | in the document all mentions on GitHub record | ||
| PC-2044✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 5 p.196-198 l.Requirements table |
Requirement status and actor responsibility remain unclear.Requirement status and actor responsibility remain unclear. Suggested revision: Harmonise normative terminology and identify reporting source, surveillance service, laboratory, analyst, authority, and consuming system obligations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-187 discuss | in the document all mentions on GitHub record | ||
| PC-2045✎ edit📣 feedback | received | Core architects WHO agent, low |
Public Health Surveillance Platform §PHSP, 5 p.196 l.Case-notification requirement anchor: medium |
“Immediate” or “real-time” reporting is not measurable and may differ by condition.“Immediate” or “real-time” reporting is not measurable and may differ by condition. Suggested revision: Define condition-specific reporting deadlines, severity, acknowledgement, failure handling, escalation, and offline fallback. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-187 discuss | in the document all mentions on GitHub record | ||
| PC-2046✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 5 p.196-197 l.Signal-detection requirement |
Automated alerts and anomaly detection can produce substantial false positives and may perform poorly when baseline rep…Automated alerts and anomaly detection can produce substantial false positives and may perform poorly when baseline reporting changes. Suggested revision: Require validated methods, threshold governance, uncertainty, human review, feedback, recalibration, and monitoring of false-positive and missed-event rates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-187 discuss | in the document all mentions on GitHub record | ||
| PC-2047✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 5 p.197 l.Alert requirement |
Generating alerts does not ensure that an accountable authority receives, assesses, and acts on them.Generating alerts does not ensure that an accountable authority receives, assesses, and acts on them. Suggested revision: Define recipient roles, acknowledgement, triage, escalation, decision, response workflow, closure, and performance monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-187 discuss | in the document all mentions on GitHub record | ||
| PC-2048✎ edit📣 feedback | received | WHO Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 5 p.197 l.Cross-border notification |
Cross-border exchange requires defined legal instruments, minimum datasets, terminology, trust, and incident coordinati…Cross-border exchange requires defined legal instruments, minimum datasets, terminology, trust, and incident coordination. Suggested revision: Link to IHR and applicable regional frameworks and define authority, data scope, security, acknowledgement, correction, and dispute handling. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-187 discuss | in the document all mentions on GitHub record | ||
| PC-2049✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 5 p.197 l.Offline reporting requirement |
Offline and low-bandwidth reporting should not remain merely recommended in relevant country contexts.Offline and low-bandwidth reporting should not remain merely recommended in relevant country contexts. Suggested revision: Require store-and-forward, SMS or other controlled channels, deduplication, delayed synchronisation, integrity, and audit where connectivity is intermittent. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-239 discuss | in the document all mentions on GitHub record | ||
| PC-2050✎ edit📣 feedback | received | Core architects WHO agent, low |
Public Health Surveillance Platform §PHSP, 5 p.197-198 l.Genomic surveillance requirement anchor: medium |
Genomic surveillance requires specialised laboratory, computing, consent or legal authority, provenance, and internatio…Genomic surveillance requires specialised laboratory, computing, consent or legal authority, provenance, and international data-sharing governance. Suggested revision: Make it an advanced conditional capability with explicit readiness, governance, security, and ethical requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2051✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 5 p.198 l.Public-dashboard requirement anchor: medium |
Public maps and dashboards can stigmatise small communities or disclose sensitive locations.Public maps and dashboards can stigmatise small communities or disclose sensitive locations. Suggested revision: Require aggregation, suppression, uncertainty, contextual explanation, accessibility, review, and community-risk assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-184 discuss | in the document all mentions on GitHub record | ||
| PC-2052✎ edit📣 feedback | received | Core architects WHO Metadata registries agent, low |
Public Health Surveillance Platform §PHSP, 6 p.198 l.Minimum dataset anchor: low |
A universal minimum case dataset may not fit all hazards and may collect unnecessary personal information.A universal minimum case dataset may not fit all hazards and may collect unnecessary personal information. Suggested revision: Define a small cross-hazard core plus condition-specific modules, with legal basis, necessity, terminology, sensitivity, and reporting deadline. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2053✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, 6 p.198 l.Geography fields anchor: low |
Fine-grained residential or exposure locations can enable re-identification.Fine-grained residential or exposure locations can enable re-identification. Suggested revision: Store and disclose geographic detail according to purpose, sensitivity, minimum necessity, and population size. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2054✎ edit📣 feedback | received | Core architects WHO agent, medium |
Public Health Surveillance Platform §PHSP, 6 p.198 l.Person identifiers anchor: low |
A national HUID should not be mandatory for every surveillance record, particularly anonymous, syndromic, environmental…A national HUID should not be mandatory for every surveillance record, particularly anonymous, syndromic, environmental, or event-based surveillance. Suggested revision: Make identity conditional by surveillance type and support anonymous, pseudonymous, temporary, or case-specific identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2055✎ edit📣 feedback | received | Core architects WHO agent, low |
Public Health Surveillance Platform §PHSP, governance p.198-199 l.Governance section |
Surveillance governance must connect data collection with operational response authority and accountability.Surveillance governance must connect data collection with operational response authority and accountability. Suggested revision: Define national and subnational authority, incident command relationships, data stewardship, scientific review, public communication, and after-action evaluation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-187 discuss | in the document all mentions on GitHub record | ||
| PC-2056✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §PHSP, governance p.198-199 l.Governance section |
Emergency powers can persist beyond the emergency or permit wider data reuse.Emergency powers can persist beyond the emergency or permit wider data reuse. Suggested revision: Require time limits, periodic review, purpose restrictions, data-retention limits, withdrawal of exceptional access, and independent oversight. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2057✎ edit📣 feedback | received | Core architects WHO agent, medium |
Public Health Surveillance Platform §PHSP overall p.194-199 l.Complete component |
The component remains broader and less bounded than the other DPI-H components.The component remains broader and less bounded than the other DPI-H components. Suggested revision: Reframe it as a modular shared surveillance capability and explicitly identify functions that remain in disease-specific, laboratory, emergency-management, and field-response systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2058✎ edit📣 feedback | received | Core architects WHO agent, medium |
Public Health Surveillance Platform §PHSP overall p.194-199 l.Complete component |
The full target assumes case-level data, interoperable laboratories, analytics, geospatial capability, eventing, cross-…The full target assumes case-level data, interoperable laboratories, analytics, geospatial capability, eventing, cross-border exchange, and advanced security. Suggested revision: Define progressive maturity from priority aggregate and case notifications to laboratory linkage, automated eventing, advanced analytics, genomic and environmental surveillance, and regional exchange. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2059✎ edit📣 feedback | received | Core architects agent, medium |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Normative terminology is inconsistent across Appendix C, particularly Required/Recommended versus SHALL/SHOULD/MAY.Normative terminology is inconsistent across Appendix C, particularly Required/Recommended versus SHALL/SHOULD/MAY. Suggested revision: Select one normative convention and apply it across every requirement table, including conditional applicability and exception documentation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-281 discuss | in the document all mentions on GitHub record | ||
| PC-2060✎ edit📣 feedback | received | Core architects agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Component granularity remains inconsistent. The Terminology Service and LIMR are bounded reference capabilities, while …Component granularity remains inconsistent. The Terminology Service and LIMR are bounded reference capabilities, while HMIS and PHSP can represent entire national programmes or platforms. Suggested revision: Normalise component abstraction and provide explicit inclusion and exclusion boundaries for every component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-193 discuss | in the document all mentions on GitHub record | ||
| PC-2061✎ edit📣 feedback | received | Core architects agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Most descriptions present sophisticated target-state capabilities without a consistent progressive maturity model.Most descriptions present sophisticated target-state capabilities without a consistent progressive maturity model. Suggested revision: Add the same maturity structure to every component: minimum governance baseline, foundational service, interoperable national service, advanced capability, and regional or cross-border maturity where relevant. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-197 discuss | in the document all mentions on GitHub record | ||
| PC-2062✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Terminology, model, mapping, profile, and implementation-guide governance are distributed across several sections witho…Terminology, model, mapping, profile, and implementation-guide governance are distributed across several sections without one unified artefact lifecycle. Suggested revision: Add a common semantic-artefact lifecycle covering intake, authoring, review, approval, publication, distribution, adoption, monitoring, change, deprecation, and retirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2063✎ edit📣 feedback | received | Core architects agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Many requirements assume continuous connectivity, national APIs, specialist teams, mature legal authority, and high-ava…Many requirements assume continuous connectivity, national APIs, specialist teams, mature legal authority, and high-availability operation. Suggested revision: Identify offline, package-based, regional, shared-service, and transitional implementation options consistently for every component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2064✎ edit📣 feedback | received | Core architects agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Organisation identity remains a recurring dependency across facilities, suppliers, manufacturers, payers, laboratories,…Organisation identity remains a recurring dependency across facilities, suppliers, manufacturers, payers, laboratories, regulators, and provider organisations, but no Organisation Registry is included. Suggested revision: Assess whether an organisation-identity capability should be added, mapped to foundational DPI, or explicitly provided through another authoritative cross-sector source. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-268 discuss | in the document all mentions on GitHub record | ||
| PC-2065✎ edit📣 feedback | received | Core architects agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Requirement tables rarely identify actor responsibility, test method, evidence, applicable profile, or maturity conditi…Requirement tables rarely identify actor responsibility, test method, evidence, applicable profile, or maturity condition. Suggested revision: Add columns for actor, normative requirement, applicability, referenced standard, test method, expected evidence, and maturity level. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-063 discuss | in the document all mentions on GitHub record | ||
| PC-2066✎ edit📣 feedback | received | Core architects agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Component descriptions generally omit operating cost, service ownership, support, staffing, licensing, infrastructure, …Component descriptions generally omit operating cost, service ownership, support, staffing, licensing, infrastructure, migration, and supplier-exit requirements. Suggested revision: Add an operating-model and sustainability subsection to every component description. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-110 discuss | in the document all mentions on GitHub record | ||
| PC-2067✎ edit📣 feedback | received | Core architects agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
Privacy and security controls vary significantly between components and are often limited to RBAC and audit logging.Privacy and security controls vary significantly between components and are often limited to RBAC and audit logging. Suggested revision: Define a common cross-cutting security and privacy baseline, then add component-specific controls according to sensitivity and risk. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-238 discuss | in the document all mentions on GitHub record | ||
| PC-2068✎ edit📣 feedback | received | Core architects agent |
Terminology Service §Appendix C overall p.166-199 l.Remaining component descriptions anchor: medium |
The catalogue does not explain how new components are proposed, assessed, added, combined, or retired in future archite…The catalogue does not explain how new components are proposed, assessed, added, combined, or retired in future architecture releases. Suggested revision: Publish an architecture-extension process using the Section 3.5.1 criteria, evidence requirements, public review, versioning, and migration rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-065 discuss | in the document all mentions on GitHub record | ||
| PC-2069✎ edit📣 feedback | received | Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D introduction p.229 l.Opening paragraph anchor: medium |
The appendix combines software tools, country implementations, regional infrastructures, and pilot programmes. These re…The appendix combines software tools, country implementations, regional infrastructures, and pilot programmes. These represent different kinds of evidence and should not be interpreted as equivalent demonstrations of DPI-H implementation. [cdn.who.int] Suggested revision: Divide Appendix D explicitly into: illustrative software implementations; national or subnational architecture examples; regional shared infrastructure; and programme or pilot implementations. Explain what each category does and does not demonstrate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2070✎ edit📣 feedback | received | WHO Core architects agent, medium |
D.1 Illustrative tools and technologies §D.1 p.229 l.Introductory text anchor: medium |
Lists of available tools demonstrate technical feasibility but do not establish successful implementation, national gov…Lists of available tools demonstrate technical feasibility but do not establish successful implementation, national governance, sustainability, scale, interoperability, or health impact. Suggested revision: Add a disclaimer that inclusion indicates potential technical relevance only and does not constitute WHO or ITU endorsement, certification, evidence of effectiveness, or confirmation that the tool satisfies all DPI-H requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-198 discuss | in the document all mentions on GitHub record | ||
| PC-2071✎ edit📣 feedback | received | Core architects agent, medium |
D.1 Illustrative tools and technologies §D.1 p.229 l.Introductory text anchor: medium |
The purpose of the tool list is not sufficiently clear. Readers may not know whether it is intended for market scanning…The purpose of the tool list is not sufficiently clear. Readers may not know whether it is intended for market scanning, procurement, architecture planning, prototyping, or capacity development. Suggested revision: State that the list is illustrative and intended to help readers understand possible technical realisations of logical components. Clarify that countries must conduct independent requirements, security, licensing, support, sustainability, and conformance assessments. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-198 discuss | in the document all mentions on GitHub record | ||
| PC-2072✎ edit📣 feedback | received | Core architects agent |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
The mapping from tools to components may imply one tool corresponds to exactly one DPI-H component. Several listed tech…The mapping from tools to components may imply one tool corresponds to exactly one DPI-H component. Several listed technologies can realise multiple capabilities, while a single component may require several tools or services. Suggested revision: Add a note that mappings are many-to-many and relate to capabilities rather than one-component-one-product procurement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-198 discuss | in the document all mentions on GitHub record | ||
| PC-2073✎ edit📣 feedback | received | Core architects agent |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
No evidence is provided that the listed tools conform to the functional and data requirements in Appendix C or to the c…No evidence is provided that the listed tools conform to the functional and data requirements in Appendix C or to the conformance model in Section 3.7. Suggested revision: Add columns for relevant component capabilities, supported standards, known profiles, available conformance evidence, version assessed, and notable gaps. Do not label a tool as component-conformant without documented testing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2074✎ edit📣 feedback | received | Core architects WHO agent, medium |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
The tool list does not identify licensing, total cost of ownership, hosting, implementation partners, support model, up…The tool list does not identify licensing, total cost of ownership, hosting, implementation partners, support model, upgrade obligations, or long-term maintainership. Suggested revision: Add a neutral assessment template covering licence, governance, maintainership, release activity, support, hosting, skills, implementation cost, operational cost, portability, and supplier dependency. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2075✎ edit📣 feedback | received | Core architects agent, medium |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
The appendix does not indicate whether tools support offline use, low bandwidth, local deployment, regional hosting, mu…The appendix does not indicate whether tools support offline use, low bandwidth, local deployment, regional hosting, multilingual operation, or deployment in resource-constrained environments. Suggested revision: Add context-relevant implementation characteristics or direct readers to independently validate them against country requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2076✎ edit📣 feedback | received | Core architects agent |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
Inclusion of a tool may be interpreted as evidence that it meets national security, privacy, clinical-safety, accessibi…Inclusion of a tool may be interpreted as evidence that it meets national security, privacy, clinical-safety, accessibility, and data-residency requirements. Suggested revision: State explicitly that these properties depend on version, configuration, deployment, operating model, and national law and require separate assessment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-198 discuss | in the document all mentions on GitHub record | ||
| PC-2077✎ edit📣 feedback | received | WHO Core architects agent, low |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
Tool names are likely to date quickly as projects change status, licensing, maintainers, versions, or product names.Tool names are likely to date quickly as projects change status, licensing, maintainers, versions, or product names. Suggested revision: Move the detailed tool catalogue to a versioned online annex or registry and retain only a small number of clearly dated examples in the stable publication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-198 discuss | in the document all mentions on GitHub record | ||
| PC-2078✎ edit📣 feedback | received | WHO Core architects agent, medium |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
Selection criteria for inclusion are not provided. This may create perceived endorsement or bias toward tools familiar …Selection criteria for inclusion are not provided. This may create perceived endorsement or bias toward tools familiar to the drafting group. Suggested revision: Publish transparent inclusion criteria, such as open standards support, public documentation, active maintenance, available source or licence information, implementation evidence, and relevance to a defined DPI-H capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-198 discuss | in the document all mentions on GitHub record | ||
| PC-2079✎ edit📣 feedback | received | Editorial agent, medium |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
The absence of a tool could be interpreted as a negative assessment despite no evidence that the list is exhaustive.The absence of a tool could be interpreted as a negative assessment despite no evidence that the list is exhaustive. Suggested revision: Label the list clearly as non-exhaustive and invite maintainers and countries to submit additional examples through a governed update process. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-198 discuss | in the document all mentions on GitHub record | ||
| PC-2080✎ edit📣 feedback | received | Core architects agent, medium |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
The appendix does not explain whether a listed tool is suitable for proof of concept, early maturity, national producti…The appendix does not explain whether a listed tool is suitable for proof of concept, early maturity, national production, regional federation, or only as a technical building block. Suggested revision: Add an implementation-maturity field distinguishing demonstrator, reference implementation, production framework, deployable product, managed service, or developer library. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2081✎ edit📣 feedback | received | Editorial agent, medium |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
The list should identify the date and version assessed. Tool capability can change materially across releases.The list should identify the date and version assessed. Tool capability can change materially across releases. Suggested revision: Add “Information current as of” and a specific version or release date for every listed tool. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2082✎ edit📣 feedback | received | Core architects agent, low |
D.1 Illustrative tools and technologies §D.1 p.229-231 l.Entire subsection anchor: medium |
The text does not identify whether listed solutions are government-owned, community-governed, foundation-maintained, co…The text does not identify whether listed solutions are government-owned, community-governed, foundation-maintained, commercially operated, or vendor-controlled. Suggested revision: Add maintainership and governance model, while avoiding value judgements based solely on open-source or commercial status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2083✎ edit📣 feedback | received | Core architects agent |
D.1 Illustrative tools and technologies §D.1, Client Registry p.229 l.Client Registry tool entries anchor: medium |
A client-registry tool may support person registration or patient matching without providing the complete national iden…A client-registry tool may support person registration or patient matching without providing the complete national identity-governance, assurance, privacy, deduplication, correction, and foundational-DPI integration required in Appendix C. Suggested revision: Distinguish registration, identifier management, deterministic matching, probabilistic matching, deduplication, cross-referencing, identity assurance, and consent or policy integration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2084✎ edit📣 feedback | received | Core architects agent |
D.1 Illustrative tools and technologies §D.1, Client Registry p.229 l.Client Registry tool entries anchor: medium |
The entries should not imply conformance to IHE PMIR, PIX, PDQ, or national FHIR profiles merely because a tool support…The entries should not imply conformance to IHE PMIR, PIX, PDQ, or national FHIR profiles merely because a tool supports FHIR APIs. Suggested revision: State the precise standards, profiles, actors, options, and versions supported and identify whether independent test evidence exists. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2085✎ edit📣 feedback | received | Core architects agent |
D.1 Illustrative tools and technologies §D.1, Client Registry p.229 l.Client Registry tool entries anchor: medium |
The tool description should identify whether provisional identity, incomplete demographic data, culturally diverse name…The tool description should identify whether provisional identity, incomplete demographic data, culturally diverse names, and non-national identifiers are supported. Suggested revision: Add these as assessment criteria rather than assuming every master-patient-index implementation supports inclusive national registration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2086✎ edit📣 feedback | received | Clinical agent, medium |
D.1 Illustrative tools and technologies §D.1, Lifelong Health Record p.229 l.LHR tool entries anchor: medium |
EHRbase or another clinical-data repository may provide structured persistence and query services but does not by itsel…EHRbase or another clinical-data repository may provide structured persistence and query services but does not by itself constitute the complete LHR capability described in Appendix C. Suggested revision: Identify which LHR capabilities are supported, such as persistence, versioning, query, federation, document access, patient access, provenance, policy enforcement, and longitudinal assembly. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2087✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
D.1 Illustrative tools and technologies §D.1, Lifelong Health Record p.229 l.LHR tool entries anchor: medium |
A repository based on openEHR or FHIR does not automatically interoperate with systems using the other formalism.A repository based on openEHR or FHIR does not automatically interoperate with systems using the other formalism. Suggested revision: State that governed models, implementation guides, terminology bindings, transformations, and conformance tests remain necessary. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2088✎ edit📣 feedback | received | Clinical Core architects agent, low |
D.1 Illustrative tools and technologies §D.1, Lifelong Health Record p.229 l.LHR tool entries anchor: medium |
Tool descriptions do not indicate whether granular access, segmentation, consent or policy enforcement, emergency acces…Tool descriptions do not indicate whether granular access, segmentation, consent or policy enforcement, emergency access, proxy access, and patient audit transparency are supported. Suggested revision: Add these as deployment-specific assessment requirements and avoid implying that a storage engine provides them automatically. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2089✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §D.1, Computable Decision Support Engine p.230 l.CDSE tool entries anchor: medium |
CDS Hooks or similar specifications define interaction mechanisms but are not complete decision-support engines, knowle…CDS Hooks or similar specifications define interaction mechanisms but are not complete decision-support engines, knowledge repositories, or clinical-governance systems. Suggested revision: Distinguish standards and protocols from executable engines, knowledge-authoring tools, knowledge repositories, and workflow integrations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-181 discuss | in the document all mentions on GitHub record | ||
| PC-2090✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §D.1, Computable Decision Support Engine p.230 l.CDSE tool entries anchor: medium |
Decision-support examples should identify whether they implement deterministic rules, guidelines, predictive models, or…Decision-support examples should identify whether they implement deterministic rules, guidelines, predictive models, or AI, because the assurance requirements differ. Suggested revision: Add logic type, intended use, evidence, required inputs, output type, human oversight, validation status, and monitoring capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-2091✎ edit📣 feedback | received | Clinical agent |
Computable Decision Support Engine §D.1, Computable Decision Support Engine p.230 l.CDSE tool entries anchor: medium |
Listing a decision-support tool without discussing clinical validation, alert fatigue, versioning, safety assurance, an…Listing a decision-support tool without discussing clinical validation, alert fatigue, versioning, safety assurance, and incident management may overstate readiness for national deployment. Suggested revision: Add a clear caution that the technical engine must be accompanied by governed computable content, clinical-safety review, testing, monitoring, and withdrawal procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-2092✎ edit📣 feedback | received | Editorial agent |
Lifelong Health Record §D.1, Health Management Information Service p.230 l.HMIS tool entries anchor: medium |
Appendix D uses “Health Management Information Service,” while the component catalogue generally uses “Health Managemen…Appendix D uses “Health Management Information Service,” while the component catalogue generally uses “Health Management Information System.” Suggested revision: Use one term consistently. If “service” is intentional to denote the bounded DPI-H capability, revise the component name consistently throughout the document. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-068 discuss | in the document all mentions on GitHub record | ||
| PC-2093✎ edit📣 feedback | received | Core architects agent |
Lifelong Health Record §D.1, Health Management Information Service p.230 l.HMIS tool entries anchor: medium |
DHIS2 or comparable platforms may implement reporting, analytics, surveillance, tracker, metadata, and programme workfl…DHIS2 or comparable platforms may implement reporting, analytics, surveillance, tracker, metadata, and programme workflows. Mapping the entire platform to one logical component obscures the architecture boundary. Suggested revision: Map individual platform capabilities to reference components and operational applications rather than equating the full product with the HMIS component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2094✎ edit📣 feedback | received | Core architects agent, low |
Lifelong Health Record §D.1, Health Management Information Service p.230 l.HMIS tool entries anchor: medium |
Widespread adoption of a platform is not evidence that national indicator governance, data quality, interoperability, o…Widespread adoption of a platform is not evidence that national indicator governance, data quality, interoperability, or reduced reporting burden have been achieved. Suggested revision: Distinguish deployment scale from implementation outcomes and cite evaluations where outcome claims are made. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2095✎ edit📣 feedback | received | Core architects WHO agent, medium |
Public Health Surveillance Platform §D.1, Public Health Surveillance Platform p.230 l.PHSP tool entries anchor: medium |
Go.Data or similar tools support selected outbreak-investigation and contact-management functions but do not necessaril…Go.Data or similar tools support selected outbreak-investigation and contact-management functions but do not necessarily represent the complete shared surveillance capability. Suggested revision: Identify the specific functions illustrated and distinguish them from routine case reporting, laboratory surveillance, genomic surveillance, analytics, emergency operations, and cross-border notification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2096✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform §D.1, Public Health Surveillance Platform p.230 l.PHSP tool entries anchor: medium |
Surveillance tools are often emergency- or disease-specific. Their suitability for long-term national shared infrastruc…Surveillance tools are often emergency- or disease-specific. Their suitability for long-term national shared infrastructure depends on governance, maintainership, integration, and reuse. Suggested revision: Add the intended scope, deployment maturity, active maintenance status, interoperability support, and suitability for routine versus emergency use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2097✎ edit📣 feedback | received | Core architects WHO agent, medium |
Public Health Surveillance Platform §D.1, Public Health Surveillance Platform p.230 l.PHSP tool entries anchor: medium |
Surveillance platforms may process contact, travel, location, laboratory, and sensitive personal data.Surveillance platforms may process contact, travel, location, laboratory, and sensitive personal data. Suggested revision: Require country assessment of legal authority, human rights, access controls, retention, secondary use, public transparency, and decommissioning after emergencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-186 discuss | in the document all mentions on GitHub record | ||
| PC-2098✎ edit📣 feedback | received | Metadata registries agent |
Public Health Surveillance Platform §D.1, Terminology Service and LIMR p.231 l.Tool entries anchor: medium |
Snowstorm and Ontoserver are terminology-server examples, while CKM supports openEHR model governance. Their functions,…Snowstorm and Ontoserver are terminology-server examples, while CKM supports openEHR model governance. Their functions, artefacts, and governance models are materially different. Suggested revision: Separate terminology authoring and runtime services from information-model authoring and repository tools. Do not present them as interchangeable semantic-infrastructure products. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2099✎ edit📣 feedback | received | Metadata registries agent |
Public Health Surveillance Platform §D.1, Terminology Service and LIMR p.231 l.Tool entries anchor: medium |
Terminology products may have different licensing, hosting, terminology-content, support, and commercial conditions.Terminology products may have different licensing, hosting, terminology-content, support, and commercial conditions. Suggested revision: State separately the software licence, content licence, support model, hosting options, and required terminology memberships or subscriptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2100✎ edit📣 feedback | received | Metadata registries agent |
Public Health Surveillance Platform §D.1, Terminology Service and LIMR p.231 l.Tool entries anchor: medium |
The entries may imply that deploying a sophisticated terminology or archetype platform is the first semantic-governance…The entries may imply that deploying a sophisticated terminology or archetype platform is the first semantic-governance step. Suggested revision: Reiterate that minimum semantic governance can begin with governed artefacts, identifiers, approval, versioning, and distribution before a dedicated platform is adopted. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-199 discuss | in the document all mentions on GitHub record | ||
| PC-2101✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
The country entries vary in length, specificity, evidence, scope, and analytical depth. Some describe national architec…The country entries vary in length, specificity, evidence, scope, and analytical depth. Some describe national architectures, while others mention individual systems or programmes. [cdn.who.int] Suggested revision: Use one standard case-study template covering context, scope, governance, architecture, components, standards, foundational-DPI dependencies, implementation status, outcomes, limitations, and sources. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2102✎ edit📣 feedback | received | Editorial agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
It is not always clear whether an example represents current production operation, partial rollout, pilot implementatio…It is not always clear whether an example represents current production operation, partial rollout, pilot implementation, planned capability, or historical architecture. Suggested revision: Add implementation status and “information current as of” date to every example. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2103✎ edit📣 feedback | received | Core architects WHO agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
The examples may be read as country endorsements of the reference architecture even though most systems were designed b…The examples may be read as country endorsements of the reference architecture even though most systems were designed before this framework and may not use its terminology or component boundaries. Suggested revision: State that the examples illustrate related capabilities and patterns and are not claims of full compliance with the DPI-H reference architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2104✎ edit📣 feedback | received | Core architects agent |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
The examples are not consistently mapped to the seven health goals or to the specific capabilities and components they …The examples are not consistently mapped to the seven health goals or to the specific capabilities and components they illustrate. Suggested revision: Add a structured mapping for each example identifying relevant goals, DPI-H components, DPI-F dependencies, and cross-cutting governance capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2105✎ edit📣 feedback | received | Core architects agent |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
The country descriptions focus on what exists but provide little explanation of implementation sequence, transition fro…The country descriptions focus on what exists but provide little explanation of implementation sequence, transition from legacy systems, data remediation, organisational change, procurement, or capacity development. Suggested revision: Add the implementation pathway, major decisions, prerequisites, transition approach, and lessons relevant to countries at different starting points. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2106✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
Financing sources, recurrent costs, operating ownership, long-term support, and supplier relationships are generally ab…Financing sources, recurrent costs, operating ownership, long-term support, and supplier relationships are generally absent. Suggested revision: Include financing and operating-model information where available, or state explicitly that it was not assessed. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2107✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
Country context is insufficient for assessing transferability. Population, decentralisation, income setting, connectivi…Country context is insufficient for assessing transferability. Population, decentralisation, income setting, connectivity, administrative capacity, foundational-DPI maturity, and legal context materially influence implementation. Suggested revision: Add a concise context box and explicit transferability limitations to every example. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2108✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
Examples rarely indicate whether rural populations, undocumented people, private providers, persons with disabilities, …Examples rarely indicate whether rural populations, undocumented people, private providers, persons with disabilities, linguistic minorities, or people without connectivity can use or benefit from the infrastructure. Suggested revision: Include coverage, exclusion risks, accessibility, offline support, and equity findings where evidence exists. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2109✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
Success-oriented descriptions may create survivorship bias by omitting implementation failures, delays, governance disp…Success-oriented descriptions may create survivorship bias by omitting implementation failures, delays, governance disputes, adoption difficulties, and unintended consequences. Suggested revision: Include at least one limitation, unresolved challenge, or lesson learned for every case. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-202 discuss | in the document all mentions on GitHub record | ||
| PC-2110✎ edit📣 feedback | received | WHO agent, low |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
References should support each specific factual claim, not merely link to a programme home page or general national str…References should support each specific factual claim, not merely link to a programme home page or general national strategy. Suggested revision: Use primary government, legislative, architecture, standards, or independent evaluation sources. Cite the exact version and publication date. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2111✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
Terms such as national EHR, shared health record, HIE, registry, platform, portal, and digital-health infrastructure ma…Terms such as national EHR, shared health record, HIE, registry, platform, portal, and digital-health infrastructure may reflect local usage and not the definitions adopted by the guidance. Suggested revision: Preserve local terminology while explaining how each local element maps, partially maps, or does not map to the DPI-H reference elements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2112✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
The examples rarely identify standards versions, national profiles, conformance mechanisms, certification, or operation…The examples rarely identify standards versions, national profiles, conformance mechanisms, certification, or operational monitoring. Suggested revision: Include technical standards, profiles, conformance approach, test infrastructure, or state that this information was unavailable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2113✎ edit📣 feedback | received | Core architects agent |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
Examples may mix foundational identity, payments, trust, and exchange with health-specific registries and records witho…Examples may mix foundational identity, payments, trust, and exchange with health-specific registries and records without explaining which layer provides each capability. Suggested revision: Add a DPI-F/DPI-H component map for each example. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2114✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2 p.231-234 l.Entire subsection anchor: medium |
Several country descriptions are too brief to support meaningful comparison, yet the appendix implicitly invites cross-…Several country descriptions are too brief to support meaningful comparison, yet the appendix implicitly invites cross-country learning. Suggested revision: Provide a comparison matrix using the same dimensions and reserve narrative text for particularly instructive implementation decisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2115✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, Australia p.231 l.Australia entry anchor: medium |
The entry should distinguish My Health Record, national provider and patient identifier services, terminology services,…The entry should distinguish My Health Record, national provider and patient identifier services, terminology services, electronic prescribing, secure messaging, and state-level clinical systems. They are not one homogenous national platform. [cdn.who.int] Suggested revision: Describe the Australian architecture as a set of nationally governed and jurisdictionally operated capabilities and map each to the relevant DPI-H or DPI-F function. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-204 discuss | in the document all mentions on GitHub record | ||
| PC-2116✎ edit📣 feedback | received | Core architects Clinical agent, low |
Australia §D.2, Australia p.231 l.Australia entry anchor: medium |
My Health Record’s implementation history, participation model, privacy governance, consumer controls, and adoption cha…My Health Record’s implementation history, participation model, privacy governance, consumer controls, and adoption challenges are relevant to transferability. Suggested revision: Include limitations and changes over time, supported by current official or independent sources, rather than presenting only the current target architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-204 discuss | in the document all mentions on GitHub record | ||
| PC-2117✎ edit📣 feedback | received | Core architects agent |
Australia §D.2, Australia p.231 l.Australia entry anchor: medium |
Healthcare identifiers and digital identity or authentication should not be conflated.Healthcare identifiers and digital identity or authentication should not be conflated. Suggested revision: Separate patient and provider identifier services, user authentication, professional credentials, organisation identity, and record access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-204 discuss | in the document all mentions on GitHub record | ||
| PC-2118✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, Australia p.231 l.Australia entry anchor: medium |
Australia’s fiscal, regulatory, connectivity, and institutional capacity differs significantly from many LMIC settings.Australia’s fiscal, regulatory, connectivity, and institutional capacity differs significantly from many LMIC settings. Suggested revision: State which patterns are transferable, such as persistent identifiers and national governance, and which depend on substantial infrastructure, workforce, and recurrent financing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-204 discuss | in the document all mentions on GitHub record | ||
| PC-2119✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, Denmark p.232 l.Denmark entry anchor: medium |
The entry should distinguish the national health portal, health-data network, medication services, registries, regional…The entry should distinguish the national health portal, health-data network, medication services, registries, regional EHRs, and national identifiers. [cdn.who.int] Suggested revision: Map these capabilities separately and describe the division of responsibilities among national, regional, municipal, and provider organisations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-205 discuss | in the document all mentions on GitHub record | ||
| PC-2120✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, Denmark p.232 l.Denmark entry anchor: medium |
The example depends on a mature civil-registration number, digital identity environment, high connectivity, and long-st…The example depends on a mature civil-registration number, digital identity environment, high connectivity, and long-standing national health-data governance. Suggested revision: State these enabling conditions and caution against transferring the technical pattern without the associated institutional foundations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-205 discuss | in the document all mentions on GitHub record | ||
| PC-2121✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Australia §D.2, Denmark p.232 l.Denmark entry anchor: medium |
If Denmark is presented as an example of an LHR or national record, the description should clarify whether data is cent…If Denmark is presented as an example of an LHR or national record, the description should clarify whether data is centrally stored, federated, summarised, or accessed through shared services. Suggested revision: Describe the actual data and service topology rather than using the general label “national health record.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-205 discuss | in the document all mentions on GitHub record | ||
| PC-2122✎ edit📣 feedback | received | Core architects agent |
Australia §D.2, Estonia p.232 l.Estonia entry anchor: medium |
Estonia is frequently used to illustrate reuse of foundational digital identity and data exchange, but the health-speci…Estonia is frequently used to illustrate reuse of foundational digital identity and data exchange, but the health-specific services and governance should be distinguished from the X-Road exchange layer. [cdn.who.int] Suggested revision: Identify which capabilities are provided by foundational infrastructure and which are provided by the health sector, including health records, prescribing, portals, registries, and terminology. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-206 discuss | in the document all mentions on GitHub record | ||
| PC-2123✎ edit📣 feedback | received | Core architects agent |
Australia §D.2, Estonia p.232 l.Estonia entry anchor: medium |
X-Road enables secure exchange but does not itself provide health semantics, clinical models, consent rules, or workflo…X-Road enables secure exchange but does not itself provide health semantics, clinical models, consent rules, or workflow interoperability. Suggested revision: State explicitly that health-sector standards and services operate above the foundational exchange capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-206 discuss | in the document all mentions on GitHub record | ||
| PC-2124✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, Estonia p.232 l.Estonia entry anchor: medium |
Estonia’s small population, national identity coverage, legal environment, administrative coherence, and digital-govern…Estonia’s small population, national identity coverage, legal environment, administrative coherence, and digital-government maturity affect transferability. Suggested revision: Include these contextual conditions and avoid presenting the model as directly replicable at different scales or governance arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-206 discuss | in the document all mentions on GitHub record | ||
| PC-2125✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, Estonia p.232 l.Estonia entry anchor: medium |
Blockchain is sometimes mentioned in descriptions of Estonia’s health infrastructure in a way that can overstate its ar…Blockchain is sometimes mentioned in descriptions of Estonia’s health infrastructure in a way that can overstate its architectural role. Suggested revision: If included, describe precisely what integrity or audit function it supports and avoid implying that health records are stored on a public blockchain. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-206 discuss | in the document all mentions on GitHub record | ||
| PC-2126✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, India p.232 l.India entry anchor: medium |
The entry should distinguish ABDM registries, ABHA identity, health-information exchange and consent, health-facility a…The entry should distinguish ABDM registries, ABHA identity, health-information exchange and consent, health-facility and professional registries, UHI, programme systems, and state-level implementations. [cdn.who.int] Suggested revision: Map each national building block to the relevant reference component and identify elements that are operational applications rather than DPI-H. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-207 discuss | in the document all mentions on GitHub record | ||
| PC-2127✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, India p.232 l.India entry anchor: medium |
Registration numbers and programme participation can be presented as evidence of implementation, but they do not necess…Registration numbers and programme participation can be presented as evidence of implementation, but they do not necessarily show effective use, longitudinal data exchange, provider adoption, or health outcomes. Suggested revision: Distinguish registrations, linked records, completed exchanges, active facilities, active professionals, geographic coverage, and service outcomes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-207 discuss | in the document all mentions on GitHub record | ||
| PC-2128✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, India p.232 l.India entry anchor: medium |
The example should address consent, access for people without smartphones, state-level digital variation, language, pri…The example should address consent, access for people without smartphones, state-level digital variation, language, private-sector participation, and exclusion risks. Suggested revision: Include assisted and offline access, multilingual considerations, voluntary identifier use, and evidence of effective inclusion where available. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-207 discuss | in the document all mentions on GitHub record | ||
| PC-2129✎ edit📣 feedback | received | Core architects agent |
Australia §D.2, India p.232 l.India entry anchor: medium |
ABHA or other health identifiers should not be described simply as Aadhaar-derived identity.ABHA or other health identifiers should not be described simply as Aadhaar-derived identity. Suggested revision: Explain the relationship among foundational identity, health identity, authentication, consent, and health-record exchange without implying that one identifier provides all these capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-207 discuss | in the document all mentions on GitHub record | ||
| PC-2130✎ edit📣 feedback | received | Editorial agent, low |
Australia §D.2, Kenya p.232 l.Kenya entry anchor: medium |
The entry should distinguish policy and architecture initiatives from capabilities that are fully operational nationall…The entry should distinguish policy and architecture initiatives from capabilities that are fully operational nationally. [cdn.who.int] Suggested revision: State the implementation status, geographic coverage, participating systems, and date of the information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-207 discuss | in the document all mentions on GitHub record | ||
| PC-2131✎ edit📣 feedback | received | Core architects agent, medium |
Australia §D.2, Kenya p.232 l.Kenya entry anchor: medium |
Kenya has multiple digital-health, facility, reporting, insurance, identity, and interoperability initiatives. A short …Kenya has multiple digital-health, facility, reporting, insurance, identity, and interoperability initiatives. A short entry may incorrectly present them as one integrated national architecture. Suggested revision: Map the initiatives separately and explain their current integration, governance, and remaining fragmentation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-208 discuss | in the document all mentions on GitHub record | ||
| PC-2132✎ edit📣 feedback | received | Core architects agent |
Australia §D.2, Kenya p.232 l.Kenya entry anchor: medium |
The example should address county-level governance, public-private service delivery, community health, connectivity, an…The example should address county-level governance, public-private service delivery, community health, connectivity, and varying facility maturity. Suggested revision: Include how national architecture and standards are implemented across counties and non-state providers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-208 discuss | in the document all mentions on GitHub record | ||
| PC-2133✎ edit📣 feedback | received | Editorial agent, medium |
Australia §D.2, Kenya p.232 l.Kenya entry anchor: medium |
Any claims about current laws, national platforms, or implementation status are time-sensitive.Any claims about current laws, national platforms, or implementation status are time-sensitive. Suggested revision: Cite current official legislation and programme documentation and provide the assessment date. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-208 discuss | in the document all mentions on GitHub record | ||
| PC-2134✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Nigeria p.233 l.Nigeria entry anchor: medium |
Nigeria’s federal structure and substantial state-level variation are central to understanding any national digital-hea…Nigeria’s federal structure and substantial state-level variation are central to understanding any national digital-health example. [cdn.who.int] Suggested revision: Explain the division of responsibility among federal, state, local, programme, and private-sector actors. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-209 discuss | in the document all mentions on GitHub record | ||
| PC-2135✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Nigeria p.233 l.Nigeria entry anchor: medium |
The entry should separate national strategies, architecture designs, pilot implementations, and production services.The entry should separate national strategies, architecture designs, pilot implementations, and production services. Suggested revision: State the maturity and coverage of each cited capability and avoid describing planned components as established infrastructure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-209 discuss | in the document all mentions on GitHub record | ||
| PC-2136✎ edit📣 feedback | received | Core architects agent, low |
Kenya §D.2, Nigeria p.233 l.Nigeria entry anchor: medium |
The example could provide valuable learning about implementation in a large, decentralised, lower-resource setting, but…The example could provide valuable learning about implementation in a large, decentralised, lower-resource setting, but the current short format may omit governance and capacity lessons. Suggested revision: Add sequencing, federal-state coordination, interoperability, financing, workforce, and legacy-system lessons. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-209 discuss | in the document all mentions on GitHub record | ||
| PC-2137✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Nigeria p.233 l.Nigeria entry anchor: medium |
The role of private providers, informal care, community systems, low-connectivity areas, and populations without reliab…The role of private providers, informal care, community systems, low-connectivity areas, and populations without reliable identity should be included. Suggested revision: Add coverage and inclusion information or state that it was not assessed. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-209 discuss | in the document all mentions on GitHub record | ||
| PC-2138✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Rwanda p.233 l.Rwanda entry anchor: medium |
Rwanda is often cited for coordinated national digital-health implementation, but the entry should distinguish health-i…Rwanda is often cited for coordinated national digital-health implementation, but the entry should distinguish health-insurance, community health, facility systems, reporting, exchange, and national registries. [cdn.who.int] Suggested revision: Map each system or capability separately, identify implementation status, and avoid treating the ecosystem as one platform. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-210 discuss | in the document all mentions on GitHub record | ||
| PC-2139✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Rwanda p.233 l.Rwanda entry anchor: medium |
Rwanda’s scale, administrative coordination, insurance arrangements, and national governance affect transferability.Rwanda’s scale, administrative coordination, insurance arrangements, and national governance affect transferability. Suggested revision: Add context and distinguish generally applicable governance lessons from scale-dependent technical choices. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-210 discuss | in the document all mentions on GitHub record | ||
| PC-2140✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Rwanda p.233 l.Rwanda entry anchor: medium |
The example should include measured results or implementation limitations rather than relying on reputation as a digita…The example should include measured results or implementation limitations rather than relying on reputation as a digital-health leader. Suggested revision: Cite current primary or independent evaluations and identify unresolved interoperability, sustainability, adoption, or data-quality challenges. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-210 discuss | in the document all mentions on GitHub record | ||
| PC-2141✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Spain p.233 l.Spain entry anchor: medium |
Spain’s health system is decentralised across autonomous communities. A national example must distinguish central coord…Spain’s health system is decentralised across autonomous communities. A national example must distinguish central coordination from regional operation. [cdn.who.int] Suggested revision: Explain national services, regional EHRs, interoperability arrangements, professional and patient identifiers, e-prescribing, and governance across autonomous communities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-211 discuss | in the document all mentions on GitHub record | ||
| PC-2142✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Spain p.233 l.Spain entry anchor: medium |
National interoperability does not necessarily imply one national LHR or one uniform EHR platform.National interoperability does not necessarily imply one national LHR or one uniform EHR platform. Suggested revision: Describe the actual exchange and access architecture and identify the national specifications enabling regional systems to interoperate. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-211 discuss | in the document all mentions on GitHub record | ||
| PC-2143✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Spain p.233 l.Spain entry anchor: medium |
Any statement about national coverage of patient summaries, e-prescriptions, or cross-border services should identify t…Any statement about national coverage of patient summaries, e-prescriptions, or cross-border services should identify the date, participating regions, and precise service scope. Suggested revision: Cite current official sources and separate domestic interoperability from MyHealth@EU participation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-211 discuss | in the document all mentions on GitHub record | ||
| PC-2144✎ edit📣 feedback | received | Core architects agent, low |
Kenya §D.2, Spain, Catalonia p.233 l.Catalonia entry anchor: medium |
Including Spain and Catalonia separately is useful, but the analytical purpose of the subnational example is not explai…Including Spain and Catalonia separately is useful, but the analytical purpose of the subnational example is not explained. [cdn.who.int] Suggested revision: State that Catalonia illustrates subnational shared infrastructure within a decentralised national system and explain its relationship to national services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-211 discuss | in the document all mentions on GitHub record | ||
| PC-2145✎ edit📣 feedback | received | Core architects Clinical agent, medium |
Kenya §D.2, Spain, Catalonia p.233 l.Catalonia entry anchor: medium |
A regional shared clinical record can combine document exchange, longitudinal access, portals, imaging, prescribing, an…A regional shared clinical record can combine document exchange, longitudinal access, portals, imaging, prescribing, and provider services. Suggested revision: Map individual capabilities rather than treating the complete Catalan digital-health environment as one LHR component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-211 discuss | in the document all mentions on GitHub record | ||
| PC-2146✎ edit📣 feedback | received | Core architects agent, medium |
Kenya §D.2, Spain, Catalonia p.233 l.Catalonia entry anchor: medium |
The example should explain which governance, technical, and financing responsibilities sit at Catalan, provider, and Sp…The example should explain which governance, technical, and financing responsibilities sit at Catalan, provider, and Spanish national levels. Suggested revision: Add a responsibility map and transferability lesson for decentralised countries. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-211 discuss | in the document all mentions on GitHub record | ||
| PC-2147✎ edit📣 feedback | received | Core architects agent, medium |
Spain — Catalonia (subnational) §D.2, Tanzania p.234 l.Tanzania entry anchor: medium |
The entry should distinguish national architecture and interoperability initiatives from particular products or program…The entry should distinguish national architecture and interoperability initiatives from particular products or programme implementations. [cdn.who.int] Suggested revision: Identify the governance, architecture, standards, shared services, operational platforms, geographic coverage, and current production status separately. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-212 discuss | in the document all mentions on GitHub record | ||
| PC-2148✎ edit📣 feedback | received | Core architects agent |
Spain — Catalonia (subnational) §D.2, Tanzania p.234 l.Tanzania entry anchor: medium |
Tanzania could provide valuable evidence on enterprise architecture, health-information mediation, facility registries,…Tanzania could provide valuable evidence on enterprise architecture, health-information mediation, facility registries, logistics, and routine reporting, but a short inventory does not show implementation sequence or lessons. Suggested revision: Add the progression from programme-specific systems toward shared standards and services, including what worked, what remains fragmented, and what was required institutionally. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-212 discuss | in the document all mentions on GitHub record | ||
| PC-2149✎ edit📣 feedback | received | Core architects agent |
Spain — Catalonia (subnational) §D.2, Tanzania p.234 l.Tanzania entry anchor: medium |
Offline operation, district and facility capacity, private providers, community health, and recurrent support are centr…Offline operation, district and facility capacity, private providers, community health, and recurrent support are central to the context. Suggested revision: Include these dimensions and avoid presenting central architecture alone as evidence of effective national coverage. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-212 discuss | in the document all mentions on GitHub record | ||
| PC-2150✎ edit📣 feedback | received | Core architects agent, medium |
Spain — Catalonia (subnational) §D.2, Uganda p.234 l.Uganda entry anchor: medium |
The entry should distinguish the national digital-health strategy and enterprise architecture from actual deployed shar…The entry should distinguish the national digital-health strategy and enterprise architecture from actual deployed shared infrastructure. [cdn.who.int] Suggested revision: State which capabilities operate nationally, which remain pilots or programme deployments, and the date and scope of available evidence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-213 discuss | in the document all mentions on GitHub record | ||
| PC-2151✎ edit📣 feedback | received | Core architects agent, low |
Spain — Catalonia (subnational) §D.2, Uganda p.234 l.Uganda entry anchor: medium |
Uganda’s experience may illustrate donor alignment, programme fragmentation, interoperability, and national architectur…Uganda’s experience may illustrate donor alignment, programme fragmentation, interoperability, and national architecture governance, but these lessons need to be stated explicitly. Suggested revision: Add implementation lessons, including governance, partner coordination, standards enforcement, financing, and capacity constraints. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-213 discuss | in the document all mentions on GitHub record | ||
| PC-2152✎ edit📣 feedback | received | Core architects agent, medium |
Spain — Catalonia (subnational) §D.2, Uganda p.234 l.Uganda entry anchor: medium |
Community health, remote facilities, low connectivity, and non-state providers should be reflected when describing the …Community health, remote facilities, low connectivity, and non-state providers should be reflected when describing the effective reach of national infrastructure. Suggested revision: Include functional and geographic coverage rather than only the existence of national systems or standards. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-213 discuss | in the document all mentions on GitHub record | ||
| PC-2153✎ edit📣 feedback | received | Editorial agent, medium |
Spain — Catalonia (subnational) §D.2, United Kingdom, England p.234 l.England entry anchor: medium |
The heading should make clear that the example concerns England rather than the entire United Kingdom, because health-s…The heading should make clear that the example concerns England rather than the entire United Kingdom, because health-system governance and digital infrastructure differ across the four nations. [cdn.who.int] Suggested revision: Use England, United Kingdom and avoid generalising English systems or governance to Scotland, Wales, and Northern Ireland. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-214 discuss | in the document all mentions on GitHub record | ||
| PC-2154✎ edit📣 feedback | received | Core architects agent, medium |
Spain — Catalonia (subnational) §D.2, United Kingdom, England p.234 l.England entry anchor: medium |
The NHS digital ecosystem includes national services, local EPRs, the NHS Spine, NHS number, Summary Care Record, e-pre…The NHS digital ecosystem includes national services, local EPRs, the NHS Spine, NHS number, Summary Care Record, e-prescribing, terminology, portals, and shared-care records. Suggested revision: Map each service to the corresponding capability and avoid treating the ecosystem as one centrally implemented architecture. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-214 discuss | in the document all mentions on GitHub record | ||
| PC-2155✎ edit📣 feedback | received | Core architects agent, low |
Spain — Catalonia (subnational) §D.2, United Kingdom, England p.234 l.England entry anchor: medium |
National services have evolved over time through multiple programmes, supplier models, restructures, and governance cha…National services have evolved over time through multiple programmes, supplier models, restructures, and governance changes. Suggested revision: Reference the current responsible bodies, current service names, implementation status, and date. Include relevant lessons from earlier programme difficulties. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-214 discuss | in the document all mentions on GitHub record | ||
| PC-2156✎ edit📣 feedback | received | Core architects agent |
Spain — Catalonia (subnational) §D.2, United Kingdom, England p.234 l.England entry anchor: medium |
England’s mature institutions, national identifier, public financing, established terminology infrastructure, and speci…England’s mature institutions, national identifier, public financing, established terminology infrastructure, and specialist workforce influence transferability. Suggested revision: Distinguish transferable architecture principles from capabilities dependent on high recurrent investment and institutional maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-214 discuss | in the document all mentions on GitHub record | ||
| PC-2157✎ edit📣 feedback | received | Core architects agent, medium |
Spain — Catalonia (subnational) §D.2, United States p.234 l.United States entry anchor: medium |
The United States does not provide a straightforward example of centrally governed national DPI-H. Its ecosystem is dec…The United States does not provide a straightforward example of centrally governed national DPI-H. Its ecosystem is decentralised across federal agencies, states, health-information networks, providers, payers, and vendors. [cdn.who.int] Suggested revision: Present it as an example of nationwide interoperability governance and network federation rather than a single national infrastructure implementation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-215 discuss | in the document all mentions on GitHub record | ||
| PC-2158✎ edit📣 feedback | received | Core architects agent |
Spain — Catalonia (subnational) §D.2, United States p.234 l.United States entry anchor: medium |
National interoperability frameworks, exchange networks, EHR certification, and APIs should be distinguished from autho…National interoperability frameworks, exchange networks, EHR certification, and APIs should be distinguished from authoritative national registries or a national LHR. Suggested revision: Map each capability accurately and identify which DPI-H reference components have no direct US equivalent. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-215 discuss | in the document all mentions on GitHub record | ||
| PC-2159✎ edit📣 feedback | received | Core architects agent, medium |
Spain — Catalonia (subnational) §D.2, United States p.234 l.United States entry anchor: medium |
The US regulatory, insurance, market, supplier, and institutional environment differs significantly from publicly gover…The US regulatory, insurance, market, supplier, and institutional environment differs significantly from publicly governed national health systems. Suggested revision: State clearly which lessons concern technical standards, network governance, and conformance and which are not directly transferable to national public infrastructure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-215 discuss | in the document all mentions on GitHub record | ||
| PC-2160✎ edit📣 feedback | received | Core architects agent, low |
Spain — Catalonia (subnational) §D.2, United States p.234 l.United States entry anchor: medium |
Claims about nationwide exchange, patient access, or conformance should be qualified because participation, implementat…Claims about nationwide exchange, patient access, or conformance should be qualified because participation, implementation, and interoperability remain variable. Suggested revision: Use current official and independent sources and distinguish regulatory availability from consistent operational adoption. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-215 discuss | in the document all mentions on GitHub record | ||
| PC-2161✎ edit📣 feedback | received | Core architects agent, medium |
WHO SMART Guidelines pilot implementations §D.3, EU and EEA regional surveillance p.234 l.EU/EEA entry anchor: medium |
The examples should identify the specific platform or network illustrated, such as TESSy, and distinguish surveillance-…The examples should identify the specific platform or network illustrated, such as TESSy, and distinguish surveillance-data collection from clinical cross-border exchange or the wider EHDS. [cdn.who.int] Suggested revision: Name each infrastructure, define its purpose and participating authorities, and avoid combining surveillance, clinical exchange, and secondary-use data access into one regional example. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-216 discuss | in the document all mentions on GitHub record | ||
| PC-2162✎ edit📣 feedback | received | Core architects WHO agent, medium |
WHO SMART Guidelines pilot implementations §D.3, EU and EEA regional surveillance p.234 l.EU/EEA entry anchor: medium |
Regional surveillance infrastructure does not necessarily provide the full Public Health Surveillance Platform describe…Regional surveillance infrastructure does not necessarily provide the full Public Health Surveillance Platform described in Appendix C. Suggested revision: Map only the capabilities demonstrated, such as standardised reporting, multi-country data submission, validation, analysis, and regional coordination. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-216 discuss | in the document all mentions on GitHub record | ||
| PC-2163✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
WHO SMART Guidelines pilot implementations §D.3, EU and EEA regional surveillance p.234 l.EU/EEA entry anchor: medium |
Regional surveillance depends on common case definitions, classifications, metadata, reporting rules, and release gover…Regional surveillance depends on common case definitions, classifications, metadata, reporting rules, and release governance. These semantic arrangements are more instructive than the platform alone. Suggested revision: Highlight the governance of shared definitions, versions, reporting obligations, validation, and changes across countries. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-216 discuss | in the document all mentions on GitHub record | ||
| PC-2164✎ edit📣 feedback | received | Core architects agent, medium |
WHO SMART Guidelines pilot implementations §D.3, EU and EEA regional surveillance p.234 l.EU/EEA entry anchor: medium |
EU and EEA arrangements operate under mature regional law, institutions, funding, and national authorities.EU and EEA arrangements operate under mature regional law, institutions, funding, and national authorities. Suggested revision: State the legal and institutional prerequisites and discuss lighter regional coordination models for settings without comparable supranational authority. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-216 discuss | in the document all mentions on GitHub record | ||
| PC-2165✎ edit📣 feedback | received | WHO agent, medium |
WHO SMART Guidelines pilot implementations §D.3, EU and EEA regional surveillance p.234 l.EU/EEA entry anchor: medium |
The entry should distinguish binding reporting obligations from voluntary surveillance networks and research collaborat…The entry should distinguish binding reporting obligations from voluntary surveillance networks and research collaboration. Suggested revision: Identify the legal basis, participating jurisdictions, dataset scope, implementation status, and date for each cited service. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-216 discuss | in the document all mentions on GitHub record | ||
| PC-2166✎ edit📣 feedback | received | Core architects WHO agent, medium |
WHO SMART Guidelines pilot implementations §D.3, EU and EEA regional surveillance p.234 l.EU/EEA entry anchor: medium |
Cross-border surveillance may involve identifiable or potentially re-identifiable data, particularly for rare condition…Cross-border surveillance may involve identifiable or potentially re-identifiable data, particularly for rare conditions and small populations. Suggested revision: Explain data minimisation, pseudonymisation, aggregate reporting, access controls, disclosure rules, retention, and national responsibility. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-216 discuss | in the document all mentions on GitHub record | ||
| PC-2167✎ edit📣 feedback | received | WHO Core architects agent, low |
WHO SMART Guidelines pilot implementations §D.3, EU and EEA regional surveillance p.234 l.EU/EEA entry anchor: medium |
The example does not clearly explain how national surveillance systems map and submit data to regional infrastructure o…The example does not clearly explain how national surveillance systems map and submit data to regional infrastructure or how validation failures are handled. Suggested revision: Add the national-to-regional workflow, source authority, submission, validation, correction, publication, and feedback process. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-216 discuss | in the document all mentions on GitHub record | ||
| PC-2168✎ edit📣 feedback | received | Core architects agent, medium |
WHO SMART Guidelines pilot implementations §D.3, EU and EEA regional surveillance p.234 l.EU/EEA entry anchor: medium |
Regional infrastructure requires a sustained funding and operating model across participating states and institutions.Regional infrastructure requires a sustained funding and operating model across participating states and institutions. Suggested revision: Include operating authority, financing approach, governance, national contributions, and service-continuity arrangements where available. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-216 discuss | in the document all mentions on GitHub record | ||
| PC-2169✎ edit📣 feedback | received | Core architects WHO agent, medium |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
Pilot implementation demonstrates feasibility and learning but should not be presented as equivalent to nationally scal…Pilot implementation demonstrates feasibility and learning but should not be presented as equivalent to nationally scaled, sustainably operated DPI-H. [cdn.who.int] Suggested revision: Label each example clearly as pilot, trial, limited deployment, national rollout, or routine operation and state the date and scale. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2170✎ edit📣 feedback | received | WHO Metadata registries Clinical agent, medium |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
SMART Guidelines primarily provide reusable requirements, workflows, data elements, decision logic, and implementation …SMART Guidelines primarily provide reusable requirements, workflows, data elements, decision logic, and implementation artefacts. They are not themselves a national DPI-H application component. Suggested revision: Map SMART Guidelines to semantic governance, LIMR, Terminology Service, CDSE knowledge, implementation guides, and operational applications rather than treating them as infrastructure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2171✎ edit📣 feedback | received | Clinical WHO agent, medium |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
The example could provide strong evidence for translating guidelines into computable artefacts, but the distinction amo…The example could provide strong evidence for translating guidelines into computable artefacts, but the distinction among Digital Adaptation Kits, FHIR implementation guides, reference applications, and country adaptations should be explicit. Suggested revision: Describe each SMART layer and specify which artefacts were adopted, adapted, implemented, or evaluated in each country. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2172✎ edit📣 feedback | received | WHO agent, low |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
The entry should identify the health domains and countries rather than referring generally to pilots.The entry should identify the health domains and countries rather than referring generally to pilots. Suggested revision: List the use case, implementing country or site, delivery setting, implementation period, number of sites or users, and evaluation status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2173✎ edit📣 feedback | received | Core architects agent, medium |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
Pilot implementations may receive exceptional technical support, funding, training, and implementation attention that a…Pilot implementations may receive exceptional technical support, funding, training, and implementation attention that are not available during national scale-up. Suggested revision: Document the support model and identify which capabilities must be institutionalised for sustainable routine operation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2174✎ edit📣 feedback | received | WHO Clinical agent, low |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
Technical implementation does not demonstrate improved guideline adherence, care quality, user experience, or health ou…Technical implementation does not demonstrate improved guideline adherence, care quality, user experience, or health outcomes unless these were evaluated directly. Suggested revision: Separate technical feasibility, usability, workflow adoption, clinical-process outcomes, and health outcomes. Report only findings supported by the evaluation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2175✎ edit📣 feedback | received | Core architects WHO agent, medium |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
The case should describe how country adaptations were tested against the reference artefacts and how deviations were do…The case should describe how country adaptations were tested against the reference artefacts and how deviations were documented. Suggested revision: Include profile validation, terminology validation, workflow testing, decision-logic tests, reference cases, national mappings, and conformance results. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2176✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
Country localisation can create divergence if adaptations, terminology bindings, and mappings are not returned to a gov…Country localisation can create divergence if adaptations, terminology bindings, and mappings are not returned to a governed national or global process. Suggested revision: Describe the feedback, publication, versioning, and change-governance process used for country adaptations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2177✎ edit📣 feedback | received | Clinical Core architects agent, low |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
Digital guideline implementations should assess language, literacy, device access, health-worker workload, connectivity…Digital guideline implementations should assess language, literacy, device access, health-worker workload, connectivity, disability access, and suitability for community settings. Suggested revision: Add these dimensions to the case-study template and report any observed exclusion or workflow burden. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2178✎ edit📣 feedback | received | Core architects Clinical agent, medium |
European Union and European Economic Area — regional surveillance §D.3, WHO SMART Guidelines pilots p.235 l.SMART Guidelines entry anchor: medium |
The entry does not explain who will maintain country profiles, terminology, applications, test assets, and decision log…The entry does not explain who will maintain country profiles, terminology, applications, test assets, and decision logic after a pilot ends. Suggested revision: Add long-term ownership, financing, maintainership, release management, training, and supplier or partner transition arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-217 discuss | in the document all mentions on GitHub record | ||
| PC-2179✎ edit📣 feedback | received | Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
Appendix D is valuable, but it currently functions mainly as an inventory. It does not consistently provide enough evid…Appendix D is valuable, but it currently functions mainly as an inventory. It does not consistently provide enough evidence to determine whether the examples demonstrate successful, sustainable, equitable, or conformant DPI-H. Suggested revision: Reframe the appendix as a set of structured illustrative cases rather than implementation endorsements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2180✎ edit📣 feedback | received | WHO Core architects agent, low |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
Cases should distinguish evidence of existence, implementation, adoption, interoperability, benefit, sustainability, an…Cases should distinguish evidence of existence, implementation, adoption, interoperability, benefit, sustainability, and health impact. Suggested revision: Use a common evidence scale and identify which level each claim supports. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2181✎ edit📣 feedback | received | Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
The appendix is not consistently connected to the seven priority health goals.The appendix is not consistently connected to the seven priority health goals. Suggested revision: Add a matrix mapping every example to relevant goals, capabilities, components, and outcomes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2182✎ edit📣 feedback | received | Core architects agent |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
The appendix does not consistently show whether identity, trust, payments, exchange, or geospatial capability comes fro…The appendix does not consistently show whether identity, trust, payments, exchange, or geospatial capability comes from foundational DPI or from health-sector infrastructure. Suggested revision: Add a standard DPI-F/DPI-H dependency map to each case. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2183✎ edit📣 feedback | received | Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
Examples describe architectures and technologies more often than implementation journeys.Examples describe architectures and technologies more often than implementation journeys. Suggested revision: Add starting point, sequence, legacy transition, governance, procurement, capacity, change management, and current maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2184✎ edit📣 feedback | received | Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
Financing and operating models are largely absent.Financing and operating models are largely absent. Suggested revision: Include capital and recurrent financing, operating ownership, partner dependence, service management, and sustainability status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2185✎ edit📣 feedback | received | Core architects agent |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
Transferability is difficult to assess without national context.Transferability is difficult to assess without national context. Suggested revision: Add population, health-system structure, decentralisation, income setting, connectivity, foundational-DPI maturity, institutional capacity, and legal environment. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2186✎ edit📣 feedback | received | Core architects agent |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
The appendix gives limited attention to people or providers not served effectively by the digital infrastructure.The appendix gives limited attention to people or providers not served effectively by the digital infrastructure. Suggested revision: Include accessibility, rural and remote coverage, private-sector participation, populations without identity, assisted access, language, disability, affordability, and offline operation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2187✎ edit📣 feedback | received | Core architects agent |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
The examples seldom describe architecture mapping, profile conformance, certification, or end-to-end testing.The examples seldom describe architecture mapping, profile conformance, certification, or end-to-end testing. Suggested revision: Include standards versions, profiles, conformance arrangements, testing evidence, and known deviations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2188✎ edit📣 feedback | received | WHO agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
Readers may interpret concise positive descriptions as WHO or ITU validation of the technologies or national programmes.Readers may interpret concise positive descriptions as WHO or ITU validation of the technologies or national programmes. Suggested revision: Add a prominent statement that inclusion is illustrative and does not constitute endorsement, certification, or comprehensive evaluation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2189✎ edit📣 feedback | received | WHO Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
Rapidly evolving programmes and software make the appendix vulnerable to becoming outdated shortly after publication.Rapidly evolving programmes and software make the appendix vulnerable to becoming outdated shortly after publication. Suggested revision: Keep the stable document concise and publish the detailed case catalogue online with dates, version history, source links, and a governed update process. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2190✎ edit📣 feedback | received | WHO agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
The examples do not consistently identify their authorship or whether the country authorities reviewed the descriptions.The examples do not consistently identify their authorship or whether the country authorities reviewed the descriptions. Suggested revision: Invite the responsible national or regional authority to verify factual descriptions while retaining editorial independence and documenting the verification date. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-200 discuss | in the document all mentions on GitHub record | ||
| PC-2191✎ edit📣 feedback | received | Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
There are no explicit negative cases or examples where implementation was delayed, fragmented, discontinued, or replace…There are no explicit negative cases or examples where implementation was delayed, fragmented, discontinued, or replaced. Suggested revision: Include lessons from mixed or unsuccessful implementations to provide a balanced evidence base and help countries avoid recurring failures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-202 discuss | in the document all mentions on GitHub record | ||
| PC-2192✎ edit📣 feedback | received | Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
The set includes countries from different income and maturity contexts, which is positive, but the entries are too shor…The set includes countries from different income and maturity contexts, which is positive, but the entries are too short to show how low-resource constraints were addressed. Suggested revision: Expand selected LMIC cases with concrete treatment of offline operation, local skills, donor coordination, recurrent financing, legacy systems, and subnational delivery. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2193✎ edit📣 feedback | received | Core architects agent, medium |
D Appendix D: Country and Regional Implementation Examples §Appendix D overall p.229-235 l.Entire appendix anchor: medium |
The appendix does not include a direct comparison showing which proposed DPI-H components have strong implementation pr…The appendix does not include a direct comparison showing which proposed DPI-H components have strong implementation precedent and which remain less established. Suggested revision: Add a matrix of components against examples, distinguishing established national precedent, partial analogue, pilot evidence, tool availability, and identified evidence gaps. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-201 discuss | in the document all mentions on GitHub record | ||
| PC-2194✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Opening text and mapping tables anchor: medium |
The appendix contains an important mapping from health goals to capabilities and infrastructure, but it does not explai…The appendix contains an important mapping from health goals to capabilities and infrastructure, but it does not explain sufficiently how ministries, architects, procurement teams, or development partners should use the mapping. Suggested revision: Add a short introduction explaining that the mapping supports priority setting, capability assessment, architecture design, investment planning, procurement alignment, and gap analysis, but does not prescribe a universal implementation sequence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2195✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Opening text anchor: medium |
The appendix does not provide enough methodological information to reproduce or independently validate the mappings. It…The appendix does not provide enough methodological information to reproduce or independently validate the mappings. It is unclear how capabilities and components were selected, reviewed, or prioritised. Suggested revision: Summarise the mapping method, source material, participants, review criteria, treatment of disagreement, and validation process. Cross-reference the detailed methodology in Section 2.4. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-023 discuss | in the document all mentions on GitHub record | ||
| PC-2196✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Opening text anchor: medium |
The mappings may appear deterministic, even though one health goal can depend on several alternative capability and com…The mappings may appear deterministic, even though one health goal can depend on several alternative capability and component arrangements. Suggested revision: State that the tables present a reference decomposition rather than the only valid architecture. Countries may adopt alternative arrangements if they preserve the intended capability and document the mapping. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2197✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Opening text anchor: medium |
The appendix does not consistently make clear which mapped components belong to the foundational shared data layer and …The appendix does not consistently make clear which mapped components belong to the foundational shared data layer and which belong to the business-services layer. Suggested revision: Add a layer column or use consistent visual notation to distinguish foundational shared data components, business-services components, DPI-F dependencies, functional applications, and cross-cutting enablers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2198✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Table headings anchor: medium |
Foundational DPI, DPI-H components, functional applications, and cross-cutting governance capabilities may appear toget…Foundational DPI, DPI-H components, functional applications, and cross-cutting governance capabilities may appear together without a consistent classification. Suggested revision: Add separate columns for DPI-F dependency, DPI-H component, operational application, and cross-cutting governance or policy requirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2199✎ edit📣 feedback | received | Editorial agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Table headings anchor: medium |
Terms such as goal, sub-goal, outcome, capability, service, component, and application are used densely. The mapping is…Terms such as goal, sub-goal, outcome, capability, service, component, and application are used densely. The mapping is difficult to interpret without referring repeatedly to Chapter 3. Suggested revision: Add a concise legend defining each architectural level and provide one worked example showing how to read a complete row from goal through outcome, capability, service, and component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2200✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
The mapping does not indicate whether a relationship is mandatory, recommended, optional, conditional, or illustrative.The mapping does not indicate whether a relationship is mandatory, recommended, optional, conditional, or illustrative. Suggested revision: Add a relationship-status field or visual convention identifying core dependency, supporting dependency, optional enhancement, and context-specific dependency. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2201✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
The mapping does not identify prerequisites or sequence. Countries may attempt to implement a high-level component with…The mapping does not identify prerequisites or sequence. Countries may attempt to implement a high-level component without the necessary identity, terminology, information-model, governance, or trust capabilities. Suggested revision: Add prerequisite and maturity indicators, or provide a companion dependency matrix showing which capabilities must exist before others can be implemented safely. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2202✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
The mapping is presented as nationally applicable but does not show how decentralised, federated, regional, offline, or…The mapping is presented as nationally applicable but does not show how decentralised, federated, regional, offline, or low-resource arrangements may realise the same capabilities differently. Suggested revision: Add a note that the mapping is logical and topology-neutral. Include examples of centralised, federated, shared regional, and transitional implementations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2203✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
Component recurrence across goals demonstrates reuse potential, but the appendix may encourage readers to interpret rec…Component recurrence across goals demonstrates reuse potential, but the appendix may encourage readers to interpret recurrence as sufficient justification for national shared infrastructure. Suggested revision: State that recurrence is one criterion and must be considered alongside public value, governance feasibility, cost, data sensitivity, lifecycle stability, standards maturity, and risk of unjustified centralisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2204✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
The mapping does not explicitly include accountable stakeholders, information objects, risks, assumptions, indicators, …The mapping does not explicitly include accountable stakeholders, information objects, risks, assumptions, indicators, or enabling laws. Suggested revision: Provide linked mappings or additional fields for accountable authority, affected stakeholders, principal data objects, legal and governance dependencies, risks, and outcome indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2205✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
The appendix may be too dense for policy and financing audiences while still lacking the implementation detail technica…The appendix may be too dense for policy and financing audiences while still lacking the implementation detail technical teams need. Suggested revision: Provide two views: a concise policy and investment matrix, and a detailed machine-readable architecture mapping for technical teams. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2206✎ edit📣 feedback | received | Editorial agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
The large tables are likely to be difficult to read in portrait PDF format and may require extensive horizontal scannin…The large tables are likely to be difficult to read in portrait PDF format and may require extensive horizontal scanning. Suggested revision: Use landscape orientation, repeated row and column headers, clear grouping, adequate font size, and visual separation by goal. Publish an accessible spreadsheet and machine-readable version. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2207✎ edit📣 feedback | received | Editorial agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
Complex merged cells, colour coding, and wide tables may not be accessible to screen-reader users or readers with visua…Complex merged cells, colour coding, and wide tables may not be accessible to screen-reader users or readers with visual impairments. Suggested revision: Provide tagged tables, descriptive headings, text alternatives, sufficient colour contrast, and a linear text version with no reliance on colour alone. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2208✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
Components and capabilities should use stable identifiers if the mapping is expected to support automated architecture …Components and capabilities should use stable identifiers if the mapping is expected to support automated architecture comparison and coverage assessment. Suggested revision: Add persistent architecture-element identifiers corresponding to the machine-readable ArchiMate model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-220 discuss | in the document all mentions on GitHub record | ||
| PC-2209✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
The appendix does not identify whether a country can satisfy a mapped capability through an existing system whose local…The appendix does not identify whether a country can satisfy a mapped capability through an existing system whose local name and boundary differ from the reference component. Suggested revision: Add a country-mapping column or template allowing each reference element to be classified as adopted, adapted, mapped, combined, deferred, replaced, or not applicable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-221 discuss | in the document all mentions on GitHub record | ||
| PC-2210✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
Relationships may imply that one component directly delivers a health outcome, although outcomes depend on adoption, se…Relationships may imply that one component directly delivers a health outcome, although outcomes depend on adoption, service delivery, workforce, policy, and operational applications. Suggested revision: Introduce an explicit distinction between infrastructure contribution and outcome achievement. Do not draw a direct causal relationship from a component to a health outcome without intermediate services, adoption, and enabling conditions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-218 discuss | in the document all mentions on GitHub record | ||
| PC-2211✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
The mapping does not show which programmes, schemes, or ministries benefit from each shared component and could therefo…The mapping does not show which programmes, schemes, or ministries benefit from each shared component and could therefore contribute to financing. Suggested revision: Add a beneficiary and funding-dependency view showing cross-programme reuse and potential cost-sharing relationships. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-221 discuss | in the document all mentions on GitHub record | ||
| PC-2212✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
Equity and inclusion are treated mainly as principles rather than mapped capabilities, requirements, or measurable outc…Equity and inclusion are treated mainly as principles rather than mapped capabilities, requirements, or measurable outcomes. Suggested revision: Add equity-related capabilities and indicators to each goal, including accessibility, assisted access, inclusion of people without identity, geographic reach, affordability, and burden on frontline workers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-222 discuss | in the document all mentions on GitHub record | ||
| PC-2213✎ edit📣 feedback | received | Core architects Metadata registries agent, low |
E Appendix E: Health Goals to DPI Mapping §Appendix E introduction p.236 l.Entire mapping anchor: medium |
Interoperability and semantic governance may appear as general cross-cutting enablers but are not visibly connected to …Interoperability and semantic governance may appear as general cross-cutting enablers but are not visibly connected to every capability that depends on them. Suggested revision: Add explicit traceability from each relevant service and component to required terminology, information models, profiles, mappings, trust, and conformance artefacts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2214✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.“Build Trusted Data Foundations” mapping anchor: medium |
The goal is mapped strongly to registries, the LHR, Terminology Service, LIMR, and interoperability, but trust also dep…The goal is mapped strongly to registries, the LHR, Terminology Service, LIMR, and interoperability, but trust also depends on governance, security, privacy, legal authority, service management, data quality, and institutional accountability. Suggested revision: Add these as explicit enabling capabilities rather than leaving them as background principles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2215✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Goal outcome rows anchor: medium |
“Capture once, use many times” can be interpreted as requiring every data item to be captured only once. Health informa…“Capture once, use many times” can be interpreted as requiring every data item to be captured only once. Health information may need confirmation, correction, updating, reconciliation, or repeated measurement. Suggested revision: Clarify that authoritative data should be captured at the appropriate source and reused where fit for purpose, while allowing legitimate recapture, verification, and updated observations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-225 discuss | in the document all mentions on GitHub record | ||
| PC-2216✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Registry capability rows anchor: medium |
The mapping appears to treat the Client, Facility, Workforce, and Product Registries as a complete set of authoritative…The mapping appears to treat the Client, Facility, Workforce, and Product Registries as a complete set of authoritative reference domains. Organisation identity and geospatial reference data remain significant dependencies. Suggested revision: Add organisation identity and authoritative geography as explicit external or foundational dependencies, or justify how they are covered through existing components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2217✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Registry and LHR rows anchor: medium |
The LHR may be presented as equivalent to the core authoritative registries, although it manages clinical information g…The LHR may be presented as equivalent to the core authoritative registries, although it manages clinical information generated by care workflows rather than stable entity master data. Suggested revision: Distinguish authoritative entity reference capabilities from longitudinal clinical-information access within the foundational shared data layer. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2218✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Data-quality capability rows anchor: medium |
Data quality may be treated as an intrinsic property of the registries rather than a managed lifecycle involving source…Data quality may be treated as an intrinsic property of the registries rather than a managed lifecycle involving source systems, validation, stewardship, monitoring, remediation, and feedback. Suggested revision: Add explicit data-quality management capabilities and assign responsibilities across data contributors, stewards, component owners, and consumers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-225 discuss | in the document all mentions on GitHub record | ||
| PC-2219✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Identity capability rows anchor: medium |
The mapping should distinguish foundational legal identity, health person identification, authentication, professional …The mapping should distinguish foundational legal identity, health person identification, authentication, professional credentials, authorisation, and record linkage. Suggested revision: Split the identity mapping into separate capabilities and show which are provided by DPI-F, the Client Registry, the Workforce Registry, trust infrastructure, and consuming applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2220✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Interoperability capability rows anchor: medium |
Interoperability should not be represented merely as data exchange between components. It also depends on service disco…Interoperability should not be represented merely as data exchange between components. It also depends on service discovery, endpoint registration, trust, versioning, provenance, workflow, and error handling. Suggested revision: Expand the mapping or link to a decomposed interoperability-capability model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2221✎ edit📣 feedback | received | Metadata registries agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Semantic capability rows anchor: medium |
The Terminology Service and LIMR are mapped as the main semantic components, but implementation guides, profiles, mappi…The Terminology Service and LIMR are mapped as the main semantic components, but implementation guides, profiles, mappings, data dictionaries, and validation artefacts are not visible. Suggested revision: Add the governed semantic artefacts and SGI capabilities required to connect terminology and logical models to implementation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2222✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Consent and governance rows anchor: medium |
Consent may be mapped as the primary mechanism for trusted reuse. Lawful processing also depends on purpose, legal basi…Consent may be mapped as the primary mechanism for trusted reuse. Lawful processing also depends on purpose, legal basis, authorisation, transparency, access rights, and accountability. Suggested revision: Replace the single consent capability with a broader data-use governance and policy-enforcement capability, retaining consent or preference as one mechanism. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2223✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Outcome and indicator rows anchor: medium |
The goal needs measurable outcomes beyond whether components exist.The goal needs measurable outcomes beyond whether components exist. Suggested revision: Add indicators for authoritative coverage, duplicate rate, completeness, timeliness, data-quality resolution, cross-programme reuse, API availability, conformance, system adoption, and user trust. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2224✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Foundational DPI dependency rows anchor: medium |
Identity, data exchange, and payments may be the only DPI-F dependencies shown, although trusted data foundations may a…Identity, data exchange, and payments may be the only DPI-F dependencies shown, although trusted data foundations may also depend on civil registration, geospatial services, trust services, organisational identity, and digital signatures. Suggested revision: Make the foundational dependency list configurable and explicitly non-exhaustive. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2225✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Component contribution rows anchor: medium |
The mapping may imply that all foundational components must be implemented before value can be produced.The mapping may imply that all foundational components must be implemented before value can be produced. Suggested revision: Add a progressive pathway showing how selected registries, governed datasets, and standards can support priority use cases before the full target foundation exists. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2226✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 p.236 l.Capability-to-component relationships anchor: medium |
The mapping does not define what evidence demonstrates that a component genuinely realises the trusted-data capability.The mapping does not define what evidence demonstrates that a component genuinely realises the trusted-data capability. Suggested revision: Link each relationship to minimum requirements, conformance tests, coverage, data-quality thresholds, governance evidence, and operational service levels. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2227✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.Workforce-goal mapping anchor: medium |
The mapping correctly identifies the Workforce and Facility Registries but may overstate what these registries can deli…The mapping correctly identifies the Workforce and Facility Registries but may overstate what these registries can deliver without HRIS, payroll, deployment, training, supervision, scheduling, and workforce-planning applications. Suggested revision: Distinguish shared reference capabilities from operational workforce-management systems required to realise the goal. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2228✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.“Proven Skills” rows anchor: medium |
Verified registration and qualifications do not prove current competence, task-specific authorisation, facility privile…Verified registration and qualifications do not prove current competence, task-specific authorisation, facility privileges, or fitness to practise. Suggested revision: Map additional operational and governance capabilities for professional regulation, supervision, credential verification, privileging, competence assessment, and disciplinary status. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2229✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.“Right Place” rows anchor: medium |
Workforce location and facility affiliation do not alone establish whether staffing is adequate. Population need, servi…Workforce location and facility affiliation do not alone establish whether staffing is adequate. Population need, service demand, full-time equivalent, workload, infrastructure, and scope of practice are also required. Suggested revision: Add planning and analytical capabilities using population, catchment, workload, service, facility, and workforce data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2230✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.“Timely Pay” rows anchor: medium |
Payment DPI may be mapped directly to timely workforce pay, but payment rails do not determine employment validity, pay…Payment DPI may be mapped directly to timely workforce pay, but payment rails do not determine employment validity, payroll amount, attendance, deductions, or budget availability. Suggested revision: Add payroll, HR, contract, public-financial-management, attendance, and authorisation systems as operational dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2231✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.“Continuous Growth” rows anchor: medium |
The Workforce Registry may be mapped to CPD and continuous learning, but detailed learning activities and competency de…The Workforce Registry may be mapped to CPD and continuous learning, but detailed learning activities and competency development belong mainly to LMS, education, accreditation, and professional-development systems. Suggested revision: Limit the registry to authoritative qualification or compliance references and map learning management as an operational capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2232✎ edit📣 feedback | received | Metadata registries agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.Workforce classification rows anchor: medium |
International classifications alone may not represent national roles, multiskilled workers, community health work, task…International classifications alone may not represent national roles, multiskilled workers, community health work, task sharing, and scope of practice. Suggested revision: Map national role and occupation models to international classifications and govern role, specialty, credential, and scope terminology separately. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2233✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.Workforce distribution rows anchor: medium |
“Right place” should not be evaluated only through facility staffing. Community, mobile, outreach, telehealth, informal…“Right place” should not be evaluated only through facility staffing. Community, mobile, outreach, telehealth, informal, and remote service models may be central in underserved settings. Suggested revision: Add non-facility deployment and service-delivery models and require geographic and population equity indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-222 discuss | in the document all mentions on GitHub record | ||
| PC-2234✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.Worker identity rows anchor: medium |
The mapping may assume that every recognised worker has a formal professional licence and foundational identity.The mapping may assume that every recognised worker has a formal professional licence and foundational identity. Suggested revision: Support non-regulated cadres, provisional workers, trainees, volunteers, and alternative national authorisation mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2235✎ edit📣 feedback | received | Core architects WHO agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.Outcome rows anchor: medium |
The goal needs outcome measures that distinguish worker registration from active deployment and effective service avail…The goal needs outcome measures that distinguish worker registration from active deployment and effective service availability. Suggested revision: Add indicators for verified and active workforce, FTE, vacancy, turnover, licence currency, geographic distribution, payroll timeliness, workload, training compliance, and service coverage. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2236✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.Worker data-sharing rows anchor: medium |
Workforce planning and payroll reuse may expose personal addresses, nationality, disciplinary status, pay, and employme…Workforce planning and payroll reuse may expose personal addresses, nationality, disciplinary status, pay, and employment data unnecessarily. Suggested revision: Map purpose-specific datasets, restricted-access capabilities, worker transparency, correction, appeal, and aggregation for planning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2237✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.Facility and workforce relationship anchor: medium |
The mapping should reflect organisation, practitioner-role, facility, service, and location relationships rather than m…The mapping should reflect organisation, practitioner-role, facility, service, and location relationships rather than merely joining a worker identifier to a facility identifier. Suggested revision: Align the capability map to a full care-services discovery model, such as the relevant mCSD entity patterns. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2238✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 2 p.236-237 l.Goal-to-component relationships anchor: medium |
The mapping does not identify which workforce capabilities can be implemented first.The mapping does not identify which workforce capabilities can be implemented first. Suggested revision: Add a sequence beginning with governed workforce identity and professional status, then affiliations and service discovery, followed by analytics, learning integration, payroll validation, and regional exchange. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2239✎ edit📣 feedback | received | Clinical Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Quality-and-continuity mapping anchor: medium |
The mapping prioritises longitudinal records and decision support but may underrepresent referral, transition-of-care, …The mapping prioritises longitudinal records and decision support but may underrepresent referral, transition-of-care, medication reconciliation, care-plan coordination, appointment, and provider-communication capabilities. Suggested revision: Add these operational care-coordination capabilities and distinguish them from shared DPI-H foundations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2240✎ edit📣 feedback | received | Clinical agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Patient-history rows anchor: medium |
The LHR is necessary for longitudinal access but does not itself ensure that clinicians review, understand, or use rele…The LHR is necessary for longitudinal access but does not itself ensure that clinicians review, understand, or use relevant information. Suggested revision: Add workflow integration, information presentation, alerting, user experience, training, and adoption capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2241✎ edit📣 feedback | received | Clinical agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Clinical-guidance rows anchor: medium |
The CDSE may be mapped as the main mechanism for guideline adherence, although protocols can also be implemented throug…The CDSE may be mapped as the main mechanism for guideline adherence, although protocols can also be implemented through forms, order sets, workflows, checklists, training, and supervision. Suggested revision: Map several implementation mechanisms and avoid implying that a shared national decision engine is always required. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2242✎ edit📣 feedback | received | Clinical agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Clinical-guidance rows anchor: medium |
Guideline conformity is not always equivalent to quality. Individual context, comorbidity, contraindications, preferenc…Guideline conformity is not always equivalent to quality. Individual context, comorbidity, contraindications, preferences, resource availability, and professional judgement remain important. Suggested revision: Add person-centred decision-making, override, exception, safety, and shared-decision capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2243✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Information exchange rows anchor: medium |
Correct exchange of clinical data requires more than transport and common structure. Provenance, timing, uncertainty, u…Correct exchange of clinical data requires more than transport and common structure. Provenance, timing, uncertainty, units, method, author, and clinical status are essential. Suggested revision: Add these semantic and provenance requirements to the capability mapping. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2244✎ edit📣 feedback | received | Clinical agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Referral capability rows anchor: medium |
Referral closure and continuity require acknowledgement, acceptance, scheduling, completion, feedback, escalation, and …Referral closure and continuity require acknowledgement, acceptance, scheduling, completion, feedback, escalation, and unresolved-referral monitoring. Suggested revision: Add closed-loop referral capability and corresponding operational systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2245✎ edit📣 feedback | received | Clinical Supply chain agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Medication capability rows anchor: medium |
Medication continuity requires prescription, dispensing, administration, self-reported use, reconciliation, product ide…Medication continuity requires prescription, dispensing, administration, self-reported use, reconciliation, product identity, allergy, and interaction information. Suggested revision: Add the relevant operational systems, Product Registry, Terminology Service, LHR, and decision-support dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2246✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Facility and workforce discovery rows anchor: medium |
Facility and workforce registries support discovery but do not guarantee service availability, appointment capacity, eq…Facility and workforce registries support discovery but do not guarantee service availability, appointment capacity, equipment, opening hours, or current staffing. Suggested revision: Add dynamic service-availability and scheduling sources as operational dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2247✎ edit📣 feedback | received | Clinical agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Quality outcome rows anchor: medium |
Quality and continuity should not be assessed solely through architecture coverage or record availability.Quality and continuity should not be assessed solely through architecture coverage or record availability. Suggested revision: Add care-process and outcome indicators such as referral completion, duplicate tests, medication discrepancies, follow-up, avoidable readmissions, protocol adherence, patient experience, safety incidents, and equity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2248✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Patient identification rows anchor: medium |
Identity matching errors can fragment care or combine records incorrectly, with disproportionate harm to people with in…Identity matching errors can fragment care or combine records incorrectly, with disproportionate harm to people with incomplete demographics or varied naming conventions. Suggested revision: Add matching-quality, adjudication, correction, subgroup performance, and safe provisional-identity capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2249✎ edit📣 feedback | received | Clinical Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Cross-border or mobility rows anchor: medium |
Continuity may involve patients moving across regions, providers, public and private sectors, or national borders.Continuity may involve patients moving across regions, providers, public and private sectors, or national borders. Suggested revision: Add portability, patient summary, trust, language, terminology translation, and cross-jurisdiction policy capabilities where relevant. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2250✎ edit📣 feedback | received | Clinical Core architects agent, low |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Consent and access rows anchor: medium |
Overly restrictive access can fragment care, while overly broad access can violate privacy.Overly restrictive access can fragment care, while overly broad access can violate privacy. Suggested revision: Map proportionate purpose-based access, emergency access, sensitive-data handling, patient preference, and audit-transparency capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2251✎ edit📣 feedback | received | Clinical Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 3 p.237 l.Goal-to-component relationships anchor: medium |
The mapping does not define end-to-end tests demonstrating continuity across several systems and organisations.The mapping does not define end-to-end tests demonstrating continuity across several systems and organisations. Suggested revision: Link the goal to scenario-based tests covering referral, discharge, medication reconciliation, emergency summary access, laboratory-result follow-up, and record correction. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2252✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Personal-health-record mapping anchor: medium |
The rights-based statement is compelling but may exceed the legal position in some jurisdictions or blur access rights …The rights-based statement is compelling but may exceed the legal position in some jurisdictions or blur access rights with ownership of the underlying clinical record. Suggested revision: Use: “Every person should be able to access and exercise meaningful control over their health information, subject to applicable law.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2253✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Access capability rows anchor: medium |
The mapping may imply that a digital wallet is the preferred or necessary access mechanism.The mapping may imply that a digital wallet is the preferred or necessary access mechanism. Suggested revision: Map wallets, portals, provider applications, printed summaries, verifiable documents, APIs, and assisted access as alternative channels. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2254✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Identity and authentication rows anchor: medium |
Person identity resolution, user authentication, credential issuance, device security, and record access authorisation …Person identity resolution, user authentication, credential issuance, device security, and record access authorisation may be combined. Suggested revision: Separate the capabilities and identify which rely on foundational identity, Client Registry, trust services, or health-sector access management. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2255✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Patient-control rows anchor: medium |
Meaningful control involves more than consent. It includes access, correction, transparency, restriction, representatio…Meaningful control involves more than consent. It includes access, correction, transparency, restriction, representation, objection, and redress. Suggested revision: Expand the mapped capabilities and recognise legal limitations and statutory uses. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2256✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Data-access rows anchor: medium |
Digital-only access excludes people without devices, connectivity, literacy, recognised identity, or safe private acces…Digital-only access excludes people without devices, connectivity, literacy, recognised identity, or safe private access. Suggested revision: Add assisted, proxy, community, offline, low-bandwidth, accessible, multilingual, and non-digital access capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2257✎ edit📣 feedback | received | Clinical Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Proxy access rows anchor: medium |
The mapping should cover guardians, caregivers, authorised representatives, minors, people lacking capacity, and access…The mapping should cover guardians, caregivers, authorised representatives, minors, people lacking capacity, and access after death. Suggested revision: Add delegated and representative access with relationship verification, validity, scope, revocation, age transition, and audit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2258✎ edit📣 feedback | received | Clinical Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Correction capability rows anchor: medium |
Individuals need mechanisms to request correction or annotation, but clinical opinions and historical documentation can…Individuals need mechanisms to request correction or annotation, but clinical opinions and historical documentation cannot always be overwritten. Suggested revision: Distinguish factual correction, clinical amendment, patient annotation, challenge, retraction, restriction, and appeal. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2259✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Access-history rows anchor: medium |
Trust requires understandable information about who accessed data, for what purpose, and what action occurred.Trust requires understandable information about who accessed data, for what purpose, and what action occurred. Suggested revision: Add patient-facing audit transparency, support for challenge, and justified security or legal exceptions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2260✎ edit📣 feedback | received | Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Record completeness rows anchor: medium |
A person may mistake an incomplete personal record for a complete history.A person may mistake an incomplete personal record for a complete history. Suggested revision: Require visible coverage, source, freshness, unavailable-source, and validation indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2261✎ edit📣 feedback | received | Clinical Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Download and portability rows anchor: medium |
Downloadable access without structured, standardised, and provenance-preserving formats may not support meaningful port…Downloadable access without structured, standardised, and provenance-preserving formats may not support meaningful portability. Suggested revision: Add human-readable and machine-readable export, standard documents, relevant structured data, provenance, signatures where appropriate, and correction history. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2262✎ edit📣 feedback | received | Clinical Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Sensitive-data rows anchor: medium |
Personal access and sharing may create risks involving domestic abuse, coercion, shared devices, adolescent privacy, or…Personal access and sharing may create risks involving domestic abuse, coercion, shared devices, adolescent privacy, or sensitive diagnoses. Suggested revision: Add safe-display, hidden-notification, session, representative-access, segmentation, and safeguarding capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2263✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Outcome rows anchor: medium |
Account creation or record availability does not demonstrate meaningful access or control.Account creation or record availability does not demonstrate meaningful access or control. Suggested revision: Add active use, successful access, accessibility, correction resolution, record comprehension, proxy-access use, trust, and user-reported value indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2264✎ edit📣 feedback | received | Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.LHR relationship anchor: medium |
The personal health record may be treated as synonymous with the LHR. A personal record or wallet may contain selected …The personal health record may be treated as synonymous with the LHR. A personal record or wallet may contain selected copies, summaries, or user-contributed information. Suggested revision: Distinguish the shared longitudinal capability from a patient-facing personal record or access channel. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-043 discuss | in the document all mentions on GitHub record | ||
| PC-2265✎ edit📣 feedback | received | Core architects Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 4 p.237-238 l.Goal-to-component relationships anchor: medium |
The mapping needs person-centred end-to-end tests, not only API conformance.The mapping needs person-centred end-to-end tests, not only API conformance. Suggested revision: Add tests for registration, authentication, access, proxy access, correction, audit history, emergency access, revocation, portability, accessibility, and low-connectivity use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2266✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Supply-chain mapping anchor: medium |
The mapping appropriately identifies product, facility, and supplier reference data but may underrepresent procurement,…The mapping appropriately identifies product, facility, and supplier reference data but may underrepresent procurement, inventory, warehousing, transport, ordering, dispensing, forecasting, and regulatory systems. Suggested revision: Distinguish shared reference components from operational supply-chain applications required to realise the goal. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2267✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Product identity rows anchor: medium |
One Product Registry cannot treat medicines, vaccines, devices, diagnostics, and general commodities as identical produ…One Product Registry cannot treat medicines, vaccines, devices, diagnostics, and general commodities as identical product types. Suggested revision: Map a common product-identity capability plus domain-specific regulatory, clinical, packaging, and logistics models. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2268✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Supplier capability rows anchor: medium |
Supplier identity may already be provided by business, tax, customs, procurement, or legal-entity registries.Supplier identity may already be provided by business, tax, customs, procurement, or legal-entity registries. Suggested revision: Map cross-sector supplier identity separately from health-specific qualification, authorisation, and product-supply relationships. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2269✎ edit📣 feedback | received | Supply chain Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Facility capability rows anchor: medium |
A Facility Registry does not necessarily identify warehouses, distribution centres, ports, laboratories, manufacturers,…A Facility Registry does not necessarily identify warehouses, distribution centres, ports, laboratories, manufacturers, or other supply-chain locations unless explicitly scoped. Suggested revision: Add logistics-location and organisation capabilities or clarify their treatment within the Facility Registry and foundational sources. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2270✎ edit📣 feedback | received | Metadata registries Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Product-classification rows anchor: medium |
Different code systems serve product identity, therapeutic classification, procurement classification, and trade-item i…Different code systems serve product identity, therapeutic classification, procurement classification, and trade-item identification. Suggested revision: Distinguish identifier and classification purposes and require governed mappings rather than treating them as equivalents. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2271✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Forecasting rows anchor: medium |
Advanced forecasting depends on reliable historical consumption, stock, demand, delivery, facility, population, and pro…Advanced forecasting depends on reliable historical consumption, stock, demand, delivery, facility, population, and programme data, which may not be available. Suggested revision: Add data-readiness requirements and support simpler rules-based approaches where data quality is insufficient. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2272✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Traceability rows anchor: medium |
Batch, lot, serial, shipment, custody, and dispensing events belong to operational traceability systems, not necessaril…Batch, lot, serial, shipment, custody, and dispensing events belong to operational traceability systems, not necessarily the Product Registry. Suggested revision: Map traceability applications separately while showing their dependency on authoritative product, supplier, facility, and organisation identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2273✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Safety and recall rows anchor: medium |
Effective recall requires event notification, product and package identity, batch or serial data, distribution location…Effective recall requires event notification, product and package identity, batch or serial data, distribution location, response acknowledgement, and closure. Suggested revision: Add end-to-end recall and safety-event capabilities and tests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2274✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Availability outcome rows anchor: medium |
Stock availability is affected by financing, procurement lead times, supplier performance, transport, demand changes, s…Stock availability is affected by financing, procurement lead times, supplier performance, transport, demand changes, storage, workforce, and policy. Suggested revision: Add these dependencies and avoid implying that shared master data alone delivers availability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2275✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Equity rows anchor: medium |
National availability can mask rural, regional, facility-level, or population-specific shortages.National availability can mask rural, regional, facility-level, or population-specific shortages. Suggested revision: Add geographic and service-level equity indicators for availability, stock-outs, lead times, wastage, and cold-chain performance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-222 discuss | in the document all mentions on GitHub record | ||
| PC-2276✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Public transparency rows anchor: medium |
Public product and supplier information is valuable, but detailed inventory, security-sensitive location, pricing, and …Public product and supplier information is valuable, but detailed inventory, security-sensitive location, pricing, and contract information may require restricted access. Suggested revision: Define public, operational, regulatory, and commercially restricted views. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-226 discuss | in the document all mentions on GitHub record | ||
| PC-2277✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Goal outcome rows anchor: medium |
The mapping needs measurable outcomes beyond deployment of the Product and Supplier Registries.The mapping needs measurable outcomes beyond deployment of the Product and Supplier Registries. Suggested revision: Add stock-out rate, expiry and wastage, forecast accuracy, fulfilment time, traceability coverage, product authenticity, recall completion, procurement lead time, and regional equity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2278✎ edit📣 feedback | received | Supply chain Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 5 p.238-239 l.Goal-to-component relationships anchor: medium |
The goal needs end-to-end scenarios rather than isolated registry tests.The goal needs end-to-end scenarios rather than isolated registry tests. Suggested revision: Add tests for product onboarding, package mapping, procurement item matching, shipment receipt, stock event, adverse-product alert, recall, supplier suspension, and offline facility synchronisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2279✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Health-financing mapping anchor: medium |
The mapping identifies the Benefits Package, Client, Facility, Workforce, Product, and Terminology components but may u…The mapping identifies the Benefits Package, Client, Facility, Workforce, Product, and Terminology components but may underrepresent beneficiary enrolment, contracts, tariffs, claims, prior authorisation, adjudication, payment, and public financial management. Suggested revision: Add these operational financing capabilities and distinguish them clearly from shared DPI-H reference components. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2280✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Eligibility rows anchor: medium |
The Benefits Package Registry may appear responsible for person-specific eligibility.The Benefits Package Registry may appear responsible for person-specific eligibility. Suggested revision: Limit it to authoritative coverage definitions and map individual eligibility to beneficiary, enrolment, scheme-administration, or operational rules services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2281✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Beneficiary identity rows anchor: medium |
The Client Registry resolves person identity but should not store scheme membership, premium status, exemption, househo…The Client Registry resolves person identity but should not store scheme membership, premium status, exemption, household contribution, or benefit utilisation. Suggested revision: Add beneficiary and enrolment systems as operational dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2282✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Provider eligibility rows anchor: medium |
Facility and Workforce Registries support identity and professional status but do not establish contracting, empanelmen…Facility and Workforce Registries support identity and professional status but do not establish contracting, empanelment, service authorisation, or payment eligibility. Suggested revision: Add provider-contracting and empanelment capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2283✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Pricing and reimbursement rows anchor: medium |
Product and Terminology Services are insufficient to support accurate pricing and reimbursement.Product and Terminology Services are insufficient to support accurate pricing and reimbursement. Suggested revision: Add tariffs, contracts, fee schedules, clinical coding rules, benefit rules, payment methods, claims logic, and adjudication systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2284✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Payment rows anchor: medium |
Payment DPI moves money but does not determine whether the payment is correct, lawful, or appropriately authorised.Payment DPI moves money but does not determine whether the payment is correct, lawful, or appropriately authorised. Suggested revision: Separate payment initiation and settlement from benefit, claim, contract, provider, and financial-control decisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2285✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Fraud and integrity rows anchor: medium |
Registry linkage can support integrity controls, but it does not by itself prevent fraud, corruption, false claims, col…Registry linkage can support integrity controls, but it does not by itself prevent fraud, corruption, false claims, collusion, or leakage. Suggested revision: Use measured language and map audit, anomaly detection, investigation, sanctions, appeal, internal control, and independent oversight. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2286✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Equity rows anchor: medium |
Financial efficiency should not be pursued at the expense of access, timely payment, administrative burden, appeal righ…Financial efficiency should not be pursued at the expense of access, timely payment, administrative burden, appeal rights, or protection from catastrophic expenditure. Suggested revision: Add equity, access, financial-protection, provider-burden, denial, delay, and appeal indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-222 discuss | in the document all mentions on GitHub record | ||
| PC-2287✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Benefits transparency rows anchor: medium |
Machine-readable benefits are not meaningful to patients unless accompanied by plain-language, multilingual, accessible…Machine-readable benefits are not meaningful to patients unless accompanied by plain-language, multilingual, accessible explanations and support. Suggested revision: Add communication and assisted-access capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2288✎ edit📣 feedback | received | Financial systems Clinical agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Claims-data rows anchor: medium |
Financing systems should not receive unrestricted clinical records when a limited coded or administrative dataset is su…Financing systems should not receive unrestricted clinical records when a limited coded or administrative dataset is sufficient. Suggested revision: Map purpose-specific minimum datasets, access controls, legal basis, audit, and separation from the full LHR. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2289✎ edit📣 feedback | received | Financial systems Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Health-worker payment rows anchor: medium |
Timely worker and provider payment depends on public-financial-management, payroll, banking, contract, attendance, budg…Timely worker and provider payment depends on public-financial-management, payroll, banking, contract, attendance, budget, and reconciliation systems beyond DPI-H. Suggested revision: Add the operational and foundational dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-188 #18 | in the document all mentions on GitHub record | ||
| PC-2290✎ edit📣 feedback | received | Financial systems agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Outcome rows anchor: medium |
The outcome mapping should distinguish administrative efficiency from health-financing performance and financial protec…The outcome mapping should distinguish administrative efficiency from health-financing performance and financial protection. Suggested revision: Add processing time, administrative cost, payment delay, rejection, appeal, fraud recovery, coverage, out-of-pocket burden, equity, provider participation, and service access. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2291✎ edit📣 feedback | received | Financial systems Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 6 p.239 l.Goal-to-component relationships anchor: medium |
Financing requires end-to-end scenario testing across identity, benefit, provider, product, claim, and payment services.Financing requires end-to-end scenario testing across identity, benefit, provider, product, claim, and payment services. Suggested revision: Add scenarios for eligibility, prior authorisation, claim submission, adjudication, rejection, correction, appeal, payment, reconciliation, and retrospective audit. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2292✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Resilience mapping anchor: medium |
The mapping may focus heavily on the Public Health Surveillance Platform, although resilience also depends on workforce…The mapping may focus heavily on the Public Health Surveillance Platform, although resilience also depends on workforce, facilities, supply chain, laboratories, emergency management, communication, financing, logistics, and continuity of essential services. Suggested revision: Add these capabilities and distinguish surveillance from preparedness, response, recovery, and continuity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2293✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Surveillance rows anchor: medium |
A single Public Health Surveillance Platform is too broad to represent case reporting, event-based surveillance, labora…A single Public Health Surveillance Platform is too broad to represent case reporting, event-based surveillance, laboratory surveillance, genomic surveillance, analytics, contact management, alerts, and response coordination. Suggested revision: Decompose the mapped surveillance capabilities and identify which are shared reference services and which remain operational or hazard-specific applications. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2294✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Indicator-based and case-based surveillance rows anchor: medium |
Aggregate and case-level surveillance require different data models, privacy controls, workflows, timeliness, and confo…Aggregate and case-level surveillance require different data models, privacy controls, workflows, timeliness, and conformance. Suggested revision: Map them separately and identify common terminology and reference-data dependencies. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2295✎ edit📣 feedback | received | Core architects Clinical Metadata registries agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Laboratory surveillance rows anchor: medium |
Laboratory systems and networks are not explicitly represented in the component catalogue, despite being central to epi…Laboratory systems and networks are not explicitly represented in the component catalogue, despite being central to epidemic detection and response. Suggested revision: Add laboratory-information and result-exchange systems as operational dependencies and identify relevant shared terminology, specimen, facility, and workforce references. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2296✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Climate and environmental rows anchor: medium |
Climate, environmental, vector, animal-health, meteorological, and geospatial data use standards and authorities beyond…Climate, environmental, vector, animal-health, meteorological, and geospatial data use standards and authorities beyond the health sector. Suggested revision: Add cross-sector data sources, governance, terminology, geospatial models, provenance, uncertainty, and One Health coordination. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2297✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Foundational DPI rows anchor: medium |
Emergency communication, geospatial infrastructure, digital credentials, identity, data exchange, and payments may all …Emergency communication, geospatial infrastructure, digital credentials, identity, data exchange, and payments may all contribute to resilience. Suggested revision: Expand the foundational-DPI dependencies and mark them as context specific. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2298✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Identity rows anchor: medium |
National identity linkage should not be mandatory for anonymous, syndromic, environmental, or event-based surveillance.National identity linkage should not be mandatory for anonymous, syndromic, environmental, or event-based surveillance. Suggested revision: Make identity conditional and support anonymous, pseudonymous, case-specific, and aggregate reporting models. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2299✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Emergency data-sharing rows anchor: medium |
Emergency powers can enable excessive surveillance, discrimination, function creep, or prolonged exceptional access.Emergency powers can enable excessive surveillance, discrimination, function creep, or prolonged exceptional access. Suggested revision: Map time-limited authority, proportionality, oversight, purpose limitation, retention, public transparency, decommissioning, and redress. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2300✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Alerting rows anchor: medium |
Detecting and publishing a signal does not ensure operational response.Detecting and publishing a signal does not ensure operational response. Suggested revision: Add triage, verification, decision authority, incident command, resource mobilisation, communication, response tracking, and after-action review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2301✎ edit📣 feedback | received | Supply chain agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Supply-chain resilience rows anchor: medium |
Product and facility reference data supports emergency planning but does not provide inventory, transport, cold chain, …Product and facility reference data supports emergency planning but does not provide inventory, transport, cold chain, surge capacity, or supplier availability. Suggested revision: Add operational logistics, inventory, supplier, procurement, and transport capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2302✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Workforce resilience rows anchor: medium |
Workforce identity alone does not establish emergency availability, competencies, deployment, safety, rostering, accomm…Workforce identity alone does not establish emergency availability, competencies, deployment, safety, rostering, accommodation, or wellbeing. Suggested revision: Add workforce-mobilisation, competence, occupational-health, scheduling, deployment, and support capabilities. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2303✎ edit📣 feedback | received | WHO Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Cross-border rows anchor: medium |
Cross-border surveillance and emergency exchange require legal authority, common definitions, trust, acknowledgement, c…Cross-border surveillance and emergency exchange require legal authority, common definitions, trust, acknowledgement, correction, and coordinated response. Suggested revision: Add IHR and applicable regional-framework dependencies, language and terminology translation, trust, and cross-border incident coordination. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2304✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Outcome rows anchor: medium |
Resilience cannot be measured only through reporting speed or platform availability.Resilience cannot be measured only through reporting speed or platform availability. Suggested revision: Add time to detection, verification, notification, response, containment, service recovery, continuity of essential care, supply availability, workforce readiness, and equity of impact. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2305✎ edit📣 feedback | received | Core architects WHO agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Applicability rows anchor: medium |
Advanced genomic, AI, climate, and predictive surveillance may be inappropriate where foundational reporting, laborator…Advanced genomic, AI, climate, and predictive surveillance may be inappropriate where foundational reporting, laboratory, or response capabilities remain weak. Suggested revision: Add maturity dependencies and prioritise core reporting, laboratory linkage, governance, communication, and response before advanced analytics. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2306✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 7 p.239-240 l.Goal-to-component relationships anchor: medium |
The mapping needs multi-system emergency scenarios rather than isolated platform tests.The mapping needs multi-system emergency scenarios rather than isolated platform tests. Suggested revision: Add exercises covering case detection, laboratory confirmation, alert escalation, cross-border notification, facility-capacity assessment, workforce mobilisation, supply allocation, public communication, and recovery. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2307✎ edit📣 feedback | received | Editorial agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The same capability or component may appear under different names or at different abstraction levels across the seven g…The same capability or component may appear under different names or at different abstraction levels across the seven goals. Suggested revision: Use the canonical architecture-element names and persistent identifiers from the formal model throughout the appendix. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-220 discuss | in the document all mentions on GitHub record | ||
| PC-2308✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Similar relationships may be represented inconsistently. For example, a registry may be shown as directly enabling an o…Similar relationships may be represented inconsistently. For example, a registry may be shown as directly enabling an outcome in one goal and as supporting a capability in another. Suggested revision: Apply a consistent relationship pattern from goal to outcome, capability, service, component, and data object. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2309✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The two-layer DPI-H model is not consistently visible across the goal mappings.The two-layer DPI-H model is not consistently visible across the goal mappings. Suggested revision: Group or label mapped components by the foundational shared data layer and business-services layer. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2310✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The recurrence of Client, Facility, Workforce, and Product Registries is clear, but organisation identity remains a rep…The recurrence of Client, Facility, Workforce, and Product Registries is clear, but organisation identity remains a repeated unmapped dependency. Suggested revision: Add or explicitly source an authoritative organisation capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2311✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Interoperability appears as a single cross-cutting capability, but technical teams need its underlying services and res…Interoperability appears as a single cross-cutting capability, but technical teams need its underlying services and responsibilities. Suggested revision: Link the appendix to a decomposed interoperability map covering identity, trust, discovery, transport, routing, validation, semantics, mapping, policy, provenance, audit, and monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2312✎ edit📣 feedback | received | Metadata registries agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
SGI is not consistently visible as an enabling capability across all mapped components and goals.SGI is not consistently visible as an enabling capability across all mapped components and goals. Suggested revision: Add SGI relationships to terminology, information models, profiles, decision logic, indicators, product classifications, benefit rules, and surveillance definitions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2313✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Privacy, security, consent, legal basis, access control, audit, and data rights may be grouped as one cross-cutting box…Privacy, security, consent, legal basis, access control, audit, and data rights may be grouped as one cross-cutting box, masking important distinctions. Suggested revision: Decompose these capabilities and map each only where applicable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-224 discuss | in the document all mentions on GitHub record | ||
| PC-2314✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The appendix does not distinguish target-state capabilities from the minimum REDDHI starting foundation.The appendix does not distinguish target-state capabilities from the minimum REDDHI starting foundation. Suggested revision: Mark each capability as minimum baseline, use-case-dependent foundation, progressive enhancement, or advanced target state. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2315✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Reuse across goals is visible but not translated into an investment or cost-sharing view.Reuse across goals is visible but not translated into an investment or cost-sharing view. Suggested revision: Add a cross-goal component-reuse matrix showing which programmes benefit and where shared investment could replace duplicated programme expenditure. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-221 discuss | in the document all mentions on GitHub record | ||
| PC-2316✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Equity is not represented as an outcome and measurable requirement within each goal.Equity is not represented as an outcome and measurable requirement within each goal. Suggested revision: Add equity outcomes, affected populations, access barriers, burden distribution, disaggregation, and safeguards for every goal. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-222 discuss | in the document all mentions on GitHub record | ||
| PC-2317✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The mappings are not connected directly to test plans or conformance profiles.The mappings are not connected directly to test plans or conformance profiles. Suggested revision: Link mapped services and components to normative profiles, test scenarios, expected evidence, and outcome measures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-223 discuss | in the document all mentions on GitHub record | ||
| PC-2318✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The derivation of relationships is not linked to country evidence, standards, literature, or expert validation.The derivation of relationships is not linked to country evidence, standards, literature, or expert validation. Suggested revision: Add evidence references or an evidence register supporting material mapping decisions, while distinguishing architectural judgement from empirical evidence. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-023 discuss | in the document all mentions on GitHub record | ||
| PC-2319✎ edit📣 feedback | received | Editorial agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Some capability names may be action phrases, while others are system nouns or desired outcomes.Some capability names may be action phrases, while others are system nouns or desired outcomes. Suggested revision: Apply a consistent capability-naming convention expressing an ability, independent of organisation or technology. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-220 discuss | in the document all mentions on GitHub record | ||
| PC-2320✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Functional applications are not always represented, potentially creating the impression that shared components deliver …Functional applications are not always represented, potentially creating the impression that shared components deliver outcomes directly. Suggested revision: Include the principal operational application categories needed to consume DPI-H services, while keeping them outside the DPI-H component boundary. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2321✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Dependencies among components are not directly visible. For example, decision support depends on governed data models a…Dependencies among components are not directly visible. For example, decision support depends on governed data models and terminology, while longitudinal records depend on identity and source systems. Suggested revision: Add a component-dependency matrix or directed dependency view. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2322✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
There is no explicit mechanism for documenting that a mapped element is inappropriate or currently unavailable in a cou…There is no explicit mechanism for documenting that a mapped element is inappropriate or currently unavailable in a country. Suggested revision: Add nationally configurable status values: existing, planned, partial, alternative, deferred, not applicable, and gap, with rationale and risk. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-221 discuss | in the document all mentions on GitHub record | ||
| PC-2323✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
A component may appear in the mapping even if only a small part of its specified functionality is required for the goal.A component may appear in the mapping even if only a small part of its specified functionality is required for the goal. Suggested revision: Map goals to specific component services rather than only to the full component. This will support targeted implementation and testing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2324✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Some components may appear under nearly every goal, reducing the mapping’s ability to distinguish critical from support…Some components may appear under nearly every goal, reducing the mapping’s ability to distinguish critical from supporting relationships. Suggested revision: Assign relationship strength or criticality, such as essential, important supporting, optional, or indirect. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-219 discuss | in the document all mentions on GitHub record | ||
| PC-2325✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The appendix would be difficult to maintain consistently if it exists only as static tables in the PDF.The appendix would be difficult to maintain consistently if it exists only as static tables in the PDF. Suggested revision: Generate Appendix E directly from the governed machine-readable architecture model and publish it as HTML, spreadsheet, and machine-readable data. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-220 discuss | in the document all mentions on GitHub record | ||
| PC-2326✎ edit📣 feedback | received | WHO Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The mapping is likely to evolve as components, standards, and evidence mature, but no version or change process is visi…The mapping is likely to evolve as components, standards, and evidence mature, but no version or change process is visible. Suggested revision: Add version, publication date, model release, change history, element status, and responsible maintainer. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-220 discuss | in the document all mentions on GitHub record | ||
| PC-2327✎ edit📣 feedback | received | Core architects agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
Appendix E does not clearly identify gaps where no mature DPI-H component or standard currently exists, particularly fo…Appendix E does not clearly identify gaps where no mature DPI-H component or standard currently exists, particularly for some surveillance, financing, or cross-sector capabilities. Suggested revision: Mark standards and component gaps explicitly and identify interim patterns rather than forcing every capability into an existing component. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-221 discuss | in the document all mentions on GitHub record | ||
| PC-2328✎ edit📣 feedback | received | Core architects agent |
E Appendix E: Health Goals to DPI Mapping §Appendix E overall p.236-240 l.All seven mappings anchor: medium |
The mapping is valuable but currently reads primarily as documentation rather than a working country-planning tool.The mapping is valuable but currently reads primarily as documentation rather than a working country-planning tool. Suggested revision: Publish an editable country workbook that allows teams to select goals, map existing capabilities, assign owners, assess maturity, identify gaps, estimate cost, and build a phased roadmap. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-220 discuss | in the document all mentions on GitHub record | ||
| PC-2329✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Opening text and capability table anchor: medium |
Appendix F provides useful detail on semantic-governance capabilities, but it does not restate clearly that SGI is an i…Appendix F provides useful detail on semantic-governance capabilities, but it does not restate clearly that SGI is an institutional and operational framework supported by tools, rather than a single software platform. Suggested revision: Add a prominent introductory statement: “SGI is a coordinated set of governance, people, processes, artefacts, and supporting technologies. It is not a separate software product or mandatory central platform.” Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2330✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Opening text anchor: medium |
The appendix does not sufficiently explain how ministries, architecture teams, terminology centres, standards bodies, p…The appendix does not sufficiently explain how ministries, architecture teams, terminology centres, standards bodies, programmes, or procurement teams should use the capability catalogue. Suggested revision: Explain that the catalogue supports current-state assessment, target operating-model design, role assignment, procurement, maturity planning, and evaluation of semantic-governance gaps. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2331✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Capability categories anchor: medium |
The five categories provide a helpful lifecycle, but they may be interpreted as a fixed sequential process. Monitoring,…The five categories provide a helpful lifecycle, but they may be interpreted as a fixed sequential process. Monitoring, feedback, dependency analysis, and change management occur continuously across the lifecycle. Suggested revision: State that the categories are interconnected capability domains rather than strictly sequential implementation phases. Add arrows or cross-references showing iterative feedback and change cycles. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2332✎ edit📣 feedback | received | Editorial agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Capability categories anchor: medium |
Terms such as intake, authoring, publication, monitoring, distribution, and consumption may be clear to semantic specia…Terms such as intake, authoring, publication, monitoring, distribution, and consumption may be clear to semantic specialists but less clear to policy, programme, and procurement readers. Suggested revision: Add one plain-language sentence describing the purpose and expected outputs of each category. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2333✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
The scope appears focused primarily on terminology and logical information models. SGI must also govern implementation …The scope appears focused primarily on terminology and logical information models. SGI must also govern implementation guides, profiles, extensions, mappings, identifier systems, data dictionaries, measures, indicators, computable guidelines, and benefit rules. Suggested revision: Add an explicit list of governed semantic artefact types and indicate which capabilities apply to each artefact type. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-2334✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
The appendix does not clearly distinguish SGI capabilities from the responsibilities of the Terminology Service and LIM…The appendix does not clearly distinguish SGI capabilities from the responsibilities of the Terminology Service and LIMR components. Suggested revision: Add a responsibility matrix distinguishing governance capabilities, authoring and repository tools, publication services, runtime terminology services, LIMR services, and consuming systems. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-227 discuss | in the document all mentions on GitHub record | ||
| PC-2335✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
The catalogue describes a mature target state but does not identify the minimum capabilities required before countries …The catalogue describes a mature target state but does not identify the minimum capabilities required before countries begin publishing national terminology, data models, or implementation guides. Suggested revision: Identify a minimum SGI baseline covering accountable ownership, artefact identifiers, versioning, review and approval, provenance, publication status, change history, and communication of updates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2336✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
The target model may assume a national terminology centre, specialist modelling team, workflow platform, repository too…The target model may assume a national terminology centre, specialist modelling team, workflow platform, repository tools, and runtime services that many countries do not yet have. Suggested revision: Add progressive implementation levels and allow regional shared services, adopted international artefacts, lightweight repositories, and manual governance processes at early maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2337✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
The capability descriptions do not consistently identify measurable outputs, evidence, conformance criteria, or indicat…The capability descriptions do not consistently identify measurable outputs, evidence, conformance criteria, or indicators. Suggested revision: Add fields for expected output, accountable owner, evidence of capability, maturity level, performance indicator, and related conformance requirement. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2338✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
Roles and decision rights are not directly assigned to the capabilities.Roles and decision rights are not directly assigned to the capabilities. Suggested revision: Add a RACI-style responsibility model covering standards authority, terminology authority, model authority, clinical review, programme owner, technical steward, publisher, implementer, and governance body. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2339✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
The appendix does not address the recurrent financing and staffing needed to maintain semantic assets after initial pub…The appendix does not address the recurrent financing and staffing needed to maintain semantic assets after initial publication. Suggested revision: Add operating-model requirements covering staffing, specialist capacity, tooling, licences, translation, support, quality assurance, publication, monitoring, and long-term maintenance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2340✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
Accessibility, multilingualism, local clinical concepts, culturally specific terminology, and participation by underrep…Accessibility, multilingualism, local clinical concepts, culturally specific terminology, and participation by underrepresented communities are not sufficiently visible as cross-cutting capabilities. Suggested revision: Add inclusive participation, multilingual authoring, accessibility, local-extension governance, and monitoring for discriminatory or exclusionary semantic representations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2341✎ edit📣 feedback | received | Metadata registries agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
The capability descriptions do not consistently distinguish policy, process, service, technology, and artefact.The capability descriptions do not consistently distinguish policy, process, service, technology, and artefact. Suggested revision: Classify every entry as governance policy, organisational capability, business process, application service, technical service, or governed artefact. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2342✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
Semantic governance must address dependencies among terminologies, information models, implementation guides, decision …Semantic governance must address dependencies among terminologies, information models, implementation guides, decision logic, indicators, and analytical models. Dependency management is not sufficiently prominent in the overall structure. Suggested revision: Add dependency and impact management as an explicit cross-cutting capability or sixth capability category. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2343✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F introduction p.241 l.Entire appendix anchor: medium |
The appendix does not explicitly connect SGI capabilities to the seven health goals or to specific component requiremen…The appendix does not explicitly connect SGI capabilities to the seven health goals or to specific component requirements in Appendix C. Suggested revision: Add traceability from each SGI capability to affected health goals, DPI-H components, semantic artefacts, and Appendix C requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-227 discuss | in the document all mentions on GitHub record | ||
| PC-2344✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Request submission” capability anchor: medium |
Request intake is useful, but the capability does not clearly distinguish requests for new concepts, value sets, data e…Request intake is useful, but the capability does not clearly distinguish requests for new concepts, value sets, data elements, models, profiles, mappings, translations, corrections, and implementation guidance. Suggested revision: Define standard request types and the minimum information required for each, including purpose, requester, urgency, affected systems, evidence, jurisdiction, and desired effective date. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2345✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Request submission” capability anchor: medium |
Requiring use of one digital request portal may exclude local facilities, programmes, or stakeholders without continuou…Requiring use of one digital request portal may exclude local facilities, programmes, or stakeholders without continuous connectivity or specialist knowledge. Suggested revision: Support web forms, email, offline templates, assisted submission, bulk requests, and regional or programme coordinators, while retaining one governed request register. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2346✎ edit📣 feedback | received | Metadata registries agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Request submission” capability anchor: medium |
“Demand” may be interpreted as market demand rather than a request for semantic content or governance action.“Demand” may be interpreted as market demand rather than a request for semantic content or governance action. Suggested revision: Define demand management as the controlled receipt, assessment, prioritisation, and resolution of requests for semantic artefacts or changes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2347✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Request validation” capability anchor: medium |
Validation may focus on whether a request is complete but not whether an existing artefact already addresses the need.Validation may focus on whether a request is complete but not whether an existing artefact already addresses the need. Suggested revision: Require searches for existing international, regional, national, and local artefacts before approving creation of a new concept or model. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2348✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Request validation” capability anchor: medium |
The criteria for determining whether a request is valid, duplicate, out of scope, or insufficiently justified are not d…The criteria for determining whether a request is valid, duplicate, out of scope, or insufficiently justified are not defined. Suggested revision: Publish assessment criteria and decision states such as accepted, clarification required, duplicate, redirected, deferred, rejected, or urgently processed. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2349✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Triage” capability anchor: medium |
Triage should consider more than urgency. A low-volume request may have critical patient-safety, legal, or interoperabi…Triage should consider more than urgency. A low-volume request may have critical patient-safety, legal, or interoperability implications. Suggested revision: Assess clinical risk, patient safety, regulatory obligation, cross-programme impact, dependency centrality, equity, implementation cost, and urgency. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2350✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Prioritisation” capability anchor: medium |
Prioritisation based mainly on number of requesting organisations or system demand may disadvantage rare diseases, mino…Prioritisation based mainly on number of requesting organisations or system demand may disadvantage rare diseases, minority languages, marginalised populations, and low-resource facilities. Suggested revision: Add equity, rights, safety, public-health importance, and unmet-need criteria. Document how underrepresented requests receive appropriate consideration. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2351✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Prioritisation” capability anchor: medium |
No mechanism is described for resolving conflicting programme priorities or requests from multiple authoritative bodies.No mechanism is described for resolving conflicting programme priorities or requests from multiple authoritative bodies. Suggested revision: Define transparent prioritisation, escalation, conflict-resolution, and appeal processes under the strategic semantic-governance body. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2352✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Request tracking” capability anchor: medium |
Tracking a request only until approval is insufficient. Requesters need visibility through authoring, review, publicati…Tracking a request only until approval is insufficient. Requesters need visibility through authoring, review, publication, implementation, and closure. Suggested revision: Track the complete lifecycle, including current owner, status, expected decision date, dependencies, decision, publication version, and implementation guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2353✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Request tracking” capability anchor: medium |
The appendix does not state whether the request register and decisions will be public.The appendix does not state whether the request register and decisions will be public. Suggested revision: Publish non-sensitive requests, decisions, rationales, status, and release plans, with justified exceptions for security, confidentiality, or protected information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2354✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Stakeholder identification” capability anchor: medium |
Stakeholder identification should vary according to artefact type and affected domain.Stakeholder identification should vary according to artefact type and affected domain. Suggested revision: Require stakeholder analysis covering authoritative agencies, clinicians, programmes, implementers, analysts, patients or affected communities, regulators, terminology specialists, and data-protection or safety experts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2355✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Impact assessment” capability anchor: medium |
Impact assessment may occur too late if it begins only after content has been authored.Impact assessment may occur too late if it begins only after content has been authored. Suggested revision: Require preliminary impact analysis during intake and detailed impact analysis before approval and publication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2356✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Impact assessment” capability anchor: medium |
Impact analysis should cover linked artefacts, deployed systems, analytics, decision support, historical data, procurem…Impact analysis should cover linked artefacts, deployed systems, analytics, decision support, historical data, procurement, and training. Suggested revision: Define the minimum dependency domains and require machine-readable dependency records where possible. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2357✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Urgent change” capability anchor: medium |
Emergency semantic changes may bypass ordinary governance but still require accountability, testing, and later review.Emergency semantic changes may bypass ordinary governance but still require accountability, testing, and later review. Suggested revision: Define urgent-change authority, minimum review, temporary status, communication, effective time, rollback, and mandatory retrospective review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-2358✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Intake p.241 l.“Request closure” capability anchor: medium |
A rejected request may materially affect a programme, population, or clinical domain, but appeal and reconsideration ar…A rejected request may materially affect a programme, population, or clinical domain, but appeal and reconsideration are not explicit. Suggested revision: Add decision rationale, appeal, resubmission, escalation, and periodic review of deferred or rejected requests. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-229 discuss | in the document all mentions on GitHub record | ||
| PC-2359✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.241-242 l.“Collaborative authoring” capability anchor: medium |
Collaborative authoring is important, but the appendix does not distinguish content author, domain authority, technical…Collaborative authoring is important, but the appendix does not distinguish content author, domain authority, technical modeller, terminology specialist, reviewer, and publisher. Suggested revision: Define authoring roles and separation of duties according to artefact type. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2360✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.241-242 l.“Collaborative authoring” capability anchor: medium |
Specialist authoring tools may not be available or affordable.Specialist authoring tools may not be available or affordable. Suggested revision: Permit governed authoring through templates, spreadsheets, standard repositories, shared regional tools, and dedicated platforms according to maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2361✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.241-242 l.“Collaborative authoring” capability anchor: medium |
Authoring processes may exclude domain experts who cannot use specialised modelling or terminology software.Authoring processes may exclude domain experts who cannot use specialised modelling or terminology software. Suggested revision: Provide accessible review formats, human-readable representations, training, facilitated workshops, and assisted contribution mechanisms. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2362✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Content modelling” capability anchor: medium |
The capability should distinguish conceptual models, logical models, implementation models, terminology artefacts, valu…The capability should distinguish conceptual models, logical models, implementation models, terminology artefacts, value sets, mappings, and computable rules. Suggested revision: Define authoring methods and validation requirements for each artefact type rather than applying one generic modelling process. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-2363✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Reuse of existing artefacts” capability anchor: medium |
Reuse may be measured by importing or copying external content, which can disconnect the national copy from its source …Reuse may be measured by importing or copying external content, which can disconnect the national copy from its source and update lifecycle. Suggested revision: Prefer governed reference, extension, specialisation, and dependency relationships. Require provenance and upstream update monitoring. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-230 discuss | in the document all mentions on GitHub record | ||
| PC-2364✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“National extension” capability anchor: medium |
National extensions risk creating divergence if namespace, purpose, compatibility, and upstream contribution are not go…National extensions risk creating divergence if namespace, purpose, compatibility, and upstream contribution are not governed. Suggested revision: Require unique namespace, authority, rationale, scope, mapping, lifecycle, compatibility rules, and a process for proposing relevant content upstream. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-230 discuss | in the document all mentions on GitHub record | ||
| PC-2365✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Local extension” capability anchor: medium |
Local variation may be necessary, but unrestricted local extensions can create non-interoperable silos.Local variation may be necessary, but unrestricted local extensions can create non-interoperable silos. Suggested revision: Require registration, ownership, use context, mapping, review, validity, and a process for consolidation or national adoption. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-230 discuss | in the document all mentions on GitHub record | ||
| PC-2366✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Terminology binding” capability anchor: medium |
A terminology binding needs more than a value-set identifier. Binding strength, version, context, extension behaviour, …A terminology binding needs more than a value-set identifier. Binding strength, version, context, extension behaviour, and fallback must be defined. Suggested revision: Require binding strength, allowed code systems, version policy, expansion parameters, jurisdiction, exceptions, and validation behaviour. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-230 discuss | in the document all mentions on GitHub record | ||
| PC-2367✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Mapping” capability anchor: medium |
Mappings may be used for clinical transformation, reporting, analytics, reimbursement, and research, each requiring dif…Mappings may be used for clinical transformation, reporting, analytics, reimbursement, and research, each requiring different precision. Suggested revision: Require intended purpose, equivalence, direction, context, source and target versions, evidence, confidence, limitations, and review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | ||
| PC-2368✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Mapping” capability anchor: medium |
The appendix does not require testing of mapping behaviour against representative data or known edge cases.The appendix does not require testing of mapping behaviour against representative data or known edge cases. Suggested revision: Add mapping test cases, regression testing, unmapped-content reporting, loss analysis, and clinical review where mappings affect care. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-275 discuss | in the document all mentions on GitHub record | ||
| PC-2369✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Multilingual authoring” capability anchor: medium |
Language translation is not merely a technical label-management task. Clinical meaning, register, literacy, and local u…Language translation is not merely a technical label-management task. Clinical meaning, register, literacy, and local usage require governance. Suggested revision: Record language, locale, source text, translator, reviewer, status, date, and context. Require clinical and linguistic validation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2370✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Multilingual authoring” capability anchor: medium |
Not every artefact requires full translation into every national language at the same time.Not every artefact requires full translation into every national language at the same time. Suggested revision: Prioritise translations according to user group, care setting, safety, population need, and implementation scope, while documenting untranslated gaps. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2371✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Automated authoring support” capability anchor: medium |
Automated generation or translation can introduce plausible but incorrect semantic content.Automated generation or translation can introduce plausible but incorrect semantic content. Suggested revision: Treat AI-assisted or automatically generated content as draft. Require provenance, human review, validation, and restrictions for safety-critical artefacts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-247 discuss | in the document all mentions on GitHub record | ||
| PC-2372✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Clinical review” capability anchor: medium |
Clinical review may be treated as one generic approval step, although the required expertise differs by speciality, pro…Clinical review may be treated as one generic approval step, although the required expertise differs by speciality, profession, population, and use case. Suggested revision: Define domain-specific reviewer qualifications, conflicts-of-interest rules, multidisciplinary review, and quorum requirements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2373✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Technical review” capability anchor: medium |
Technical review should cover implementability and validation, not only schema correctness.Technical review should cover implementability and validation, not only schema correctness. Suggested revision: Include formal validation, dependency checks, terminology resolution, performance, security, migration, implementation examples, and conformance-test readiness. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2374✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Policy and legal review” capability anchor: medium |
Semantic artefacts may encode sensitive classifications, protected attributes, benefit restrictions, or surveillance co…Semantic artefacts may encode sensitive classifications, protected attributes, benefit restrictions, or surveillance concepts. Suggested revision: Require privacy, human-rights, legal, ethical, and equity review for artefacts with material individual or population impact. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2375✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Public consultation” capability anchor: medium |
Public consultation may be absent or left as an optional national practice.Public consultation may be absent or left as an optional national practice. Suggested revision: Require proportionate consultation for high-impact national artefacts, with accessible materials, response publication, and explanation of decisions. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2376✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Approval” capability anchor: medium |
Approval authority is not consistently tied to artefact ownership and legal mandate.Approval authority is not consistently tied to artefact ownership and legal mandate. Suggested revision: Define who approves each artefact type and separate clinical, semantic, technical, regulatory, and publication approval where necessary. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2377✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Approval” capability anchor: medium |
A single approval status may not cover draft, trial use, normative, informative, experimental, deprecated, and retired …A single approval status may not cover draft, trial use, normative, informative, experimental, deprecated, and retired content. Suggested revision: Establish controlled publication statuses with permitted uses and transition rules. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2378✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Versioning” capability anchor: medium |
Versioning requirements should distinguish content version, package version, implementation-guide version, model versio…Versioning requirements should distinguish content version, package version, implementation-guide version, model version, and terminology edition. Suggested revision: Define version semantics by artefact type and require immutable historical resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2379✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Versioning” capability anchor: medium |
A new version may be syntactically compatible but semantically breaking.A new version may be syntactically compatible but semantically breaking. Suggested revision: Require explicit compatibility classification, migration impact, predecessor and successor links, and consumer guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2380✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Publication” capability anchor: medium |
Publication through a central web portal or API alone may exclude low-connectivity implementations.Publication through a central web portal or API alone may exclude low-connectivity implementations. Suggested revision: Support APIs, downloadable packages, local mirrors, offline bundles, documents, examples, and accessible browsing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2381✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Publication” capability anchor: medium |
Published artefacts need usage guidance, examples, test data, known limitations, licence, dependencies, and support con…Published artefacts need usage guidance, examples, test data, known limitations, licence, dependencies, and support contact. Suggested revision: Define a minimum publication package rather than publishing the primary artefact alone. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2382✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Release management” capability anchor: medium |
Publication does not ensure that consumers can safely adopt the release.Publication does not ensure that consumers can safely adopt the release. Suggested revision: Require release calendar, change notice, impact analysis, implementation guidance, transition period, test environment, support, and rollback. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2383✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Deprecation and retirement” capability anchor: medium |
Deprecation may be treated as simple status change without consumer migration or preservation of historic interpretatio…Deprecation may be treated as simple status change without consumer migration or preservation of historic interpretation. Suggested revision: Require replacement guidance, support period, consumer notification, migration tests, historical access, and retirement criteria. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2384✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Publication integrity” capability anchor: medium |
Semantic packages and releases can be tampered with or obtained from unauthorised sources.Semantic packages and releases can be tampered with or obtained from unauthorised sources. Suggested revision: Require source authentication, checksums or signatures, trusted publication channels, access logging where appropriate, and consumer verification. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-231 discuss | in the document all mentions on GitHub record | ||
| PC-2385✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Authoring and publication p.242 l.“Licensing and intellectual property” capability anchor: medium |
Licensing conditions can materially affect national access, redistribution, localisation, and long-term reuse but are n…Licensing conditions can materially affect national access, redistribution, localisation, and long-term reuse but are not sufficiently explicit. Suggested revision: Require licence metadata, permitted use, redistribution, translation, derivative works, access conditions, and long-term continuity planning. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-231 discuss | in the document all mentions on GitHub record | ||
| PC-2386✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.242-243 l.“Governance monitoring” capability anchor: medium |
Compliance with governance processes should be monitored separately from semantic-content quality and implementation ad…Compliance with governance processes should be monitored separately from semantic-content quality and implementation adoption. Suggested revision: Divide monitoring into governance-process performance, content quality, implementation conformance, adoption, runtime use, and observed outcomes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2387✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.242-243 l.“Governance monitoring” capability anchor: medium |
No indicators are specified for process performance.No indicators are specified for process performance. Suggested revision: Add request backlog, triage time, review time, approval time, overdue review, publication time, appeal resolution, and emergency-change frequency. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2388✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Content quality” capability anchor: medium |
Quality is multidimensional and cannot be represented by a single approval status.Quality is multidimensional and cannot be represented by a single approval status. Suggested revision: Define correctness, completeness, consistency, uniqueness, clarity, implementability, provenance, currency, accessibility, and fitness for purpose. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2389✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Automated validation” capability anchor: medium |
Automated validation can test formal constraints but cannot establish clinical appropriateness, legal acceptability, or…Automated validation can test formal constraints but cannot establish clinical appropriateness, legal acceptability, or usability. Suggested revision: Distinguish automated structural validation from expert semantic, clinical, policy, safety, and implementation review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2390✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Conformance monitoring” capability anchor: medium |
The appendix does not distinguish conformance of artefacts, implementations, exchanged data, and operational use.The appendix does not distinguish conformance of artefacts, implementations, exchanged data, and operational use. Suggested revision: Define separate conformance domains and specify evidence and responsible authority for each. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-232 discuss | in the document all mentions on GitHub record | ||
| PC-2391✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Implementation adoption” capability anchor: medium |
Download or API-access counts do not demonstrate actual adoption or correct implementation.Download or API-access counts do not demonstrate actual adoption or correct implementation. Suggested revision: Measure declared implementation, validated implementation, production use, geographic and programme coverage, transaction volume, and conformance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2392✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Usage analytics” capability anchor: medium |
Monitoring who queries or uses terminology and model services can reveal organisational, programme, or clinical activit…Monitoring who queries or uses terminology and model services can reveal organisational, programme, or clinical activity. Suggested revision: Apply data minimisation, aggregation, purpose restriction, retention, and access controls to semantic-service telemetry. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2393✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Runtime error monitoring” capability anchor: medium |
Runtime semantic errors should include invalid codes, version mismatch, unresolved identifiers, failed mappings, reject…Runtime semantic errors should include invalid codes, version mismatch, unresolved identifiers, failed mappings, rejected profiles, and unknown extensions. Suggested revision: Define a common semantic-error taxonomy and require dashboards, alerts, remediation ownership, and trend analysis. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2394✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Implementation feedback” capability anchor: medium |
Free-text feedback alone is insufficient for diagnosing semantic interoperability failures.Free-text feedback alone is insufficient for diagnosing semantic interoperability failures. Suggested revision: Require structured feedback linked to artefact identifier, version, system, profile, use case, severity, example payload, and proposed resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-2395✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Data-quality feedback” capability anchor: medium |
Semantic issues identified in downstream data need to reach both artefact stewards and source-system owners.Semantic issues identified in downstream data need to reach both artefact stewards and source-system owners. Suggested revision: Define feedback and remediation workflows covering semantic artefact correction, implementation correction, source-data correction, and communication to affected consumers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-2396✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Dependency monitoring” capability anchor: medium |
External terminologies, classifications, standards, and implementation guides can change independently of national rele…External terminologies, classifications, standards, and implementation guides can change independently of national release cycles. Suggested revision: Monitor upstream releases, licences, deprecations, security notices, and dependencies and assess national impact systematically. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2397✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Impact analysis” capability anchor: medium |
Impact analysis must occur before and after change to verify predicted and actual effects.Impact analysis must occur before and after change to verify predicted and actual effects. Suggested revision: Require pre-release dependency analysis and post-release monitoring of errors, adoption, performance, safety, and unintended effects. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2398✎ edit📣 feedback | received | Metadata registries Clinical agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Safety monitoring” capability anchor: medium |
Semantic errors can affect clinical care, benefits, claims, product selection, surveillance, and public reporting, but …Semantic errors can affect clinical care, benefits, claims, product selection, surveillance, and public reporting, but safety escalation is not sufficiently prominent. Suggested revision: Add severity classification, patient-safety escalation, urgent correction, notification, rollback, and incident review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-2399✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Equity monitoring” capability anchor: medium |
Semantic content can exclude or misrepresent groups through code choices, language, demographic categories, or unavaila…Semantic content can exclude or misrepresent groups through code choices, language, demographic categories, or unavailable local concepts. Suggested revision: Monitor representation, rejected local concepts, translation gaps, differential data quality, and effects on underserved populations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2400✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Review cycle” capability anchor: medium |
Fixed review intervals may be inappropriate across artefacts with different risk and update frequency.Fixed review intervals may be inappropriate across artefacts with different risk and update frequency. Suggested revision: Use risk-based review periods and event-triggered review following upstream changes, incidents, law changes, implementation failure, or evidence updates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2401✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Audit” capability anchor: medium |
Semantic-governance audit must cover authoring, review, approval, publication, access, imports, mapping changes, emerge…Semantic-governance audit must cover authoring, review, approval, publication, access, imports, mapping changes, emergency changes, and administrative actions. Suggested revision: Define the audit-event model, retention, integrity, monitoring, authorised access, and investigation procedures. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-231 discuss | in the document all mentions on GitHub record | ||
| PC-2402✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Performance monitoring” capability anchor: medium |
Runtime service monitoring should not be limited to availability and response time.Runtime service monitoring should not be limited to availability and response time. Suggested revision: Add freshness, cache status, package synchronisation, validation accuracy, expansion consistency, unresolved requests, and recovery performance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2403✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Corrective action” capability anchor: medium |
Monitoring without assigned remediation authority and deadlines may not improve semantic quality.Monitoring without assigned remediation authority and deadlines may not improve semantic quality. Suggested revision: Define corrective-action ownership, severity-based deadlines, escalation, root-cause analysis, closure evidence, and communication to affected consumers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-2404✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Monitoring p.243 l.“Outcome evaluation” capability anchor: medium |
The appendix does not explain how SGI success contributes to wider interoperability or health-system outcomes.The appendix does not explain how SGI success contributes to wider interoperability or health-system outcomes. Suggested revision: Add indicators such as reduced local duplication, fewer mapping errors, faster implementation, improved conformance, reduced reporting inconsistency, and safer data reuse, while avoiding direct attribution to health outcomes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2405✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.243-244 l.“Artefact distribution” capability anchor: medium |
Distribution must cover more than a central API. National ecosystems require several consumption patterns.Distribution must cover more than a central API. National ecosystems require several consumption patterns. Suggested revision: Support live APIs, downloadable packages, container or package registries, local mirrors, offline bundles, event notifications, human-readable documents, and accessible web browsing. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2406✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.243-244 l.“Artefact distribution” capability anchor: medium |
Continuous online access may not be available in remote facilities or lower-resource environments.Continuous online access may not be available in remote facilities or lower-resource environments. Suggested revision: Require locally deployable packages, synchronisation, integrity checks, update status, and safe operation when disconnected. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2407✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Version discovery” capability anchor: medium |
Consumers need to discover supported, current, deprecated, and future versions and their compatibility.Consumers need to discover supported, current, deprecated, and future versions and their compatibility. Suggested revision: Publish machine-readable release metadata, compatibility, effective date, replacement, support period, and migration guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2408✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Package management” capability anchor: medium |
Packages may contain linked terminology, profiles, mappings, examples, and validators, but dependency resolution is not…Packages may contain linked terminology, profiles, mappings, examples, and validators, but dependency resolution is not explicit. Suggested revision: Require package manifests, dependencies, version constraints, integrity, licence metadata, and reproducible installation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2409✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Publication channels” capability anchor: medium |
Human-readable artefacts and documentation need accessible formats, language support, and low-bandwidth options.Human-readable artefacts and documentation need accessible formats, language support, and low-bandwidth options. Suggested revision: Require accessible HTML or PDF, clear documentation, machine-readable exports, multilingual labels, and downloadable compact packages. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2410✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Access control” capability anchor: medium |
Some semantic assets are public, while others may be restricted because of licence, security, draft status, or sensitiv…Some semantic assets are public, while others may be restricted because of licence, security, draft status, or sensitive mappings. Suggested revision: Define public, registered, restricted, confidential, and administrative access classes and their governing criteria. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-231 discuss | in the document all mentions on GitHub record | ||
| PC-2411✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Authentication” capability anchor: medium |
Authentication for restricted semantic services may be provided by foundational identity or trust services rather than …Authentication for restricted semantic services may be provided by foundational identity or trust services rather than recreated within each platform. Suggested revision: Map the capability to available foundational authentication and organisation-credential services while preserving health-specific authorisation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-231 discuss | in the document all mentions on GitHub record | ||
| PC-2412✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Subscription” capability anchor: medium |
Consumers need targeted notifications rather than undifferentiated alerts for every release.Consumers need targeted notifications rather than undifferentiated alerts for every release. Suggested revision: Support subscriptions by artefact, domain, version, dependency, jurisdiction, change severity, and implementation profile. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2413✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Critical change notification” capability anchor: medium |
Passive publication is insufficient for safety-critical corrections or deprecations.Passive publication is insufficient for safety-critical corrections or deprecations. Suggested revision: Require active notification, acknowledgement, escalation, and affected-consumer tracking for critical changes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2414✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Federated distribution” capability anchor: medium |
Regional or federated terminology and model services may be important where national capacity is limited.Regional or federated terminology and model services may be important where national capacity is limited. Suggested revision: Add federation, trusted mirror, national override, regional package, and source-precedence patterns. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2415✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Integrity verification” capability anchor: medium |
Consumers must know that a package came from the authorised publisher and was not modified.Consumers must know that a package came from the authorised publisher and was not modified. Suggested revision: Require cryptographic checksums or signatures, trusted publisher metadata, secure transport, and verification guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-231 discuss | in the document all mentions on GitHub record | ||
| PC-2416✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Archival access” capability anchor: medium |
Historical versions are necessary to interpret old records, reproduce reports, evaluate past decisions, and support leg…Historical versions are necessary to interpret old records, reproduce reports, evaluate past decisions, and support legal review. Suggested revision: Make immutable historical access mandatory, subject to licensing and security, with clear version resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2417✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Distribution p.244 l.“Service-level management” capability anchor: medium |
Distribution services require accountable ownership, monitoring, backup, recovery, support, and recurrent funding.Distribution services require accountable ownership, monitoring, backup, recovery, support, and recurrent funding. Suggested revision: Add measurable service levels and an operating model for publication and runtime services. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2418✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Artefact discovery” capability anchor: medium |
Users need to discover artefacts by purpose, domain, status, language, jurisdiction, use case, and implementation stand…Users need to discover artefacts by purpose, domain, status, language, jurisdiction, use case, and implementation standard, not only identifier or title. Suggested revision: Add rich searchable metadata, filtering, related artefacts, examples, and recommended-use information. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2419✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Artefact evaluation” capability anchor: medium |
Consumers need to determine whether an artefact is appropriate for their use, but fitness-for-purpose criteria are not …Consumers need to determine whether an artefact is appropriate for their use, but fitness-for-purpose criteria are not explicit. Suggested revision: Publish intended use, excluded use, evidence, maturity, status, limitations, dependencies, risk level, and implementation prerequisites. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2420✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Implementation guidance” capability anchor: medium |
Semantic artefacts without worked examples and implementation guidance are difficult to apply consistently.Semantic artefacts without worked examples and implementation guidance are difficult to apply consistently. Suggested revision: Require examples, sample payloads, common errors, migration guidance, validation tools, test data, and mappings to operational workflows. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2421✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Implementation support” capability anchor: medium |
Countries and local implementers may lack specialist support to interpret models and terminology.Countries and local implementers may lack specialist support to interpret models and terminology. Suggested revision: Provide support channels, office hours, documentation, training, communities of practice, regional assistance, and escalation for safety-critical issues. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2422✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Local configuration” capability anchor: medium |
Local configuration can undermine national conformance if it changes bindings, cardinalities, codes, or definitions wit…Local configuration can undermine national conformance if it changes bindings, cardinalities, codes, or definitions without governance. Suggested revision: Define permitted configuration separately from semantic extension and require validation against the national profile. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-230 discuss | in the document all mentions on GitHub record | ||
| PC-2423✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Conformance validation” capability anchor: medium |
Consumers need accessible validation before production deployment.Consumers need accessible validation before production deployment. Suggested revision: Provide open validators, test servers, example data, negative tests, implementation checklists, and standard result reports. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-232 discuss | in the document all mentions on GitHub record | ||
| PC-2424✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Runtime validation” capability anchor: medium |
Live validation against a national service may not be feasible for every transaction or location.Live validation against a national service may not be feasible for every transaction or location. Suggested revision: Support local validators, caches, version-pinned packages, batch validation, and controlled offline operation. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-232 discuss | in the document all mentions on GitHub record | ||
| PC-2425✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Implementation declaration” capability anchor: medium |
Consumers should not claim conformance merely because they downloaded or referenced an artefact.Consumers should not claim conformance merely because they downloaded or referenced an artefact. Suggested revision: Require a conformance statement identifying implemented version, profiles, options, extensions, mappings, test results, known limitations, and deployment scope. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-232 discuss | in the document all mentions on GitHub record | ||
| PC-2426✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Usage reporting” capability anchor: medium |
Mandatory detailed usage reporting may impose burdens or disclose sensitive organisational activity.Mandatory detailed usage reporting may impose burdens or disclose sensitive organisational activity. Suggested revision: Use proportionate, privacy-preserving usage reporting and distinguish registration, declared implementation, validated conformance, and observed runtime use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2427✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Feedback submission” capability anchor: medium |
Feedback should be linked to a specific artefact and implementation context.Feedback should be linked to a specific artefact and implementation context. Suggested revision: Require artefact identifier, version, use case, system, issue type, severity, evidence, and proposed resolution. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-2428✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Feedback submission” capability anchor: medium |
Feedback mechanisms may privilege large vendors and national programmes over frontline workers, local developers, patie…Feedback mechanisms may privilege large vendors and national programmes over frontline workers, local developers, patients, and smaller organisations. Suggested revision: Provide accessible feedback channels and ensure transparent consideration of input from underrepresented implementers and affected users. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2429✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Issue resolution” capability anchor: medium |
The appendix should distinguish content defects, implementation errors, local configuration issues, source-data errors,…The appendix should distinguish content defects, implementation errors, local configuration issues, source-data errors, and training needs. Suggested revision: Add issue classification, responsible owner, service level, escalation, resolution decision, release linkage, and communication. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-2430✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Community participation” capability anchor: medium |
Community contribution requires more than an open mailing list or technical forum.Community contribution requires more than an open mailing list or technical forum. Suggested revision: Define participation rights, moderation, code of conduct, accessible documentation, language support, conflict-of-interest management, and response obligations. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-2431✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Adoption monitoring” capability anchor: medium |
Adoption should not be measured only through registered users, downloads, or API calls.Adoption should not be measured only through registered users, downloads, or API calls. Suggested revision: Measure implementation coverage, validated conformance, production use, geographic reach, programme reuse, version currency, and error rates. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2432✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Migration support” capability anchor: medium |
Consumer migration between semantic versions is not sufficiently explicit.Consumer migration between semantic versions is not sufficiently explicit. Suggested revision: Provide change summaries, machine-readable diffs, impact reports, transformation scripts where safe, test cases, transition periods, and rollback guidance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2433✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Deprecation response” capability anchor: medium |
The governance body cannot assume that every consumer will migrate following a notice.The governance body cannot assume that every consumer will migrate following a notice. Suggested revision: Track affected implementations, require migration plans for critical artefacts, monitor outdated versions, and escalate unsafe continued use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2434✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Consumer assurance” capability anchor: medium |
Implementers need confidence that artefacts are clinically and technically approved for their intended use.Implementers need confidence that artefacts are clinically and technically approved for their intended use. Suggested revision: Publish approval authority, status, intended use, validation evidence, known limitations, support status, and safety notices. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-240 discuss | in the document all mentions on GitHub record | ||
| PC-2435✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F, Consumption p.244 l.“Consumption metrics” capability anchor: medium |
Use metrics can support the investment case but should not incentivise unnecessary central service calls when local pac…Use metrics can support the investment case but should not incentivise unnecessary central service calls when local packages are safer or more efficient. Suggested revision: Measure successful semantic adoption and conformance rather than raw API volume alone. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2436✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The capability catalogue does not explicitly distinguish governance of terminology, information models, implementation …The capability catalogue does not explicitly distinguish governance of terminology, information models, implementation guides, indicators, computable guidelines, mappings, and benefit rules. Suggested revision: Add artefact-applicability columns showing which capabilities apply universally and which require artefact-specific processes. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-057 discuss | in the document all mentions on GitHub record | ||
| PC-2437✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Dependency management is distributed across several capabilities rather than visible as a core architectural function.Dependency management is distributed across several capabilities rather than visible as a core architectural function. Suggested revision: Add a dedicated cross-cutting domain for dependency, impact, compatibility, and coordinated release management. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2438✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Capabilities are described narratively but lack standard measurable maturity and conformance criteria.Capabilities are described narratively but lack standard measurable maturity and conformance criteria. Suggested revision: Add maturity definitions, expected evidence, indicators, assessment questions, and target outcomes to every capability. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2439✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The appendix provides the target capability set but no prioritised implementation roadmap.The appendix provides the target capability set but no prioritised implementation roadmap. Suggested revision: Define progressive stages: minimum governance baseline; governed publication; national distribution; implementation and conformance support; monitoring and continuous improvement; and federated or regional maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2440✎ edit📣 feedback | received | Metadata registries Core architects agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
It remains unclear which SGI capabilities are required for the REDDHI minimum foundation and which can mature later.It remains unclear which SGI capabilities are required for the REDDHI minimum foundation and which can mature later. Suggested revision: Mark each capability as REDDHI baseline, use-case-dependent, intermediate maturity, or advanced maturity. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2441✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The capability model may appear to require each country to establish every specialist function nationally.The capability model may appear to require each country to establish every specialist function nationally. Suggested revision: Allow national, regional, shared, outsourced, and internationally provided capabilities, while defining the governance responsibilities that must remain nationally accountable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2442✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
No financial or workforce model accompanies the capability catalogue.No financial or workforce model accompanies the capability catalogue. Suggested revision: Add indicative roles, competencies, minimum staffing patterns, shared-service options, tooling costs, licensing, translation, and recurrent operational costs. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2443✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Multilingual and local-content governance is present but not clearly treated as a cross-cutting obligation.Multilingual and local-content governance is present but not clearly treated as a cross-cutting obligation. Suggested revision: Add language, accessibility, inclusive representation, local concepts, rights, and equity review across intake, authoring, publication, monitoring, distribution, and feedback. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2444✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Semantic assets may themselves contain sensitive definitions, mappings, rule logic, or security-relevant details, yet s…Semantic assets may themselves contain sensitive definitions, mappings, rule logic, or security-relevant details, yet security classification is not consistently addressed. Suggested revision: Add security classification, access conditions, integrity, trusted publication, audit, incident response, and protection of restricted artefacts. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-231 discuss | in the document all mentions on GitHub record | ||
| PC-2445✎ edit📣 feedback | received | Editorial Metadata registries agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
“Content,” “artefact,” “model,” “standard,” and “semantic asset” may be used interchangeably.“Content,” “artefact,” “model,” “standard,” and “semantic asset” may be used interchangeably. Suggested revision: Define and use a controlled vocabulary consistently throughout Appendix F. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2446✎ edit📣 feedback | received | Metadata registries Core architects agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
SGI capabilities overlap with Terminology Service, LIMR, architecture governance, conformance services, and national st…SGI capabilities overlap with Terminology Service, LIMR, architecture governance, conformance services, and national standards bodies. Suggested revision: Add a capability-to-component and capability-to-organisation matrix showing where each capability is realised and who remains accountable. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-227 discuss | in the document all mentions on GitHub record | ||
| PC-2447✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Clinical safety and patient-safety escalation are not sufficiently visible across the lifecycle.Clinical safety and patient-safety escalation are not sufficiently visible across the lifecycle. Suggested revision: Add safety review, hazard assessment, critical-change handling, urgent withdrawal, consumer notification, and post-incident review. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-272 discuss | in the document all mentions on GitHub record | ||
| PC-2448✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The appendix does not explicitly address provenance of semantic artefacts and transformations across national, regional…The appendix does not explicitly address provenance of semantic artefacts and transformations across national, regional, and global sources. Suggested revision: Require source, author, contributor, derivation, imported version, transformation, approval, publication, and custody provenance. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-231 discuss | in the document all mentions on GitHub record | ||
| PC-2449✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The relationship between the Appendix F capability catalogue and the separately maintained machine-readable architectur…The relationship between the Appendix F capability catalogue and the separately maintained machine-readable architecture model is not specified. Suggested revision: Version Appendix F against a named architecture-model release and identify persistent capability identifiers. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-227 discuss | in the document all mentions on GitHub record | ||
| PC-2450✎ edit📣 feedback | received | Metadata registries agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The capability table may be too dense to function as a country assessment tool in the PDF.The capability table may be too dense to function as a country assessment tool in the PDF. Suggested revision: Publish an editable assessment workbook with capability description, maturity scale, current state, target state, owner, evidence, gap, action, priority, cost, and deadline. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2451✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Countries need a mechanism for recording exceptions where an SGI capability is provided through an alternative arrangem…Countries need a mechanism for recording exceptions where an SGI capability is provided through an alternative arrangement. Suggested revision: Add implementation-status values such as national, regional, externally provided, manual, partially implemented, planned, deferred, not applicable, and gap. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2452✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The capability catalogue has limited practical examples showing how countries at different maturity levels realise sema…The capability catalogue has limited practical examples showing how countries at different maturity levels realise semantic governance. Suggested revision: Add short examples of lightweight, intermediate, national-platform, and regional shared-service implementations, including limitations and prerequisites. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-273 discuss | in the document all mentions on GitHub record | ||
| PC-2453✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The capability catalogue is not directly connected to the component requirements in Appendix C or the architecture conf…The capability catalogue is not directly connected to the component requirements in Appendix C or the architecture conformance model in Section 3.7. Suggested revision: Link each capability to relevant component requirements, architecture elements, test evidence, and maturity indicators. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-227 discuss | in the document all mentions on GitHub record | ||
| PC-2454✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The appendix does not show how semantic governance contributes to the seven priority health goals.The appendix does not show how semantic governance contributes to the seven priority health goals. Suggested revision: Add a goal-contribution matrix showing which SGI capabilities are critical to trusted data, workforce, care continuity, personal records, supply chain, financing, and resilience. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-227 discuss | in the document all mentions on GitHub record | ||
| PC-2455✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
The top-down governance model remains stronger than the feedback and upward-sensing model.The top-down governance model remains stronger than the feedback and upward-sensing model. Suggested revision: Make bidirectional governance explicit, including local requests, implementation evidence, unresolved concepts, mapping limitations, adoption data, and user feedback. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-233 discuss | in the document all mentions on GitHub record | ||
| PC-2456✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Retiring semantic artefacts can affect the interpretation of historical health records and reports for decades.Retiring semantic artefacts can affect the interpretation of historical health records and reports for decades. Suggested revision: Require permanent resolution of historical identifiers and versions, even after content is retired from active use. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-274 discuss | in the document all mentions on GitHub record | ||
| PC-2457✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Dependence on one software platform, supplier, terminology licence, or small specialist team could undermine semantic-g…Dependence on one software platform, supplier, terminology licence, or small specialist team could undermine semantic-governance resilience. Suggested revision: Require portability, open export, documented processes, succession, cross-training, disaster recovery, alternative distribution, and supplier-exit arrangements. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-055 discuss | in the document all mentions on GitHub record | ||
| PC-2458✎ edit📣 feedback | received | Metadata registries agent |
F Appendix F: Semantic Governance Infrastructure: capability details §Appendix F overall p.241-244 l.Entire appendix anchor: medium |
Appendix F is currently informative but not yet directly actionable as a national operating model.Appendix F is currently informative but not yet directly actionable as a national operating model. Suggested revision: Convert the catalogue into a practical SGI operating-model template covering governance bodies, roles, workflows, services, artefacts, tools, maturity, indicators, financing, and improvement roadmap. Michael Anywar, EY DHEC, Germany |
none | not yet | CS-228 discuss | in the document all mentions on GitHub record | ||
| PC-2459✎ edit📣 feedback | received | WHO Editorial agent, medium |
Acronyms §Acronyms p.6 l.A01.01 anchor: medium |
ICD-11 acronym — The full formal title adopted by WHA72.15 (https://apps.who.int/gb/ebwha/pdf_files/WHA72/A72_R15-en.pd…ICD-11 acronym — The full formal title adopted by WHA72.15 (https://apps.who.int/gb/ebwha/pdf_files/WHA72/A72_R15-en.pdf) includes “Statistical”; restore that word in the acronym expansion. The title does not limit the clinical terminology role explained in the glossary and A07.01. Suggested revision: Replace expansion: ICD-11 — International Statistical Classification of Diseases and Related Health Problems, Eleventh Revision (not stated) |
none | not yet | CS-131 discuss | in the document all mentions on GitHub record | ||
| PC-2460✎ edit📣 feedback | received | Metadata registries Editorial agent, medium |
Acronyms §Acronyms p.6 l.A01.02 anchor: medium |
ICF acronym — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the m…ICF acronym — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the modern architecture of ICD-11 before interpreting later lists. Evidence: WHO ICD overview (https://www.who.int/standards/classifications/classification-of-diseases), WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub), ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/). Suggested revision: Insert acronym row: ICF — International Classification of Functioning, Disability and Health (not stated) |
none | not yet | CS-131 discuss | in the document all mentions on GitHub record | ||
| PC-2461✎ edit📣 feedback | received | Metadata registries Editorial agent, medium |
Acronyms §Acronyms p.6 l.A01.03 anchor: medium |
ICHI acronym — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the …ICHI acronym — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the modern architecture of ICD-11 before interpreting later lists. Evidence: WHO ICD overview (https://www.who.int/standards/classifications/classification-of-diseases), WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub), ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/). Suggested revision: Insert acronym row: ICHI — International Classification of Health Interventions (not stated) |
none | not yet | CS-131 discuss | in the document all mentions on GitHub record | ||
| PC-2462✎ edit📣 feedback | received | Editorial agent |
Acronyms §Acronyms p.6 l.A01.04 anchor: medium |
MMS acronym — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the m…MMS acronym — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the modern architecture of ICD-11 before interpreting later lists. Evidence: WHO ICD overview (https://www.who.int/standards/classifications/classification-of-diseases), WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub), ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/). Suggested revision: Insert acronym row: MMS — Mortality and Morbidity Statistics (not stated) |
none | not yet | CS-131 discuss | in the document all mentions on GitHub record | ||
| PC-2463✎ edit📣 feedback | received | Editorial agent |
Acronyms §Acronyms p.6 l.A01.05 anchor: medium |
WHO-FIC acronym — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need t…WHO-FIC acronym — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the modern architecture of ICD-11 before interpreting later lists. Evidence: WHO ICD overview (https://www.who.int/standards/classifications/classification-of-diseases), WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub), ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/). Suggested revision: Insert acronym row: WHO-FIC — WHO Family of International Classifications (not stated) |
none | not yet | CS-131 discuss | in the document all mentions on GitHub record | ||
| PC-2464✎ edit📣 feedback | received | Metadata registries agent |
Glossary §Glossary p.1 l.A01.07 anchor: medium |
Foundation glossary definition — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11.…Foundation glossary definition — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the modern architecture of ICD-11 before interpreting later lists. Evidence: WHO ICD overview (https://www.who.int/standards/classifications/classification-of-diseases), WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub), ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/). Suggested revision: Insert glossary entry: Foundation component: The multidimensional concept base underlying ICD-11, in which entities have persistent identifiers and may have more than one parent. A Foundation entity identifier and an MMS category code identify different representations and must not be treated as interchangeable identifiers. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2465✎ edit📣 feedback | received | Metadata registries WHO agent |
Glossary §Glossary p.1 l.A01.06 anchor: medium |
ICD-11 glossary definition — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Rea…ICD-11 glossary definition — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the modern architecture of ICD-11 before interpreting later lists. Evidence: WHO ICD overview (https://www.who.int/standards/classifications/classification-of-diseases), WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub), ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/). Suggested revision: Insert glossary entry: ICD-11: WHO's international standard combining a classification for mortality and morbidity statistics with a terminology and digital infrastructure for recording and exchanging clinical information. Its Foundation supplies identified health concepts and their relationships; its Mortality and Morbidity Statistics (MMS) linearization supplies the statistical classification. ICD-11 supports clinical detail through its terminology and permitted combinations of stem and extension codes. Clinical use and statistical use apply their respective rules and retain the identifiers and release information needed to interpret the data. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2466✎ edit📣 feedback | received | Metadata registries agent |
Glossary §Glossary p.2 l.A04.02 anchor: medium |
GPS glossary scope — The existing “representative subset” wording does not tell readers which semantic capabilities the…GPS glossary scope — The existing “representative subset” wording does not tell readers which semantic capabilities they actually receive. This correction should not be used to claim that GPS is only a demonstration product or that free IPS terminology is unavailable. Evidence: GPS (https://www.snomed.org/gps), IPS Terminology overview (https://docs.snomed.org/implementation-guides/snomed-ips-terminology-implementation-guide/2-ips-terminology-overview). Suggested revision: Replace definition: The Global Patient Set is a freely accessible SNOMED International product supporting exchange, storage, display, and basic validation of SNOMED CT identifiers. It does not include SNOMED CT relationships or hierarchies. It is distinct from full SNOMED CT and from SNOMED International's IPS Terminology. (not stated) |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | ||
| PC-2467✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
Glossary §Glossary p.2 l.A01.08 anchor: medium |
WHO-FIC glossary definition — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Re…WHO-FIC glossary definition — The glossary explains SNOMED CT and GPS but gives no comparable explanation of ICD-11. Readers need the modern architecture of ICD-11 before interpreting later lists. Evidence: WHO ICD overview (https://www.who.int/standards/classifications/classification-of-diseases), WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub), ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/). Suggested revision: Insert glossary entry: WHO Family of International Classifications (WHO-FIC): WHO's family of related health classifications, including ICD for diseases and related health problems, ICF for functioning and disability, and ICHI for health interventions. Their roles, implementation specifications, release status, and applicable governance are identified separately for each use case. (not stated) |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | ||
| PC-2468✎ edit📣 feedback | received | Core architects agent, medium |
Executive Summary §Figure 1, Phase 01 p.1 l.A28.01 |
Planning figure includes data workflows and uses — Extends the systems inventory to the data landscape. Uses compact fi…Planning figure includes data workflows and uses — Extends the systems inventory to the data landscape. Uses compact figure wording; the operational detail is in B01.01 and A28.02. Preserve the existing WHO-FIC/ICD-11 box and source attribution. Mark the Phase 01 adaptation through A28.03. Suggested revision: Replace Phase 01 bullet; retain the remaining figure; coordinate with A28.03 and re-render for legibility: Inventory existing and previously used applications, ICT systems and tools, together with their data workflows, uses and reporting obligations, to establish requirements for reuse and interoperability. (not stated) |
none | not yet | CS-003 discuss | in the document all mentions on GitHub record | ||
| PC-2469✎ edit📣 feedback | received | Editorial agent, medium |
Executive Summary §Figure 1 caption p.1 l.A28.03 |
Identify the planning-figure adaptation — Distinguishes the proposed extension from reproduced source wording. This cha…Identify the planning-figure adaptation — Distinguishes the proposed extension from reproduced source wording. This changes the caption, so it is separately assignable from the figure artwork. No assertion is made that the proposed wording is a verbatim DIIG quotation. Suggested revision: Append caption sentence when A28.01 is applied; retain the existing caption and any source attribution: Phase 01 is adapted here to include data workflows, data uses and reporting obligations. (not stated) |
none | not yet | CS-003 discuss | in the document all mentions on GitHub record | ||
| PC-2470✎ edit📣 feedback | received | Metadata registries WHO agent |
1.2.2 Data exchange DPI and Interoperability in the health sector §§1.2.2, Box 1.3, item 1 p.15 l.A02.01 anchor: medium |
Semantic content alongside exchange format — Introduces ICD-11 in an actual interoperability role at the first explanat…Semantic content alongside exchange format — Introduces ICD-11 in an actual interoperability role at the first explanation of why health needs more than transport. Evidence: WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub). Suggested revision: Insert sentence group: The exchange format must be combined with an agreed clinical information model and identified semantic content. For example, ICD-11 can supply the terminology used to record and exchange a diagnosis and the classification used to report it, with the original clinical detail retained. FHIR supplies an exchange representation; it does not, by itself, select or replace that semantic content. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2471✎ edit📣 feedback | received | WHO Metadata registries agent |
1.5.1 The Health Sector Goals §§1.5.1, first health-sector goal p.22 l.A25.01 anchor: medium |
Goal 1 includes the ICD statistical reporting pathway — Goal 1 expressly promises CRVS and mortality analytics. This ma…Goal 1 includes the ICD statistical reporting pathway — Goal 1 expressly promises CRVS and mortality analytics. This makes the supporting pathway explicit without claiming that the draft lacks all CRVS or reporting provisions. Coordinate with B02.01, A22.01 and A25.04. Evidence: WHO Nomenclature Regulations 1967 (https://www.who.int/publications/m/item/who-nomenclature-regulations-1967); WHA72.15 (https://apps.who.int/gb/ebwha/pdf_files/WHA72/A72_R15-en.pdf). Suggested revision: Append to the first-goal paragraph; retain existing Goal 1 wording: Trusted data foundations also preserve the mortality and morbidity statistical pathways required under the WHO Nomenclature Regulations, within their applicable scope and transition arrangements. They connect clinical documentation and death certification to ICD coding and reported statistics, with traceable responsibilities and derivations. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2472✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
2.2.2 The enabling conditions for REDDHI §§2.2.2, Open Standards bullet p.28–29 l.A03.01 anchor: medium |
ICD-11 as primary semantic standard — Naming “ICD” in a list leaves its version and clinical role unclear. This wording…ICD-11 as primary semantic standard — Naming “ICD” in a list leaves its version and clinical role unclear. This wording gives a positive alternative while preserving other valid choices. Evidence: WHO ICD overview (https://www.who.int/standards/classifications/classification-of-diseases), WHO interoperability hub (https://www.who.int/standards/classifications/who-fic-interoperability-hub). International reporting and national implementation choices are distinguished; see WHO Nomenclature Regulations 1967 (https://www.who.int/publications/m/item/who-nomenclature-regulations-1967) and WHA72.15 (https://apps.who.int/gb/ebwha/pdf_files/WHA72/A72_R15-en.pdf). Reviewer A25.03 is incorporated here. Suggested revision: Replace whole bullet; retain asterisk marker and apply A04.01: Open Standards: grounding implementation in publicly specified standards with transparent governance and stated terms of use. These include HL7 FHIR for health data exchange; ICD-11 as both a clinical terminology and a statistical classification; other WHO-FIC standards for their respective domains; LOINC for observations; and SNOMED CT* where selected for clinical terminology. Selection should match the intended use, required clinical detail, available implementation support, applicable Member State reporting obligations under the WHO Nomenclature Regulations, other national obligations, and sustainable operating costs. The architecture supports ICD-11 as a primary semantic choice within its scope and does not require an intervening SNOMED CT representation. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2473✎ edit📣 feedback | received | Metadata registries agent |
2.2.2 The enabling conditions for REDDHI §§2.2.2, asterisk footnote p.29 l.A04.01 anchor: medium |
SNOMED product and licence distinctions — The existing “representative subset” wording does not tell readers which sema…SNOMED product and licence distinctions — The existing “representative subset” wording does not tell readers which semantic capabilities they actually receive. This correction should not be used to claim that GPS is only a demonstration product or that free IPS terminology is unavailable. Evidence: GPS (https://www.snomed.org/gps), IPS Terminology overview (https://docs.snomed.org/implementation-guides/snomed-ips-terminology-implementation-guide/2-ips-terminology-overview). Suggested revision: Replace whole footnote: *Implementers should distinguish full SNOMED CT, the Global Patient Set (GPS), and SNOMED International's IPS Terminology and check the terms and capabilities of the actual product and release used. GPS provides identifiers, selected English names, and status information, but excludes the relationships and hierarchies of full SNOMED CT. IPS Terminology is a separate, more limited clinical-content product with its own scope. Free access to one product does not imply that it supplies the functionality or usage rights of another. ICD-11 content and WHO software also have published terms of use; see the Terminology Service licensing requirements.* (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2474✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
3.4.5 Semantic Governance Infrastructure §§3.4.5, Global, national and local content p.61 l.A05.01 anchor: medium |
WHO maintenance and proposals — The current paragraph describes HL7 and SNOMED governance, but gives no corresponding W…WHO maintenance and proposals — The current paragraph describes HL7 and SNOMED governance, but gives no corresponding WHO route. Evidence: WHO interoperability hub (https://www.who.int/standards/classifications/who-fic-interoperability-hub), ICD-11 Reference Guide (https://icdcdn.who.int/icd11referenceguide/en/refguide.pdf), §1.6.4 and maintenance material. Suggested revision: Insert paragraph: WHO-FIC provides a further international governance route. For ICD-11, national implementers should use the WHO maintenance and proposal processes to request changes to international content, distinguish proposals from approved releases, and govern adoption of each published release. National deployment should preserve WHO identifiers and meaning while recording locally governed value sets, annotations, and implementation rules separately. Governance should include classification and clinical coding expertise as well as terminology and information-model expertise. (not stated) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-2475✎ edit📣 feedback | received | Metadata registries Clinical agent |
3.5.3.1 The foundational shared data layer §§3.5.3.1, immediately after Table 3.5 p.70 l.A06.01 anchor: medium |
Worked direct ICD-11 diagnosis pathway — ICD-11 is already in the table's standards list, but is absent from its worked…Worked direct ICD-11 diagnosis pathway — ICD-11 is already in the table's standards list, but is absent from its worked interactions. A diagnosis example demonstrates its strengths without trying to substitute it for laboratory or measurement terminology. Evidence for the identifier example: WHO ICD API v2 (https://icd.who.int/docs/icd-api/APIDoc-Version2/). This is an explanatory scenario, not a claim of a tested deployment or a complete FHIR instance. Suggested revision: Insert complete worked-example box; retain blood-pressure example: Worked example: an ICD-11-coded clinical diagnosis A clinician records a diagnosis using ICD-11 terminology. The terminology service resolves the selected concept against the specified WHO release and provides its identifier, title, relevant properties, and available coding instructions. For example, the WHO API documentation identifies cholera by Foundation URI http://id.who.int/icd/entity/257068234; its MMS category code is 1A00. The Foundation URI and the MMS code are recorded with their respective namespace and release, rather than treated as the same identifier. The LIMR defines the clinical statement: whose condition it is, the encounter, onset or relevant time, clinical and verification status, and other context required for the use case. The record preserves the clinician's statement and any valid coded expression, including linked postcoordination detail when applicable. A receiving clinical system interprets the diagnosis using the same identified ICD-11 content. A statistical process derives the applicable MMS representation and applies the relevant selection and aggregation rules, retaining a link to the source statement. No conversion to SNOMED CT is a prerequisite for this path. Where another system requires a different terminology, any additional mapping is governed separately, with its limitations recorded. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2476✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
3.6.2 Data and health content standards §§3.6.2, Data and health content standards p.74 l.A07.01 anchor: medium |
Central ICD-11 terminology and classification pathway — The main correction presents ICD-11 as a primary clinical termi…Central ICD-11 terminology and classification pathway — The main correction presents ICD-11 as a primary clinical terminology and statistical classification, with continuity into reporting. The legal paragraph incorporates reviewer A07.02 with corrected instruments and scope: WHO Constitution, Articles 2(s), 21(b), 22 and 64 (https://apps.who.int/gb/bd/pdf_files/BD_49th-en.pdf); WHO Nomenclature Regulations 1967 (https://www.who.int/publications/m/item/who-nomenclature-regulations-1967); WHA72.15 (https://apps.who.int/gb/ebwha/pdf_files/WHA72/A72_R15-en.pdf); WHA54.21 (https://apps.who.int/gb/ebwha/pdf_files/WHA54/ea54r21.pdf). It omits the unsupported 2023 amendment claim. Clinical capabilities: WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub) and WHO ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/). The supplied data-continuity discussion paper supports the design proposal but is not an adopted WHO position. Suggested revision: Replace one existing paragraph with all four proposed paragraphs, in this order: Health content standards supply the shared meaning and structure on which interoperability depends. The architecture distinguishes exchange and information-model standards from clinical terminology, statistical classification, measurement identifiers, and product identification. HL7 FHIR provides an exchange-oriented representation; ICD-11 provides both clinical terminology and statistical classification; ICF addresses functioning and disability; and ICHI addresses health interventions. SNOMED CT, LOINC, GS1 and IDMP-family identifiers, DICOM, IHE profiles, and specifications such as the International Patient Summary serve their respective purposes. These standards are selected and combined according to the information and functions required. ICD-11 is a viable primary semantic standard for clinical information within its scope. It provides a Foundation of identified concepts, multilingual terminology, a statistical linearization for Mortality and Morbidity Statistics, and rules for adding detail through postcoordination. Systems may capture clinical information directly in ICD-11, exchange the identified concepts and valid expressions, and reuse that information for reporting under the applicable classification rules. Implementing this route does not depend on first recording or converting the information into SNOMED CT. The original clinical statement, its precise identifiers and coded expression, and its context should remain available when a statistical category or other derived representation is produced. A statistical grouping is not a substitute for the more detailed source meaning. Additional standards remain necessary for data outside the selected terminology's scope and for such functions as laboratory measurement, units, medicinal-product identification, imaging, and exchange structure. Countries should publish their selected profiles and demonstrate semantic preservation through conformance tests. National standards selection should distinguish clinical implementation choices from international statistical obligations. Articles 21(b) and 22 of the WHO Constitution provide for Health Assembly regulations on disease, cause-of-death and public-health nomenclatures, with entry into force subject to the prescribed rejection and reservation procedures. The WHO Nomenclature Regulations 1967 establish ICD-based mortality and morbidity statistics, annual cause-of-death statistics, medical certification and provision of statistics to WHO within their stated scope. WHA72.15 adopted ICD-11 with effect from 1 January 2022, subject to transitional arrangements that accommodate continued reporting with earlier revisions. Architecture should therefore preserve the applicable ICD statistical reporting pathway from clinical documentation and death certification through coding to reported results. ICF was endorsed by WHA54.21 for use as appropriate; ICHI addresses interventions within WHO's nomenclature mandate. These classifications have distinct roles and legal status. Their inclusion in WHO-FIC does not itself place all three under identical reporting obligations or require them in every clinical field. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2477✎ edit📣 feedback | received | Metadata registries Core architects agent |
3.6.4 Cross-border health data flows §§3.6.4, cross-border requirements p.78 l.A08.01 anchor: medium |
IPS profile and permitted ICD-11 diagnosis binding — “IPS requires SNOMED everywhere” is an inaccurate basis for archit…IPS profile and permitted ICD-11 diagnosis binding — “IPS requires SNOMED everywhere” is an inaccurate basis for architecture or procurement. Equally, a permitted coding choice alone does not establish full document conformance or receiver capability. Evidence: IPS 2.0.1 Condition profile (https://hl7.org/fhir/uv/ips/2.0.1/StructureDefinition-Condition-uv-ips.html), machine-readable profile (https://hl7.org/fhir/uv/ips/2.0.1/StructureDefinition-Condition-uv-ips.json), FHIR R4 binding strengths (https://hl7.org/fhir/R4/terminologies.html#strength). Checked against the published 2.0.1 snapshot, including the referenced CodeableConcept profile; this is not an assertion that a comprehensive WHO-FIC IPS implementation guide has already been published. Suggested revision: Replace bullet: • A shared, internationally aligned patient summary specification, such as the International Patient Summary (IPS), should define the meaningful minimum exchanged for care. Implementations shall declare the IPS edition, national or regional profile, and terminology bindings used. ICD-11 is an available option for directly encoding diagnoses where the applicable binding permits it. For example, the published HL7 IPS 2.0.1 Condition profile uses a preferred SNOMED CT binding for the problem/diagnosis code; that binding does not require a SNOMED CT code for conformance. More restrictive derived profiles and the constraints on other fields must be assessed separately. (not stated) |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | ||
| PC-2478✎ edit📣 feedback | received | Metadata registries WHO agent |
3.6.4 Cross-border health data flows §§3.6.4, cross-border requirements p.78 l.A08.02 anchor: medium |
Cross-border terminology and language preservation — “IPS requires SNOMED everywhere” is an inaccurate basis for archit…Cross-border terminology and language preservation — “IPS requires SNOMED everywhere” is an inaccurate basis for architecture or procurement. Equally, a permitted coding choice alone does not establish full document conformance or receiver capability. Evidence: IPS 2.0.1 Condition profile (https://hl7.org/fhir/uv/ips/2.0.1/StructureDefinition-Condition-uv-ips.html), machine-readable profile (https://hl7.org/fhir/uv/ips/2.0.1/StructureDefinition-Condition-uv-ips.json), FHIR R4 binding strengths (https://hl7.org/fhir/R4/terminologies.html#strength). Checked against the published 2.0.1 snapshot, including the referenced CodeableConcept profile; this is not an assertion that a comprehensive WHO-FIC IPS implementation guide has already been published. Suggested revision: Replace bullet: • Terminology and language services should preserve original codes, expressions, releases, and clinical context while enabling interpretation in the receiving clinician's language. Where an additional representation is needed for the receiving profile, it should be explicitly linked to the source and its equivalence or loss of detail documented. A terminology conversion should not be imposed where direct ICD-11 coding meets the agreed profile and use-case requirements. (not stated) |
none | not yet | CS-279 discuss | in the document all mentions on GitHub record | ||
| PC-2479✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
3.7.4 Planning testing from the architecture §§3.7.4, Planning testing from the architecture p.84 l.B03.01 anchor: medium |
Test specifications do not establish product conformance — Prevents procurement from treating a server's general standa…Test specifications do not establish product conformance — Prevents procurement from treating a server's general standards claim as proof of correct ICD-11 support. Apply together with A09. Suggested revision: Replace bullet; apply B03.02 and coordinate with A09.01: • Standardised components may have reusable test specifications and tools. Where an implementation claims a standardised actor or interface, the adopter should reuse the applicable test plans, simulators, and reference data where these exist. The actual product version, configuration, terminology releases, and deployment integrations still require verification. A published standard or available test suite is not evidence that the deployed component conforms. (not stated) |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-2480✎ edit📣 feedback | received | Core architects Metadata registries agent, medium |
3.7.4 Planning testing from the architecture §§3.7.4, Planning testing from the architecture p.84 l.B03.02 anchor: medium |
Consequential testing-planning phrase — Prevents procurement from treating a server's general standards claim as proof …Consequential testing-planning phrase — Prevents procurement from treating a server's general standards claim as proof of correct ICD-11 support. Apply together with A09. Suggested revision: Replace phrase; retain remaining sentence: separates reusable test assets from additional tests that need to be developed and executed (not stated) |
none | not yet | CS-079 discuss | in the document all mentions on GitHub record | ||
| PC-2481✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
3.7.4 Planning testing from the architecture §§3.7.4, Planning testing from the architecture p.84 l.A09.01 anchor: medium |
Semantic pathway acceptance tests — Generic terminology operations do not by themselves test the clinical-to-statistica…Semantic pathway acceptance tests — Generic terminology operations do not by themselves test the clinical-to-statistical continuity the architecture promises. This is proposed acceptance-test design, informed by WHO coding guidance (https://icdcdn.who.int/icd11referenceguide/en/refguide.pdf) and the local continuity paper. Suggested revision: Insert paragraph; coordinate with B03.01–B03.02: Testing shall include the semantic pathway selected for the use case. For an ICD-11 pathway, test cases should cover identification of the code system and release; preservation of the selected Foundation entity, MMS code, and postcoordinated expression where used; multilingual display without change of concept identity; applicable coding constraints; and preservation of the original statement and clinical context through storage, exchange, and retrieval. Statistical tests should verify the intended selection and aggregation rules and retain traceability to source data. Code existence, value-set membership, syntactic conformance, clinical coding correctness, and fitness for the intended decision are different assertions and should have separate test results. The same outcome-based criteria should be used when comparing alternative semantic implementations. (not stated) |
none | not yet | CS-072 discuss | in the document all mentions on GitHub record | ||
| PC-2482✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
4.1.2 Assessing Where You Are §§4.1.2, Assessing Where You Are p.89 l.B01.01 anchor: medium |
Data and workflow baseline — A modern ICD-11 decision should be tested against the information chain and the intended u…Data and workflow baseline — A modern ICD-11 decision should be tested against the information chain and the intended uses. This adapts the useful evaluation method in the supplied bit4health standards survey, especially §§1.2–1.3 and 5.1–5.2; it does not import its 2004 product assessments. Suggested revision: Insert paragraph: Alongside the system inventory, inventory the clinical statements, forms, datasets, classifications, terminology releases, reporting obligations, and exchanges already in use. Trace the priority data flows from capture through clinical use to reporting, identifying who records or transforms the information, which rules apply, and where detail is lost or collected again. Evaluate candidate standards against the actual use cases, coverage, implementation maturity, maintained tooling, governance, conformance evidence, and total lifecycle cost. Record the reasons for each selection and any identified gaps. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2483✎ edit📣 feedback | received | Core architects Metadata registries WHO agent, medium |
4.2.2 A Phased Implementation Approach §§4.2.2, Phase 1 — Assess, align, and plan p.91 l.A28.02 anchor: medium |
Data-workflow analysis in Phase 1 — Turns the assessment added by B01.01 into an explicit planning activity and aligns …Data-workflow analysis in Phase 1 — Turns the assessment added by B01.01 into an explicit planning activity and aligns the body with A28.01. This is a targeted strengthening of Phase 1, not a claim that the entire architecture ignores data flows. Suggested revision: Insert bullet: • Analyse existing data workflows and uses alongside the systems inventory: trace priority flows from capture through clinical use, certification, coding and reporting; record the classifications and terminology releases in use, where detail is lost or re-collected, and the reporting obligations each flow serves; and use these findings to specify the required semantic services. (not stated) |
none | not yet | CS-088 discuss | in the document all mentions on GitHub record | ||
| PC-2484✎ edit📣 feedback | received | Metadata registries Clinical agent |
4.3.1 Design Data Structures and Data Models First §§4.3.1, minimum data models p.95 l.A10.01 anchor: medium |
Clinical profile content preservation — A list of accepted terminologies does not tell implementers how to preserve an …Clinical profile content preservation — A list of accepted terminologies does not tell implementers how to preserve an ICD-11 clinical statement. These are proposed profile requirements, with identifier distinctions grounded in WHO API documentation (https://icd.who.int/docs/icd-api/APIDoc-Version2/). Suggested revision: Insert paragraph: Minimum clinical data profiles should also specify how a coded statement preserves its code-system namespace, concept identifier or code, title or display, applicable release, original clinical text, and provenance. For ICD-11, the profile should distinguish Foundation identifiers from MMS codes and specify how the complete postcoordinated expression and any associated concept identifiers are retained and exchanged. The information model should carry the subject, encounter, timing, certainty or verification status, and other required context. When multiple codings are supplied, their relationship must be defined; additional codings must not silently change the meaning or replace a more precise source expression. Derived statistical outputs should be linked to the source statement and the rule version used to derive them. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2485✎ edit📣 feedback | received | WHO Metadata registries Core architects agent |
4.3.4 Integration Interfaces with Foundational DPI §First §4.3.4, Integration Interfaces with Foundational DPI p.97 l.B02.01 anchor: medium |
Mortality certification-to-statistics interfaces — The present death-event API example concerns registry updates. It is…Mortality certification-to-statistics interfaces — The present death-event API example concerns registry updates. It is an appropriate insertion point for the separate WHO classification and certification chain. Evidence: WHO Nomenclature Regulations (https://www.who.int/publications/m/item/who-nomenclature-regulations-1967), Articles 2–6, and WHA72.15 (https://apps.who.int/gb/ebwha/pdf_files/WHA72/A72_R15-en.pdf), paragraph 1. Editorial note: the PDF has two subsections numbered 4.3.4; this amendment concerns the first, not “Interoperability Implementation Pathways” beginning at line 369 on the same page. Promoted to P1 because it operationalises the stated Goal 1 mortality commitment; coordinate with A25.01 and A25.04. Suggested revision: Insert paragraph: Death-event notification should be linked to the distinct mortality-information workflow: medical certification of cause of death, preservation of the certified causal sequence and contributing conditions, ICD coding and selection of the underlying cause, and production of vital statistics. Interfaces should retain the certificate or source statement, identifiers, amendments, coding release, and rule provenance. Updating a person's death status in a registry does not supply these mortality functions; responsibilities and exchanges among health services, civil registration, and statistical authorities should be specified explicitly. (not stated) |
none | not yet | CS-101 discuss | in the document all mentions on GitHub record | ||
| PC-2486✎ edit📣 feedback | received | Metadata registries WHO agent |
4.5.2 The Roles and Skills Needed to Build and Govern the Architecture §§4.5.2, skills and roles p.101 l.A11.01 anchor: medium |
Classification and clinical coding responsibilities — The existing example frames expertise around mappings “to” standa…Classification and clinical coding responsibilities — The existing example frames expertise around mappings “to” standards. Direct capture and correct classification use require additional named responsibilities. Suggested revision: Replace bullet: • Terminology, classification, and clinical coding specialists, who support direct implementation of standards such as ICD-11 and other WHO-FIC content; curate code systems and value sets; apply the relevant clinical coding and statistical rules; govern mappings where needed; and operate semantic governance processes with clinical and public-health users. (not stated) |
none | not yet | CS-106 discuss | in the document all mentions on GitHub record | ||
| PC-2487✎ edit📣 feedback | received | Metadata registries Core architects agent |
5.2 Why data foundations determine what AI can deliver §Chapter 5, §5.2 p.106 l.A26.01 anchor: medium |
ICD-11 Foundation graph in AI grounding — Adds the missing explicit ICD-11 example. Does not claim that FHIR is inheren…ICD-11 Foundation graph in AI grounding — Adds the missing explicit ICD-11 example. Does not claim that FHIR is inherently flat, that all grounding requires a graph, or that the Foundation supplies clinical recommendations. Evidence: WHO ICD API data model (https://icd.who.int/docs/icd-api/APIDoc-Version2/); FHIR complex code systems (https://hl7.org/fhir/R4/terminologies.html#Complex). The final sentence requires checking applicable rights, without asserting unverified future licence provisions. Suggested revision: Insert paragraph: Governed semantic content can also be represented as knowledge graphs: entities have persistent, resolvable identifiers and explicit relationships, with use-specific classifications derived from the underlying content. The ICD-11 Foundation provides a concrete example, including entities with more than one parent and their relationship to statistical linearizations. Entity linking and retrieval can use this content to retain the source statement, identified entity, content release and any derived statistical category. Such traceability complements the provenance and validation controls described above; a graph alone does not establish that a model's interpretation or recommendation is correct. Terminology content is not a complete clinical decision-support knowledge base. Implementations should record the applicable terms for content used in retrieval, model training and generated outputs, and test the accuracy and clinical suitability of these uses. (not stated) |
none | not yet | CS-119 discuss | in the document all mentions on GitHub record | ||
| PC-2488✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
Lifelong Health Record §Lifelong Health Record, §5 p.160 l.A12.01 |
LHR retains precise clinical source — Existing provenance and versioning requirements are useful. These additions make …LHR retains precise clinical source — Existing provenance and versioning requirements are useful. These additions make semantic specificity, historical validity, and derived representations explicit rather than adding a duplicate record system. Suggested revision: Append; retain Required status: Where ICD-11 is used, the LHR shall retain the source concept identifiers, applicable code-system release, complete coded expression, and required clinical context, together with the original clinical statement or a retrievable link to it. A derived statistical category or mapped code shall not overwrite the more detailed source representation. Links between source and derived representations shall be preserved. (not stated) |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-2489✎ edit📣 feedback | received | Metadata registries Clinical agent |
Lifelong Health Record §Lifelong Health Record, §5 p.160 l.A12.02 |
LHR validation and historical validity — Existing provenance and versioning requirements are useful. These additions ma…LHR validation and historical validity — Existing provenance and versioning requirements are useful. These additions make semantic specificity, historical validity, and derived representations explicit rather than adding a duplicate record system. Suggested revision: Append; retain Required status: Validation shall use the declared profile and terminology release, distinguish code or expression validity from clinical coding correctness, and return actionable findings. An identifier valid in the recorded historical release shall not be rejected solely because it has subsequently been retired. Reconciliation and any recoding shall preserve the source record and provenance. (not stated) |
none | not yet | CS-174 discuss | in the document all mentions on GitHub record | ||
| PC-2490✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §1, What it is p.164 l.A13.01 anchor: medium |
TS definition supports native WHO services — Existing wording calls the national service the authority for what concept…TS definition supports native WHO services — Existing wording calls the national service the authority for what concepts mean. National deployment and stewardship should preserve, rather than supersede, WHO's authority over WHO identifiers. Federation is already allowed elsewhere in the draft; this makes the definition consistent with it. Suggested revision: Replace paragraph: The Terminology Service is a governed service that manages or provides controlled access to the semantic content used across the digital health ecosystem. It supports international and national code systems, classifications, terminologies, value sets, and concept maps through published interfaces. These include ICD-11 as both terminology and classification, other WHO-FIC content where applicable, and standards such as SNOMED CT, LOINC, ICPC, and ATC according to their intended roles. Access may be delivered through a national deployment, a conforming local service, or a governed connection to an authoritative publisher service. The implementation shall preserve the content's identifiers, release, meaning, and applicable use rules. It complements the structural definitions in the LIMR and supports direct use of the chosen semantic standard as well as mapping where needed. (not stated) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-2491✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
Terminology Service §Terminology Service, §1, What it is p.164 l.A13.02 anchor: medium |
National stewardship versus international meaning — Existing wording calls the national service the authority for what …National stewardship versus international meaning — Existing wording calls the national service the authority for what concepts mean. National deployment and stewardship should preserve, rather than supersede, WHO's authority over WHO identifiers. Federation is already allowed elsewhere in the draft; this makes the definition consistent with it. Suggested revision: Replace span: The national TS is the authoritative institutional point for national adoption, access, approved profiles, and lifecycle management of semantic content. It does not acquire authority to redefine the meaning of an international publisher's identifiers. Nationally governed additions and implementation choices shall be distinguishable from international content, with change requests routed through the relevant maintenance process. This national governance function distinguishes the shared TS capability from a terminology tool used only within one facility or programme. (not stated) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-2492✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, Architecture placement p.164 l.A27.01 anchor: medium |
TS relationship to cross-cutting semantic governance — Section 3.4.5, printed pp. 57–58 (PDF 68–69), distinguishes gove…TS relationship to cross-cutting semantic governance — Section 3.4.5, printed pp. 57–58 (PDF 68–69), distinguishes governance from runtime services and gives governance a cross-registry scope. The two services should not be equated with the whole governance capability. The wording avoids treating the LIMR as exclusively a runtime tool. Suggested revision: Replace that sentence only: Together, the TS and the LIMR provide technical services through which governed semantic content is made available; they operate within the broader cross-cutting Semantic Governance Infrastructure described in section 3.4.5. (not stated) |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-2493✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §2 p.165 l.A14.01 anchor: medium |
Governed international releases and permitted national content — Unqualified “local modifications of ICD” can imply per…Governed international releases and permitted national content — Unqualified “local modifications of ICD” can imply permissions the architecture cannot confer. Technical import capability is not itself a licence breach: distinguish unchanged international content, authorised extensions and separately identified additions. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time; verify the terms in force at publication. ICD-11 Reference Guide (https://icdcdn.who.int/icd11referenceguide/en/refguide.pdf), §1.6.4, supports international comparability and governed maintenance. Suggested revision: Replace paragraph: International terminology and classification content is updated through its publisher's maintenance process. National adoption should distinguish published international releases, authorised extensions where the relevant standard permits them, and separately governed national value sets or annotations. Changes should undergo clinical, classification, and informatics review, with explicit release selection, impact assessment, and transition arrangements. Local deployment must not be treated as permission to redefine international content. (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2494✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §2 p.165 l.A18.01 anchor: medium |
Managed access does not transfer licence rights — A managed service cannot grant rights absent from the applicable term…Managed access does not transfer licence rights — A managed service cannot grant rights absent from the applicable terms. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time, separately to content and software; verify the terms in force at publication. Translations, mappings and supplementary metadata require source-specific treatment. See C037; unpublished draft agreements are not substituted for operative terms. Suggested revision: Replace bullet: • A managed access service can support compliance with the applicable terms of each content source. Central access does not itself remove obligations applying to individual users, applications, redistribution, or particular uses. (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2495✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §3 p.165 l.A14.02 anchor: medium |
Source integrity in code-system management — Unqualified “local modifications of ICD” can imply permissions the archite…Source integrity in code-system management — Unqualified “local modifications of ICD” can imply permissions the architecture cannot confer. Technical import capability is not itself a licence breach: distinguish unchanged international content, authorised extensions and separately identified additions. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time; verify the terms in force at publication. ICD-11 Reference Guide (https://icdcdn.who.int/icd11referenceguide/en/refguide.pdf), §1.6.4, supports international comparability and governed maintenance. Suggested revision: Replace bullet: – Code system management. Storage or governed access and lifecycle management of concepts, identifiers, designations, properties, relationships, and releases, including graph-structured content with persistent, resolvable entity identifiers and typed relationships. International content shall remain attributable to its publisher. National and local code systems, authorised extensions, and clearly identified supplementary metadata shall be governed separately and used within the applicable standard's rules and licence. (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2496✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §3 p.166 l.A18.05 anchor: medium |
Translation authority and concept identity — A managed service cannot grant rights absent from the applicable terms. Ap…Translation authority and concept identity — A managed service cannot grant rights absent from the applicable terms. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time, separately to content and software; verify the terms in force at publication. Translations, mappings and supplementary metadata require source-specific treatment. See C037; unpublished draft agreements are not substituted for operative terms. Suggested revision: Append qualification: Use official language releases where available; distinguish locally supplied designations from publisher-approved translations and obtain any authorisation required by the applicable terms. Preserve the language-independent concept identity and identify the language and source of each designation. (not stated) |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2497✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
Terminology Service §Terminology Service, §3 p.166 l.A18.02 anchor: medium |
Source-specific content and software licences — A managed service cannot grant rights absent from the applicable terms.…Source-specific content and software licences — A managed service cannot grant rights absent from the applicable terms. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time, separately to content and software; verify the terms in force at publication. Translations, mappings and supplementary metadata require source-specific treatment. See C037; unpublished draft agreements are not substituted for operative terms. Suggested revision: Replace bullet: – Licensing management. Record and implement the applicable terms for all managed content and software, including attribution, permitted uses, access, redistribution, modifications, translations, and mappings. Maintain a clear distinction between the licence for a terminology or classification and the licence for the software that exposes it. Do not assume that a single institutional access point confers rights on every consumer. (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2498✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §3 p.166 l.A17.01 anchor: medium |
WHO-hosted and local publisher-service access — The draft already provides for federation; the correction makes the WHO…WHO-hosted and local publisher-service access — The draft already provides for federation; the correction makes the WHO option visible and prevents compliance from being judged solely by a particular server's storage model. Evidence: WHO API local deployment (https://icd.who.int/docs/icd-api/ICDAPI-LocalDeployment/). Suggested revision: Replace bullet: – Federation and alignment with international sources. Governed access to, synchronisation with, or reference to content from WHO and other international terminology authorities. For ICD-11, an implementation may use the WHO-hosted API or an appropriate local deployment, with the release, language, supported functions, availability arrangements, and update process declared. Local proposals shall be routed to the publisher's maintenance process; national deployment shall preserve the international source's identity and meaning. (not stated) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-2499✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §5 p.167 l.A14.03 anchor: medium |
Import does not authorise ICD modification — Unqualified “local modifications of ICD” can imply permissions the archite…Import does not authorise ICD modification — Unqualified “local modifications of ICD” can imply permissions the architecture cannot confer. Technical import capability is not itself a licence breach: distinguish unchanged international content, authorised extensions and separately identified additions. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time; verify the terms in force at publication. ICD-11 Reference Guide (https://icdcdn.who.int/icd11referenceguide/en/refguide.pdf), §1.6.4, supports international comparability and governed maintenance. Suggested revision: Replace sentence; retain other text and Required status: Import shall preserve international identifiers, meaning, attribution, and release information. It shall distinguish local code systems and authorised extensions from the unmodified international source; technical import capability does not authorise modification or redistribution of that source. (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2500✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, §5 p.168 l.A16.01 |
Separate identifier and expression validation — The draft should permit an ICD-11-native pathway and avoid equating a v…Separate identifier and expression validation — The draft should permit an ICD-11-native pathway and avoid equating a vocabulary match with correct classification. These are proposed implementation controls, not claims that a particular FHIR operation performs all these checks. Suggested revision: Append; retain Required status: The response shall distinguish identifier existence, value-set membership, release validity, and any expression constraints actually checked. For ICD-11, validation shall not treat the independent existence of stem and extension codes as sufficient evidence that their combination is permitted. Unsupported checks shall be reported explicitly. Clinical coding accuracy requires the relevant documentation and rules in addition to terminology validation. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2501✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §5 p.169 l.A16.02 |
Mapping only when needed; classify under appropriate rules — The draft should permit an ICD-11-native pathway and avoid…Mapping only when needed; classify under appropriate rules — The draft should permit an ICD-11-native pathway and avoid equating a vocabulary match with correct classification. These are proposed implementation controls, not claims that a particular FHIR operation performs all these checks. Suggested revision: Append; retain Required status: Translation shall be requested only where a different representation is needed. It shall not be a prerequisite for data already coded in the agreed standard. Results shall retain source and target releases, mapping provenance, direction, applicability conditions, and the asserted relationship, including unmatched or non-equivalent results. ICD-11 statistical derivation shall use the applicable classification and selection rules; it shall not be assumed to be equivalent to a generic concept-map lookup. Derived results shall remain linked to the original expression. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2502✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §5 p.169 l.A18.06 |
Translation qualification in functional requirement — A managed service cannot grant rights absent from the applicable …Translation qualification in functional requirement — A managed service cannot grant rights absent from the applicable terms. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time, separately to content and software; verify the terms in force at publication. Translations, mappings and supplementary metadata require source-specific treatment. See C037; unpublished draft agreements are not substituted for operative terms. Suggested revision: Append same qualification as A18.05; retain Recommended status: Use official language releases where available; distinguish locally supplied designations from publisher-approved translations and obtain any authorisation required by the applicable terms. Preserve the language-independent concept identity and identify the language and source of each designation. (not stated) |
none | not yet | CS-276 discuss | in the document all mentions on GitHub record | ||
| PC-2503✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
Terminology Service §Terminology Service, §5 p.169–170 l.A18.03 |
Licence-compliance requirement — A managed service cannot grant rights absent from the applicable terms. Apply the publ…Licence-compliance requirement — A managed service cannot grant rights absent from the applicable terms. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time, separately to content and software; verify the terms in force at publication. Translations, mappings and supplementary metadata require source-specific treatment. See C037; unpublished draft agreements are not substituted for operative terms. Suggested revision: Replace whole cell; retain Required status: Licence compliance. The TS shall maintain source-specific licence and access metadata and implement the controls required by the applicable terms. It shall document responsibilities for the service operator and consuming systems, preserve attribution and source identifiers, and distinguish the permissions applying to original content, translations, mappings, supplementary metadata, and software. Access controls shall be applied where required by the relevant terms. (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2504✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §5 p.170 l.A17.02 |
Federation as a conforming delivery arrangement — The draft already provides for federation; the correction makes the W…Federation as a conforming delivery arrangement — The draft already provides for federation; the correction makes the WHO option visible and prevents compliance from being judged solely by a particular server's storage model. Evidence: WHO API local deployment (https://icd.who.int/docs/icd-api/ICDAPI-LocalDeployment/). Suggested revision: Append; retain Recommended status; also apply A17.03 in this cell: Federation shall be assessed as a delivery arrangement for the declared national TS functions. A federation-based implementation shall demonstrate how it meets each applicable mandatory requirement, including continuity during loss of external connectivity where required. It shall not be required to duplicate the entire publisher repository solely to demonstrate that those functions are available. Where a required function is not supplied by the publisher service, the national implementation shall identify and test the component that supplies it. (not stated) |
none | not yet | CS-056 discuss | in the document all mentions on GitHub record | ||
| PC-2505✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §5 p.170 l.A17.03 |
Authorised extensions qualification — The draft already provides for federation; the correction makes the WHO option vi…Authorised extensions qualification — The draft already provides for federation; the correction makes the WHO option visible and prevents compliance from being judged solely by a particular server's storage model. Evidence: WHO API local deployment (https://icd.who.int/docs/icd-api/ICDAPI-LocalDeployment/). Suggested revision: Replace phrase; retain rest of cell and coordinate with A17.02: support for authorised extensions of globally curated content where permitted by the publisher's rules and terms (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2506✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §5 p.170 l.A15.01 |
Native ICD-11 service capability — Existing requirements name generic functions but do not ensure that any offered serv…Native ICD-11 service capability — Existing requirements name generic functions but do not ensure that any offered server actually implements ICD-11's distinctive model and coding workflow. The conditional status avoids requiring every country or every deployed service to implement an unused standard. Evidence: WHO API (https://icd.who.int/docs/icd-api/APIDoc-Version2/), Embedded Coding Tool (https://icd.who.int/docs/icd-api/icd11ect-1.8/EmbeddedCodingTool/), Reference Guide (https://icdcdn.who.int/icd11referenceguide/en/refguide.pdf). Suggested revision: Insert row: Business process = Native classification and terminology support; Status = Required where ICD-11 is included in the implementation’s declared scope: ICD-11 terminology and classification support. Where ICD-11 is selected, the TS, directly or through a declared integrated service, shall support the WHO content model needed by the use case. This includes distinguishing Foundation entities from MMS categories; resolving their identifiers and releases; providing available designations, definitions, relationships, and coding guidance; and preserving complete expressions and their applicable postcoordination constraints. The implementation shall identify which validation and coding-assistance functions it supplies and which are supplied by an integrated WHO tool or other validated component. An implementation used for statistical coding shall apply the relevant ICD-11 rules; a code lookup alone shall not be represented as complete coding support. National conformance documentation shall specify the supported content, release, language, interfaces, and tested functions. A connection to WHO services or a local deployment may satisfy the relevant functions when it meets the same conformance, availability, and governance requirements. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2507✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §5, conformance note p.170 l.A15.02 |
Conformance-note count — Existing requirements name generic functions but do not ensure that any offered server actuall…Conformance-note count — Existing requirements name generic functions but do not ensure that any offered server actually implements ICD-11's distinctive model and coding workflow. The conditional status avoids requiring every country or every deployed service to implement an unused standard. Evidence: WHO API (https://icd.who.int/docs/icd-api/APIDoc-Version2/), Embedded Coding Tool (https://icd.who.int/docs/icd-api/icd11ect-1.8/EmbeddedCodingTool/), Reference Guide (https://icdcdn.who.int/icd11referenceguide/en/refguide.pdf). Suggested revision: Replace phrase when A15.01 and A15.03 are adopted: eight respects (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2508✎ edit📣 feedback | received | Metadata registries WHO agent |
Terminology Service §Terminology Service, §5, conformance note p.171 l.A15.03 |
Conformance-note description of new capability — Existing requirements name generic functions but do not ensure that an…Conformance-note description of new capability — Existing requirements name generic functions but do not ensure that any offered server actually implements ICD-11's distinctive model and coding workflow. The conditional status avoids requiring every country or every deployed service to implement an unused standard. Evidence: WHO API (https://icd.who.int/docs/icd-api/APIDoc-Version2/), Embedded Coding Tool (https://icd.who.int/docs/icd-api/icd11ect-1.8/EmbeddedCodingTool/), Reference Guide (https://icdcdn.who.int/icd11referenceguide/en/refguide.pdf). Suggested revision: Append item (8); coordinate with A15.01–A15.02: (8) native ICD-11 terminology and classification support is required where ICD-11 is in the declared implementation scope; its implementation functions are tested separately from generic terminology operations. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2509✎ edit📣 feedback | received | Metadata registries agent |
Terminology Service §Terminology Service, Governance p.171 l.A11.02 |
Classification expertise on governance committee — The existing example frames expertise around mappings “to” standards…Classification expertise on governance committee — The existing example frames expertise around mappings “to” standards. Direct capture and correct classification use require additional named responsibilities. Suggested revision: Add the exact phrase to the list, alongside technical terminology experts: classification and clinical coding specialists (not stated) |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2510✎ edit📣 feedback | received | Metadata registries WHO agent, medium |
Terminology Service §Terminology Service, Governance p.171 l.A18.04 |
Institutional licensing responsibilities — A managed service cannot grant rights absent from the applicable terms. Appl…Institutional licensing responsibilities — A managed service cannot grant rights absent from the applicable terms. Apply the published WHO terms of use for ICD-11 content and software (https://icd.who.int/en/docs/ICD11-license.pdf), as revised from time to time, separately to content and software; verify the terms in force at publication. Translations, mappings and supplementary metadata require source-specific treatment. See C037; unpublished draft agreements are not substituted for operative terms. Suggested revision: Replace whole item: (4) Licensing obligations. Governance should identify the applicable terms, accountable parties, and recurring costs for each selected content source and software component. WHO's published ICD-11 content and software terms should be documented alongside those of other suppliers. Free access or a royalty-free software licence should not be described as permission to alter the international classification. Licence compliance should be monitored throughout deployment and exchange. (not stated) |
none | not yet | CS-277 discuss | in the document all mentions on GitHub record | ||
| PC-2511✎ edit📣 feedback | received | WHO Metadata registries agent |
Terminology Service §Terminology Service, Governance p.171 l.A25.02 |
Reporting conformance and ICD release adoption — Adds the reporting consequence to release governance. An adopted ICD r…Reporting conformance and ICD release adoption — Adds the reporting consequence to release governance. An adopted ICD revision and an annual content release are different; this does not make the newest API release immediately mandatory or impose ICD statistical obligations on every WHO-FIC member. Evidence: WHO Nomenclature Regulations 1967 (https://www.who.int/publications/m/item/who-nomenclature-regulations-1967); WHA72.15 (https://apps.who.int/gb/ebwha/pdf_files/WHA72/A72_R15-en.pdf). Coordinate with A05.01. Suggested revision: Append; retain existing release-testing and transition provisions: For ICD-based statistical reporting, this coordination should identify the applicable ICD revision, release policy, coding rules and transition arrangements needed to meet the Member State's reporting obligations. Proposed changes to WHO content should be routed through WHO's maintenance process. National adoption of a new release should be tested and documented, preserving the reproducibility of earlier reports. (not stated) |
none | not yet | CS-178 #19 | in the document all mentions on GitHub record | ||
| PC-2512✎ edit📣 feedback | received | Metadata registries agent |
Logical Information Model Repository §Logical Information Model Repository, Architecture placement p.172 l.A27.02 anchor: medium |
LIMR relationship to cross-cutting semantic governance — Aligns the component sheet with the cross-cutting capability d…LIMR relationship to cross-cutting semantic governance — Aligns the component sheet with the cross-cutting capability definition on printed pp. 57–58 (PDF 68–69). The PDF already spells DPI-H correctly across a line break; no separate typo correction is needed. Suggested revision: Replace that clause; retain the following TS/LIMR role explanation: Together with the TS, the LIMR provides technical services within the broader cross-cutting Semantic Governance Infrastructure described in section 3.4.5 (not stated) |
none | not yet | CS-066 discuss | in the document all mentions on GitHub record | ||
| PC-2513✎ edit📣 feedback | received | Metadata registries WHO agent |
Logical Information Model Repository §Logical Information Model Repository, §5 p.176 l.A19.01 |
Binding strength and complete expression handling — Binding strength and expression handling must be declared, rather t…Binding strength and complete expression handling — Binding strength and expression handling must be declared, rather than inferred from a permitted-value list. Evidence: FHIR coding and binding rules (https://hl7.org/fhir/R4/terminologies.html) and WHO FHIR interface documentation (https://icd.who.int/docs/icd-api/ICDAPI-FHIR-Support/). The WHO FHIR interface is under active development; an implementation relying on it must declare its FHIR version, release coverage, publication status and tested operations at implementation. See C033 for the dated status check and R4/R5 compatibility distinction. Suggested revision: Append; retain Required status: Each binding shall identify its strength, intended use, code-system namespace, and applicable release policy, in addition to the value-set identifier and version. For ICD-11 content, profiles shall specify the representation of Foundation identifiers, MMS codes, and complete postcoordinated expressions where applicable. Components of one expression shall not be presented as unrelated diagnoses or as equivalent alternative codings. The profile shall specify how source text, context, and any separately derived statistical or mapped representation are linked. Where a base profile permits alternative coding, any national restriction shall be explicit and justified for the use case. (not stated) |
none | not yet | CS-179 discuss | in the document all mentions on GitHub record | ||
| PC-2514✎ edit📣 feedback | received | Metadata registries Clinical agent, medium |
Computable Decision Support Engine §Computable Decision Support Engine, §3 p.183 l.A20.01 anchor: medium |
Direct ICD-11 input to decision support — Establishes a primary clinical use without claiming that ICD-11 itself is a c…Direct ICD-11 input to decision support — Establishes a primary clinical use without claiming that ICD-11 itself is a complete decision-support knowledge base. This is a design recommendation consistent with the WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub). Suggested revision: Insert paragraph: Decision logic may reference ICD-11 concepts and expressions directly where they represent the information required by the rule. The rule package shall identify the terminology release, relevant clinical context, and tested interpretation of any postcoordination. It shall not require a SNOMED CT intermediate solely to consume ICD-11-coded data. Terminology services supply identified meaning and applicable relationships; the clinical recommendation, drug knowledge, inference logic, and validation of the decision remain separately governed responsibilities. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2515✎ edit📣 feedback | received | Metadata registries Financial systems WHO agent, medium |
Benefits Package Registry §Benefits Package Registry, §4 p.201 l.A21.01 anchor: medium |
WHO-FIC content for benefits definitions — WHO-FIC should be represented by its substantive domains, rather than ICD-11…WHO-FIC content for benefits definitions — WHO-FIC should be represented by its substantive domains, rather than ICD-11 being its only visible member. The qualification prevents an unsupported claim that a classification itself supplies tariffs, a grouper, or all billing detail. Evidence: WHO clinical documentation hub (https://www.who.int/standards/classifications/clinician-documentation-hub). Suggested revision: Replace bullet: • The Terminology Service provides the identified clinical and service concepts used in benefit definitions. These may include ICD-11 for diagnoses, ICHI for health interventions, and ICF for functioning-related criteria, where selected and supported by the implementation. The registry shall identify the applicable releases and distinguish these concepts from national service items, tariffs, product identifiers, eligibility rules, and claims-grouping logic. Links between these representations shall be explicit and governed. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2516✎ edit📣 feedback | received | Metadata registries WHO agent |
Health Management Information System §Health Management Information System, §4 p.212 l.A22.01 anchor: medium |
Clinical-to-statistical HMIS pathway — The existing “capture once” principle is strong; its classification-aware mechan…Clinical-to-statistical HMIS pathway — The existing “capture once” principle is strong; its classification-aware mechanism is missing. This is the most direct place to operationalise the supplied data-continuity paper without claiming that reuse needs no rules or information beyond terminology. Suggested revision: Insert paragraph: Where the source record is coded directly in ICD-11, the HMIS should reuse that representation and derive the required statistical output using the selected MMS release and applicable morbidity or mortality rules. It should retain traceability from the output to the original clinical statement, including any more detailed Foundation concept or postcoordinated expression. Where source data uses another terminology, the mapping and classification process should be identified separately, with unresolved cases and loss of detail visible. A single coded diagnosis is not, by itself, a complete case definition, episode definition, denominator, or reporting rule. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2517✎ edit📣 feedback | received | Metadata registries WHO agent |
Health Management Information System §Health Management Information System, §5 p.214 l.A22.03 anchor: medium |
Validate historical data against its source release — The existing “capture once” principle is strong; its classificati…Validate historical data against its source release — The existing “capture once” principle is strong; its classification-aware mechanism is missing. This is the most direct place to operationalise the supplied data-continuity paper without claiming that reuse needs no rules or information beyond terminology. Suggested revision: Replace final clause: and should flag unrecognised codes or inconsistencies with the declared release for review. Historical codes shall be assessed against the release recorded with the source, rather than rejected solely because they are deprecated in a later release. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2518✎ edit📣 feedback | received | Metadata registries WHO agent |
Health Management Information System §Health Management Information System, §5 p.214 l.A22.02 anchor: medium |
Classification and derivation metadata for indicators — The existing “capture once” principle is strong; its classifica…Classification and derivation metadata for indicators — The existing “capture once” principle is strong; its classification-aware mechanism is missing. This is the most direct place to operationalise the supplied data-continuity paper without claiming that reuse needs no rules or information beyond terminology. Suggested revision: Append; retain Required status: For classification-based outputs, this metadata shall include the classification release, applicable selection and aggregation rules, and lineage from source clinical statements to derived results. Recalculation under a later release or rule set shall be distinguishable from the original reported result. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2519✎ edit📣 feedback | received | Metadata registries WHO agent |
Public Health Surveillance Platform §Public Health Surveillance Platform, §4 p.222 l.A23.01 anchor: medium |
Direct ICD-11 use with distinct surveillance case rules — Extends the direct ICD-11 route to a major downstream user wh…Direct ICD-11 use with distinct surveillance case rules — Extends the direct ICD-11 route to a major downstream user while avoiding the unsafe inference that a diagnosis code alone establishes a confirmed surveillance case. The draft already addresses WHO and IHR reporting later on the same page; those passages should be retained. Suggested revision: Replace Terminology Service paragraph: The Terminology Service enables consistent interpretation of disease concepts, pathogen identifiers, clinical findings, and other coded inputs to surveillance. ICD-11-coded diagnoses and relevant postcoordinated detail may be consumed directly where they satisfy the surveillance use case, without a mandatory intermediate terminology conversion. The PHSP shall separately govern the case definition, evidence and laboratory requirements, time window, classification of suspected or confirmed cases, and reporting rules. Terminology updates shall trigger impact assessment; they shall not silently change a case definition or retrospectively reinterpret historical cases. Original clinical and laboratory evidence, coding releases, and derivation rules shall remain traceable. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2520✎ edit📣 feedback | received | Metadata registries WHO agent |
Public Health Surveillance Platform §Appendix D.1, TS and LIMR tools p.231 l.A24.01 anchor: medium |
WHO ICD API and local deployment example — Appendix D supplies named SNOMED-oriented and generic servers, but omits WHO…WHO ICD API and local deployment example — Appendix D supplies named SNOMED-oriented and generic servers, but omits WHO's own relevant services. This is a straightforward, verifiable correction. These tools are not claimed to be a complete national governance platform or an LIMR. API documentation (https://icd.who.int/docs/icd-api/APIDoc-Version2/), local deployment (https://icd.who.int/docs/icd-api/ICDAPI-LocalDeployment/), FHIR interface status (https://icd.who.int/docs/icd-api/ICDAPI-FHIR-Support/), Embedded Coding Tool (https://icd.who.int/docs/icd-api/icd11ect-1.8/EmbeddedCodingTool/). Suggested revision: Insert first WHO tools bullet; place A24.02 immediately after it: • WHO ICD API and local deployments — WHO services exposing ICD-11 Foundation and MMS content, identifiers, releases, search, and coding-related information. The API can be accessed through WHO-hosted services or suitable local deployments, including operation without a continuous external connection. It provides a concrete implementation route for an ICD-11-based semantic service. Implementers should declare the supported content, release, language, and operations. The separately documented WHO FHIR interface is under active development; implementations relying on it should declare its FHIR version, release coverage, publication status and tested operations at the time of implementation. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2521✎ edit📣 feedback | received | Metadata registries WHO agent |
Public Health Surveillance Platform §Appendix D.1, TS and LIMR tools p.231 l.A24.02 anchor: medium |
WHO Coding Tool and Embedded Coding Tool example — Appendix D supplies named SNOMED-oriented and generic servers, but o…WHO Coding Tool and Embedded Coding Tool example — Appendix D supplies named SNOMED-oriented and generic servers, but omits WHO's own relevant services. This is a straightforward, verifiable correction. These tools are not claimed to be a complete national governance platform or an LIMR. API documentation (https://icd.who.int/docs/icd-api/APIDoc-Version2/), local deployment (https://icd.who.int/docs/icd-api/ICDAPI-LocalDeployment/), FHIR interface status (https://icd.who.int/docs/icd-api/ICDAPI-FHIR-Support/), Embedded Coding Tool (https://icd.who.int/docs/icd-api/icd11ect-1.8/EmbeddedCodingTool/). Suggested revision: Insert second WHO tools bullet; retain existing tool entries: • WHO ICD-11 Coding Tool and Embedded Coding Tool — tools supporting selection of ICD-11 concepts and applicable coding detail within clinical applications. An implementation should select the appropriate coding workflow and retain its resulting identifiers and expressions. A simplified search interface should not be represented as providing the full medical-coding workflow. (not stated) |
none | not yet | CS-278 #17 | in the document all mentions on GitHub record | ||
| PC-2522✎ edit📣 feedback | received | WHO Metadata registries agent, medium |
E Appendix E: Health Goals to DPI Mapping §Appendix E, Goal 1 — Build Trusted Data Foundations p.236 l.A25.04 anchor: medium |
Goal 1 realisation in Appendix E — This is the second location in reviewer A25.01, separated for allocation. The origin…Goal 1 realisation in Appendix E — This is the second location in reviewer A25.01, separated for allocation. The original paragraph expressly says Goal 1 has no mapping of its own; the reviewer's proposed “first row” therefore cannot be used as an anchor. Preserves the shared-foundation explanation while making B02.01 and A22.01 operational. See A07.01 for the legal sources. Suggested revision: Insert paragraph after the Goal 1 explanation; no Goal 1 mapping table exists: For mortality and morbidity statistics, this shared foundation supports a traceable pathway from clinical documentation and death certification to ICD coding and reporting under the applicable WHO Nomenclature Regulations and transition arrangements. The interfaces described in “Integration Interfaces with Foundational DPI” (§4.3.4) connect certification, registration and statistical responsibilities; the Terminology Service supports the declared ICD content and coding functions; the Health Management Information System supports statistical derivation; and the Public Health Surveillance Platform applies its separately governed surveillance and reporting rules. These responsibilities should be allocated and tested across the relevant components and national authorities. (not stated) |
none | not yet | CS-225 discuss | in the document all mentions on GitHub record | ||
| PC-2523✎ edit📣 feedback | received | Core architects agent, low |
unplaced |
HWF sections to be reviewed:1.5 health workforce goal (page 32)2.4.1 how each health goal is articulated (page 49)Appen…HWF sections to be reviewed:1.5 health workforce goal (page 32)2.4.1 how each health goal is articulated (page 49)Appendix C Health workforce registry (page 146)Appendix E: 2 support a capable well-distributed health workforce (page 247) WHO Health Workforce Dept, (not stated) |
none | not yet | none | all mentions on GitHub record | ||
| PC-2524✎ edit📣 feedback | received | Editorial agent, medium |
unplaced |
Note: page numbers are slightly different.Note: page numbers are slightly different. WHO Health Workforce Dept, (not stated) |
none | not yet | none | all mentions on GitHub record | ||
| PC-2525✎ edit📣 feedback | received | Core architects agent, medium |
4.2.2 A Phased Implementation Approach anchor: low |
Important to highlight this and elaborate the phased implementation approach further to make it more practical for coun…Important to highlight this and elaborate the phased implementation approach further to make it more practical for country uptake. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-246 discuss | in the document all mentions on GitHub record | ||
| PC-2526✎ edit📣 feedback | received | Editorial agent, medium |
Glossary anchor: low |
Please include these terms in the Glossary.Please include these terms in the Glossary. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-130 discuss | in the document all mentions on GitHub record | ||
| PC-2527✎ edit📣 feedback | received | Editorial agent, low |
1.1 About the Reference Architecture for health Digital Public Infrastructure (DPI-H) Guidance anchor: medium |
Global strategy on digital health 2020-2027. Geneva: World Health Organization; 2025. https://iris.who.int/handle/10665…Global strategy on digital health 2020-2027. Geneva: World Health Organization; 2025. https://iris.who.int/handle/10665/383924 WHO Health Workforce Dept, (not stated) |
none | not yet | CS-005 discuss | in the document all mentions on GitHub record | ||
| PC-2528✎ edit📣 feedback | received | Core architects WHO agent, low |
1.5 The Seven Priority Health Sector Goals anchor: medium |
Would be good to articulate how these seven priority health sector goals were conceptualized and validated, either in t…Would be good to articulate how these seven priority health sector goals were conceptualized and validated, either in the main text itself or in a separate annex WHO Health Workforce Dept, (not stated) |
none | not yet | CS-023 discuss | in the document all mentions on GitHub record | ||
| PC-2529✎ edit📣 feedback | received | Core architects agent, low |
1.5.1 The Health Sector Goals anchor: medium |
notion of equitable distribution (link to subnational, skill mix,...)notion of equitable distribution (link to subnational, skill mix,...) WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2530✎ edit📣 feedback | received | Core architects agent, low |
1.5.1 The Health Sector Goals |
The document might improve the presentation of the system approach in which instruments with specfic and independent go…The document might improve the presentation of the system approach in which instruments with specfic and independent goals act together. The second goal speak to capable and well-distributed health workforce while HRHIS are sometimes used for such health goals, but also very often to comply with labour rights in the first place (accreditation, CPD, salary, pension,...). WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2531✎ edit📣 feedback | received | WHO Core architects agent, medium |
1.5.1 The Health Sector Goals anchor: low |
It would be good to better align with NHWA and health labour market framework which try to minimise any imbalance in th…It would be good to better align with NHWA and health labour market framework which try to minimise any imbalance in the HLM. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2532✎ edit📣 feedback | received | Core architects Financial systems agent, low |
1.5.1 The Health Sector Goals anchor: medium |
Health workers should be individually identifiable and verifiable, deployed where they are needed, paid reliably, and s…Health workers should be individually identifiable and verifiable, deployed where they are needed, paid reliably, and supported to maintain and extend their competencies across the course of their careers, considering their HR admin related factors (long absences, admin actions etc) WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2533✎ edit📣 feedback | received | Core architects agent, medium |
1.5.1 The Health Sector Goals anchor: medium |
Payroll and HR notes such admin actions and long leaves may be captured elsewhere. Or are we suggesting the HWF registr…Payroll and HR notes such admin actions and long leaves may be captured elsewhere. Or are we suggesting the HWF registry accounts for this as well? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2534✎ edit📣 feedback | received | Core architects agent, low |
1.5.1 The Health Sector Goals anchor: medium |
Education qualifications and professional licensesEducation qualifications and professional licenses WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2535✎ edit📣 feedback | received | Core architects WHO agent, low |
1.5.1 The Health Sector Goals anchor: medium |
This seems to be developed from the health workers' perspective. It would also be worth including the health system's p…This seems to be developed from the health workers' perspective. It would also be worth including the health system's perspective - "Every country should ensure that the right number of trained health and care personnel with the right skills are in the right place at the right time to cater to population health needs". WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2536✎ edit📣 feedback | received | Core architects agent, low |
1.5.1 The Health Sector Goals anchor: low |
At the national level, health system planners and policymakers should have the information that enables them to track t…At the national level, health system planners and policymakers should have the information that enables them to track the number of ‘active’ health workers, ensure their equitable distribution and thus improve health workforce and health service planning. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2537✎ edit📣 feedback | received | Core architects agent, medium |
1.5.1 The Health Sector Goals anchor: low |
The HWF registry must comply with exitsing data confidentiality and data privacy lawsThe HWF registry must comply with exitsing data confidentiality and data privacy laws WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2538✎ edit📣 feedback | received | Core architects agent, low |
1.5.1 The Health Sector Goals anchor: medium |
health practitioner regulatorshealth practitioner regulators WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2539✎ edit📣 feedback | received | Core architects WHO Metadata registries agent, low |
1.5.1 The Health Sector Goals anchor: low |
To align to NHWA, there is a distinction between health workers licensed to practice, professionally active, and practi…To align to NHWA, there is a distinction between health workers licensed to practice, professionally active, and practising. Several system could capture those mutually useful information.. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2540✎ edit📣 feedback | received | Core architects agent, low |
1.5.1 The Health Sector Goals anchor: medium |
planning, distribution and retention.planning, distribution and retention. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2541✎ edit📣 feedback | received | Core architects agent, medium |
1.5.1 The Health Sector Goals anchor: low |
Sub goals could be articulated as 2.1 Identity and credentials for each health worker established. The credentials shou…Sub goals could be articulated as 2.1 Identity and credentials for each health worker established. The credentials should be linked to any other existing systems such as payroll, licensing, national identifications systems etc2.2 Equitable deployment and distribution enabled.2.3 Reliable and timely remuneration. Payroll systems to be linked and synced with HWF Registry2.4 Continuous competency and development Qualifications, continuing professional development, and licensing status are tracked over a worker's career.2.5 Safety and accountability. Patients, payers, and regulators can trust that a practitioner's registration and licence status is accurate and current — protecting against fraud in payroll, and against patients receiving care from unlicensed or improperly credentialed practitioners. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2542✎ edit📣 feedback | received | Editorial Clinical agent, low |
1.5.1 The Health Sector Goals |
current, computable and can be updated periodically as and when the standard of care evolves for a certain condition.current, computable and can be updated periodically as and when the standard of care evolves for a certain condition. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2543✎ edit📣 feedback | received | Editorial agent, low |
1.5.1 The Health Sector Goals anchor: medium |
capabilities rather than capability? This would be different for each disease/ health condition.capabilities rather than capability? This would be different for each disease/ health condition. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2544✎ edit📣 feedback | received | Editorial agent, low |
1.5 The Seven Priority Health Sector Goals anchor: low |
what does this mean?what does this mean? WHO Health Workforce Dept, (not stated) |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2545✎ edit📣 feedback | received | WHO Core architects agent, medium |
1.5.1 The Health Sector Goals |
These are 2 of the key public health challenges of our time. Why are we focussed solely on these and not on the others …These are 2 of the key public health challenges of our time. Why are we focussed solely on these and not on the others - vaccine hesitancy, NCDs, AMR, environemental pollution, etc?Suggest to revise this goal to make it focussed on holistic public health, covering the spectrum of health promotion, disease prevention, health protection, and surveillance. This will then cover all the major public health challenges, including emergency preparedness and response. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2546✎ edit📣 feedback | received | Core architects WHO agent, low |
1.5.1 The Health Sector Goals |
Surveillance data, analytical tools and coordination mechanisms to trigger and track response activities are required f…Surveillance data, analytical tools and coordination mechanisms to trigger and track response activities are required for other public health challenges too WHO Health Workforce Dept, (not stated) |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2547✎ edit📣 feedback | received | Editorial agent, medium |
2.4 Methodology: Mapping Health Goals to DPI-H anchor: medium |
What does "consume" mean, in this context?What does "consume" mean, in this context? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-035 discuss | in the document all mentions on GitHub record | ||
| PC-2548✎ edit📣 feedback | received | Editorial agent, medium |
2.4.1 How each health goal is articulated anchor: medium |
IMHO, all the goals should be presented in the main text (perhaps as separate boxes or sub-sections) in addition to the…IMHO, all the goals should be presented in the main text (perhaps as separate boxes or sub-sections) in addition to their mapping in Appendix E. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-034 discuss | in the document all mentions on GitHub record | ||
| PC-2549✎ edit📣 feedback | received | Editorial agent |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing anchor: low |
This sentence feels like classic AI language: "A does not do B; instead it does C".This sentence feels like classic AI language: "A does not do B; instead it does C". WHO Health Workforce Dept, (not stated) |
none | not yet | CS-035 discuss | in the document all mentions on GitHub record | ||
| PC-2550✎ edit📣 feedback | received | Editorial Financial systems agent, low |
2.4.2 Worked example: Advance Efficient and Equitable Health Financing anchor: medium |
Where can we access this?Where can we access this? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-035 discuss | in the document all mentions on GitHub record | ||
| PC-2551✎ edit📣 feedback | received | Core architects agent, medium |
unplaced |
It must be noted that countries would have mixed level of maturity in their data sources and it would depend on the pur…It must be noted that countries would have mixed level of maturity in their data sources and it would depend on the purpose, some not for population's health. For example for health workforce, it can be helpful to rely on census data or labour force survey data conducted by national statistical office; another example are data from national pension scheme which has potential great utility (was utilised successfully in some country for HRHIS). Although these are not really great for health purpose, although it would be almost impossible to modify them or have any weight on their governance as their main purpose is totally scalar, there can be attempts to improve the interoperability to make use of these data into a HRHIS. I am not seeing in the report this subtlety that national infrastructure would build on pieces which purpose vary drastically. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | all mentions on GitHub record | ||
| PC-2552✎ edit📣 feedback | received | Core architects agent, medium |
unplaced |
I saw several references to private sector, it would be good to have a specific section on the private sector to show t…I saw several references to private sector, it would be good to have a specific section on the private sector to show the specific elements to consider for it. From my understanding, this is (with military, worth the thinking as well) the most difficult element to incorporate in any digital architecture. It has its specificity and rational that could be worth highlighting. Why would private sector join, and even contribute to funding an infrastructure which is design for public purpose? The private sector (military sector is the same) logic needs to be analysed, discussed, and incorporate so that there are mutual benefits. The data protection would have particular components to consider both for avoiding the private sector to make a commercial use of the architecture, but also for the public sector to use an architecture with private sector to conduct retaliation on some elements such as dual practice. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-117 discuss | all mentions on GitHub record | ||
| PC-2553✎ edit📣 feedback | received | WHO Core architects agent, low |
Health Workforce Registry |
@KUNJUMEN, Teena please review this section.@KUNJUMEN, Teena please review this section. WHO Health Workforce Dept, (not stated) |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2554✎ edit📣 feedback | received | Editorial Core architects agent, low |
Health Workforce Registry |
When you say LMS, I think of the traditional institution-based LMS that contains a name wise list of all students, thei…When you say LMS, I think of the traditional institution-based LMS that contains a name wise list of all students, their details such as name, age, sex, residence, year of registration, course registered, scores in various subjects/modules, year of graduation, etc. Is this what you intend, or are you thinking of something at a more macro level? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2555✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
You have presented this as two systems but in reality the situation is much more complex.HRIS - may be a single system …You have presented this as two systems but in reality the situation is much more complex.HRIS - may be a single system for the public sector, sometimes there may be multiple systems even in the public sector (eg. (a) in countries with federal systems, each state may have their own HRIS, (b) MoH owned and operated health facilities may have a single HRIS, while those health facilities operated by other departments/Ministries (eg. defence, labour, railways, etc) may have their own HRIS). Meanwhile, private sector may be heavily fragmented, each hospital operating their own HRIS or perhaps clinics doing it all offline using facility registers.LMS - again, this could be extremely fragmented, with each health workforce education and training institution having their own LMS. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2556✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry anchor: medium |
It would be good to describe the characteristics of this registry - governance mechanisms, coverage (eg. how to get dat…It would be good to describe the characteristics of this registry - governance mechanisms, coverage (eg. how to get data from private sector), key stakeholders that need to be involved, how to ensure that the registry is continually updated, etc WHO Health Workforce Dept, (not stated) |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-2557✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
We need to also list what the Regsitry is NOT. Either here or elsewhere. Building on my earlier comments that the HWF r…We need to also list what the Regsitry is NOT. Either here or elsewhere. Building on my earlier comments that the HWF registry will be consumed/linked/synced by other systems such as payroll etc. Suggested text«The registry is distinct from operational systems that manage (i) employment and payroll, HR actions records (ii) learning records on CPD trainings etc » WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2558✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Worth mentioning here that a national HRHIS is a system of systems - it includes HWF registry, HRIS, LMS (covering the …Worth mentioning here that a national HRHIS is a system of systems - it includes HWF registry, HRIS, LMS (covering the gamut of pre-service and continuing education), payroll, etc. It also involves diversification and triangulation with multiple data sources, such as Census, labour force surveys, etc. So in order to monitor the entire aspects of the health labour market, a health workforce registry in itself is not sufficient. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2559✎ edit📣 feedback | received | WHO Financial systems Core architects agent, low |
Health Workforce Registry |
can also provide information for certain indicators in Module 3 (finance and expenditure), if linked with payroll syste…can also provide information for certain indicators in Module 3 (finance and expenditure), if linked with payroll systems (eg. total expenditure on compensation of health workforce, average entry-level wages and salaries).Wage data can also be used to do pay gap analysis (eg. gender gap, gap between public and private sector, gap between provinces of a country, etc) WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2560✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Note that all health workers may not need to be either registered or licensed to practice (eg. those who are associate…Note that all health workers may not need to be either registered or licensed to practice (eg. those who are associate professionals, personal care workers, health management and support personnel, etc). WHO Health Workforce Dept, (not stated) |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-2561✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
At which point in time is a record created in the HWF registry- on graduation or emplyoment. Depending on the the occup…At which point in time is a record created in the HWF registry- on graduation or emplyoment. Depending on the the occupation maybe only after licensure. What about foreign trained health workers? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-2562✎ edit📣 feedback | received | No agent |
unplaced |
excellentexcellent WHO Health Workforce Dept, (not stated) |
none | not yet | none | all mentions on GitHub record | ||
| PC-2563✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: low |
Many of them work in the informal sector. Need to be careful and be more specificMany of them work in the informal sector. Need to be careful and be more specific WHO Health Workforce Dept, (not stated) |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-2564✎ edit📣 feedback | received | Editorial Core architects agent, low |
Health Workforce Registry |
what does this term "non-intelligent identifier" mean? do we have any reference to support this recommendation?what does this term "non-intelligent identifier" mean? do we have any reference to support this recommendation? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-155 discuss | in the document all mentions on GitHub record | ||
| PC-2565✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry |
I am proposing a text to be included «A ‘non-intelligent identifier’ carries no embedded meaning (no encoded district,…I am proposing a text to be included «A ‘non-intelligent identifier’ carries no embedded meaning (no encoded district, cadre, or facility code) and does not change when a worker's name, employer, or location changes. This keeps the identifier stable over a worker's whole career rather than requiring reassignment whenever an underlying attribute changes. » WHO Health Workforce Dept, (not stated) |
none | not yet | CS-155 discuss | in the document all mentions on GitHub record | ||
| PC-2566✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
Since not all health workers may require registration, how will the identifier be assigned?Since not all health workers may require registration, how will the identifier be assigned? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-2567✎ edit📣 feedback | received | Editorial agent, low |
Health Workforce Registry anchor: low |
What does this mean?What does this mean? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-285 discuss | in the document all mentions on GitHub record | ||
| PC-2568✎ edit📣 feedback | received | Metadata registries WHO agent |
Health Workforce Registry |
The language needs to aligned with NHWA approach. Countries are encouraged to create a national classification of occup…The language needs to aligned with NHWA approach. Countries are encouraged to create a national classification of occupations that can be mapped to ISC0-08. Refer to Annex 2 in NHWA Handbook https://www.who.int/publications/i/item/9789240081291 WHO Health Workforce Dept, (not stated) |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-2569✎ edit📣 feedback | received | Metadata registries Core architects agent, medium |
Health Workforce Registry anchor: medium |
note that ISCO is revised every 20 years, next update will be published in 2028, so suggest replacing "ISCO-08" with ju…note that ISCO is revised every 20 years, next update will be published in 2028, so suggest replacing "ISCO-08" with just "ISCO". WHO Health Workforce Dept, (not stated) |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-2570✎ edit📣 feedback | received | Metadata registries agent |
Health Workforce Registry |
Suggest revising this to - "Classification of health workers using national standard classification of occupations that…Suggest revising this to - "Classification of health workers using national standard classification of occupations that is aligned with ISCO....." WHO Health Workforce Dept, (not stated) |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-2571✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Include an option for relicensure of an expired licenseInclude an option for relicensure of an expired license WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2572✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
perhaps add a "not applicable" option for those occupations that do not require a license to practice?perhaps add a "not applicable" option for those occupations that do not require a license to practice? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2573✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: medium |
Is this through linkage with the LMS/education and training database? or will this be done manually?Is this through linkage with the LMS/education and training database? or will this be done manually? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2574✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Deisgn the field to capture/link to Place of training - national trained /foreign trainedDeisgn the field to capture/link to Place of training - national trained /foreign trained WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2575✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: low |
How will this be updated on a regular basis?How will this be updated on a regular basis? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-154 discuss | in the document all mentions on GitHub record | ||
| PC-2576✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
For core attributes on licensing and verification: seems like HWF registry must be closely linked to the licensing body…For core attributes on licensing and verification: seems like HWF registry must be closely linked to the licensing body, regulatory bodies. Brings back the question - is HWF registry the entry point for health worker digital record or is the Licensing body database/registry or any other? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-154 discuss | in the document all mentions on GitHub record | ||
| PC-2577✎ edit📣 feedback | received | WHO agent, medium |
Health Workforce Registry |
We don't have any indicator on qualifications in the NHWA. There is an indicator on graduates but that will be extracte…We don't have any indicator on qualifications in the NHWA. There is an indicator on graduates but that will be extracted from the LMS/education and training database WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2578✎ edit📣 feedback | received | Core architects Financial systems agent, medium |
Health Workforce Registry anchor: medium |
can also support analytics on inflows and outflows of health workers.if linked with payroll, can also support analytics…can also support analytics on inflows and outflows of health workers.if linked with payroll, can also support analytics for remuneration. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2579✎ edit📣 feedback | received | Core architects WHO agent, low |
Health Workforce Registry |
Note that reporting on NHWA is a byproduct, the original purpose is that quality HWF is generated that can be used to i…Note that reporting on NHWA is a byproduct, the original purpose is that quality HWF is generated that can be used to inform national HWF planning and policymaking.Suggest revising this to "enabling Ministries of Health to generate accurate and reliable health workforce data that can be used to inform national planning and policymaking processes as well as meet their national and international reporting obligations using registry data". WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2580✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
this would also need to be updated periodically to ensure that newly established facilities are included in the registr…this would also need to be updated periodically to ensure that newly established facilities are included in the registry. Sometimes. facility type may also change (eg. a primary health centre may be upgraded to a hospital, etc) WHO Health Workforce Dept, (not stated) |
none | not yet | CS-149 discuss | in the document all mentions on GitHub record | ||
| PC-2581✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
Not that not all health workers may have (or need) a facility affiliation (eg. community health workers, personal care …Not that not all health workers may have (or need) a facility affiliation (eg. community health workers, personal care workers, environmental and occupational health inspectors, etc) WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2582✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Not true in all cases- Private practice, currently unemployed - between jobs. I expect HWF Registry to be the master da…Not true in all cases- Private practice, currently unemployed - between jobs. I expect HWF Registry to be the master database of all health workers- currently employed and actice, or currently unemployed but licensed to practice WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2583✎ edit📣 feedback | received | Metadata registries agent, medium |
Health Workforce Registry |
With strong alignment with National Classification of Occupations, developed by MoH, and employed by National Statistic…With strong alignment with National Classification of Occupations, developed by MoH, and employed by National Statistical Offices for the Labour force surveys, populations census etc WHO Health Workforce Dept, (not stated) |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-2584✎ edit📣 feedback | received | Editorial agent, low |
Health Workforce Registry anchor: low |
Please elaborate this bullet?Please elaborate this bullet? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-285 discuss | in the document all mentions on GitHub record | ||
| PC-2585✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
These data sources are relevant only for those occupations that require registration/license to practice/both. What abo…These data sources are relevant only for those occupations that require registration/license to practice/both. What about other occupations? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-2586✎ edit📣 feedback | received | Editorial agent |
Health Workforce Registry |
What do these terms mean - HWWF and HWRF?What do these terms mean - HWWF and HWRF? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-194 discuss | in the document all mentions on GitHub record | ||
| PC-2587✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
This is more a process question. For health workers that need a license to practice, are the sytems expected to be lin…This is more a process question. For health workers that need a license to practice, are the sytems expected to be linked with data exchange? Assuming the record creation is initiated by the workers itself, how will the licensing which is a mandatory filled be updated/verified. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-154 discuss | in the document all mentions on GitHub record | ||
| PC-2588✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Note that this may differ across occupations - more attributes for health professionals, etc.Note that this may differ across occupations - more attributes for health professionals, etc. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-2589✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: low |
might be also good to consider interoperability of systems to enable automatic data exchangemight be also good to consider interoperability of systems to enable automatic data exchange WHO Health Workforce Dept, (not stated) |
none | not yet | CS-154 discuss | in the document all mentions on GitHub record | ||
| PC-2590✎ edit📣 feedback | received | Editorial Metadata registries agent, medium |
Health Workforce Registry anchor: medium |
We discourage the use of "cadre" as it has a military connotation. Instead, we recommend using "occupation" or "job tit…We discourage the use of "cadre" as it has a military connotation. Instead, we recommend using "occupation" or "job title". WHO Health Workforce Dept, (not stated) |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-2591✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
Not applicable option should be available for those occupations that don't require licensing.Not applicable option should be available for those occupations that don't require licensing. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2592✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Some countries may offer a lifelong license that does not need renewal.Some countries may offer a lifelong license that does not need renewal. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2593✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: medium |
facility type and facility ownershipfacility type and facility ownership WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2594✎ edit📣 feedback | received | Core architects WHO agent, medium |
Health Workforce Registry anchor: medium |
Suggestion to include: Data elements needed for HWF planning are based on different data elements some that are obtaine…Suggestion to include: Data elements needed for HWF planning are based on different data elements some that are obtained from other registry that look at service demands etc. the WISN tool for example, requires the workload /service demand estimates. Could this be incorporated in the relevant registry, if possible.https://www.who.int/tools/wisn WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2595✎ edit📣 feedback | received | Editorial agent, low |
Health Workforce Registry anchor: low |
What is this referring to?What is this referring to? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-285 discuss | in the document all mentions on GitHub record | ||
| PC-2596✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Data confidentiality and privacy of health workers needs to be includedData confidentiality and privacy of health workers needs to be included WHO Health Workforce Dept, (not stated) |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-2597✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Data confidentiality and privacy of health workers needs to be includedData confidentiality and privacy of health workers needs to be included WHO Health Workforce Dept, (not stated) |
none | not yet | CS-160 discuss | in the document all mentions on GitHub record | ||
| PC-2598✎ edit📣 feedback | received | Editorial agent, low |
Health Workforce Registry anchor: low |
What does this mean?What does this mean? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-285 discuss | in the document all mentions on GitHub record | ||
| PC-2599✎ edit📣 feedback | received | Editorial agent, medium |
Health Workforce Registry anchor: low |
What does this mean? Could add a footnote.What does this mean? Could add a footnote. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-285 discuss | in the document all mentions on GitHub record | ||
| PC-2600✎ edit📣 feedback | received | Metadata registries agent |
Health Workforce Registry anchor: medium |
Countries are expected to apply the National classification of occupations (NCOs) which should be aligned with ISCO-08 …Countries are expected to apply the National classification of occupations (NCOs) which should be aligned with ISCO-08 to facilitate sub-regional, regional and global comparison and data use. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-2601✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
To add: Place of training (national trained /foreign trained) for each record of specialisationTo add: Place of training (national trained /foreign trained) for each record of specialisation WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2602✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Though this is not applicable to all health occupations, but in the case of Specialists it is a mandatory field (condit…Though this is not applicable to all health occupations, but in the case of Specialists it is a mandatory field (conditional mandatory) WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2603✎ edit📣 feedback | received | Core architects Metadata registries agent, low |
Health Workforce Registry anchor: medium |
SpecialisationSpecialisation WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2604✎ edit📣 feedback | received | Metadata registries Core architects agent |
Health Workforce Registry |
Standard national occupation classification code that would be ideally be aligned with ILO’s International Standard Cla…Standard national occupation classification code that would be ideally be aligned with ILO’s International Standard Classification of Occupations (ISCO) codes and mapped with the WHO health worker classification framework….. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-2605✎ edit📣 feedback | received | Core architects agent |
Health Workforce Registry anchor: medium |
To add: Provision for multiple licensesTo add: Provision for multiple licenses WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2606✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: medium |
Employment institution ownershipEmployment institution ownership WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2607✎ edit📣 feedback | received | Editorial agent |
Health Workforce Registry |
Change ‘emplyment type’ in Employment StatusChange ‘emplyment type’ in Employment Status WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2608✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: medium |
The health practitioner regulator…..The health practitioner regulator….. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2609✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
NOTE: not every health worker may have a license (eg. a personal care worker, or a community health worker).NOTE: not every health worker may have a license (eg. a personal care worker, or a community health worker). WHO Health Workforce Dept, (not stated) |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-2610✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: medium |
These 4 data elements may not be relevant for all occupations.These 4 data elements may not be relevant for all occupations. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-152 discuss | in the document all mentions on GitHub record | ||
| PC-2611✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
NOTE: In some countries or for some occupations, the license may not have an expiry date.NOTE: In some countries or for some occupations, the license may not have an expiry date. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2612✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: low |
Even so, Mandatory field is needed to understand and document the mechanismEven so, Mandatory field is needed to understand and document the mechanism WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2613✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
These could be considered as 4 sub elements under Qualification details. For some health workers, they may have more th…These could be considered as 4 sub elements under Qualification details. For some health workers, they may have more than 1 degree (eg. undergraduate {eg. bachelors} degree details; postgraduate {eg. masters} degree details; doctorate/fellowship details, etc), so would need to capture information for each degree. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-157 discuss | in the document all mentions on GitHub record | ||
| PC-2614✎ edit📣 feedback | received | Metadata registries WHO agent, low |
Health Workforce Registry |
In NHWA, we call this “facility ownership” and we have 3 categories - public, private for profit, private not for profi…In NHWA, we call this “facility ownership” and we have 3 categories - public, private for profit, private not for profit. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2615✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry anchor: medium |
These are very different elements.These are very different elements. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-285 discuss | in the document all mentions on GitHub record | ||
| PC-2616✎ edit📣 feedback | received | Metadata registries agent, low |
Health Workforce Registry |
What is the difference between this and the “occupation code” mentioned above?What is the difference between this and the “occupation code” mentioned above? WHO Health Workforce Dept, (not stated) |
none | not yet | CS-156 discuss | in the document all mentions on GitHub record | ||
| PC-2617✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
These should be dynamic elements captured over time with dates. As the registry needs to capture changes over time, wit…These should be dynamic elements captured over time with dates. As the registry needs to capture changes over time, with dates, in term of contract type, in education (as people can get certifications), entrance, exists, reentrance, leaves ... WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2618✎ edit📣 feedback | received | Core architects agent, low |
Health Workforce Registry |
This phenomenon is commonly known as "dual practice". However, in some countries, the 2nd or 3rd practice may be an inf…This phenomenon is commonly known as "dual practice". However, in some countries, the 2nd or 3rd practice may be an informal arrangement between the health worker and the employer and hence this may be difficult to measure. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2619✎ edit📣 feedback | received | Core architects WHO agent, medium |
Health Workforce Registry |
Maybe we can also mention "type of entry" somewhere. This would be the number of new health workers entering the countr…Maybe we can also mention "type of entry" somewhere. This would be the number of new health workers entering the country's health labour market in a year and could be computed by the number of new unique records. This could also be disaggregated by domestic trained and foreign trained, in alignment with NHWA indicators. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-153 discuss | in the document all mentions on GitHub record | ||
| PC-2620✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
Field could be: Date of first employment, MandatoryField could be: Date of first employment, Mandatory WHO Health Workforce Dept, (not stated) |
none | not yet | CS-158 discuss | in the document all mentions on GitHub record | ||
| PC-2621✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
How do you ensure the cross sectoral governance, in particular with role of private sector? As a contributor, the priva…How do you ensure the cross sectoral governance, in particular with role of private sector? As a contributor, the private sector would have access to health workers data, but on the other hand you do not want the private sector to be able to use this as a shopping list for hiring staff from public sector. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-2622✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
As it currently reads as very horizontale, the notion of multilayered information should be mentionned somewhere. The l…As it currently reads as very horizontale, the notion of multilayered information should be mentionned somewhere. The legal component is also missing from the governance to accomodate with national laws on data protection (such as GDPR in Europe). WHO Health Workforce Dept, (not stated) |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-2623✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry |
Also need to talk about governance for the overall HRHIS ("system of systems") here.Also need to talk about governance for the overall HRHIS ("system of systems") here. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-2624✎ edit📣 feedback | received | Core architects agent, medium |
Health Workforce Registry anchor: medium |
this would be multistakeholder and multisectoral, since health workforce is a multisectoral issue, requiring the involv…this would be multistakeholder and multisectoral, since health workforce is a multisectoral issue, requiring the involvement of MOH, Labour, Finance, Education, national statistical office, licensing bodies, education bodies, professional associations, etc. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-161 discuss | in the document all mentions on GitHub record | ||
| PC-2625✎ edit📣 feedback | received | WHO Metadata registries Editorial agent, low |
E Appendix E: Health Goals to DPI Mapping |
Some initial comments for this mapping:2.1 first column - revise to "high-quality workforce data for planning, deployme…Some initial comments for this mapping:2.1 first column - revise to "high-quality workforce data for planning, deployment and shortage mapping"2.2 - can include some description on the lines of "Payroll data can inform reporting on NHWA indicators on expenditure for compensation, entry-level wages and salaries, and pay gaps".2.3 "cross-border verification informed by the WHO Global Code of Practice on International Recruitment" I don't the Code recommends any such verification, need to cross-check and revise language.2.4 last column - replace "ISCO or competency taxonomies" with "ISCED taxonomy"Reference 1 should be 2023, not 2024.Reference 3 is now being updated, will be published soon. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-021 #20 | in the document all mentions on GitHub record | ||
| PC-2626✎ edit📣 feedback | received | Editorial agent, medium |
E Appendix E: Health Goals to DPI Mapping anchor: medium |
The Goals and sub goals in the above sections are not fully aligned. Need to relist/reorder/reword, to allow a smooth r…The Goals and sub goals in the above sections are not fully aligned. Need to relist/reorder/reword, to allow a smooth reading flow for the user. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-220 discuss | in the document all mentions on GitHub record | ||
| PC-2627✎ edit📣 feedback | received | Clinical agent, low |
E Appendix E: Health Goals to DPI Mapping anchor: low |
these need to be flexible and dynamic (eg. different treatment options based on family history, comorbidities, other on…these need to be flexible and dynamic (eg. different treatment options based on family history, comorbidities, other ongoing medications, etc) WHO Health Workforce Dept, (not stated) |
none | not yet | CS-019 discuss | in the document all mentions on GitHub record | ||
| PC-2628✎ edit📣 feedback | received | Core architects agent, low |
1.5.1 The Health Sector Goals anchor: medium |
Also need to talk about strengthening this further by applying AI/ML for signal identification and risk stratificationAlso need to talk about strengthening this further by applying AI/ML for signal identification and risk stratification WHO Health Workforce Dept, (not stated) |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2629✎ edit📣 feedback | received | Core architects WHO agent, low |
E Appendix E: Health Goals to DPI Mapping anchor: low |
The system should also be able to create aggregate reports based on these client records (eg. service statistics report…The system should also be able to create aggregate reports based on these client records (eg. service statistics reports, disease burden reports, civil registration and vital statistics reports, public health monitoring reports, that can be drilled down across levels (national/subnational/facility level). WHO Health Workforce Dept, (not stated) |
none | not yet | CS-225 discuss | in the document all mentions on GitHub record | ||
| PC-2630✎ edit📣 feedback | received | Core architects WHO agent, medium |
E Appendix E: Health Goals to DPI Mapping |
Suggest revising this goal to "Strengthen health systems resilience" then the goal can be stated as "anticipate public …Suggest revising this goal to "Strengthen health systems resilience" then the goal can be stated as "anticipate public health threats early enough......". This would then ensure that the goal has a holistic public health lens rather than the narrow focus solely on two public health challenges. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-020 discuss | in the document all mentions on GitHub record | ||
| PC-2631✎ edit📣 feedback | received | Core architects WHO Clinical agent, low |
Public Health Surveillance Platform anchor: low |
This is also important for immunization (eg. VPD surveillance. AEFI surveillance), maternal and newborn health (MPDSR),…This is also important for immunization (eg. VPD surveillance. AEFI surveillance), maternal and newborn health (MPDSR), etc WHO Health Workforce Dept, (not stated) |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2632✎ edit📣 feedback | received | Core architects agent, medium |
Public Health Surveillance Platform anchor: medium |
This platform could be used for surveillance of all public health events, not just epidemics and climate events.This platform could be used for surveillance of all public health events, not just epidemics and climate events. WHO Health Workforce Dept, (not stated) |
none | not yet | CS-185 discuss | in the document all mentions on GitHub record | ||
| PC-2633✎ edit📣 feedback | received | editorial | not routed | unplaced §Apllicable to the full document p.NA l.Images containing text |
Low resolution does not allow a proper analysis of the pictures.Low resolution does not allow a proper analysis of the pictures. Suggested revision: Consider providing the image in SVG format, as the text in the current bitmap image cannot be properly analysed due to limited resolution. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | all mentions on GitHub record | |
| PC-2634✎ edit📣 feedback | received | editorial | not routed | §Appendix p.NA l.NA anchor: medium |
The distinction between the content provided in the appendices is unclear. While appendices typically contain supplemen…The distinction between the content provided in the appendices is unclear. While appendices typically contain supplementary information, Appendix C appears to contain normative content, whereas Appendix D appears to be illustrative. This may create uncertainty about the intended status and purpose of the information included in each appendix. Suggested revision: Clarify the nature and purpose of the content in each appendix, explicitly indicating whether it is normative, informative, or illustrative. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2635✎ edit📣 feedback | received | general | not routed | Glossary §Glossary p.2 l.Registry anchor: medium |
Centralisation is an implementation topology and should not form part of the definition of a registry. The current defi…Centralisation is an implementation topology and should not form part of the definition of a registry. The current definition is also inconsistent with the Guidance itself: p. 54 states that registries are authoritative and canonical constructs while “whether they are realised centrally, in a federated manner, or as a hybrid remains a national implementation choice.” The glossary should reflect the same topology-neutral principle. Suggested revision: Replace with: “Registry: A governed and authoritative information capability that captures, stores and maintains, or provides authoritative access to, the identifiers and core attributes of health facilities, health service users, health products and/or the health workforce using a predefined canonical minimum dataset. A registry may be implemented centrally, in a federated manner or through a hybrid architecture, provided that authoritative sources, stewardship, identity resolution and conformance requirements are clearly defined.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2636✎ edit📣 feedback | received | technical | not routed | 1.4 DPI-H Principles §1.4 DPI-H Principles p.21 l.414-416 |
The objective of preventing strategic dependency and vendor lock-in is appropriate. However, standards themselves shoul…The objective of preventing strategic dependency and vendor lock-in is appropriate. However, standards themselves should not necessarily remain “under national control.” Digital-health interoperability depends extensively on internationally maintained standards and, in some jurisdictions, binding supranational specifications. The distinction should be between public control over the architecture and its implementation, on the one hand, and ownership/governance of individual interoperability standards, on the other. For EU Member States, the EHDS Regulation establishes a common legal and technical framework for electronic health data and EHR-system interoperability at Union level. A formulation requiring national control over standards could therefore be interpreted inconsistently with both the open-standards principle elsewhere in the Guidance and binding regional frameworks. Suggested revision: Replace with: “Countries should retain effective public control, accountability and strategic autonomy over critical DPI-H capabilities and should avoid unacceptable dependencies on individual external providers. Applicable standards and governance may be nationally defined or established through international or supranational frameworks, provided that public authorities retain effective decision-making, assurance and accountability over their implementation.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2637✎ edit📣 feedback | received | technical | not routed | 1.5 The Seven Priority Health Sector Goals §1.5 The Seven Priority Health Sector Goals p.21 l.429-432 |
The objective of eliminating unnecessary duplicate data entry is strongly supported, but “captured once” should not be …The objective of eliminating unnecessary duplicate data entry is strongly supported, but “captured once” should not be formulated as an unconditional rule applying to all health information. Clinical information may legitimately be generated, verified or recorded by different actors at different points in a care pathway, and provenance must be preserved. The principle is most directly applicable to authoritative reference data and to avoiding duplicate administrative/reporting collection. Similarly, data collected for one purpose cannot automatically be made available “wherever it is needed”; reuse remains subject to lawfulness, purpose limitation, data minimisation and other applicable safeguards. Finally, “consent and permissions” should not imply that consent is always the relevant legal basis. Under the GDPR, health data may also be processed for healthcare delivery and management, substantial public interest, public health, research and statistical purposes under defined conditions. Suggested revision: Replace with: “At the heart of the architecture is the principle that, where an authoritative source exists and reuse is appropriate, data should not need to be captured repeatedly solely because systems are unable to exchange it. Authoritative data should be governed well and made available for lawful, necessary and proportionate uses under the applicable access, data-protection and governance framework.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2638✎ edit📣 feedback | received | technical | not routed | 2.3 DPI-H Reference Architecture Design Principles §2.3 DPI-H Reference Architecture Design Principles p.35 l.355-357 |
Consent should not be characterised as the primary universal mechanism governing health-data processing.Consent should not be characterised as the primary universal mechanism governing health-data processing. This conflates three distinct concepts: the legal basis authorising processing; individual/data-subject rights; and consent as one particular legal or governance mechanism. Article 9(2) GDPR expressly provides multiple grounds for processing health data besides explicit consent, including substantial public interest, healthcare provision and management, public health, and scientific research/statistics. The EHDS Regulation likewise combines individual control with access restrictions and opt-out rights and does not make individual consent a general prerequisite for lawful secondary use. An architecture that operationalises consent as the default authorisation layer could therefore incorrectly constrain healthcare, public-health and statutory secondary-use processing in many jurisdictions. Suggested revision: Replace the second sentence and align the first as follows: “Consent is one mechanism through which individuals may exercise control over health information where consent is applicable under the relevant legal or policy framework. Individual control may also be exercised through rights of access, information, rectification, restriction, objection or opt-out, and through legally defined confidentiality and access safeguards. DPI-H should support technically enforceable consent where required, without assuming that consent is the universal legal basis for access to or processing of health data.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2639✎ edit📣 feedback | received | technical | not routed | 3.1 The architecture description approach §3.1 The architecture description approach p.43 l.Table 3.1 |
The table appears to be incomplete and should include all element types used in the DPI-H reference architecture and th…The table appears to be incomplete and should include all element types used in the DPI-H reference architecture and their corresponding representations. Suggested revision: Add the following elements: Application Function, Application Interaction, Application Interface, Business Role, Business Process, and Grouping element types GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2640✎ edit📣 feedback | received | technical | not routed | 3.1 The architecture description approach §3.1 The architecture description approach p.44 l.Table 3.2 |
The table appears to be incomplete, as it does not include all relationship types used in the DPI-H reference architect…The table appears to be incomplete, as it does not include all relationship types used in the DPI-H reference architecture and what they represent. Suggested revision: Include 'Assignment' and 'Triggering', as they are used in the conformance table and table 3.3 GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2641✎ edit📣 feedback | received | technical | not routed | 3.1 The architecture description approach §3.1 The architecture description approach p.45 l.Figure 3.1 anchor: medium |
The relationship types are not consistent with those defined in the conformance table.The relationship types are not consistent with those defined in the conformance table. Suggested revision: Replace the relation between 'Application Component' and 'Application Fuction' from 'realizes' to 'assigned to'. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2642✎ edit📣 feedback | received | technical | not routed | 3.1 The architecture description approach §3.1 The architecture description approach p.46 l.Table 3.3 |
The relationship types are not consistent with those defined in the ArchiMate metamodel.The relationship types are not consistent with those defined in the ArchiMate metamodel. Suggested revision: Replace the relation between 'Capability' and 'Goal' from 'serving' to 'realization'. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2643✎ edit📣 feedback | received | technical | not routed | 3.4.5 Semantic Governance Infrastructure §3.4 Governance of Digital Health Architectures and DPI-H p.62 l.Section 3.4.5/3.4.6 anchor: medium |
The Guidance currently addresses national governance and then uses “regional governance” principally for multi-country …The Guidance currently addresses national governance and then uses “regional governance” principally for multi-country arrangements, leaving an important governance model insufficiently covered: distribution of responsibilities within a country. Federal, devolved and decentralised health systems may combine shared national infrastructure with autonomous or subnational ownership and service-delivery responsibilities. This is not equivalent to undesirable fragmentation. For example: Spain provides an established implementation pattern: the Interterritorial Council created the Digital Health Commission specifically to support co-governance between the Ministry of Health and the Autonomous Communities and to ensure interoperability across public administrations. The national TSI/CIP-SNS (Tarjeta Sanitaria Individual / Código de identificación de paciente SNS) architecture similarly combines regional databases and management responsibilities with shared national identity and interoperability services. Explicitly addressing multi-level governance would improve the applicability of the Guidance to decentralised countries and would also reinforce the subsidiarity principle already included in Section 3.4.2 Suggested revision: Insert a new subsection immediately before the current Section 3.4.6: “Subnational and multi-level governance. In federal, devolved or otherwise decentralised health systems, legal responsibility, stewardship and operational control may be distributed between national and subnational public authorities. Governance should explicitly define: (i) decision rights at each level; (ii) common national or jurisdiction-wide interoperability and conformance requirements; (iii) capabilities and data remaining under subnational stewardship; (iv) co-governance, coordination and dispute-resolution mechanisms; and (v) accountability across federated nodes. A national DPI-H architecture does not require national ownership or operational control of all underlying systems or data.” Rename existing 3.4.6 “Cross-country and supranational governance considerations.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2644✎ edit📣 feedback | received | editorial | not routed | 3.6.4 Cross-border health data flows §3.6 Interoperability Architecture within DPI-H p.77 l.Footnote 33 anchor: medium |
The existing statement is not necessarily incorrect as a compressed description of Article 105, but it can give readers…The existing statement is not necessarily incorrect as a compressed description of Article 105, but it can give readers the impression that the principal operational EHDS obligations generally take effect in March 2027. The implementation timetable is more differentiated. The European Commission identifies March 2027 primarily as the deadline for several key implementing acts, March 2029 as the point when major primary-use and most secondary-use provisions begin applying, and March 2031 for the second group of priority health-data categories and remaining secondary-use categories. Since the Guidance uses EHDS as a major example of regional interoperability governance, accurately distinguishing the stages of application would help implementers understand the regulatory transition. Suggested revision: Replace with: “Regulation (EU) 2025/327 entered into force on 26 March 2025 and applies progressively. Several key implementing acts are due by March 2027; major primary-use requirements concerning Patient Summaries and ePrescriptions/eDispensations and most secondary-use rules begin to apply from March 2029; further priority data categories and secondary-use provisions apply from March 2031.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2645✎ edit📣 feedback | received | technical | not routed | 3.6.4 Cross-border health data flows §3.6 Interoperability Architecture within DPI-H p.78 l.948-951 |
Consent is not the universal governance mechanism for cross-border processing. Depending on the use case and legal fram…Consent is not the universal governance mechanism for cross-border processing. Depending on the use case and legal framework, processing may be based on statutory healthcare functions, legal obligations or public-interest grounds, while individuals may exercise control through mechanisms such as access restrictions or opt-out rights. The EHDS expressly distinguishes these mechanisms. The Reference Architecture would therefore be more jurisdiction-neutral if it required implementers to establish the lawful basis and applicable individual-control model, rather than presuming a consent model. Suggested revision: Replace with: “The legal basis, applicable individual rights and control mechanisms, access-control rules and other data-governance arrangements for cross-border processing shall be explicit, including consent, restriction or opt-out mechanisms where applicable under the relevant legal framework.” Replace “consent considerations” with “health-specific legal, confidentiality, patient-rights and access-control requirements.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2646✎ edit📣 feedback | received | technical | not routed | 3.7.3 Alignment with IHE profiles §3.7 Conformance and Testing across Architecture and Components p.83 l.1125 |
The sentence appears to mix terminology from different modelling vocabularies, namely ArchiMate (e.g., “Components” and…The sentence appears to mix terminology from different modelling vocabularies, namely ArchiMate (e.g., “Components” and “Services”) and IHE (e.g., “Actors” and “Transactions”), which may create ambiguity. Suggested revision: Consider using terminology consistently with a single vocabulary, or clearly distinguish the ArchiMate and IHE terms where both are intended. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2647✎ edit📣 feedback | received | technical | not routed | 4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3 Profiles and Specifications for Implementation p.94 l.306 309-310 Footnote anchor: medium |
FHIR is appropriately identified as a major framework for modern interoperability, and the proposed amendment does not …FHIR is appropriately identified as a major framework for modern interoperability, and the proposed amendment does not weaken that recommendation. However, a global reference architecture should distinguish FHIR as an interoperability framework from a particular FHIR release. Mature national infrastructures may use different releases during migration, and jurisdiction-specific implementation specifications may define the applicable profiles and versions. The draft itself correctly states that generic FHIR conformance does not guarantee shared meaning and that two valid FHIR implementations can remain semantically inconsistent unless they conform to the same governed information model. A release-neutral formulation would therefore be more consistent with the Guidance's own semantic-interoperability approach and would avoid unnecessary coupling of the architecture to FHIR R5. IMPORTANT: the current proposal in the implementing acts of the EHDS regulation is NOT to use FHIR R5, but a different version. Suggested revision: Retain FHIR as a recommended framework but amend to: “HL7 FHIR is a major recommended framework for implementing standards-based health-data exchange APIs. Conformance should be assessed against the applicable implementation guide, profile, terminology bindings and semantic model. The Reference Architecture should remain neutral regarding the FHIR release unless a specific release is required by an applicable jurisdictional or programme specification, and should accommodate equivalent standards-based implementations and managed migration paths for established infrastructures.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2648✎ edit📣 feedback | received | technical | not routed | 4.3.3 Services and Transactions: FHIR as the Recommended Framework §4.3 Profiles and Specifications for Implementation p.96 l.330 |
It would be helpful to mention that IHE has already profiled some eHealth use cases using the FHIR standard. Including …It would be helpful to mention that IHE has already profiled some eHealth use cases using the FHIR standard. Including this information in this chapter would make readers aware that some use cases have already been defined in terms of services and transactions, which they may be able to leverage or build upon. Suggested revision: In the end of the current paragraph add: "A number of widely-used digital health use-cases are profiled by IHE using the FHIR standard and RESTful APIs. Those profiles constrain FHIR in a way so that the workflows of the use-case can be optimally fulfilled by technical systems and sustainability is maximized (search parameters, content, response, …)1" Add as footnote: 1 See FHIR Implementation Guide Registry (select “authority” as IHE): https://www.fhir.org/guides/registry GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2649✎ edit📣 feedback | received | technical | not routed | 4.3.4 Interoperability Implementation Pathways §4.3 Profiles and Specifications for Implementation p.98 l.382-384 |
The statement that centralised infrastructure inherently provides “stronger” public governance, security or accountabil…The statement that centralised infrastructure inherently provides “stronger” public governance, security or accountability is not topology-neutral and is not demonstrated by the architectural model. Governance strength derives from the allocation and enforcement of decision rights, conformance rules, auditability, security controls and accountability, rather than necessarily from physical or logical centralisation. The Guidance itself states on p. 54 that whether registries are centralised, federated or hybrid is an implementation choice. For exameple, Spain's HCDSNS provides a practical example of a nationally interoperable system in which personal clinical data remain in Autonomous Community databases while national services enable access across the SNS. The proposed wording would therefore preserve the legitimate advantages of centralised implementations without suggesting that federated architectures are intrinsically weaker. Suggested revision: Replace with: “Centralised models. National shared infrastructure may simplify certain common-service, conformance, operational-control and monitoring functions, but can also concentrate operational, availability and cybersecurity risks. Federated and hybrid models can provide equally strong public governance, standards enforcement, security and accountability where common conformance requirements, trust frameworks, audit mechanisms and decision rights are effectively governed. Architectural topology should therefore be selected according to context rather than ranked by presumed governance strength.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2650✎ edit📣 feedback | received | technical | not routed | Client Registry §Appendix C: Client Registry p.116, 119-121 l.112-113 |
Replace with: “compliance with applicable data-protection frameworks, including rights of access, rectification, restri…Replace with: “compliance with applicable data-protection frameworks, including rights of access, rectification, restriction and erasure where legally applicable, subject to statutory retention requirements and applicable healthcare, public-interest, research, archival or legal-claims exceptions.” Apply equivalent qualification to Requirement 19. Suggested revision: The right to erasure is not an unconditional right to delete health records, and the informal expression “right-to-be-forgotten” may obscure this important limitation. Article 17 GDPR itself contains exceptions. Healthcare legislation may additionally impose positive retention duties. Spanish Law 41/2002, for example, requires clinical documentation to be retained for the period appropriate to care and for at least five years after discharge from each care episode, with further preservation for judicial, epidemiological, research and health-system purposes. The Spanish Data Protection Agency consequently states that discharge from care does not permit automatic deletion of the corresponding clinical data. The architecture should implement data-subject rights but should explicitly accommodate statutory record-retention regimes GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2651✎ edit📣 feedback | received | technical | not routed | Client Registry §Appendix C: Client Registry p.116, 120-121 l.110-111 |
The terminology should distinguish pseudonymisation from anonymisation. Under the GDPR, pseudonymisation means processi…The terminology should distinguish pseudonymisation from anonymisation. Under the GDPR, pseudonymisation means processing data so that they cannot be attributed to a specific data subject without additional information; it is a safeguard, but the resulting data remain within the personal-data framework. The phrase “pseudo-anonymisation” is therefore both non-standard and potentially misleading. This distinction is also operationally important under the EHDS: personal electronic health data may be made available in pseudonymised form when anonymous data would be insufficient for an authorised secondary-use purpose, but access remains controlled through a permit and secure processing environment. Suggested revision: Replace “pseudo-anonymisation” / “pseudo-anonymised” throughout with “pseudonymisation” / “pseudonymised”. Add: “Pseudonymised data remain personal data where they can be attributed to an individual through additional information. Pseudonymisation is a technical and organisational safeguard and does not, by itself, establish a legal basis for secondary use. Data that have been rendered genuinely non-identifiable should be described as anonymised.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2652✎ edit📣 feedback | received | technical | not routed | C Appendix C: DPI-H Application Component Descriptions §Appendix C: Client Registry p.119 l.Identity Querie and Retrieval Table. Element 7 anchor: medium |
Returning the entire identifier cross-reference map by default may disclose substantially more information than a reque…Returning the entire identifier cross-reference map by default may disclose substantially more information than a requesting system requires. Identity-resolution functionality can be preserved while applying data-minimisation and least-privilege principles to downstream responses. A clinical application confirming that a patient identifier resolves to the correct person does not necessarily need every foundational, local or programme identifier ever associated with that person. The complete mapping can remain available for authorised master-patient-index or identity-management operations. Suggested revision: Replace the final part with: “…receiving the authorised demographic attributes and identifier mappings necessary for the requesting transaction. Access to a complete identifier cross-reference map shall be restricted to specifically authorised identity-management functions where operationally necessary.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2653✎ edit📣 feedback | received | technical | not routed | Client Registry §Appendix C: Client Registry p.122 l.Data Requirements Table. anchor: medium |
A global Reference Architecture should avoid mandating collection of personal attributes that are not universally neces…A global Reference Architecture should avoid mandating collection of personal attributes that are not universally necessary for identity resolution. Nationality and residence are distinct concepts and should not be represented as a single attribute. A mother's/guardian's name may be highly relevant to newborn identification but is not inherently necessary in every adult record; similarly, address and contact details may support matching in one jurisdiction but be unnecessary in another with a robust persistent identifier. Making such attributes universally mandatory could lead to avoidable collection and synchronisation of personal data. In Spain, the CIP-SNS is unique and lifelong and serves as the linking key between the regional identifiers assigned by different health administrations, allowing identity interoperability while preserving regional databases. This illustrates why the minimum identity dataset should be adapted to the identification architecture. Suggested revision: Revise the dataset classification so that attributes are mandatory only where systematically necessary for the jurisdiction's identity-resolution model. Specifically: (i) separate nationality/citizenship from country/place of residence; (ii) change address, contact information, local identifiers and mother's/guardian's name to Conditional unless needed for the applicable identity-resolution workflow; (iii) replace “where available and consented” for foundational identifiers with “where available, necessary and lawfully permitted under the applicable framework”; and (iv) state that jurisdictions using robust persistent identifiers may use a smaller mandatory demographic matching dataset. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2654✎ edit📣 feedback | received | technical | not routed | Lifelong Health Record §Appendix C: Client Registry p.157, 161 l.105-106; Identity, Access and Consent Element 12 |
The objective-preventing independent, uncoordinated identity silos-is appropriate. However, the current requirement is …The objective-preventing independent, uncoordinated identity silos-is appropriate. However, the current requirement is too prescriptive for federated health systems. Local and regional EHR systems may legitimately maintain operational patient identifiers while a national or shared identity service provides the cross-reference required for interoperability. Requiring the LHR to have no independent identification capability could be interpreted as prohibiting this pattern. Suggested revision: Replace with: “The LHR shall use authoritative identity services to link records reliably to the correct individual. It may retain local, regional or source-system identifiers required for operational use and provenance, provided that these identifiers can be reconciled through the jurisdiction's shared identity framework. The architecture shall not require a single physical Client Registry to be the exclusive operational source of person identification where authoritative identity responsibility is federated.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2655✎ edit📣 feedback | received | technical | not routed | Lifelong Health Record §Appendix C: Lifelong Health Record p.157, 161, 163 l.111; Governance |
The current model risks representing consent as the universal authorisation layer for access to longitudinal health rec…The current model risks representing consent as the universal authorisation layer for access to longitudinal health records. In many public healthcare systems, ordinary professional access for healthcare delivery is based on statutory healthcare functions rather than individual consent to each data-processing operation. The same is true for certain health-system management and public-health activities. Research and secondary use may be governed by separate legal mechanisms. Under the GDPR, healthcare provision/management, public health and research are expressly recognised as possible grounds for processing health data. The architecture should therefore distinguish consent to a clinical intervention, legal basis for processing, professional access authorisation, and individual data-control rights. Suggested revision: Replace the overarching concept with “Lawful access and patient-control governance.” Amend Requirements 13-14 to state: “The LHR shall enforce access according to the applicable legal basis, purpose of processing, authenticated role, professional relationship, statutory access rules and applicable individual-control mechanisms. Consent shall be enforced where consent is the applicable legal or policy mechanism; other mechanisms may include access restrictions, objection or opt-out. Emergency or break-glass access shall operate under predefined lawful conditions and shall be fully audited.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2656✎ edit📣 feedback | received | technical | not routed | C Appendix C: DPI-H Application Component Descriptions §Appendix C: Lifelong Health Record p.161 l.Secondary Use and Integration Table. Element 16 anchor: medium |
“Export” suggests a direct LHR-to-user data-transfer model that is not appropriate for all secondary-use governance fra…“Export” suggests a direct LHR-to-user data-transfer model that is not appropriate for all secondary-use governance frameworks. Under the EHDS, processing for secondary use is permitted only for specified purposes and, in the ordinary access model, is authorised by a health data access body. Personal electronic health data are processed in secure processing environments, and personal data cannot be downloaded from those environments. The Reference Architecture should therefore treat secondary-use infrastructure as a distinct governance layer, rather than assuming that research and analytics platforms directly receive exports from the clinical LHR. This also makes the architecture compatible with federated health-data-space implementations. Suggested revision: Replace with: “Secondary-use data provision. The LHR shall support governed interfaces through which data necessary for legally authorised secondary purposes can be made available to the applicable secondary-use infrastructure. Where the legal framework provides for an access-authorisation body, data permit and/or secure processing environment, person-level data shall be routed through that mechanism rather than exported directly to secondary users or research applications.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2657✎ edit📣 feedback | received | technical | not routed | Health Management Information System §Appendix C: Health Management Information System p.212 l.101-104 |
“De-identified” is legally and technically ambiguous. Removal of direct identifiers does not necessarily make a dataset…“De-identified” is legally and technically ambiguous. Removal of direct identifiers does not necessarily make a dataset anonymous. If individuals remain identifiable through additional information or reasonably available means, the data remain personal data and continue to require an applicable legal basis and safeguards. The Reference Architecture should therefore use the clearer categories of anonymous/anonymised and pseudonymised data or define any broader term precisely. This distinction is particularly important for secondary use: EHDS permits access to pseudonymised personal data when anonymous data are insufficient, but only through its regulated access and secure-processing model. Suggested revision: Replace with: “Provision of mechanisms for authorised secondary use. Anonymous aggregate or anonymised outputs may be made available where appropriate. Pseudonymised or otherwise personal data shall remain subject to the applicable legal basis, access authorisation and security requirements. The term ‘de-identified’ should be used only where its relationship to anonymisation or pseudonymisation is explicitly defined.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2658✎ edit📣 feedback | received | technical | not routed | Health Management Information System §Appendix C: Health Management Information System p.212 l.114-116 |
Reducing duplicate reporting is a sound objective, but defining the LHR as the primary universal source for HMIS data i…Reducing duplicate reporting is a sound objective, but defining the LHR as the primary universal source for HMIS data is too restrictive. Health-system monitoring commonly depends on administrative and statistical datasets that are not, and should not necessarily become, part of a longitudinal clinical record. For example, activity reporting, waiting-list information, healthcare-facility registers, financing data and population-level statistical systems have different purposes, structures and governance from the clinical EHR. Spain's SNS information environment illustrates this multi-source pattern: the Ministry's current treatment inventory separately identifies HCDSNS, RAE-CMBD, BDCAP, SIAE, waiting-list systems, REGCESS, RESNS and BDPP-SNS, among others. The appropriate architectural principle is therefore reuse authoritative data and eliminate unnecessary duplicate capture, rather than require all health-system information to originate in the LHR. Suggested revision: Replace with: “The LHR may be an important source of person-level clinical data for the HMIS. However, HMIS architectures should support multiple governed authoritative sources according to the indicator and use case, including clinical records, administrative and activity datasets, population and disease registries, laboratory systems, surveys, financing systems and other relevant health-information sources. DPI-H should minimise unnecessary duplicate reporting while preserving purpose-specific authoritative datasets and provenance.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2659✎ edit📣 feedback | received | technical | not routed | Public Health Surveillance Platform §Appendix C: Public Health Surveillance Platform p.221 l.162 |
Public-health surveillance cannot generally be reduced to a downstream use of the LHR. Surveillance architectures requi…Public-health surveillance cannot generally be reduced to a downstream use of the LHR. Surveillance architectures require data from multiple sources, including information that may never form part of an individual clinical record. Statutory reporting and surveillance powers may also establish a different lawful-access model from ordinary clinical use. Suggested revision: Replace with: “The LHR may be an important source of person-level clinical information for public-health surveillance, but the PHSP shall support multiple legally authorised data sources appropriate to the surveillance function, including laboratories, mandatory case notifications, disease and population registries, environmental and occupational information, administrative datasets and surveillance-specific systems. Access to identifiable data shall be governed by the statutory public-health legal basis and applicable safeguards, which may differ from the access model governing direct clinical care.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2660✎ edit📣 feedback | received | technical | not routed | C Appendix C: DPI-H Application Component Descriptions §Appendix C: Public Health Surveillance Platform p.226-227 l.Table Data Quality, Governance and Access Control. Element 21 anchor: medium |
The offline-capability requirement is useful, but “central platform” unnecessarily prescribes a topology that conflicts…The offline-capability requirement is useful, but “central platform” unnecessarily prescribes a topology that conflicts with the Guidance's otherwise stated support for centralised, federated and hybrid implementation. Surveillance in decentralised systems may involve regional operational nodes synchronising with national coordination infrastructure without one central platform functioning as the sole operational data store. The requirement concerns reliable synchronisation and continuity, not architectural centralisation, and should therefore remain topology-neutral Suggested revision: Replace “the central platform” with “the designated surveillance platform or authorised synchronisation endpoint(s), which may be centralised, federated or hybrid according to the jurisdiction's architecture.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2661✎ edit📣 feedback | received | technical | not routed | C Appendix C: DPI-H Application Component Descriptions §Appendix C: Public Health Surveillance Platform p.226 l.Governance anchor: medium |
A global Reference Architecture should not assume that a single national public-health authority legally owns or operat…A global Reference Architecture should not assume that a single national public-health authority legally owns or operates all surveillance functions. Public-health competence may be distributed between national and subnational authorities. The critical requirements are coherent standards, coordination, accountability and interoperability. Spain's legal framework is an example: the State Public Health Surveillance Network comprises the Ministry and the health administrations of the Autonomous Communities and Ceuta and Melilla; the Ministry coordinates the network, while Autonomous Communities organise and manage it in their territories, and the Interterritorial Council ensures cohesion and quality. Moreover, public-health processing authorised by law is not appropriately described as an emergency “override” of normal consent, because consent may not be the ordinary legal basis in the first place. Suggested revision: Replace with: “Stewardship should be vested in the competent public-health authority or authorities under the jurisdiction's constitutional and statutory allocation of responsibilities. In decentralised systems, governance should establish clear national-subnational coordination, interoperability, common surveillance standards and accountability while respecting the responsibilities of subnational authorities. Governance should distinguish undesirable programme silos from legitimate multi-level public governance.” Replace the consent sentence with: “Where statutory public-health powers authorise identifiable-data processing without consent, the applicable purpose limitations, necessity and proportionality safeguards, confidentiality requirements, access controls, retention rules and auditing shall be explicitly defined. Emergency provisions should govern additional exceptional access beyond ordinary statutory surveillance powers.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2662✎ edit📣 feedback | received | editorial | not routed | D.2 Country implementation examples §Appendix D: Country implementation examples p.231 l.91 |
Suggestion to include Austria's exampleSuggestion to include Austria's example Suggested revision: Components illustrated: LHR, Terminology Service Austria operates a national eHealth interoperability infrastructure (elga.gv.at), with ELGA serving as the electronic health record system for its citizens. It enables authorized healthcare professionals to securely access relevant health information across healthcare providers and institutions, while the ELGA Portal provides patients with access to their own health data. ELGA is deployed nationwide, connecting virtually all healthcare providers and pharmacies across Austria. ELGA supports the exchange of information such as discharge letters, laboratory and radiology reports, e-Medication, and e-prescriptions, improving continuity of care and patient safety. The ELGA Terminology Service1 provides centrally managed medical terminologies, code systems, value sets, and mappings, ensuring semantic interoperability and consistent interpretation of health information across different IT systems. Add as foonote: 1 ELGA Terminology Service: https://termgit.elga.gv.at/index_en.html GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2663✎ edit📣 feedback | received | editorial | not routed | D.2 Country implementation examples §Appendix D: Country implementation examples p.231 l.91 |
Suggestion to include Canada's exampleSuggestion to include Canada's example Suggested revision: Canada's foundational DPI-H layer is constituted at two levels of government. The metadata registries are provincial and territorial shared infrastructure and vary across provinces: Provincial Client Registries that assign and maintain the personal health number for every person who has received care in the province or serve as an enterprise master patient index, and a Provider and Location Registry as the trusted source for practitioners and care locations. Typically, these services are publicly governed, serve many programmes and clinical systems within the province, and are consumed through published interfaces. The semantic and structural components are national: the Terminology Server, based on Ontoserver, is a high-performance, FHIR-compliant terminology platform accessible via FHIR APIs operated by the national release centre for SNOMED CT, pCLOCD and HL7, maintaining the SNOMED CT Canadian Edition on a fixed cadence release cycle, while pan-Canadian FHIR profiles (CA Core+) and CACDI with its logical data model hold the shared structural definitions. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2664✎ edit📣 feedback | received | technical | not routed | Spain §Appendix D: Country implementation examples p.233 l.153 |
The current three-component classification understates the architectural capabilities illustrated by the Spanish exampl…The current three-component classification understates the architectural capabilities illustrated by the Spanish example. Spain provides a relevant example of a shared identity layer through BDPP-SNS/CIP-SNS; federated clinical-document exchange through HCDSNS; interoperable electronic prescription and dispensation; common semantic/modelling services; and connection to European cross-border services. Reflecting these capabilities would make the case study substantially more useful to implementers because it demonstrates how several foundational and health-specific DPI components can coexist in a decentralised national health system. Suggested revision: Replace with: “Components illustrated: Client Registry / shared identity services; LHR and federated clinical-data exchange; ePrescription/eDispensation interoperability; HMIS and health-information services; LIMR / terminology and semantic services; cross-border health-data exchange.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2665✎ edit📣 feedback | received | technical | not routed | Spain §Appendix D: Country implementation examples p.233 l.154-160 |
The current case study is broadly positive but should be corrected and expanded to describe the architecture accurately…The current case study is broadly positive but should be corrected and expanded to describe the architecture accurately. 1) “SOMSNS” should be corrected to the official name somSNS - Servidor de Objetos de Modelado del Sistema Nacional de Salud. 2) HCDSNS does not itself represent the entirety of the Spanish health-information system; multiple purpose-specific clinical, administrative, registry and statistical information systems contribute to SNS information and monitoring. 3) the case currently omits foundational capabilities that are especially relevant to DPI-H, including BDPP-SNS/CIP-SNS person identification and interoperable electronic prescription. 4) the phrase “regional autonomy over data governance” should reflect the common legal and co-governance framework: Autonomous Community stewardship coexists with national coordination and interoperability agreements. 5) describing the architecture merely as exchange across “seventeen autonomous communities” does not fully reflect SNS-wide arrangements, which also encompass the relevant health administration for Ceuta and Melilla (which have a separate healthcare service called INGESA). Suggested revision: Replace with: “Spain operates a federated, multi-level digital-health architecture across the National Health System (SNS). The Historia Clínica Digital del SNS (HCDSNS) enables citizens and authorised health professionals to access interoperable clinical documents irrespective of the SNS health service in which they were generated, while source personal health data remain in the databases of the Autonomous Communities and INGESA (regional healthcare authority of the cities of Ceuta and Melilla). Shared SNS infrastructure also includes the Protected Population Database and Individual Health Card services, with the unique CIP-SNS linking regional person identifiers; interoperable electronic prescription and dispensation across the SNS; and common semantic resources, including terminology services and somSNS (Servidor de Objetos de Modelado del Sistema Nacional de Salud). National interoperability is governed cooperatively by the Ministry of Health and the Autonomous Communities through the Interterritorial Council and its Digital Health Commission. The SNS health-information environment draws on multiple governed clinical, administrative, registry and statistical sources rather than constituting a single federated dataset. Spain therefore illustrates how common national interoperability services, standards and co-governance can coexist with distributed source systems and subnational stewardship.” GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2666✎ edit📣 feedback | received | general | not routed | Health Facility Registry §Appendix C — Health Facility Registry (see Section 6) p.133 (in relation to page 107) l.Signature-domain table, "Infrastructure attributes" row (see Section 5.3, lines 120–123) anchor: medium |
Remote and online care is mentioned only once in the whole document, on p.133, as a reason to record whether a facility…Remote and online care is mentioned only once in the whole document, on p.133, as a reason to record whether a facility has internet. It is not listed as a component, a service, or an example under any of the seven health goals. The document treats clinical apps as sitting on top of the shared foundation (Section 5.3), which is a fair reason not to make telemedicine its own component. But the shared parts still assume the patient and the health worker are in the same building: the patient is identified at a facility, the record is tied to a facility, and the worker’s credentials are checked at a facility. Remote and store-and-forward care break these assumptions. A patient may join from home, and a specialist may read a scan or photo without ever meeting the patient. The document never checks whether the shared parts still work in these cases. Suggested revision: Add remote and online care as a named example under the health goal it fits best, and use it to test the shared components. State how the record shows who made an entry when a remote specialist reads a case without seeing the patient, how the client registry and consent service identify a patient connecting from home outside any facility, and how the workforce and facility registries confirm a provider’s identity across two facilities during an online consult. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2667✎ edit📣 feedback | received | technical | not routed | Lifelong Health Record §Appendix C — Lifelong Health Record p.162 l.Operational requirement #19 anchor: medium |
Row #19 says the record "shall" work offline. "Shall" means required. But the status beside it says "Recommended", whic…Row #19 says the record "shall" work offline. "Shall" means required. But the status beside it says "Recommended", which means optional. The two do not match. The three comparable rows (Computable Decision Support Engine #25 p.189, Health Management Information System #21 p.216, Public Health Surveillance Platform #21 p.226) say "should" and are marked Recommended, so those are consistent. Only row #19 contradicts itself. Suggested revision: Make the wording and the status agree in row #19: either change "shall" to "should", or change the status to Required. See the next comment for a better option. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2668✎ edit📣 feedback | received | technical | not routed | Lifelong Health Record §Appendix C — LHR, CDSE, HMIS, PHSP p.162, 189, 216, 226 l.Requirements #19, #25, #21, #21 anchor: medium |
All four offline rows say they are meant for remote and low-resource areas, yet all four are only Recommended. In real …All four offline rows say they are meant for remote and low-resource areas, yet all four are only Recommended. In real procurement, anything marked Recommended is usually dropped to save cost, so the feature that matters most for far-flung areas is the easiest one to skip. But making all four Required is also a problem: it would force offline support even on well-connected hospitals that do not need it, and could make the standard too hard to meet for the small local vendors who serve remote areas. Status and setting are being squeezed into one value. Suggested revision: Make offline support Required only where the system will serve areas with weak or no internet, and Recommended elsewhere. WHO SMART Guidelines and FHIR guides already use this "required only if" pattern. Also spell out what "offline" must actually do, because the rows differ: some ask the system to hold full records and sync later (LHR, HMIS), one only asks it to keep working on saved results (CDSE). These are different levels and should be tested differently. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2669✎ edit📣 feedback | received | technical | not routed | 3.4.5 Semantic Governance Infrastructure §3.4.5 (see 3.6.2) p.60 (see 74) l.Lines 452–464 (see 822–827) |
The document lets a country set up its code lists and data-sharing tools first and decide who manages them later, espec…The document lets a country set up its code lists and data-sharing tools first and decide who manages them later, especially in low-resource areas. But another part (Section 3.6.2) says the main reason health systems cannot share data is that everyone changes the standards their own way. So a country could follow the step-by-step advice, go live with no one yet in charge of the standards, and end up with the exact problem the document warns against. Suggested revision: State the minimum that must exist before a country switches on its code lists or data-sharing, even at the earliest stage: one named office in charge, a written log of every change, and a way to warn other systems before a code is removed. Allow the "set up first, govern later" path only once this minimum is in place. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2670✎ edit📣 feedback | received | technical | not routed | 3.4.5 Semantic Governance Infrastructure §3.4.5 p.59–60 (see 61) l.SGI five-category capability table (see lines 469–486, p.61) anchor: medium |
The document lists the jobs involved in managing health standards, but folds one big job inside another. Keeping the "t…The document lists the jobs involved in managing health standards, but folds one big job inside another. Keeping the "translation tables" current, the ones that match local codes to global codes and ICD to SNOMED CT, is constant work with its own reviews and versions. The document raises this as a concern later but never lists it as its own job, so it is easy to under-resource. Suggested revision: Add the upkeep of these translation tables (concept maps) as its own job in the list, covering how they are made, checked, versioned, and kept current when either the local or the global side changes. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2671✎ edit📣 feedback | received | technical | not routed | 2.2.1 What REDDHI is and its foundational core §2.2 / Table 2.2 (see 3.6.2) p.27 (see 74) l.Table 2.2 (see line 827) |
Table 2.2 marks the shared library of agreed data structures (the Logical Information Model Repository) as optional at …Table 2.2 marks the shared library of agreed data structures (the Logical Information Model Repository) as optional at the start, and the component write-up calls it a progressive enabler rather than a prerequisite. But Section 3.6.2 says this same library is what systems are checked against to confirm they are built correctly. If a country skips it early, there is nothing to check against, so the idea of confirming that systems "follow the standard" has no basis yet. Suggested revision: Say what minimum data-structure control a country still needs early on, for example a small set of nationally agreed templates (profiles) to test against, so that checking whether systems follow the standard is not pushed entirely to a later stage. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2672✎ edit📣 feedback | received | technical | not routed | 2.2.1 What REDDHI is and its foundational core §2.3 / Table 2.2 / Appendix C (LHR) p.27, 34–35, 161 l.Table 2.2 (consent row); Section 2.3 p.34–35; LHR req #14 |
The document makes consent the main way individuals control their health data (Section 2.3, p.34–35), lists a "health-s…The document makes consent the main way individuals control their health data (Section 2.3, p.34–35), lists a "health-sector consent service" in Table 2.2, and tells several components to "integrate with consent management services" (for example the Lifelong Health Record, req #14). But consent is the only one of these capabilities with no component write-up and no functional requirements. The twelve other components each get a full specification; the consent service they all rely on does not. Implementers are told to connect to something the guidance never defines, which risks consent being recorded but not consistently enforced. Suggested revision: Give the consent service its own component description with functional requirements, at the same level of detail as the other components: what a consent record contains, how consent is checked at the point of data exchange, how a withdrawal takes effect across systems, and how it works with a national cross-sector consent service where one exists. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2673✎ edit📣 feedback | received | technical | not routed | 2.3 DPI-H Reference Architecture Design Principles §2.3 (see 5.4) p.35–37 (see 107–109) l.Design principles, lines 355–361 and 436–445 |
The document promises two things that pull against each other but are never reconciled. In Section 2.3 (p.35) it says c…The document promises two things that pull against each other but are never reconciled. In Section 2.3 (p.35) it says consent must be something people can withdraw, and it gives individuals a right to have records erased. In the same Section 2.3 (p.36–37) it endorses using health data to train AI models, with de-identified data as the safeguard. The problem is that once data has been used to train a model, that model cannot practically "un-learn" one person’s data. So withdrawal and erasure can stop future training but cannot remove a person’s influence from a model already trained. The AI chapter (Section 5.4) covers safety, fairness, and evaluation well, but not this. Two further gaps: the document offers de-identification as the safeguard but does not say what the lawful basis is when de-identification is not feasible; and it does not note that rich health data can often be re-identified by linking datasets, so "de-identified" is not a guarantee. Suggested revision: Add explicit guidance on training AI with health data. State a lawful basis for training on identifiable data when de-identification is not feasible (for example a research or public-interest basis with safeguards, rather than relying on consent alone). State plainly that withdrawal and erasure stop future training but cannot undo training already done, so any consent notice must say this for consent to count as informed. Flag that de-identified health data can be re-identified through linkage and should be risk-assessed, not assumed safe. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2674✎ edit📣 feedback | received | general | not routed | 2.2.1 What REDDHI is and its foundational core §2.2.1 p.26–27 l.118–135 |
The REDDHI minimum viable foundation is, at capability level, genuinely minimum for disease surveillance: unique identi…The REDDHI minimum viable foundation is, at capability level, genuinely minimum for disease surveillance: unique identification, facility attribution, provenance, and consistent case definitions are the irreducible preconditions of case-based surveillance, and their absence maps precisely onto known pathologies of national systems such as the Philippine PIDSR (manual deduplication, unstable denominators, unreconciled facility lists). However, the draft only defines surveillance functionality on a COMPLETED foundation; it is silent on what surveillance-grade capability looks like when the foundation is partially present, which is the operating condition of most LMICs for the next decade. Suggested revision: Retain the capability set unchanged, but add to 2.2.1 an explicit statement that each application component (surveillance foremost) must be implementable in a defined degraded mode on a partially present foundation, with a progression path, and cross-reference the conformance tiers requested below (see comments on Appendix C and 4.3.5). Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2675✎ edit📣 feedback | received | technical | not routed | C Appendix C: DPI-H Application Component Descriptions §Appendix C — PHSP p.226 l.Functional requirements table, req. 21 anchor: medium |
Offline and low-connectivity operation for the PHSP is classified 'Recommended' while FHIR-based integration, terminolo…Offline and low-connectivity operation for the PHSP is classified 'Recommended' while FHIR-based integration, terminology subscription, and audit logging are 'Required'. For archipelagic, disaster-prone, devolved contexts this polarity is inverted: surveillance infrastructure must function precisely when infrastructure fails. Post-Haiyan assessments in the Philippines documented suspension of routine ESU surveillance, with roughly seven weeks to restore reporting in Leyte; operational resilience in practice meant paper and improvised channels. A platform 'designed to manage' public health emergencies (the requirement's own wording) cannot treat emergency operating conditions as optional. Suggested revision: Reclassify req. 21 from Recommended to Required. Specify a minimum offline floor: store-and-forward case capture, SMS-compatible notification of immediately notifiable events, and reconciliation rules on synchronisation, with conflict handling for case records edited offline at multiple sites. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2676✎ edit📣 feedback | received | technical | not routed | C Appendix C: DPI-H Application Component Descriptions §Appendix C — PHSP p.225–226 l.Functional requirements table, reqs. 16–18 anchor: medium |
The Required rows presuppose an operational Lifelong Health Record (LHR-derived case reporting), a Terminology Service …The Required rows presuppose an operational Lifelong Health Record (LHR-derived case reporting), a Terminology Service with push subscription for case-definition updates, and a LIMR — in most LMICs the three least mature components of the entire architecture. In the Philippines, the health information exchange has never reached production scale, LGU EMRs (iClinicSys, CHITS, private systems) remain largely non-interoperable, and frontline PIDSR reporting is still substantially paper, spreadsheet, and SMS (e.g., the TUGON module of FASSSTER). As drafted, a country cannot be conformant on surveillance until nearly the whole stack exists, which delays exactly the capability with the greatest health-security urgency. Suggested revision: Add a degraded-mode surveillance conformance profile: (i) case capture against nationally issued standard case definitions distributed centrally (no edge subscription required); (ii) person linkage via a foundational-ID-derived token where the Client Registry is not yet queryable in real time; (iii) facility attribution via the facility registry code list distributed in lightweight formats; (iv) batch or store-and-forward submission accepted as conformant, with FHIR query interfaces as the target state. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2677✎ edit📣 feedback | received | technical | not routed | Public Health Surveillance Platform §Appendix C — PHSP p.221 l.Lines 162–168 ('How it connects') |
The LHR is described as the PHSP's 'primary source of person-level clinical data'. In transitional states, surveillance…The LHR is described as the PHSP's 'primary source of person-level clinical data'. In transitional states, surveillance data flows will precede a functioning LHR by years; facility-direct notification will remain the dominant channel. Stating the LHR as primary source risks implementers de-prioritising direct reporting channels or deferring surveillance investment pending the LHR. Suggested revision: Reframe: facility-direct case notification is the primary channel in early and transitional maturity states; LHR-derived reporting is the target-state channel that progressively reduces parallel reporting burden. Make the transition explicit rather than implied. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2678✎ edit📣 feedback | received | technical | not routed | 2.3 DPI-H Reference Architecture Design Principles §2.3 (Principle II) p.31–32 l.226–238 |
The allowance for 'lighter-weight formats in lower-readiness contexts, provided a clear progression path... is establis…The allowance for 'lighter-weight formats in lower-readiness contexts, provided a clear progression path... is established' is exactly right, but it lives only at design-principle level. The normative weight of the document sits in the component functional-requirement tables (Appendix C), whose Required rows encode connected-state, full-stack assumptions and nowhere reference this allowance. As drafted, the principle and the conformance machinery contradict each other, and the tables will govern procurement. Suggested revision: In each Appendix C component profile, add a row or note operationalising Principle II: name the accepted lighter-weight formats (CSV batch, SMS, store-and-forward), the functions they must preserve, and the progression checkpoints toward open-standards compliance. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2679✎ edit📣 feedback | received | technical | not routed | 2.3 DPI-H Reference Architecture Design Principles §2.3 (Principle VII) p.33–34 l.325–345 |
'Degrade gracefully rather than exclude' is asserted as a structural property but is nowhere testable: no component pro…'Degrade gracefully rather than exclude' is asserted as a structural property but is nowhere testable: no component profile states what its degraded-mode behaviour is, and the conformance section (4.3.5) does not test for it. An untestable equity principle will be designed out in implementation, and the settings least well served — the draft's own phrase — will be excluded by conformance requirements rather than by intent. Suggested revision: Require each component profile to declare degraded-mode behaviour (what functions persist under intermittent connectivity, absent national ID, or partial registry coverage) and include degraded-mode operation in the conformance and testing framework of 4.3.5. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2680✎ edit📣 feedback | received | general | not routed | 4.2.1 Different Entry Points toward REDDHI §4.2.1 p.89–90 l.63–111 |
The entry-point typology takes the country as the unit of analysis. In devolved health systems this conceals the bindin…The entry-point typology takes the country as the unit of analysis. In devolved health systems this conceals the binding constraint: intra-national heterogeneity. The Philippines is squarely Entry Point 2 nationally (integrating existing systems), yet a large share of its 1,400+ municipalities — where surveillance operating capacity actually sits post-devolution — are functionally at Entry Point 1, with epidemiology and surveillance units that are designation-based (existing RHU staff deputised by executive order) rather than resourced, and without dedicated connectivity or hardware budgets. National-level classification will misdirect sequencing and investment in any devolved system (Philippines, Indonesia, Kenya, Nigeria). Suggested revision: Add a sub-national tiering paragraph to 4.2.1: countries should classify entry points at the level at which health services are governed and financed, and the national roadmap should provide differentiated pathways for sub-national units at different entry points, including a floor package for the least-resourced tier. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2681✎ edit📣 feedback | received | technical | not routed | 4.1.2 Assessing Where You Are §4.1.2 p.88–89 l.28–61 |
The assessment question 'What is the state of our foundational DPI?' is framed in terms of existence and reach, not dis…The assessment question 'What is the state of our foundational DPI?' is framed in terms of existence and reach, not distribution. A country can report near-universal foundational-ID registration (as the Philippines now can for PhilSys) while the identifier is absent from actual surveillance workflows, and can report that an electronic surveillance system 'exists' while most local health offices submit by paper, spreadsheet, or SMS. Existence-framed assessment systematically overstates readiness in devolved systems. Suggested revision: Add distributional assessment prompts: share of local health offices with (i) functional connectivity, (ii) staffed and budgeted surveillance units, (iii) electronic submission to the national surveillance system, and (iv) routine use of the foundational identifier in health transactions. These become the baseline values referenced in Phase 1 (4.2.2). Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2682✎ edit📣 feedback | received | technical | not routed | 4.3.5 Minimum Conformance and Testing §4.3.5 p.98 l.398–415 |
'Minimum conformance' as drafted risks meaning full-stack conformance, because requirements are only stated at the targ…'Minimum conformance' as drafted risks meaning full-stack conformance, because requirements are only stated at the target state. Without tiers, ministries and development partners will treat the complete Required set as the procurement bar, pricing out the majority of sub-national implementers and incentivising parallel donor systems — the fragmentation scenario the document opens with. Suggested revision: Define explicit conformance tiers per component (e.g., T1: standard case definitions plus store-and-forward/SMS-compatible capture with facility and person identifiers; T2: batch standards-based exchange; T3: full FHIR query and subscription), each with defined progression evidence. Reference the tiers from Appendix C profiles. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2683✎ edit📣 feedback | received | technical | not routed | 2.2.1 What REDDHI is and its foundational core §2.2.1 p.27–28 l.Table 2.2 |
The table maps foundational capabilities to components but does not indicate which capabilities are critical for which …The table maps foundational capabilities to components but does not indicate which capabilities are critical for which application functions. For surveillance specifically, the critical subset (unique identification of people and facilities, consistent case definitions via the terminology function, provenance) is smaller than the full foundation; countries sequencing under resource constraint cannot derive this from the table. Suggested revision: Add a column or annotation marking capability criticality per major application function (surveillance, care continuity, financing), or a companion mini-table for the surveillance-critical subset, so that sequencing decisions can be grounded in the table rather than inferred. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2684✎ edit📣 feedback | received | editorial | not routed | 2.2.1 What REDDHI is and its foundational core §2.2.1 / 4.2.1 p.26, 89 l.131–135; 78 |
Terminology drift: 'minimum viable foundation' (2.2.1), 'foundational core' / 'essential core' (2.2.1), and 'REDDHI min…Terminology drift: 'minimum viable foundation' (2.2.1), 'foundational core' / 'essential core' (2.2.1), and 'REDDHI minimum viable layer' (4.2.1, line 78) are used interchangeably without definition of whether they denote the same construct. Given that this construct carries the document's sequencing logic, the drift invites divergent interpretation in procurement and conformance documents. Suggested revision: Standardise on one term ('minimum viable foundation'), define it once in 2.2.1 with an explicit pointer to Table 2.2, and replace the variants throughout. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2685✎ edit📣 feedback | received | general | not routed | 5.3 Where artificial intelligence can support the health system §5.3 p.107 l.120-123 |
Can this bullet/paragraph explicitly specify examples of AI-enabled clinical services? like triaging and recording and …Can this bullet/paragraph explicitly specify examples of AI-enabled clinical services? like triaging and recording and transcribing of clinical encounters (ambient scribes) Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2686✎ edit📣 feedback | received | technical | not routed | 5.3 Where artificial intelligence can support the health system §5.3 p.107 l.120-123 |
Can we rephrase "image interpretation" to "data and signals processing and interpretation"?Can we rephrase "image interpretation" to "data and signals processing and interpretation"? Suggested revision: "in clinical services, diagnostic and decision support, imaging and signals data interpretation,..." Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2687✎ edit📣 feedback | received | general | not routed | 5.3 Where artificial intelligence can support the health system §5.3 p.107 l.124-129 |
Can we add a bullet item for AI use to support local, regional and national health policy making?Can we add a bullet item for AI use to support local, regional and national health policy making? Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2688✎ edit📣 feedback | received | general | not routed | 5.3 Where artificial intelligence can support the health system §5.3 p.107 l.109 |
Can we add AI use in health research?Can we add AI use in health research? Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2689✎ edit📣 feedback | received | general | not routed | 5.4.1 What AI readiness means §5.4.1 p.108 l.147 |
Why is AI readiness only measured at the institutional level? Or is the institution referred to the country itself, thu…Why is AI readiness only measured at the institutional level? Or is the institution referred to the country itself, thus encompassing the individual citizen as patient, healthcare provider, health facility administrator, local, regional, national health offices? Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2690✎ edit📣 feedback | received | general | not routed | 5.4.2 Trustworthy AI in a health setting §5.4.1 p.108 l.158-159 anchor: medium |
What kind of human oversight should be instituted? A national-level "regulatory" office within or separate from the FDA?What kind of human oversight should be instituted? A national-level "regulatory" office within or separate from the FDA? Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2691✎ edit📣 feedback | received | technical | not routed | 5.4.4 Cost, sustainability, and commercial pressure §5.4.4 p.109 l.183-186 |
The text characterises sovereign models as "hosted and governed within national or regional control," treating hosting …The text characterises sovereign models as "hosted and governed within national or regional control," treating hosting location and governance authority as a single choice. It is possible to separate hosting for countries with limited domestic compute. At the same time, hosting domestically does not guarantee sovereignty if models remain externally controlled. Suggested revision: Distinguish data and model residency from sovereignty, and note that pooled or regional compute arrangements are a third option alongside domestic hosting and single-provider dependence. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2692✎ edit📣 feedback | received | general | not routed | 4.5.3 Building and Sustaining National Capacity §4.53 p.101 l.526-533 |
The section identifies national training programmes as the means to develop and retain capacity in the public sector, b…The section identifies national training programmes as the means to develop and retain capacity in the public sector, but does not address the institutional preconditions on which retention depends. Training capacity alone does not produce retention where (a) no academic pathway produces the specialist roles listed in 4.5.2, (b) the civil service has no position classification or establishment item for informatics roles, so trained staff have no post to occupy, and (c) no career progression competes with private-sector or donor-funded alternatives. Suggested revision: Add brief guidance on establishing a national capacity programme that names academic pathway development, civil service position classification, and retention as explicit prerequisites; and reference competency frameworks for digital health as the bridge between role definitions and curricula. Include at least one low- or middle-income exemplar. Digital Health Committee, University of the Philippines Manila, The Philippines |
none | not yet | none | in the document all mentions on GitHub record | |
| PC-2693✎ edit📣 feedback | received | general | not routed | unplaced (no citation) |
I. GDHP General Remarks on the Draft WHO Digital Public Infrastructure- The Global Digital Health Partnership (GDHP) is…I. GDHP General Remarks on the Draft WHO Digital Public Infrastructure- The Global Digital Health Partnership (GDHP) is pleased to contribute to the consultation on the Draft Reference Architecture Guidance for Digital Public Infrastructure for Health (DPI-H), drawing on the insights of its members. The Guidance succeeds in providing a global reference framework for countries to design health data systems that are interoperable, secure, and scalable. Its modular structure and adaptable standards allow the architecture to be applied flexibly rather than as a rigid template, with countries taking up the components most relevant to their own circumstances. This flexibility also extends to pace of adoption: the guidance allows for incremental implementation based on a country's existing digital health maturity, a realistic feature given how widely that maturity varies across regions. The underlying design principles are a particular strength of the document. They are comprehensive and well-rounded, spanning governance, interoperability, sustainability, and related dimensions in a way that gives countries a solid conceptual reference point regardless of where they sit on the maturity spectrum. Furthermore, the inclusion of country and regional implementation examples adds considerable practical value. These examples help translate the architecture's principles into tangible experience, illustrating how the framework can play out in real settings rather than remaining purely conceptual. GDHP considers this guidance a comprehensive and valuable contribution that lays a strong conceptual foundation for DPI-H, offering countries a credible and adaptable reference point from which to advance interoperable, secure, and people-centred digital health systems in the years ahead. II. GDHP Suggestions for Strengthening the Draft WHO Digital Public Infrastructure- Health GDHP recognises the solid foundation established by the draft Reference Architecture Guidance for DPI-H, and its principal suggestion is to further strengthen the guidance's practical implementation dimension, including clearer prioritisation, maturity assessment, governance operating models and financing sustainability. This could also include more explicit consideration of how healthcare providers might be engaged in planning and implementing DPI-H, as well as additional operational toolkits to support countries in practice. Conclusion GDHP considers the draft Reference Architecture Guidance for DPI-H to be grounded in a strong and well-conceived basis. The comments set out above aim to further support its practical implementation guidance, technical clarity, and governance framing, so that it can serve as a clear and actionable reference for countries developing interoperable, secure, and sustainable digital public infrastructure for health. Contributing GDHP Members The GDHP contributions to the draft WHO Digital Public Infrastructure - Health reflect the collective input and expertise of participating GDHP members. Contributing countries (by alphabetical order): • Australia • Austria • Canada • Hong Kong • Ireland • Lithuania • Portugal • Spain • Yemen GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | all mentions on GitHub record | |
| PC-2694✎ edit📣 feedback | received | not routed | [Chapter 1, Introduction (the letter: "Section 1 (DPI-H Principles and Priority Goals)")] 1. Strengthen the DPI-H Princi |
[Chapter 1, Introduction (the letter: "Section 1 (DPI-H Principles and Priority Goals)")] 1. Strengthen the DPI-H Princ…[Chapter 1, Introduction (the letter: "Section 1 (DPI-H Principles and Priority Goals)")] 1. Strengthen the DPI-H Principles and Health Sector Priority Goals GDHP recommends adjusting certain principles and goals within Section 1 (DPI-H Principles and Priority Goals) to better account for real-world implementation conditions. In particular: • Separate core principles from implementation principles and clarify which ones are essential for countries to adopt the framework successfully. • Reframe the Autonomy and Sovereignty point: avoiding dependency is the right goal, but it shouldn't mean every standard must be nationally controlled. Health-data interoperability relies heavily on international standards, and sometimes on binding regional rules. • Consider placing greater emphasis on citizen agency, including access transparency, consent management, portability, digital identity integration and trusted presentation of health information across organisational and national boundaries. • Qualify the "captured once" principle so it is not framed as an unconditional rule applying to all health information. Clinical information may legitimately be generated, verified, or recorded by different actors at different points in a care pathway. • Clarify that data collected for one purpose can't automatically be shared wherever it might be useful, since reuse must follow the law and data- protection safeguards, and that consent isn't the only legal basis for using health data. These refinements would help align the stated principles and goals more closely with how digital health systems function in practice, without diminishing the overall strength of the framework. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2695✎ edit📣 feedback | received | not routed | [Chapter 2, DPI-H Reference Architecture Framework] 2. Refine the Architecture Framework GDHP finds the Resilient Essent |
[Chapter 2, DPI-H Reference Architecture Framework] 2. Refine the Architecture Framework GDHP finds the Resilient Essen…[Chapter 2, DPI-H Reference Architecture Framework] 2. Refine the Architecture Framework GDHP finds the Resilient Essential Data and Digital Health Infrastructure concept particularly valuable and suggests a few refinements to strengthen how it is presented in the guidance. In particular, the guidance could: • Add a maturity model or staged assessment framework, so that countries can evaluate their current capability level and track their progress toward REDDHI over time, including how specific capabilities and components evolve across maturity levels. • For REDDHI, clarify the notion of a “starting point”: while a country does not need the full REDDHI framework in place to begin, capabilities such as a lifelong health record and data exchange may already represent a significant achievement. • Acknowledge that implementing REDDHI across different jurisdictions and health authorities requires substantial change management, extending well beyond technical work to include political and governance efforts. • Clarify that the requirement for consistent data structures (information models) applies to how systems exchange data with one another and does not necessarily need to extend to how each system stores its data internally. On the architecture design principles, GDHP welcomes the guidance's emphasis on governance and suggests two further refinements. In particular, the guidance could: • Provide greater clarity on accountability and operating models across national, sub-national and regional levels, including decision rights, stewardship responsibilities and cross-sector coordination. • Avoid presenting consent as the main or default way of authorising the use of health data. This risks blurring three separate things: the legal basis for using data, people's rights over their own data, and consent as just one possible tool among several. Treating consent as the default could unintentionally get in the way of legitimate healthcare and public-health uses of data. Addressing these points would strengthen REDDHI and the design principles by grounding them more firmly in the practical, governance, and legal complexities. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2696✎ edit📣 feedback | received | not routed | [Chapter 3, The Reference Architecture for DPI-H] 3. Strengthen Reference Architecture, Governance and Conformance The g |
[Chapter 3, The Reference Architecture for DPI-H] 3. Strengthen Reference Architecture, Governance and Conformance The …[Chapter 3, The Reference Architecture for DPI-H] 3. Strengthen Reference Architecture, Governance and Conformance The governance framework and approach to testing and conformance are well developed and address the core dimensions needed to support national digital health transformation. A few areas would nonetheless benefit from further elaboration. In particular, the guidance could: • Consider adding a concise visual summary of the progression health goals → capabilities → services → components → data to improve accessibility for policymakers and senior decision-makers. • Expand the governance framework to cover financing sustainability, stewardship arrangements, cross-ministerial decision-making (spanning health, finance, digital government, and data protection authorities), and governance approaches for AI-enabled services. • Give further attention to the distribution of responsibilities within a country, alongside the treatment of national and regional governance already provided. • Consider including examples of regional interoperability ecosystems in addition to national implementations. Regional initiatives can provide useful lessons on governance, trust frameworks, interoperability and cross-border information exchange. • Highlight earlier in the document that Semantic Governance Infrastructure is a national capability requiring sustained investment, stewardship, and ongoing operational management. Also, provide practical guidance on progressively establishing semantic governance capabilities, including terminology services, information models, value sets, governance structures, and change- management processes. • Identify a minimum viable set of DPI-H capabilities and components for countries beginning their digital health transformation journey, along with guidance on sequencing and dependencies between them. • Strengthen the link between the architecture, procurement, and conformance testing, so countries can verify that procured systems meet agreed standards and avoid fragmentation from proprietary approaches. • Clarify how national coverage is assessed in countries with layered governance. • Clarify the minimum foundational data and semantic capabilities needed before advancing to more sophisticated interoperability and FHIR-based exchange. These points are largely practical in nature, concerned with how the architecture will be understood, implemented, and verified once countries begin to apply it. Addressing them would help ensure that the guidance holds up equally well in centralised and federated governance contexts, and that the mechanisms for building, procuring, and validating DPI-H are as well defined. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2697✎ edit📣 feedback | received | not routed | [Chapter 4, Implementing a National Digital Health Architecture] 4. Enhance the National Digital Health Architecture The |
[Chapter 4, Implementing a National Digital Health Architecture] 4. Enhance the National Digital Health Architecture Th…[Chapter 4, Implementing a National Digital Health Architecture] 4. Enhance the National Digital Health Architecture The National Digital Health Architecture chapter provides a solid foundation, though a few areas could be clarified further, particularly around legacy transition and some of the technical framing. Towards this, the following adjustments could be considered: • Strengthening the chapter with clearer guidance on sequencing, legacy transition, financing sustainability and capacity-building. Many countries will need to modernise fragmented legacy systems rather than build from scratch, so a staged pathway covering minimum viable capabilities, transitional coexistence, and long-term target architecture would support more practical adoption. • Adopt a release-neutral formulation of FHIR, distinguishing the framework from any specific release. • Reconsider the claim that centralised infrastructure inherently provides "stronger" governance, security, or accountability. Governance strength comes from clear decision rights, conformance rules, auditability, and accountability. These points suggest the value of a more flexible, technology-neutral framing that accommodates the different starting points, standards environments, and governance models that countries bring to digital health transformation. GDHP Members (compiled by GDHP Secretariat), Global Digital Health Partnership (GDHP), Global |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2698✎ edit📣 feedback | duplicate | not routed | 4.3.3 Services and Transactions: FHIR as the Recommended Framework Section 4.3.3, Line 331: A small extension mentioning IHE having profiled some eH use-cases in the FHIR standard. We thi |
Section 4.3.3, Line 331: A small extension mentioning IHE having profiled some eH use-cases in the FHIR standard. We th…Section 4.3.3, Line 331: A small extension mentioning IHE having profiled some eH use-cases in the FHIR standard. We think it would be helpful to point this out in this chapter, so that the reader gets the information that some use-cases are already profiled in terms of services and transactions and they can profit from. Feel free to formulate a better expression or location of this thought. Inserted in the .docx, at the end of the paragraph: "A number of widely-used digital health use-cases are profiled by IHE using the FHIR standard and RESTful APIs. Those profiles constrain FHIR in a way so that the workflows of the use-case can be optimally fulfilled by technical systems and sustainability is maximized (search parameters, content, response, …)." Austria |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2699✎ edit📣 feedback | duplicate | not routed | D.2 Country implementation examples Section D.2: Added a short description of the Austrian ELGA alongside the other countries. Inserted in the .docx, as a n anchor: medium |
Section D.2: Added a short description of the Austrian ELGA alongside the other countries.Section D.2: Added a short description of the Austrian ELGA alongside the other countries. Inserted in the .docx, as a new country example after the existing ones: Austria Components illustrated: LHR, Terminology Service Austria operates a national eHealth interoperability infrastructure (elga.gv.at), with ELGA serving as the electronic health record system for its citizens. It enables authorized healthcare professionals to securely access relevant health information across healthcare providers and institutions, while the ELGA Portal provides patients with access to their own health data. ELGA is deployed nationwide, connecting virtually all healthcare providers and pharmacies across Austria. ELGA supports the exchange of information such as discharge letters, laboratory and radiology reports, e-Medication, and e-prescriptions, improving continuity of care and patient safety. The ELGA Terminology Service provides centrally managed medical terminologies, code systems, value sets, and mappings, ensuring semantic interoperability and consistent interpretation of health information across different IT systems. Austria |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2700✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 234–235. [note] I suggest to add: including for tax collection |
§1.2.3, p. 16, lines 234–235. [note]§1.2.3, p. 16, lines 234–235. [note] I suggest to add: including for tax collection a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2701✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 237. [highlight] On the text: «provider». I suggest to add: supprting for instance |
§1.2.3, p. 16, lines 237. [highlight] On the text: «provider».§1.2.3, p. 16, lines 237. [highlight] On the text: «provider». I suggest to add: supprting for instance a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2702✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 242. [highlight] On the text: «Finance,». based on tax collection |
§1.2.3, p. 16, lines 242. [highlight] On the text: «Finance,».§1.2.3, p. 16, lines 242. [highlight] On the text: «Finance,». based on tax collection a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2703✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 243–244. [highlight] On the text: «from». from different population groups, such as formal and info |
§1.2.3, p. 16, lines 243–244. [highlight] On the text: «from».§1.2.3, p. 16, lines 243–244. [highlight] On the text: «from». from different population groups, such as formal and informal sector workers, as well as employers, a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2704✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 244–245. [highlight] On the text: «Achieving financing». health financing goals (it sounds repetiti |
§1.2.3, p. 16, lines 244–245. [highlight] On the text: «Achieving financing».§1.2.3, p. 16, lines 244–245. [highlight] On the text: «Achieving financing». health financing goals (it sounds repetitive, but financing can also be understood in different ways) a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2705✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 245–246. [highlight] On the text: «clinical». definition of health benefit packages, |
§1.2.3, p. 16, lines 245–246. [highlight] On the text: «clinical».§1.2.3, p. 16, lines 245–246. [highlight] On the text: «clinical». definition of health benefit packages, a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2706✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 246–247. [highlight] On the text: «and». claims management procedures |
§1.2.3, p. 16, lines 246–247. [highlight] On the text: «and».§1.2.3, p. 16, lines 246–247. [highlight] On the text: «and». claims management procedures a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2707✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 246–248. [highlight] On the text: «budget and expenditure rules.». please shift this before "eligib |
§1.2.3, p. 16, lines 246–248. [highlight] On the text: «budget and expenditure rules.».§1.2.3, p. 16, lines 246–248. [highlight] On the text: «budget and expenditure rules.». please shift this before "eligibility", and change to: budget formation, expenditure and monitoring rules a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2708✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 248. [highlight] On the text: «determinations have been made». to link better with the next paragra |
§1.2.3, p. 16, lines 248. [highlight] On the text: «determinations have been made».§1.2.3, p. 16, lines 248. [highlight] On the text: «determinations have been made». to link better with the next paragraph, I suggest to slightly re-edit: ".... once these determinants have been established...." a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2709✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 252–253. [highlight] On the text: «— benefit entitlement, clinical coding, prior authorisation, ser |
§1.2.3, p. 16, lines 252–253. [highlight] On the text: «— benefit entitlement, clinical coding, prior authorisation, se…§1.2.3, p. 16, lines 252–253. [highlight] On the text: «— benefit entitlement, clinical coding, prior authorisation, service delivery verification —». this appears redundant. I would suggest to delete here, and edit: "... contingent on these health-specific determinants and becomes..." a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2710✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 255–256. [highlight] On the text: «line.». budget or funding flow line |
§1.2.3, p. 16, lines 255–256. [highlight] On the text: «line.».§1.2.3, p. 16, lines 255–256. [highlight] On the text: «line.». budget or funding flow line a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2711✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 256–257. [highlight] On the text: «frameworks». delete "s" framework in singular |
§1.2.3, p. 16, lines 256–257. [highlight] On the text: «frameworks».§1.2.3, p. 16, lines 256–257. [highlight] On the text: «frameworks». delete "s" framework in singular a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2712✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 256–258. [highlight] On the text: «budget appropriations, treasury controls, expenditure reporting, |
§1.2.3, p. 16, lines 256–258. [highlight] On the text: «budget appropriations, treasury controls, expenditure reporting…§1.2.3, p. 16, lines 256–258. [highlight] On the text: «budget appropriations, treasury controls, expenditure reporting, and fiscal accountability mechanisms». our standard terminology is: budget formation, budget expenditure reporting, budget monitoring a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2713✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 257–258. [highlight] On the text: «outside». I would prefer to say: that cuts across the health sys |
§1.2.3, p. 16, lines 257–258. [highlight] On the text: «outside».§1.2.3, p. 16, lines 257–258. [highlight] On the text: «outside». I would prefer to say: that cuts across the health system as well as .... (it is for sure not outside the health system) IFMIS for example can be considered as part of DPI, and it is part of PFM. So "adjacent" does better justice to these connections. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2714✎ edit📣 feedback | received | not routed | 1.2.3 Payments DPI and financial transactions in the health sector §1.2.3, p. 16, lines 258–259. [highlight] On the text: «requiring integration with government-wide PFM systems». this is |
§1.2.3, p. 16, lines 258–259. [highlight] On the text: «requiring integration with government-wide PFM systems».§1.2.3, p. 16, lines 258–259. [highlight] On the text: «requiring integration with government-wide PFM systems». this is contradictory: First part of sentence says: many flows within PFM, second part: these flows require integration with PFM .... I suggest to say: "... that sit adjacent to both the health financing system and foundational payment DPIs, requiring alignment with health financing processes." a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2715✎ edit📣 feedback | received | not routed | 1.3 Value of DPI-H p. 17, lines 263 (margin note; nearest line). [highlight] On the text: «claims». I suggest to add: ".... rules against w anchor: low |
p. 17, lines 263 (margin note; nearest line). [highlight] On the text: «claims».p. 17, lines 263 (margin note; nearest line). [highlight] On the text: «claims». I suggest to add: ".... rules against which financial flows, claims and payments are assessed." a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2716✎ edit📣 feedback | received | not routed | 1.3.3 Value Across Stakeholders §1.3.3, p. 19, lines 340. [highlight] On the text: «financing». health financing |
§1.3.3, p. 19, lines 340. [highlight] On the text: «financing».§1.3.3, p. 19, lines 340. [highlight] On the text: «financing». health financing a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2717✎ edit📣 feedback | received | not routed | 1.3.3 Value Across Stakeholders §1.3.3, p. 19, lines 347–348. [highlight] On the text: «time and». I suggest to add: "on time, for quality services bein |
§1.3.3, p. 19, lines 347–348. [highlight] On the text: «time and».§1.3.3, p. 19, lines 347–348. [highlight] On the text: «time and». I suggest to add: "on time, for quality services being delivery, ..." a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2718✎ edit📣 feedback | received | not routed | 1.5.1 The Health Sector Goals §1.5.1, p. 23, lines 498. [highlight] On the text: «coverage .». please add: to progress towards UHC. (it must be clear |
§1.5.1, p. 23, lines 498. [highlight] On the text: «coverage .».§1.5.1, p. 23, lines 498. [highlight] On the text: «coverage .». please add: to progress towards UHC. (it must be clear to readers that financial protection and service coverage are the two key dimensions for UHC) a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2719✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2, p. 39, lines 502–503. [note] please kindly expand: "...determines wehther sufficient funds are raised in an effi |
§2.4.2, p. 39, lines 502–503. [note]§2.4.2, p. 39, lines 502–503. [note] please kindly expand: "...determines wehther sufficient funds are raised in an efficient way, funds reach providers whilst setting the right incentives for adequate service provision, quality and efficiency, are allocated equitably a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2720✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2, p. 39, lines 506–507. [note] please rephrase: Whatever the composition of health funds (primarily a mix of taxa |
§2.4.2, p. 39, lines 506–507. [note]§2.4.2, p. 39, lines 506–507. [note] please rephrase: Whatever the composition of health funds (primarily a mix of taxation, insurance contributions, as well as out-of-pocket payments) a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2721✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2, p. 39, lines 507–509. [note] and financial flows (the word budget does not perfectly capture all kinds of financ |
§2.4.2, p. 39, lines 507–509. [note]§2.4.2, p. 39, lines 507–509. [note] and financial flows (the word budget does not perfectly capture all kinds of financial flows), hence this proposed addition a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2722✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2, p. 39, lines 511–512. [highlight] On the text: «that already exists for other purposes:». this is not clear: Wha |
§2.4.2, p. 39, lines 511–512. [highlight] On the text: «that already exists for other purposes:».§2.4.2, p. 39, lines 511–512. [highlight] On the text: «that already exists for other purposes:». this is not clear: What do you mean for "other purposes"? Lots of countries don't have all these registries at all. Facility registry and health workforce registry are probably the ones most frequently being available, but not the others. So may rephrase last sentence just above table: "these capabilites draw or would ideally draw on shared DPI that is also used for managing the health workforce, supply chains and other health system domains. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2723✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2, p. 39, lines 513. [note] From line 513 onwards, the focus becomes too narrow (ie on scheme registries and claims |
§2.4.2, p. 39, lines 513. [note]§2.4.2, p. 39, lines 513. [note] From line 513 onwards, the focus becomes too narrow (ie on scheme registries and claims management). The text should be broadened to reflect a wider range of DPI applications relevant to health financing, including revenue collection, FMIS, pooling, strategic purchasing and provider-level financial management. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2724✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2, p. 39, lines 513 (margin note; nearest line). [highlight] On the text: «by». are we sure that this is complete? |
§2.4.2, p. 39, lines 513 (margin note; nearest line). [highlight] On the text: «by».§2.4.2, p. 39, lines 513 (margin note; nearest line). [highlight] On the text: «by». are we sure that this is complete? I think we should crticially check again. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2725✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2, p. 39, lines 521–522. [note] On the text: «claims engines,». payment systems |
§2.4.2, p. 39, lines 521–522. [note] On the text: «claims engines,».§2.4.2, p. 39, lines 521–522. [note] On the text: «claims engines,». payment systems a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2726✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing p. 40, lines 524. [note] On the text: «enrol people,». make more generic e.g. identify beneficiaries....enrolling is one |
p. 40, lines 524. [note] On the text: «enrol people,».p. 40, lines 524. [note] On the text: «enrol people,». make more generic e.g. identify beneficiaries....enrolling is one function, and of course important one in some systems and/or parts of some systems. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2727✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing p. 40, lines 524–526. [highlight] On the text: «These applications sit outside DPI-H:». I think this needs more explanat |
p. 40, lines 524–526. [highlight] On the text: «These applications sit outside DPI-H:».p. 40, lines 524–526. [highlight] On the text: «These applications sit outside DPI-H:». I think this needs more explanation, what do you mean by "stting outside" a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2728✎ edit📣 feedback | received | not routed | 2.4.2 Worked example: Advance Efficient and Equitable Health Financing §2.4.2, p. 40, lines 528–530. [note] their own capability situation and possible gaps |
§2.4.2, p. 40, lines 528–530. [note]§2.4.2, p. 40, lines 528–530. [note] their own capability situation and possible gaps a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2729✎ edit📣 feedback | received | not routed | 4.3.4 Interoperability Implementation Pathways §4.3.4, p. 97, lines 373–375. [note] what is this? |
§4.3.4, p. 97, lines 373–375. [note]§4.3.4, p. 97, lines 373–375. [note] what is this? a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2730✎ edit📣 feedback | received | not routed | 4.3.4 Interoperability Implementation Pathways §4.3.4, p. 98, lines 393–395. [highlight] On the text: «while health financing claims are orchestrated through a claims |
§4.3.4, p. 98, lines 393–395. [highlight] On the text: «while health financing claims are orchestrated through a claims…§4.3.4, p. 98, lines 393–395. [highlight] On the text: «while health financing claims are orchestrated through a claims exchange component.». I suggest to rephrase: ".... while financial flows to providers are orchestrated through a separate transaction system" (or another word: through a separate financial flow system). a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2731✎ edit📣 feedback | received | not routed | 4.3.4 Interoperability Implementation Pathways §4.3.4, p. 98, lines 394–395. [highlight] On the text: «financing». in HF, we are not using this term "health financing |
§4.3.4, p. 98, lines 394–395. [highlight] On the text: «financing».§4.3.4, p. 98, lines 394–395. [highlight] On the text: «financing». in HF, we are not using this term "health financing claims" Only countries with explicit health coverage schemes and separate purchaser would operate on the basis of claims, but they could also use budgets. We need a more generic wording here to not be health insurance biased. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2732✎ edit📣 feedback | received | not routed | 4.3.4 Interoperability Implementation Pathways §4.3.4, p. 98, lines 396–397. [highlight] On the text: «claims transactions,». I would suggest to say: "orchestrating fi |
§4.3.4, p. 98, lines 396–397. [highlight] On the text: «claims transactions,».§4.3.4, p. 98, lines 396–397. [highlight] On the text: «claims transactions,». I would suggest to say: "orchestrating financial flows and related transactions, which in the case of a health insurance scheme, for instance, would involve membership and benefits confirmation, ...." a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2733✎ edit📣 feedback | received | not routed | 4.6.1 The Investment Case §4.6.1, p. 102, lines 551–553. [note] measure improvements in revenue raising, pooling, purchasing and resource allocat |
§4.6.1, p. 102, lines 551–553. [note]§4.6.1, p. 102, lines 551–553. [note] measure improvements in revenue raising, pooling, purchasing and resource allocation. DELETE the others, they are sub-tasks of these key functions a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2734✎ edit📣 feedback | received | not routed | 4.6.3 Approaches to Financing §4.6.3, p. 103, lines 582–583. [highlight] On the text: «co-financing». are there country examples for this from HIC? N |
§4.6.3, p. 103, lines 582–583. [highlight] On the text: «co-financing».§4.6.3, p. 103, lines 582–583. [highlight] On the text: «co-financing». are there country examples for this from HIC? Not aware of HIC HI schemes that pay contribution.... a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2735✎ edit📣 feedback | received | not routed | Client Registry §C, p. 123, lines 210 (margin note; nearest line). [note] I think what is meant here: heath finanicng functions |
§C, p. 123, lines 210 (margin note; nearest line). [note]§C, p. 123, lines 210 (margin note; nearest line). [note] I think what is meant here: heath finanicng functions a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2736✎ edit📣 feedback | received | not routed | Supplier Registry §C, p. 193, lines 123–125. [highlight] On the text: «Finance». The text has been using "financial system" as well as fin |
§C, p. 193, lines 123–125. [highlight] On the text: «Finance».§C, p. 193, lines 123–125. [highlight] On the text: «Finance». The text has been using "financial system" as well as financing systems. So I suggest to stick to at most those two, not additional ones. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2737✎ edit📣 feedback | received | not routed | Benefits Package Registry §C, p. 199, lines 5 (margin note; nearest line). [note] I don't konw about other registries: but most LMIC don't have su anchor: low |
§C, p. 199, lines 5 (margin note; nearest line). [note]§C, p. 199, lines 5 (margin note; nearest line). [note] I don't konw about other registries: but most LMIC don't have such a registry. The national public HI scheme would have a benefiaricy data base, which probably comes closest to this beneficary registry. So I am just wondering to what extend we may use "would" to indicate this current situation? a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2738✎ edit📣 feedback | received | not routed | Benefits Package Registry §C, p. 199, lines 25–28. [note] please delete "entitlement" just: govt-funded programmes |
§C, p. 199, lines 25–28. [note]§C, p. 199, lines 25–28. [note] please delete "entitlement" just: govt-funded programmes a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2739✎ edit📣 feedback | received | not routed | Benefits Package Registry §C, p. 199, lines 27–30. [highlight] On the text: «What distinguishes a scheme from general health service provision is |
§C, p. 199, lines 27–30. [highlight] On the text: «What distinguishes a scheme from general health service provision is…§C, p. 199, lines 27–30. [highlight] On the text: «What distinguishes a scheme from general health service provision is the existence of a defined benefit package — a governed specification of what is covered, for whom, and under what conditions.». let's please delete this sentence. General health services provision is also a a "HF scheme" a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2740✎ edit📣 feedback | received | not routed | Benefits Package Registry §C, p. 199, lines 33–34. [highlight] On the text: «depends on knowing,». this sounds as if this knowledge is the most de |
§C, p. 199, lines 33–34. [highlight] On the text: «depends on knowing,».§C, p. 199, lines 33–34. [highlight] On the text: «depends on knowing,». this sounds as if this knowledge is the most decisive factor for progress towards UHC. But this type of "definition" for progress is not correct. UHC means that people can access quality health services without financial hardship. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2741✎ edit📣 feedback | received | not routed | Benefits Package Registry §C, p. 201, lines 105–106. [highlight] On the text: «The». I suggest to also put this para into bullet points. |
§C, p. 201, lines 105–106. [highlight] On the text: «The».§C, p. 201, lines 105–106. [highlight] On the text: «The». I suggest to also put this para into bullet points. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2742✎ edit📣 feedback | received | not routed | Benefits Package Registry §C, p. 201, lines 109–112. [note] production and analyses |
§C, p. 201, lines 109–112. [note]§C, p. 201, lines 109–112. [note] production and analyses a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2743✎ edit📣 feedback | received | not routed | Benefits Package Registry §C, p. 201, lines 127–129. [highlight] On the text: «downstream». I don't think that PFM is downstream only. It is certa |
§C, p. 201, lines 127–129. [highlight] On the text: «downstream».§C, p. 201, lines 127–129. [highlight] On the text: «downstream». I don't think that PFM is downstream only. It is certainly also upstream in terms of budget formation, influencing benefit package definition. a reviewer |
none | not yet | none | in the document all mentions on GitHub record | ||
| PC-2744✎ edit📣 feedback | received | general | not routed | Health Facility Registry (no citation) anchor: medium |
Email comment, forwarded by the chief editor on litlfred/folio-assistant#197 (public consultation). Attachment: A Healt…Email comment, forwarded by the chief editor on litlfred/folio-assistant#197 (public consultation). Attachment: A Health Geo-Registry as DPI-H, an 8-page PDF (https://github.com/user-attachments/files/33431528/A.Health.Geo-Registry.as.DPI-H.pdf). Thank you for sending this reminder email. I discussed the reference architecture with Steeve Ebner, a mutual colleague of Ravi, who emphasized the importance of distinguishing between a Catchment Area and a Health Service Area: A health service area represents the geographic area or population that a facility is formally designated or intended to serve and should be maintained as an authoritative, temporally governed geographic relationship. A facility catchment area represents the geographic distribution of the population that actually utilizes the facility and may be derived from patient-origin or service-utilization data. Because designated service areas and observed catchment areas may differ substantially and change independently over time, the Health Facility Registry should avoid conflating the two concepts. Also, regarding the Health Geo-Registry concept, I continue to believe, as before, that its role needs to be distinct from the Common Geo-Registry. Whether these are two separate systems or distinct roles within a single system, the CGR should manage cross-domain geographies and hierarchies (such as the administrative hierarchy), and the HGR should manage the health operational hierarchy and other geographies that cut across health systems. Attached is the document I drafted for our discussion with Ravi, for reference. a reviewer |
none | not yet | none | in the document all mentions on GitHub record |