Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

Version: 1.0.0 Last Updated: 2026-05-15 Source: Compass Artifact deep review + ONC Certification Gap Matrix + existing compliance infrastructure analysis Owner: Product / Compliance / CL / PM / PF

1. Executive Summary

This plan operationalizes the findings from the May 2026 ONC Certification Strategy & Regulatory Readiness analysis (“Compass Artifact”) into concrete deliverables: new skills, updated rules, new specs, regulatory tracker updates, and AGENTS.md amendments. The recommendation is Alignment-Only now, Modular certification when a trigger fires — but the alignment work itself is substantial.

Key Strategic Decisions

DecisionRecommendationTrigger to Escalate
ONC CertificationAlignment-Only (no formal filing)Named enterprise prospect with “CEHRT required” in mandatory RFP terms
Contexture/HIESign Participation Agreement within 30 daysAlready justified — DAP 8.0% uplift
DEA EPCSBegin partner evaluation immediatelyFirst MAT-prescribing customer signed
HITRUSTe1 assessment within 12 monthsKipu competitive parity
EKRA/NorthSightP0 legal review immediatelyShared-founder structure is textbook risk

2. Deep Review — Gaps Found in Compass Artifact

2.1 Items Missing from the Compass Artifact

The compass artifact is thorough but omits several areas that Encore’s existing compliance infrastructure already tracks or should add:
#GapSeverityRationale
1OTP/Part 8 compliance (42 CFR Part 8) — mentioned in passing under EPCS but no dedicated analysis of OTP licensing, SAMHSA certification, and medication-unit dosing rulesMediumEncore serves MAT/OTP programs; Part 8 governs OTP operations including daily dosing, take-home schedules, and drug testing. Existing tracker already tracks this.
2Arizona PDMP (CSPMP) integration — the regulatory-compliance rule lists this but the compass artifact omits PDMP query requirements entirelyHighA.R.S. § 36-2608 requires PDMP query before prescribing opioids. MAT prescribers using Encore must have PDMP integration or documented workaround.
3Psychotherapy notes segregation (45 CFR 164.501) — existing decision tree includes this but compass artifact does not address ONC criterion mapping for psychotherapy note handlingLowBH-specific HIPAA carve-out; existing compliance tracking covers this.
4HIPAA Breach Notification (HITECH Act) — compass artifact discusses information blocking penalties but omits breach notification obligations under HITECH, which the IT compliance tracker already coversLowAlready tracked in IT_SECURITY_COMPLIANCE_TRACKING.md.
5CMS-0057-F Prior Authorization API — compass artifact mentions HTI-2 withdrawal of (g)(30)-(g)(33) but does not explicitly cover the separate CMS-0057-F rule (finalized Jan 2024) requiring payer prior auth APIs by Jan 1, 2027 — existing spec PM-52 covers thisMediumPM-52 already tracks Da Vinci CRD/DTR/PAS for this rule.
6HEDIS/Quality Measures — compass artifact §7 mentions CARF/Joint Commission as N/A for Encore (correct) but does not address BH HEDIS measures (FUH, FUM, AMM, SSD) that payer contracts frequently require. CL-51 spec and GR tracker already cover this.LowAlready in compliance tracker and CL-51 spec.
7Collections compliance (TCPA/FDCPA/PCI) — compass artifact omits patient collections compliance, which the regulatory tracker already coversLowAlready tracked in REGULATORY_COMPLIANCE_TRACKER.md.
8No Surprises Act/Good Faith Estimate — omitted from compass artifact; PM tracker covers thisLowAlready tracked; PM specs address GFE.
9Surescripts certification pathway — compass artifact mentions e-prescribing partners but does not detail Surescripts’ staged certification process (application → validation → production) which is separate from both ONC and DEA EPCSMediumCritical path dependency for any e-prescribing feature.
10State Medicaid Promoting Interoperability successors — compass artifact correctly notes AZ PI ended Oct 2021 but does not survey other states (e.g., CO, NY, TX) that still have active HIT incentive programs, relevant for multi-state expansion via PF-96LowDeferred until multi-state expansion is in scope.

