Skip to main content
Version: 1.1.0
Last Updated: 2026-05-15
Owner: Product / Compliance / CL / PM / PF
Purpose: Decision-grade matrix for choosing ONC pathway (Full certification, modular certification, or alignment-only), with criterion-level coverage and implementation gaps.

1) Executive Summary and Decision Framework

Encore OS already has meaningful ONC-oriented groundwork in specs and partial implementation, especially around FHIR, patient access, C-CDA, information blocking, and prior authorization. Strongest existing anchors: Most important missing areas for certification readiness:
  • Conditions and Maintenance of Certification artifacts (Real World Testing, Insights condition, attestations cadence, CHPL documentation artifacts).
  • Public health reporting criteria (f-family) and transport criteria (h-family) at certification depth.
  • Design/process criteria (g(3) Safety-Enhanced Design, g(4) QMS, g(5) Accessibility-centered design) as ONC evidence artifacts.
  • Predictive DSI transparency and HTI-2 additions (j(20), j(21)).

1.1 Path Comparison

1.2 Required Artifacts by Path

1.3 Decision Triggers


2) 45 CFR §170.315 Criteria Gap Matrix (Criterion Families)

Coverage Status Legend:
  • None
  • Spec-only
  • Spec + partial impl
  • Spec + impl-complete
  • Certified-ready

2.1 (a) Clinical Criteria

2.2 (b) Care Coordination Criteria

2.3 (c) Clinical Quality Measure Criteria

2.4 (d) Privacy and Security Criteria

2.5 (e) Patient Engagement Criteria

2.6 (f) Public Health Criteria

2.7 (g) Design and Performance Criteria

2.8 (h) Transport Criteria

2.9 (j) HTI-2 Additions

2.10 SVAP / Version Cutover Flags (Cross-Criterion)


3) Conditions and Maintenance of Certification Matrix


4) ONC Tooling Readiness Matrix


5) ONC Resource Adoption Assessment (Non-Certification Resources)


6) Recommended Next-Step Batches (Post-Decision)

These are not implemented in this document. They are recommended work packages after path selection.

Batch A: Decision Lock

  • Choose one path: Full, Modular, or Alignment-only.
  • Set scope statement by criterion family and target deadlines.
  • Name accountable owners and evidence calendar.

Batch B: Critical Safety and Conditions

  • New specs for Real World Testing, Insights condition, and attestation packaging.
  • Dedicated predictive DSI transparency spec (b(11)).
  • SAFER Guides adoption and governance spec.

Batch C: Modular Certification Core

  • Production conformance for g(10) (Inferno-ready API package).
  • Direct transport criterion hardening (h(1) / h(2)).
  • Patient engagement criterion completion (e(1)/e(2)/e(3) as selected).
  • d-family criterion evidence bundle finalization.

Batch D: Public Health Decision and Execution

  • Formal in-scope/N/A determinations for f(1)-f(7).
  • Implement only contract-required public health criteria.
  • Build corresponding NIST validation workflows.

Batch E: HTI-2 Extensions

  • Implement and certify j(15)/j(16)/j(19) to production level.
  • Add new specs for j(20) CDS Hooks client and j(21) subscriptions client.

Batch F: ONC Resource Adoption

  • Health IT Playbook operational adoption guide.
  • Patient engagement playbook integration plan.
  • SRA tool integration and annual safety review process.

Batch G: Governance and Process Updates


7) Cross-References and Sources

7.1 External ONC/HHS Sources

7.2 Internal Compliance and Spec Sources

7.3 Known Internal Consistency Notes

  • PF-96 file header indicates complete status while registry/tracker entries may lag in some contexts.
  • ONC_CERTIFICATION_ROADMAP.md is intentionally high-level and should be refreshed after path selection.

Appendix A: Current ONC Readiness Scorecard (Snapshot)

Overall snapshot: 1.8 / 5.0 for certification readiness; 2.5 / 5.0 for alignment-only interoperability posture (revised down from 3.0 per May 2026 analysis — USCDI v3 is now the baseline and most BH competitors already meet that bar).

Appendix B: Immediate No-Regret Actions (Regardless of Path)

  1. Finalize and run Inferno-aligned test harness for current FHIR API scope.
  2. Normalize USCDI v3 mapping inventory and close known terminology gaps.
  3. Formalize information blocking denial taxonomy and review queue disposition standards.
  4. Add explicit criterion ownership tags to each ONC-relevant spec.
  5. Create one annual ONC compliance calendar (deadlines, attestations, test windows).
  6. Create DS4P send/receive spec (CL-63) for §170.315(b)(7)/(b)(8) — critical for Part 2 SUD data exchange.
  7. Create DEA EPCS spec (CL-64) for 21 CFR 1311 — required for MAT prescribing.
  8. Create Contexture HIE integration spec (PF-108) — highest-ROI Arizona move for DAP/TI 2.0.
  9. Create EKRA compliance spec (PF-107) — P0 legal priority due to NorthSight relationship.
  10. Create DSI transparency spec (CL-65) for §170.315(b)(11) — required before AI features ship.
Note: Alignment score revised from 3.0/5.0 to 2.5/5.0. USCDI v3 is now the baseline (Jan 1, 2026); most BH competitors already meet that bar. Target 4.0/5.0 within 6 months. See docs/compliance/ONC_REGULATORY_READINESS_IMPLEMENTATION_PLAN.md for the full implementation plan with 12 new skills and 12 new specs.