Modeled vs SSSM
Difference between Modeled and SSSM
Modeled Forms are unique to your system. You can model functionality into your form such as the selection leaf to link the treatment plan, Draft/Final to enable workflow, or a state form data element to identify inclusion in state reporting, but you have to manually build in the functionality. Your data will be stored in its own table and your report writers will need to join the tables with product tables for reporting if product tabled data needs to be included. However, there are some system processes that are typical enough across the industry that we create those forms for you. For these forms, you would need to use SSSM such as the case with progress notes.
Site Specific Section Modeling leverages the built in functionality within the product form while allowing the flexibility for you to add custom data collection fields to these forms. The data is stored in the product table(s) for ease in reporting. However, the event logic is not as robust as with full-fledged modeling.
Difference between Core Progress Note forms and Copied (PNGI) forms
In myAvatar – you have copies of each of the Product Progress Notes available for SSSM use.
- Ambulatory Progress Note
- Ambulatory Progress Note (Diagnosis Entry)
- Inpatient Progress Note
- Inpatient Progress Note (Diagnosis Entry)
- Edit Individual Client Group Progress Notes
- Independent Group Progress Notes
- Group Default Notes Entry
Until you use Site Specific Section Modeling, these additional copies of the forms do not appear on the Menu. You assign the form to the menu when you complete the SSSM. In essence you enable the copy and place it on the menu, but you do not create a new copy - it already existed in the background – nor can you create additional copies.
In contrast, you have 1 instance of the Progress Note (Group and Individual). You control how many copies are created. When you create the copy, it is placed on the menu and made available for SSSM.
Although SSSM is available for the 1 core instance – it is not recommended that you use SSSM on the core form. Best Practice is to create a copy of PGNI and only complete SSSM on your copies.
Difference between SS Note Single Select and SS Note Copy Single Select
SS Note Single Select and SS Note Multiple Select are shared across all copies of the Progress Note (Group and Individual) PGNI. So if you wanted to be able to document “Interpreter Offered” (Yes/No) on 3 out of 4 copies of your PNGI you could use the SS Note Single Select 1 and in each copy you would be collecting responses specific to “Interpreter Offered”. You can use a single data object on multiple forms to collect the same data thereby best utilizing a SSSM object.
If however, you have an item that you track on one of your PGNI copies and you don’t anticipate collecting it on other PGNI copies, you could use SS Note Copy Single Select 1. This value is specific to the copy you are working with. So, for instance you could collect “HUD Application Completed” (Yes/No) on a Housing Note. Later on, you could then create a new copy of PNGI specific to your Jail Transition program and use the SS Note Copy Single Select 1 to collect “Court Reportable” (Yes/No). You use a unique data object on an individual form to collect unique data. By doing so you free up the standard SS Note objects for use across multiple notes and you are less likely to run out of SSSM fields.