2.2 Items in Compass Artifact Not Yet in Encore’s Compliance Infrastructure

#New FindingCurrent CoverageAction Required
1DEA EPCS certification (21 CFR 1311) — required for MAT prescribingNot trackedAdd to regulatory tracker + create new spec
2EKRA (18 U.S.C. § 220) — NorthSight relationship riskNot trackedAdd to regulatory tracker + legal memo
3Section 1557 ACA nondiscrimination — language access/TTY for patient portalPartially covered under WCAG/Section 504Expand coverage
4ADA Title III digital accessibility (WCAG 2.1 AA) — DOJ April 2024 final ruleTracked under PF-93 + Section 504Update timeline
5SAMHSA SUPTRS/MHBG/TEDS reporting — block-grant reporting hooksNot trackedAdd to GR compliance tracker
6USCDI+ Behavioral Health profiles — SAMHSA/ONC $20M initiativeNot trackedAdd to CL-16 roadmap
7HITRUST e1 → i1 pathway — competitive parity with KipuNot trackedAdd to IT compliance tracker
8DS4P (Data Segmentation for Privacy) — §170.315(b)(7)/(b)(8) — critical for Part 2 SUD dataGap matrix shows “None” for b(7)/b(8)Create new spec
9DEA Special Registration for Telemedicine — MAT-via-telehealthNot trackedAdd to regulatory tracker
10Contexture/Health Current Participation Agreement — DAP/TI 2.0 gateNot tracked as deliverableAdd to roadmap
11HTI-4 NCPDP SCRIPT 2023011 — Jan 1, 2028 deadlineMentioned in gap matrixEnsure CL-06 enhancement tracks this
12Information blocking penalty enforcement — $1M per violationTracked in regulatory trackerEnsure PM-55 info-blocking workflows complete

3. New Skills to Create

Skills are organized by priority tier. Each skill follows the .cursor/skills/ convention with YAML frontmatter, references directory where needed, and pointers to authoritative docs.

Tier 1 — Alignment-Critical (Create in first 30 days)

3.1 onc-alignment-assessment (.cursor/skills/)

Purpose: Assess any feature or spec against ONC alignment criteria without requiring formal certification. Scope:
  • Map feature data elements to USCDI v3 data classes/elements
  • Check US Core 6.1.0 FHIR profile conformance
  • Validate SMART App Launch v2 OAuth flow design
  • Evaluate information blocking compliance
  • Generate alignment score (0-5) per criterion family
References directory:
  • references/uscdi-v3-data-classes.md — USCDI v3 data class inventory
  • references/onc-criterion-checklist.md — Per-criterion implementation checklist
Trigger phrases: “ONC alignment”, “USCDI mapping”, “certification readiness”, “FHIR conformance check”

3.2 fhir-profile-conformance (.cursor/skills/)

Purpose: Author and validate FHIR R4 resources against US Core 6.1.0 + USCDI v3 profiles. Scope:
  • US Core 6.1.0 profile requirements per resource type
  • USCDI v3 data element mapping
  • CapabilityStatement authoring
  • Inferno test alignment
  • USCDI+ BH profile awareness (future-proofing)
References directory:
  • references/us-core-profiles.md — Profile-by-profile requirements
  • references/fhir-resource-patterns.md — Encore-specific FHIR resource authoring patterns
Trigger phrases: “FHIR profile”, “US Core”, “CapabilityStatement”, “Inferno test”, “USCDI mapping”

3.3 ds4p-privacy-segmentation (.cursor/skills/)

Purpose: Implement Data Segmentation for Privacy (DS4P) for 42 CFR Part 2 SUD data. Scope:
  • DS4P confidentiality codes (V, R, N) on C-CDA and FHIR resources
  • Part 2 consent-to-segmentation pipeline
  • Redisclosure notice generation
  • DS4P send/receive criterion mapping for §170.315(b)(7)/(b)(8)
  • Integration with CL-11 consent management
