Publishing and Updating an OASIS form within Form Builder

In this article, you will learn how to:

• Publish an OASIS form within Form Builder, 
• Configure Control Items at Agency-Level,
• Updating OASIS versions within Form Builder, and read up on 
• Additional OASIS Data Specification Information

Publishing an OASIS form

OASIS forms can be published within Form Builder, which is accessible by navigating to Settings > Form Settings > + Add Form. 

Click on the "Add form" button and the below dialog will appear. Users are to then select the form type “OASIS”, then select the applicable "RFA". Please note that ACC supports OASIS-D1 and onwards.

Be sure to add the appropriate form configuration settings as well as filling in the name and instructions. Once complete, click on “save” and you may now customize the OASIS form. Once it is published, users will be able to see this agency-specific OASIS form on the platform.

Configure Control Items at Agency-Level

There are different control items available for configuration at the agency level. You may configure the dropdown options with the applicable values for your agency.

⚠️Please note that the following items are editable fields (that cannot be deleted) starting in the OASIS-E template.⚠️

⚠️ The value must always precede the text and is separated by a period. ⚠️

• (STATE_CD) Agency’s postal code

The OASIS-E template contains all possible state options for this question. Remove the state options not used by your agency, and a minimum of 1 state option must remain. If there are state options that need to be added again in the future, create a new version of the form, and add the new options following the correct formatting. e.g. [ AL.Alabama]. This is a required item.

• (HHA_AGENCY_ID) Assigned agency submission ID

This is the provider's submission ID. The value submitted for HHA_AGENCY_ID must match the HHA_AGENCY_ID in the National Database System for the provider. This is a required item with a maximum of 16 characters. If your agency has multiple submission IDs, create an ID dropdown option per applicable branch/service office etc using the required format, e.g. “1234567890123456.New York”.

• (NATL_PRVDR_ID) Agency NPI

This is the National Provider ID for your agency (Lookup your organization NPI here: NPPES NPI Registry. There can be a maximum of 10 characters. If your agency has multiple submission IDs, then create an ID dropdown option per applicable branch/service office etc using the required format, e.g.  “1234567890.New York”. This is a required item.

• (M0010_CCN) Facility CMS Certification Number

The value submitted in M0010_CCN must either be blank, or must be exactly 6 characters in length. When a record is submitted, IQIES will determine if the provider has been certified. If the provider is not certified, then the submitted record is considered (processed as) a test record. If the provider is certified, then the submitted record is considered (processed as) a production record. If the record is a production record, then a system edit will reject the record if M0010_CCN is blank.

• M0014_BRANCH_STATE

The OASIS-E template contains all possible state options for this question. Remove the state options not used by your agency, and a minimum of 1 state option must remain. If there are state options that need to be added again in the future, create a new version of the form, and add the new options following the correct formatting, e.g. [ AL.Alabama]. If M0016_BRANCH_ID is set as [N.Assessment was performed by an HHA which has no branches, or by a subunit which has no branches], OR [P.Assessment was performed by the home office of an HHA which has branches or by the home office of a subunit which has branches], then the M0014_BRANCH_STATE dropdown can be left as “Not Set”.

• (M0016_BRANCH_ID) Branch ID

If there is a Branch ID, it can accept a maximum of 10 characters. If your agency does not have branches, or the OASIS form will only be performed by the home office, at least one of the [N] and [P] options must remain. This is a required item. 

Updating OASIS Versions

You may also update OASIS versions directly within the Form Builder. To start, you can create new forms in the form builder using the latest OASIS templates based on the reason for assessment (RFA). Select the appropriate version in the configuration dialog, as shown below.

You may then customize the form by responding to the relevant OASIS-E standard questions. Refer to the section above on how to publish an OASIS form and the related configurations.

You can also copy configurations from existing, customized OASIS forms. Simply click on “Existing Fields” and search for your desired customized OASIS form to copy across versions, as shown below.

You are then to identify the field, sub-section, and/or section that you wish to copy over to your new OASIS template. Drag and drop the the fields from the old to new form, section by section. Please note that only the custom (non-OASIS) questions can be copied, and fields cannot be copied. This is done to prevent duplicate or invalid fields creating errors during the upload to CMS.

To start submitting the form, click on "Publish". Repeat these steps for each RFA.

Watch the below video to learn about how you can further customize your forms if you are using OASIS, and refer to this article for more information.

Additional OASIS Data Specification Information

Refer to the below for more information on OASIS data fields.

Learn More

Please note that OASIS questions corresponding with the selected RFA and version will be pre-populated into the form builder. They will be displayed as read-only fields with a fixed ranking, meaning that the order of “M00” fields cannot be changed.

OASIS questions are created based on the CMS’ OASIS specifications. To prevent user error, they will not be editable within the builder. Please note that permissions required for this task will be the same as a regular form building task. You can access this by navigating to Workflow> Create and edit custom forms.

For more information, refer to the How do I create/configure/build/publish a new form article on Zendesk.