Info
ADT Population of Origin Unit
If TeleTracking receives an A05 that does not have anything in the EVN.5, or a Bed Request order that does not have anything in the ORC.10, the bed request will be created with a blank NULL Origin Unit.
Capacity IQ® PreAdmit doesn't like it if the Origin Unit is blank. It does everything it can to populate this field. This is important because it is often what the advanced filters are based on.
Anytime a placement (bed request, preadmit) is created, updated or activated, it attempts to fill out this field by performing the following actions:
Does the patient have a specialty location?
If So, the origin unit is the unit the specialty location is in.
Does the patient have a home location?
If So, the origin unit is the unit the home location is in.
Does the user modifying the record have a fixed or variable membership?
If Fixed, Check to see what the base location of the user creating, modifying, or activating the request is. The origin unit will be the same unit that the user's base location is in.
Does the patient have a current location?
If So, the origin unit is the unit the current location is in.
Does the user modifying the record have a fixed or variable membership?
If Variable, and logged into a cluster, the Origin unit will remain blank. If they are logged into a specific unit (not a cluster), then the origin unit will be the unit of the users membership at the time they were logged in.
If you find that the origin unit is being updated via an interface transaction and both of the following is true, then there may be special processing in place to update either field.
The EVN.5 is blank
The ORC.10 is blank (or not present)