References directory:
  • references/ds4p-codes.md — Confidentiality code table and mapping rules
  • references/part2-consent-flows.md — Part 2 → DS4P decision tree
Trigger phrases: “DS4P”, “data segmentation”, “privacy segmentation”, “Part 2 FHIR”, “confidentiality codes”

3.4 information-blocking-compliance (.cursor/skills/)

Purpose: Ensure all data-sharing decisions comply with 21st Century Cures Act information blocking provisions. Scope:
  • Exception documentation (8 exceptions + TEFCA Manner + Protecting Care Access)
  • Denial taxonomy and review queue
  • Annual governance packet assembly
  • OIG CMP risk assessment ($1M per violation)
  • Information blocking response workflow
References directory:
  • references/exception-matrix.md — Exception-by-exception documentation template
  • references/denial-taxonomy.md — Standardized denial categories and review workflow
Trigger phrases: “information blocking”, “Cures Act”, “data sharing denial”, “EHI export”, “exception documentation”

Tier 2 — Pre-Certification Readiness (Create in 30-90 days)

3.5 dsi-transparency-disclosure (.cursor/skills/)

Purpose: Generate §170.315(b)(11) DSI source attribute disclosures for AI features. Scope:
  • Source attribute documentation per HTI-1 requirements
  • Predictive DSI vs. evidence-based DSI classification
  • Algorithm transparency requirements
  • User-facing disclosure content generation
  • Integration with PM-64 (AI coding) and CL-08 (CDS)
Trigger phrases: “DSI transparency”, “AI disclosure”, “b(11)”, “algorithm transparency”, “predictive DSI”

3.6 epcs-audit-preparation (.cursor/skills/)

Purpose: Prepare for DEA EPCS third-party audit (21 CFR 1311). Scope:
  • Identity proofing documentation (NIST SP 800-63-3)
  • Two-factor authentication evidence
  • Prescription signing workflow design
  • Audit trail requirements for controlled substances
  • Drummond/DEA audit checklist
  • ARCOS reporting integration points
Trigger phrases: “EPCS”, “DEA audit”, “controlled substance”, “e-prescribing controlled”, “buprenorphine”, “21 CFR 1311”

3.7 contexture-hie-integration (.cursor/skills/)

Purpose: Guide integration with Contexture (Health Current) HIE for AHCCCS DAP/TI 2.0. Scope:
  • ADT notification send/receive (HL7 v2.5.1)
  • CCD exchange (C-CDA R2.1)
  • Contexture participation agreement requirements
  • DAP milestone evidence generation
  • TEFCA connectivity path (Contexture → eHealth Exchange QHIN → national)
Trigger phrases: “Contexture”, “Health Current”, “HIE integration”, “ADT notification”, “DAP attestation”, “TI 2.0”

3.8 hitrust-assessment-preparation (.cursor/skills/)

Purpose: Prepare for HITRUST e1 (Essentials) validated assessment. Scope:
  • HITRUST CSF control mapping to existing Encore controls
  • Evidence collection checklist
  • Gap analysis between SOC 2 Type II and HITRUST e1
  • Authorized external assessor engagement guide
  • Escalation path to i1
Trigger phrases: “HITRUST”, “e1 assessment”, “i1 assessment”, “security certification”, “HITRUST CSF”

Tier 3 — Certification-Phase Skills (Create when trigger fires)

3.9 onc-criterion-mapper (.agents/skills/)

Purpose: Generate per-criterion compliance evidence packages. Scope:
  • Criterion text → Encore feature → test case → screenshot/log evidence mapping
  • Relied-upon software documentation
  • CHPL listing metadata generation
  • Mandatory disclosure URL content

3.10 inferno-test-author (.agents/skills/)

Purpose: Write Inferno test plans and expected response fixtures. Scope:
  • (g)(10), (g)(7), (g)(9) test plan authoring
  • CapabilityStatement validation fixtures
  • SMART App Launch v2 test flow documentation
  • CI harness integration for Inferno tests

3.11 rwt-plan-author (.agents/skills/)

