Modeled forms - ProviderConnect NX
System administrators can publish forms that have modeled content supported in ProviderConnect NX.
Entity databases
When modeling a form, entity databases help control the security access configured in System Code Definition and ProviderConnect NX Defaults. For example, when modeling a client-based episodic form, ProviderConnect NX will first filter the available client search results for clients that have a relationship (current or previous admission) with the logged in system code and associated program(s). After selecting a client, ProviderConnect NX will only display episodes the logged in user should see based upon their associated system code and programs.
In Envelope Definition, select one of the following entity databases supported by ProviderConnect NX:
| Forms | Entity database |
|---|---|
| CWS |
|
| PM |
|
| MSO |
|
Draft / Final
Draft/Final functionality is supported for forms accessed in ProviderConnect NX.
In Table Definition select Draft/Final for the Type of Column. Do not select Draft/Final (Document Routing). Document Routing is not supported in ProviderConnect NX. If you add Draft/Final (Document Routing) to a form it will not function in ProviderConnect NX.
Signatures
In Table Definition you can add signature functionality to forms supported by ProviderConnect NX. Signatures can be captured with Topaz Signature pads or with a stylus, mouse, or other touchscreen feature.
Form access
After you configure a form, the only step needed to publish the form in ProviderConnect NX is to update form access for applicable user role(s). myAvatar recognizes any PM, CWS, or MSO modeled form that is configured with an entity database supported by ProviderConnect NX, and adds the form to the list of available forms.