Default SmartText for Notes
It is possible to specify a default SmartText that will be automatically loaded when a new instance of a specific note type.
Setting a Default Note Type
The following instructions are provided for builders to facilitate understanding capabilities and testing in the SBX environment so that appropriate requests can be directed to analysts. Builders should not attempt changes to note configurations in POC or any Connect Care environment other than SBX.
These steps are performed in the SmartText editor (step 1) and Clinical Administration (step 2)
Default SmartText (SmartText editor)
Create a new SmartText template, following all Connect Care style, numbering and other documentation design guides.
Ensure that the SmartText has functional types "IP Charting" and "MR Charting", possibly also adding "IP Notewriter" and "MR Notewriter" specified on the "Restrictions" tab.
Ensure that the SmartText is released and accepted.
Note Type Association (Clinical Administration)
Select #1, Management Options (System Definitions, Profiles, Utilities, etc.)
Select #5, Profiles (LPR)
Open a profile record corresponding to the level (department) at which the default SmartText behavior should apply for the note type in question.
For default SmartText associations that should apply broadly (and no lower level note profiles already exist), select Profile #1 (System Definitions)
Select #17, Note, Letter, Transcription
Go to the "Default Note Templates" screen (~13th screen).
Scroll to the note type of interest (noting the intended note type ID). If the intended note type is not already configured for default SmartText, scroll to the bottom of the list to add a new note type default specification, entering the note type identifier, tab to the Default Note Template field, then entering the default SmartText identifier.
Dynamic Default SmartText
It may be desirable to have a generic (or blank) SmartText that all users see on first creating a particular note type (e.g., Hospital Course [32]) while retaining the ability to substitute a more specific SmartText for users who document under a specific specialty (or other rule-discoverable clinical context properties such as the current department or the patient age group).
Although it would be possible to specify a different note configuration for each of many user profiles, it is more efficient to keep the Note properties specified at the system level. The assigned default SmartText can take advantage of SmartText override rules to swap-in a different SmartText when specific user, patient or facility conditions are met. This has the advantage of being easily and flexibly extendible while still being triggered only by a new-note event.