Purpose: Generate Real World Testing plans and results reports. Scope:
  • RWT plan template per ONC requirements
  • Metrics collection framework
  • Results report generation
  • Enforcement discretion tracking (HTI-5 pending)

3.12 drummond-engagement-orchestrator (.agents/skills/)

Purpose: Pre-populate Drummond ATL test scripts and ACB documentation. Scope:
  • Drummond Advisory Services engagement guide
  • ATL test script pre-population
  • ACB vendor form completion
  • CHPL listing preparation
  • Compliance Learning Series planning


4. Regulatory Rules Updates

4.1 Update .cursor/rules/regulatory-compliance.md

Changes needed: Add the following branches to the decision tree:
├─ CL (Clinical)
│  ├─ [EXISTING branches...]
│  ├─ Involves e-prescribing of controlled substances? → DEA EPCS (21 CFR 1311), Drummond audit
│  ├─ Involves MAT/buprenorphine prescribing? → DEA EPCS + X-waiver removal (CAA 2023 §1262) + DEA Telemedicine Special Registration
│  ├─ Involves FHIR data export with SUD data? → DS4P §170.315(b)(7)/(b)(8) confidentiality coding
│  ├─ Involves AI clinical recommendations? → HTI-1 DSI transparency §170.315(b)(11)
│  └─ Involves Arizona HIE/Contexture? → AHCCCS DAP/TI 2.0 requirements

├─ PM (Practice Management)
│  ├─ [EXISTING branches...]
│  ├─ Involves patient access API? → ONC HTI-1 §170.315(g)(10), SMART App Launch v2, US Core 6.1.0
│  ├─ Involves AI coding/billing? → HTI-1 DSI transparency §170.315(b)(11), human acceptance required
│  └─ Involves e-prescribing standards? → HTI-4 NCPDP SCRIPT 2023011 (deadline Jan 1, 2028)

├─ PF (Platform Foundation)
│  ├─ [EXISTING branches...]
│  ├─ Involves patient portal language access? → Section 1557 ACA nondiscrimination
│  └─ Involves HITRUST assessment? → HITRUST CSF e1/i1 controls

├─ GR (Governance & Risk)
│  ├─ [EXISTING branches...]
│  └─ Involves SAMHSA reporting? → SUPTRS, TEDS, MHBG block grant data
Add new footer section:
**ONC/Interoperability-specific:**
- `docs/compliance/ONC_CERTIFICATION_GAP_MATRIX.md` — Criterion-level gap analysis
- `docs/compliance/ONC_REGULATORY_READINESS_IMPLEMENTATION_PLAN.md` — Skills, specs, and roadmap

**Beyond-ONC compliance:**
- EKRA (18 U.S.C. § 220) — Kickback risk for recovery treatment referrals
- HITRUST e1/i1 — Security assessment pathway
- DEA EPCS (21 CFR 1311) — Controlled substance e-prescribing audit

4.2 Update .cursor/skills/module-regulatory-compliance/

Changes to SKILL.md:
  • Add ONC alignment, FHIR/USCDI, DS4P, EPCS, HITRUST, and EKRA to the decision tree
  • Add new common mistakes table entries for ONC-specific errors
  • Update tags to include [regulatory, compliance, HIPAA, ONC, FHIR, USCDI, EPCS, DS4P, HITRUST]
Changes to references/per-core-compliance.md:
  • Add “ONC / Interoperability Compliance” section under CL
  • Add “EPCS / DEA Audit” section under CL
  • Add “ONC Patient Access API” section under PM
  • Add “HITRUST Assessment” section under IT/PF
  • Add “EKRA / Anti-Kickback” section under GR/PF
  • Add “SAMHSA Reporting” section under GR

5. New Specs Required

5.1 Specs to Create (ordered by priority)

