ACADM Phase 1 QA 082126.pdf
Posted: Aug. 21, 2026
• Type: .pdf
• Size: 0.22MB
Opportunity Assistant
Loading
Overview
Related Opportunity
Related Agency
Summary
This Q&A document for the Autonomous Coding and Automated Appeals & Denials Management Request for Solutions (RFS), issued by the Government/DHA, clarifies solicitation requirements, submission rules, security obligations, evaluation criteria, data access, integration, schedule, and performance expectations for proposed autonomous medical-coding and appeals/denials-management capabilities.
The Government extended the white-paper deadline by one week to **August 28, 2026**, and confirmed that white papers will be evaluated against the RFS problem statement. The bracketed draft Statement of Objectives (SOO) targets—such as at least **60% autonomous coding** of approved test volume, an **80% correlation match**, and milestone periods of **90, 90, and 120 days**—should be used for planning but may be finalized during Phase 2 discussions or negotiations.
The main white paper body is limited to **10 pages**. Diagrams and figures count toward that limit, while the cover page, Bill of Materials, and specified addenda do not. The nontraditional defense contractor statement normally counts within the 10-page limit but may be placed on the cover page.
Security and authorization are central requirements. Vendors must address their current authorization status and path to meeting all security requirements, including the minimum **DoD Impact Level 4 or higher authorization**, before production-environment integration at Milestone 3/ATO-C.
A FedRAMP Moderate authorization, deployment in an already authorized IL 4+/IL 5 environment, or another agency’s authorization is not confirmed as automatically sufficient or reciprocal. Each proposed team member must provide SPRS assessment and CMMC Level 2 self-attestation status at submission, including teaming partners and subcontractors.
The Government will facilitate deidentified data and a sandbox/pre-production environment with Leidos and Oracle. Vendors must ensure personnel have the required clearances. If the planned sandbox is unavailable within the schedule, vendors may be required to host and test the solution as an alternative.
Leidos will support integration with MHS GENESIS, with specific integration details to be addressed in Phase 2. The Phase 3 live demonstration will use a vendor-provided sample data set, while Government-approved test data will be supplied for pre-production.
The Government has deferred several requested details concerning data volume, system sources, claims portfolio characteristics, baseline metrics, appeal channels, automation authority, and invoicing tiers.
Several material issues remain pending, including treatment and marking of trained models, tuned parameters, and other model artifacts under the SOO’s Distribution Statement C and non-proprietary-deliverable requirements; information sharing and protection of proprietary assets when separate vendors support Autonomous Coding and Appeals & Denials Management; joint integration funding; the scope and scoring of correlation-match and recoverable-claim metrics; and the approximately **143,000 encounters-per-day** volume.
Vendors must plan for collaboration across both capabilities, including shared learning insights, unified dashboards, secure exchanges, and joint integration and testing. The Government has not definitively resolved whether the August 2026 award assumption, approximately June 2027 ATO-C milestone, 13–16-month period of performance, and **June 30, 2027** production-validation target will be rebaselined or which schedule provision governs.
Offerors should therefore clearly state their proposed schedule and authorization strategy.
The Government extended the white-paper deadline by one week to **August 28, 2026**, and confirmed that white papers will be evaluated against the RFS problem statement. The bracketed draft Statement of Objectives (SOO) targets—such as at least **60% autonomous coding** of approved test volume, an **80% correlation match**, and milestone periods of **90, 90, and 120 days**—should be used for planning but may be finalized during Phase 2 discussions or negotiations.
The main white paper body is limited to **10 pages**. Diagrams and figures count toward that limit, while the cover page, Bill of Materials, and specified addenda do not. The nontraditional defense contractor statement normally counts within the 10-page limit but may be placed on the cover page.
Security and authorization are central requirements. Vendors must address their current authorization status and path to meeting all security requirements, including the minimum **DoD Impact Level 4 or higher authorization**, before production-environment integration at Milestone 3/ATO-C.
A FedRAMP Moderate authorization, deployment in an already authorized IL 4+/IL 5 environment, or another agency’s authorization is not confirmed as automatically sufficient or reciprocal. Each proposed team member must provide SPRS assessment and CMMC Level 2 self-attestation status at submission, including teaming partners and subcontractors.
The Government will facilitate deidentified data and a sandbox/pre-production environment with Leidos and Oracle. Vendors must ensure personnel have the required clearances. If the planned sandbox is unavailable within the schedule, vendors may be required to host and test the solution as an alternative.
Leidos will support integration with MHS GENESIS, with specific integration details to be addressed in Phase 2. The Phase 3 live demonstration will use a vendor-provided sample data set, while Government-approved test data will be supplied for pre-production.
The Government has deferred several requested details concerning data volume, system sources, claims portfolio characteristics, baseline metrics, appeal channels, automation authority, and invoicing tiers.
Several material issues remain pending, including treatment and marking of trained models, tuned parameters, and other model artifacts under the SOO’s Distribution Statement C and non-proprietary-deliverable requirements; information sharing and protection of proprietary assets when separate vendors support Autonomous Coding and Appeals & Denials Management; joint integration funding; the scope and scoring of correlation-match and recoverable-claim metrics; and the approximately **143,000 encounters-per-day** volume.
Vendors must plan for collaboration across both capabilities, including shared learning insights, unified dashboards, secure exchanges, and joint integration and testing. The Government has not definitively resolved whether the August 2026 award assumption, approximately June 2027 ATO-C milestone, 13–16-month period of performance, and **June 30, 2027** production-validation target will be rebaselined or which schedule provision governs.
Offerors should therefore clearly state their proposed schedule and authorization strategy.
Show All