Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Pcs Form topic
No spam. Unsubscribe anytime.
EMS TAC seeks electronic PCS form that Epic and Cerner can generate
Summary
The EMS Technical Advisory Committee asked DMS and MCOs to review sample electronic PCS (Patient Care Statement) outputs from Epic/Cerner so EMS claims can be generated from EHRs and avoid denials tied to format differences. DMS said it will raise the item with its transportation group.
The EMS Technical Advisory Committee on the Department for Medicaid Services call pressed for a standardized electronic PCS (Patient Care Statement) that Epic and Cerner can generate so EMS providers do not lose reimbursement when forms arrive in a nonstandard format. Chair said the recurring question "has been regarding the PCS form, and the question that has, come up is specifically around Epic, but also, I believe the the, question also invert involves Cerner" and asked whether DMS or MCOs could help coordinate a solution.
Troy Walker, a committee member, said the intent is to keep all of the data elements on the approved PCS form while allowing minor formatting differences for an electronic version: "I don't wanna change any documentation. I don't wanna change any information. Everything that's on the current form that they've approved would be there." A provider representative noted existing vendor platforms can integrate with Epic but cautioned that automated checks can verify a signature without determining whether clinical criteria were met — and that small missing items cause denials.
Barbara from the Department for Medicaid Services said she would take the request to DMS' transportation group and clarified DMS' role: "DMS doesn't require this form. So when you bill a fee for service member, you're not required to submit this form or any form like it. This is only for the MCOs, and so that that is strictly a contractual issue between you and MCO." MCO representatives (including UnitedHealthcare and Humana participants) said they would review draft samples and recommended a joint call to confirm required data points and signature handling.
The committee agreed to gather sample PDF outputs and local Epic builds, circulate them to TAC members, and then send consolidated examples to DMS for distribution to MCOs. Chair said the committee may call a special meeting if substantive issues arise before the next TAC meeting on Oct. 26.
Provenance: topicintro SEG 041, topfinish SEG 412.