PrioritySpec IDTitleCoreRationale
P0PF-107EKRA Compliance and Related-Party Transaction ControlsPFShared-founder NorthSight relationship; higher enforcement probability than ONC
P1CL-63DS4P Data Segmentation for Privacy (Send/Receive)CL§170.315(b)(7)/(b)(8); critical for Part 2 SUD data in FHIR/C-CDA exchange
P1CL-64DEA EPCS Integration and Audit ReadinessCL21 CFR 1311; required for MAT prescribing market
P1PF-108Contexture HIE Integration (ADT/CCD Exchange)PFAHCCCS DAP 8.0% uplift; TI 2.0 eligibility; highest-ROI Arizona move
P2PF-109HITRUST e1 Security Assessment ReadinessPFCompetitive parity with Kipu; hospital/payer procurement signal
P2CL-65DSI Transparency Disclosure FrameworkCL§170.315(b)(11) HTI-1; required if AI clinical features ship
P2PM-72ONC API Conditions of Certification GovernancePMTerms, fees, transparency, maintenance for FHIR APIs
P2CL-16-EN-03USCDI+ Behavioral Health Profile MappingCLSAMHSA/ONC $20M initiative; proactive alignment
P3GR-26SAMHSA SUPTRS/TEDS/MHBG Reporting IntegrationGRBlock-grant reporting for SOR sub-grantees
P3CL-66Immunization Registry Reporting (ASIIS/VXU)CL§170.315(f)(1); required for MAT/OTP clinics administering vaccines
P3CL-67Electronic Case Reporting (eCR)CL§170.315(f)(5); HIV/HCV reportable conditions for MAT/SUD programs
P3PM-73Surescripts Certification PathwayPMProduction e-prescribing requirement; staged onboarding

5.2 Existing Specs Requiring Updates

SpecUpdate Needed
CL-16Add USCDI v3 mapping checklist; reference USCDI+ BH; add Inferno CI harness requirement; add DS4P cross-reference to CL-63
CL-16-EN-02Update US Core from “planned” to alignment target with specific 6.1.0 profile list
PM-55Add information blocking denial taxonomy; add §170.315(g)(10) SMART v2 requirements; cross-reference new PM-72 governance spec
CL-06Add HTI-4 NCPDP SCRIPT 2023011 transition timeline; cross-reference CL-64 EPCS
CL-48Add C-CDA R4.1 companion guide update; cross-reference DS4P send via CL-63
PM-52Note HTI-2 withdrawal of (g)(30)-(g)(33) but CMS-0057-F independence; track HTI-5
PF-93Add DOJ April 2024 Title II WCAG 2.1 AA rule; add Section 1557 language access
PF-44Add EHI export criterion b(10) evidence requirements
CL-11Cross-reference DS4P spec CL-63; add redisclosure notice in FHIR context

6. AGENTS.md Updates

6.1 Root AGENTS.md

Add to “What AI Must NEVER Do”:
- Ship FHIR resources that do not conform to US Core 6.1.0 profiles when CL-16/PM-55 features are in scope.
- Omit DS4P confidentiality codes on any FHIR resource or C-CDA document containing 42 CFR Part 2 SUD data.
- Implement controlled substance e-prescribing without DEA EPCS audit trail (21 CFR 1311).
- Bypass information blocking exception documentation when denying data access requests.
Add to “Other Patterns (Pointers)”:
- **ONC Alignment (Alignment-Only):** Build to USCDI v3 + US Core 6.1.0 + SMART v2 + DS4P without formal certification. Gap matrix: `docs/compliance/ONC_CERTIFICATION_GAP_MATRIX.md`. Implementation plan: `docs/compliance/ONC_REGULATORY_READINESS_IMPLEMENTATION_PLAN.md`.
- **Contexture/HIE (Arizona):** ADT and CCD exchange via Contexture for AHCCCS DAP/TI 2.0. See PF-108.
- **DEA EPCS:** Required for MAT prescribing. Third-party audit via Drummond. See CL-64.
- **DS4P (Part 2 + FHIR):** Confidentiality coding on all SUD data in FHIR/C-CDA. See CL-63.
- **HITRUST e1:** Security assessment for hospital/payer procurement. See PF-109.
- **EKRA:** Anti-kickback for recovery treatment referrals. P0 legal priority. See PF-107.
Add to “Landmines (Non-Discoverable)“:
- [2026-05] USCDI v3 is the baseline as of Jan 1, 2026 (with ASTP/ONC enforcement discretion through Feb 28, 2026). All new FHIR work must target v3, not v1.
- [2026-05] HTI-2 non-finalized provisions (g(30)-(g)(33), CDS Hooks, Subscriptions) were withdrawn Dec 29, 2025. Do not implement withdrawn criteria.
- [2026-05] OIG information blocking penalties ($1M per violation) are live since Sept 2023. Joint HHS-OIG/ASTP enforcement alert issued Sept 4, 2025.
- [2026-05] DEA Telemedicine Special Registration rule remains in flux; MAT-via-telehealth must use feature flags.

