We have enhanced the CMS-485 generation workflow to allow data population directly from OASIS assessment forms of version E2, ensuring better alignment with state-mandated documentation requirements.
Previously:
CMS-485 forms could be generated from other standard V3 assessments; however, data mapping from the OASIS E1-version of different OASIS assessments to CMS-485 was introduced only in the most recent release.
With this enhancement:
Agencies can now also generate CMS-485 forms using data captured from the following below mentioned OASIS assessments:
· OASIS-E2 Start of Care (SOC)
· OASIS – E2 Resumption of Care (ROC)
· OASIS – E2 Follow-Up (FU)
This improvement streamlines documentation, reduces duplicate data entry, and supports greater compliance across assessment workflows.
The following forms are now created using a custom PDF solution, which enables mapped data from completed assessments to be used for generating the CMS-485 form.
· OASIS-E2 Start of Care (SOC)
· OASIS – E2 Resumption of Care (ROC)
· OASIS – E2 - Follow Up (FU)
· Once these forms are marked active from the backend (Office Settings); it becomes available under the client’s profile → Assessment tab.
· The user can Access these forms under the Client’s Profile → Assessment tab.
· Complete the form and generate the CMS-485 with mapped data.
Once completed, the OASIS form allows users to generate a CMS-485 with all mapped fields populated as per the agency’s specifications.
---------------------------------------------------------------------------------------Common fields present in the CMS 485 & OASIS -E2 Assessment forms are automatically populated from the assessment form, based on the pre-entered data provided by the user while completing the assessment.
Additionally, as per the existing workflow, certain fields in the CMS-485 form are populated from other sections of the system. The details are listed below and will continue to function as currently implemented.
· Fields in CMS 485 Populated from Client’s Profile:
o Patient’s Name
o Patient’s Address
o Date of Birth
o Sex
o Patient’s HI Claim Number → Fetched from the Client Main Profile (Medicaid ID / Patient ID).
o Goals / Rehabilitation Potential / Discharge Plans → Fetched from Client → Care Assessment → Goals.
o Physician’s Name and Address → Fetched from Client Contacts when the relationship type is set to “Family Physician.”
o ICD 10 Codes (Principal Diagnosis/Surgical Procedure/Other Pertinent Diagnoses) → Fetched from Billing tab → Claim Codes section (If added).
· Fields Populated from Agency Details
o Provider’s Name
o Provider’s Address
o Provider’s Telephone Number
o Provider Number (Provider ID -Populated from Billing Tab)
Please note: Based on the current implementation using Custom Forms utility, if data is entered manually in the OASIS assessment form, OASIS will be considered the updated information and will serve as the primary source of truth, with its data flowing to the CMS‑485.
The screenshot below provides an example of how assessment data is mapped into CMS‑485 and displayed into their respective fields:
This update ensures:
· Accurate field mapping between OASIS E2 and CMS-485.
· Seamless integration of custom PDF forms into the existing assessment workflow
· Consistent output generation matching uploaded PDF templates
· Improved compliance with CMS submission standards
Please note: This feature is built on top of the existing custom PDF solution.
Limitations: The CMS Standard dataset uses PDFs with block-based custom forms for data entry. Due to this design & implementation using CS360-custom forms utility, users must navigate between fields using the TAB key. Additionally, each block accepts only one alphanumeric character, and users should ensure that only a single character is entered per block, as this validation is not currently available within the custom forms utility.