Difference between revisions of "SSMT: Encounter Type"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
(Created page with "==Description== Stored Procedures used: *Extracting data: ImpSSMTExtract 'Encounter Type' *Loading data: ImpSetEncounterTypeDE ==Column Listing and Descriptions== *'''Entry C...")
 
m
Line 1: Line 1:
 
==Description==
 
==Description==
 
+
The Encounter Type SSMT content category can be used to assist in managing the [[Encounter Type|Encounter Type dictionary]] in EHR.  This dictionary can typically be managed manually given its nature and relatively small record count.
  
 
Stored Procedures used:
 
Stored Procedures used:
Line 25: Line 25:
  
 
*'''LinkedAppointmentFLAG''' - acceptable values for this field are:
 
*'''LinkedAppointmentFLAG''' - acceptable values for this field are:
 +
 +
    * Y - indicates the encounter type is
 +
    * 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.
  
 
*'''IsInactiveFLAG''' -  
 
*'''IsInactiveFLAG''' -  
  
*'''Create?''' -  
+
    * 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 ==
 
== Migration Considerations ==

Revision as of 14:01, 1 April 2011

Description

The Encounter Type SSMT content category can be used to assist in managing the Encounter Type dictionary in 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 that a new entry is being created; use to add new entries.
   * Blank - indicates an already existing entry; use to update already existing entries.
  • LinkedAppointmentFLAG - acceptable values for this field are:
   * Y - indicates the encounter type is 
   * 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.
  • IsInactiveFLAG -
   * 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

back to SSMT main page