Configure MarketLink CMS EDE runs
Configure MarketLink access, validate CMS-native mappings, launch browser/API collectors from the approved runtime boundary, review generated artifacts, and package only after auditor gates are clear. This is the operator workspace for real CMS EDE evidence collection.
ControlFrame should not be the public SaaS reaching into internal apps. The web app plans and reviews; the private runner executes inside the organization or trusted operator workstation where URLs, credentials, browser state, CMS UAT, and API endpoints are available.
61% preflight readiness, 2 blocked package gates, 2 review gates, and 24 credential/runtime blockers.
3 blocked / 2 review checks
30 total CMS EDE scenarios
CMS UAT, IDM, Okta, API, or manual dependencies
Visible scope, not evidence yet
292 capture mappings
87 artifacts in latest run
2 blocked / 2 review
Configure the target, bind access, choose the test scope, and run it.
Run all, rerun one suite, or collect auditor evidence only for the test that needs it.
The dashboard separates source coverage from executable automation so assessors can see UI, eligibility, API, and package lanes without confusing current runnable tests with rows that still need generated collectors, credentials, or manual evidence.
Entire CMS EDE program
partialAll registered CMS EDE source-backed browser, API, document, configuration, and manual evidence lanes.
Eligibility Results Toolkit / MarketLink 3.C field-level script
readyPhase 3 PY2026 Eligibility Results Toolkit Test Case 3.C against /admin/application-preview.
Application UI Toolkit
partialApplication UI Toolkit UI Questions Item #1-#302, including conditional branches, required text, disclosures, inputs, dropdowns, and applicationAnswers mappings.
Eligibility Results Toolkit
partialEligibility Results Toolkit Phase 3 test case IDs, determination payloads, plan eligibility, APTC/CSR, Medicaid/CHIP, and SEP outcomes.
Partner Test Case Suite
partialCMS EDE Partner Test Case Suite IDs and Test Case Suite User Guide execution evidence.
API Functional Integration Toolkit
partialAPI Functional Integration Toolkit IDs, EDE API Companion Guide operations, and FFM Hub integration controls.
Communications Toolkit
partialCommunications Toolkit requirement numbers, standardized disclaimers, legal notices, language assistance, and consumer-facing content.
Eligibility Determination Notices
partialEligibility Determination Notice generation, content, language, distribution, archive, and metadata evidence.
Identity Proofing
blockedYear 9 RIDP-RBA / GetRecord requirements, NIST SP 800-63-3 identity assurance, and acceptable documentation paths.
Registration and Onboarding
partialAgent/broker registration, onboarding, pending approval, MFA setup, authorization gates, and role-specific access.
Security Controls - ARC-AMPE / MARS-E
partialARC-AMPE, MARS-E 2.2, NIST SP 800-53 Rev. 5, SSPP, SAR, POA&M, ISA, and privacy/security controls.
Current full matrix coverage is 148 of 1155 source rows. One-click execution can run every runnable collector today, but full auditor coverage requires generating the remaining toolkit-specific collectors and binding CMS UAT/API access.
See every registered CMS EDE test by toolkit, then dry-run one test or collect evidence for the whole suite.
This is the operator view for Application UI, Eligibility Results, API FIT, Partner, Communications, EDN, identity, registration, and security lanes. Rows marked blocked stay visible so assessors can see what is missing without silently losing scope.
Project and target application
Choose the collection adapter
Runtime access and CMS endpoints
Assisted application, plan, consent, and submission flows.
Agent-assisted application and onboarding-adjacent flows.
Eligibility, notices, EDN, identity, and dashboard flows.
Role, reporting, and agency administration evidence.
Security, onboarding, and configuration evidence slots.
Select tests, suites, or full CMS EDE
This adapter executes one source-anchored auditor script end to end: it logs in as the platform-admin demo account, starts from a blank answer state, fills the 3.C workbook inputs in forward order, traverses all 41 steps, and fails any mapped workbook field that is missing from the UI or final answer state.
Launch validation, dry-run, or evidence collection
Choose validate, dry-run, or collect evidence. The monitor will show the active phase, progress, and the latest runner events while the request is executing.
Events will appear here immediately after a run starts.
Run the CMS EDE module where the target can actually be reached
ControlFrame does not need source-code access for the normal evidence run. It needs authorized runtime access: target URLs, browser login personas, approved MFA/session handling, CMS UAT or toolkit endpoints, and API routes that the collector can observe or call from inside the customer boundary.
Works only when the target app, auth, and CMS test endpoints are reachable from the runner boundary.
Operator-led Playwright/API collection on a trusted workstation with local evidence review before export.
A customer-controlled VM/container runner reaches internal URLs, vaults, IDM, Okta, CMS UAT, and APIs.
Raw evidence remains local; reviewed, hashed, redacted packages move through a signed export path.
Every run starts with CMS-native authority, not ControlFrame IDs
The collector validates the Year 9 source contract before collection. Evidence must map back to CMS toolkit documents, native framework identifiers, source rows, and prescribed evidence shapes.
cms-ede-year9-source-native-evidence-contract
CMS toolkit/source authorities
scenario source references
explicit native ID mappings
Source currentness
Existing reference evidence remains format-reference only. Fresh ControlFrame collector runs must create audit-readiness evidence.
Show CMS identifiers first, then ControlFrame orchestration IDs
CMS reviewers and third-party auditors should be able to reconcile every artifact back to toolkit, row, case, step, and security control references. Internal IDs like UI-006 or scenario slugs help operators run the module, but the package has to lead with the CMS-native reference.
Full-page screenshots, DOM/text extract, route, persona, timestamp, source-row sidecar.
Redacted request/response JSON, status, endpoint, checksum, source-row evidence index.
Eligibility result screenshot, API payload evidence, reviewer notes for CMS UAT dependencies.
Scenario trace, screenshots, JSON captures, blocker notes for CMS-controlled paths.
Message artifact, delivery proof, notice payload, redaction manifest, manual/connector evidence slot.
SSPP, SAP, SAR, POA&M, IAM/IDM/Okta evidence, scanner reports, reviewer approval state.
Break the run exactly where CMS breaks the audit
The console separates CMS Year 9 business requirement toolkits, API functional testing, identity proofing, onboarding, and security/privacy audit package evidence. ControlFrame orchestration IDs stay internal; auditor-facing rows preserve CMS source files, native references, required evidence, and blocked dependencies.
Application UI Toolkit
readyThe applicable phase Application UI Toolkit is reviewed in full; auditors need a methodology that evaluates each UI element, not only test-case-covered questions.
- Full-page screenshots for each applicable UI element and conditional branch
- Source-row mapping keyed to UI Questions Item #
- Application answers / extracted text where emitted by the application
- screenshots/application-ui-toolkit/*.png + *.meta.json
- source-row-evidence-index.json
- text-extracts/application-ui-toolkit/*.txt
Eligibility Results Toolkit
credential gatedPhase-specific required test cases must be completed according to the User Guide tab, with screenshots through eligibility results and consistency between the results page and EDN.
- Entire application-flow screenshots from the required starting point through eligibility results
- Eligibility results page screenshot with correct EDN
- Raw Get App API response JSON for the application version depicted
- screenshots/eligibility-results-toolkit/*.png + *.meta.json
- json-responses/eligibility-results-toolkit/*.json
- reports/source-row-evidence-map.csv
EDE Partner Test Case Suite
credential gatedSupplemental partner test cases increase approval readiness and should not replace required toolkit cases.
- CMS UAT test case ID, step, and execution result
- Per-step screenshot or API request/response evidence
- Exception log for unresolved UAT cases
- reports/latest-report.html
- screenshots/partner-test-case-suite/*.png
- open-blockers.json
API Functional Integration Toolkit
credential gatedEach required API test case needs correct results and complete required evidence, including complete request/response headers and body where required; raw JSON/XML must remain unmodified.
- Complete header and body for required API request and response
- Raw JSON/XML captured before redaction copy is produced
- Separate evidence for Agent/Broker and Consumer pathways when both are in scope
- json-responses/api-functional-integration-toolkit/*.json
- artifact-manifest.json
- redaction-manifest.json
EDE Communications Toolkit
dry-runRequired consumer communications, notices, disclaimers, language access, and associated critical communications must be evidenced in the applicable pathway.
- Screenshots of required communication and notice surfaces
- Extracted text next to screenshot metadata
- Non-English-language application UI and associated communications where applicable
- screenshots/communications-toolkit/*.png + *.meta.json
- text-extracts/communications-toolkit/*.txt
- source-row-evidence-index.json
Eligibility Determination Notices / Notice Retrieval
credential gatedThe consumer must be able to access the most recent EDN; EDN and raw Get App API JSON requirements apply across required toolkit cases.
- EDN download/view screenshot
- Notice Retrieval or Metadata Search API request/response capture
- EDN consistency check against eligibility results page
- screenshots/edn-notices/*.png
- json-responses/edn-notices/*.json
- source-row-evidence-index.json
Identity Proofing / RIDP-RBA / FARS
manual / connectorIdentity proofing, RBA outcomes, acceptable documentation, IDM, Okta, and MFA gates must be evidenced or explicitly blocked until authorized access exists.
- RIDP/RBA UI outcome screenshot or auditor-observed result
- Redacted response metadata where available
- IDM/Okta/configuration evidence by reference
- manual-evidence-registry.json
- screenshots/identity-proofing/*.png
- open-blockers.json
Business Audit Instructions / DE Entity Documentation
manual / connectorAuditors must provide complete descriptions of each requirement and must not exclude required review-standard criteria; the DE Entity Documentation Package must be complete at submission.
- Completed business audit instructions/report template sections
- DE Entity Documentation Package references
- Evidence resolving CMS feedback by toolkit or related risk
- 08-manual-evidence/manual-evidence-registry.json
- 06-auditor-packages/<package-id>/business-audit/
- open-blockers.json
Registration, Onboarding, and Mini-Audit Access
manual / connectorTesting credentials must be valid and all APIs/components accessible during CMS mini audit; post-submission changes must follow the applicable change process.
- Registration and onboarding status evidence
- Valid testing credential proof by persona/pathway
- Change/EICR and approval-gate documentation where applicable
- manual-evidence-registry.json
- open-blockers.json
- reports/latest-report.html
Security and Privacy Audit - ARC-AMPE / MARS-E
manual / connectorThe security/privacy audit package needs SAP, ARC-AMPE SSPP, SAR, and POA&M completeness; SAR findings include documentation review, control testing, scanning, penetration testing, and interviews.
- SAP scope and methodology before SCA
- ARC-AMPE Volume 2 SSPP control implementation details
- SAR all findings and POA&M open finding traceability
- 08-manual-evidence/manual-evidence-registry.json
- security-evidence/scans-and-pentest/
- 06-auditor-packages/<package-id>/security-privacy/
A collection run behaves like a flight recorder, not a black box
Operators can explain each stage to CMS assessors: the target configuration, source validation, dry-run, artifact capture, reviewer gate, and export decision.
Target URL, persona credentials, MFA path, and approved audit window.
Prove every runnable scenario maps to CMS source documents and native IDs.
Exercise scope, routes, selectors, and blockers before writing evidence.
Capture screenshots, text extracts, API JSON, and framework mappings.
Inspect redaction, evidence status, source rows, and open blockers.
Export only after source, manual, freshness, and redaction gates clear.
CMS EDE toolkit coverage
Each lane keeps the CMS toolkit language and native source references. Blocked lanes stay visible so the auditor can see what requires CMS UAT APIs, IDM, Okta, production credentials, or manual external evidence.
Application UI Toolkit
not-runApplication UI Toolkit UI Questions Item #1-#302, including conditional branches, required text, disclosures, inputs, dropdowns, and applicationAnswers mappings.
Eligibility Results Toolkit
not-runEligibility Results Toolkit Phase 3 test case IDs, determination payloads, plan eligibility, APTC/CSR, Medicaid/CHIP, and SEP outcomes.
Partner Test Case Suite
blockedCMS EDE Partner Test Case Suite IDs and Test Case Suite User Guide execution evidence.
API Functional Integration Toolkit
blockedAPI Functional Integration Toolkit IDs, EDE API Companion Guide operations, and FFM Hub integration controls.
Communications Toolkit
not-runCommunications Toolkit requirement numbers, standardized disclaimers, legal notices, language assistance, and consumer-facing content.
Eligibility Determination Notices
not-runEligibility Determination Notice generation, content, language, distribution, archive, and metadata evidence.
Identity Proofing
blockedYear 9 RIDP-RBA / GetRecord requirements, NIST SP 800-63-3 identity assurance, and acceptable documentation paths.
Registration and Onboarding
not-runAgent/broker registration, onboarding, pending approval, MFA setup, authorization gates, and role-specific access.
Security Controls - ARC-AMPE / MARS-E
not-runARC-AMPE, MARS-E 2.2, NIST SP 800-53 Rev. 5, SSPP, SAR, POA&M, ISA, and privacy/security controls.
Package readiness before anything leaves ControlFrame
0 errors / 0 warnings
1155 workbook-native IDs extracted; 0 pending sourceRefs
1155 source-native row(s), 1121 unique native ID(s), 1007 row(s) outside the original scenario registry
15 package checklist item(s), 0 without source paragraph matches
123 source file(s), 118 current local candidate(s), CMS zONE confirmation: not-confirmed-in-this-session
1 run(s), latest cms-ede-marketlink-application-preview-3c-2026-04-30T13-47-48-116Z, 87 artifacts
0 approved / 0 needs review / 27 missing manual evidence slot(s).
24 blocked scenario(s), 3 placeholder scenario(s); 27 missing and 0 needs-review external slot(s)
Review screenshot sidecars, text extracts, API JSON, and redaction manifest before export.