SSMT: Encounter Type

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to: navigation, search

Description

The Encounter Type SSMT content category can be used to assist in managing the Encounter Type dictionary in Allscripts Enterprise EHR. This dictionary can typically be managed manually given its nature and relatively small record count.

Stored Procedures used:

  • Extracting data: ImpSSMTExtract 'Encounter Type'
  • Loading data: ImpSetEncounterTypeDE

Column Listing and Descriptions

  • Entry Code - this is the unique entry code value for the encounter type.
  • Full Name - this is the entry name value for the encounter type. This value is visible when selecting or viewing the encounter selector screen in EHR.
  • Entry Mnemonic - this is the unique entry mnemonic value for the encounter type. This value will typically mirror the entry code value for the given encounter type.
  • IsEnforcedFLAG? - acceptable values for this field are:
    • Y - indicates the entry is system delivered, is enforced, and cannot be edited.
    • N - indicates the entry is not enforced, MAY or MAY NOT be system delivered, and that the general properties of the encounter type may be edited or updated.
  • IsChargeableLFLAG? - acceptable values for this field are:
    • Y - indicates the encounter type is available to submit charges or generate encounter forms with in EHR.
    • N - indicates the encounter type will not be available to generate encounter forms or submit charges against in EHR.
  • LinkedAppointmentFLAG - acceptable values for this field are:
    • Y - indicates the encounter type is available to link or file appointments against in EHR. This is most commonly seen and used by encounter types that will be called by the registration and scheduling interface.
    • N - indicates the encounter type is not available to link or file appointments against in EHR.
  • IsInactiveFLAG - acceptable values for this field are:
    • Y - indicates the encounter type is currently inactive. Use when attempting to inactive encounter type entries.
    • N - indicates the encounter type is currently active. Use when attempting to update or create new encounter type entries.
  • Create? - acceptable values for this field are:
    • Y - indicates the encounter type will attempted to be added as a net new entry. Use when attempting to create new encounter types.
    • N - indicates the encounter type will attempted to be updated. Use when updating the properties of already existing encounter types.

Migration Considerations

  • Interfaces - in most cases the encounter type dictionary is called by interfaces that are extracting from and filing into EHR. It is a good practice to evaluate what changes, updates, or additions might need to take place to this dictionary prior to moving existing or installing new interfaces in different EHR environments.
  • Auditing/Reporting - encounter types can also be useful values upon which to report against and also can represent certain types of clinical and non-clinical encounters in EHR. Before making edits to already existing encounter types it may be useful to evaluate the importance and relevance of these encounter types.