6.2 Core-Specific AGENTS.md Updates

src/cores/cl/AGENTS.md:
  • Add DS4P requirements for SUD data in FHIR/C-CDA
  • Add EPCS audit trail requirements
  • Add USCDI v3 / US Core 6.1.0 conformance requirement for all FHIR resources
  • Add DSI transparency requirement for AI clinical features
src/cores/pm/AGENTS.md:
  • Add information blocking exception documentation requirement
  • Add ONC API governance (PM-72) reference
  • Add HTI-4 NCPDP SCRIPT 2023011 deadline awareness
  • Add CMS-0057-F Da Vinci timeline independence from HTI-2 withdrawal

7. Regulatory Tracker Updates

7.1 Add to REGULATORY_COMPLIANCE_TRACKER.md

RegulationRequirementDeadlineOwning SpecStatus
DEA EPCS (21 CFR 1311)Third-party audit for controlled substance e-prescribingBefore MAT prescribing launchCL-64Not Started
EKRA (18 U.S.C. § 220)Anti-kickback compliance for NorthSight relationshipImmediate (P0)PF-107Not Started
HITRUST e1Security assessment validated by authorized external assessor12 monthsPF-109Not Started
Section 1557 ACALanguage access, TTY, nondiscrimination in patient portalOngoingPF-93 updatePartially Covered
ADA Title III / DOJ RuleWCAG 2.1 AA for patient-facing web propertiesHHS May 2026 deadlinePF-93In Progress
SAMHSA SUPTRS/TEDSTreatment episode reporting for block-grant compliancePer grant cycleGR-26Not Started
USCDI+ BHFHIR BH profiles mappingProactive alignmentCL-16-EN-03Not Started
DS4P b(7)/b(8)Privacy segmentation for SUD data in FHIR/C-CDABefore production FHIR exchangeCL-63Not Started
HTI-4 NCPDP SCRIPT 2023011E-prescribing standard upgradeJan 1, 2028CL-06 updateNot Started
DEA Telemedicine RegistrationMAT-via-telehealth prescribing rulesPending final rule (2026?)CL-64Monitoring
Contexture ParticipationHIE connectivity for AHCCCS DAP/TI 2.030 days (business)PF-108Not Started
OIG Info Blocking CMP$1M per violation for HIT developersLive since Sept 2023PM-55In Progress

7.2 Update ONC_CERTIFICATION_ROADMAP.md

  • Increase version to 2.0.0
  • Replace generic phased timeline with the compass artifact’s 30/90/180/365-day roadmap
  • Add DEA EPCS, Contexture, HITRUST, and EKRA as parallel tracks
  • Add competitive landscape section (10 of 11 BH competitors are ONC-certified)
  • Add trigger-based escalation framework
  • Cross-reference gap matrix and implementation plan

7.3 Update ONC_CERTIFICATION_GAP_MATRIX.md

  • Add DEA EPCS row
  • Add EKRA risk assessment row
  • Add Contexture/DAP evidence requirements
  • Update alignment score from 3.0 to 2.5 per compass artifact analysis
  • Add USCDI+ BH as future-state alignment target

8. Content Licensing Tracker

Add to compliance infrastructure (new section in AUTHORITATIVE_REFERENCES.md):
ContentLicenseCostStatus
LOINCRegenstrief InstituteFreeNot yet obtained
SNOMED CT US EditionNLM UMLS MetathesaurusFree (US)Not yet obtained
RxNormNLMFreeNot yet obtained
ICD-10-CMCMSFreeNot yet obtained
CPTAMA500500–3,500/yr for distributionNot yet licensed
CVX/MVX vaccine codesCDCFreeNot yet obtained
NCPDP SCRIPTNCPDPMembership requiredNot yet licensed
Action: Obtain NLM UMLS license within 30 days (prerequisite for SNOMED CT, RxNorm, LOINC distribution in production).

9. Phased Implementation Timeline

Phase 1: Foundation (Days 0–30)

#DeliverableTypeOwner
1Create PF-107 (EKRA) specSpecLegal/PF
2Create PF-108 (Contexture) specSpecPF
3Update regulatory-compliance.md ruleRulePlatform
4Update module-regulatory-compliance skillSkillPlatform
5Update AGENTS.md (root + CL + PM)DocsPlatform
6Update REGULATORY_COMPLIANCE_TRACKER.mdDocsCompliance
7Update ONC_CERTIFICATION_ROADMAP.md to v2.0DocsCompliance
8Create onc-alignment-assessment skillSkillPlatform
9Create information-blocking-compliance skillSkillPlatform
10Obtain NLM UMLS licenseBusinessProduct

Phase 2: Interoperability Core (Days 31–90)

#DeliverableTypeOwner
11Create CL-63 (DS4P) specSpecCL
12Create CL-64 (DEA EPCS) specSpecCL
13Create fhir-profile-conformance skillSkillPlatform
14Create ds4p-privacy-segmentation skillSkillPlatform
15Create dsi-transparency-disclosure skillSkillPlatform
16Create epcs-audit-preparation skillSkillPlatform
17Create contexture-hie-integration skillSkillPlatform
18Update CL-16, CL-16-EN-02, PM-55, CL-06, CL-48 specsSpec updatesCL/PM
19Create PF-109 (HITRUST e1) specSpecPF/IT
20Create PM-72 (ONC API Governance) specSpecPM

Phase 3: Expanded Coverage (Days 91–180)

#DeliverableTypeOwner
21Create CL-65 (DSI Transparency) specSpecCL
22Create CL-16-EN-03 (USCDI+ BH) specSpecCL
23Create GR-26 (SAMHSA Reporting) specSpecGR
24Create hitrust-assessment-preparation skillSkillPlatform
25Update per-core-compliance.md referencesSkill refPlatform
26Create CL-66 (Immunization ASIIS) spec if in-scopeSpecCL
27Create CL-67 (eCR) spec if in-scopeSpecCL
28Create PM-73 (Surescripts) specSpecPM

Phase 4: Certification Readiness (Months 6–12, only if trigger fires)

#DeliverableTypeOwner
29Create onc-criterion-mapper skillSkillPlatform
30Create inferno-test-author skillSkillPlatform
31Create rwt-plan-author skillSkillPlatform
32Create drummond-engagement-orchestrator skillSkillPlatform
33Build Inferno CI harnessEngineeringCL/PM
34Formal Drummond Advisory engagementBusinessProduct

10. Validation Checklist

Before considering this plan complete, verify:
  • All 12 new skills have SKILL.md with correct YAML frontmatter
  • All new specs follow specs/_templates/SPEC_TEMPLATE.md structure
  • SPEC_STATUS_REGISTRY.md updated with new spec IDs
  • regulatory-compliance.md rule updated with new decision tree branches
  • module-regulatory-compliance skill and references updated
  • Root AGENTS.md updated with new patterns/landmines/prohibitions
  • Core AGENTS.md files (CL, PM) updated
  • REGULATORY_COMPLIANCE_TRACKER.md has new rows
  • ONC_CERTIFICATION_ROADMAP.md version bumped and expanded
  • ONC_CERTIFICATION_GAP_MATRIX.md updated with new findings
  • AUTHORITATIVE_REFERENCES.md has content licensing section
  • All cross-references between documents are valid

11. Cross-References