Difference between revisions of "11.2 Requisition Grouping Logic"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
*To Be Done Date | *To Be Done Date | ||
*Ordering Provider | *Ordering Provider | ||
| − | *[ | + | *[[Requested_Performing_Location]] |
*Order not duplicated or already on the associated requisition | *Order not duplicated or already on the associated requisition | ||
*Authorizing Provider | *Authorizing Provider | ||
Revision as of 19:57, 16 July 2014
As of v11.2 the criteria that causes the requisition to split is noted below.
- Ordering Encounter
- To Be Done Date
- Ordering Provider
- Requested_Performing_Location
- Order not duplicated or already on the associated requisition
- Authorizing Provider
- Order Priority
- Ordering Site
- OID’s Never Combine on 1 Req Flag = False (Unchecked), if True (Checked) item gets its own req
- Specimen/Data Collection Date/Time (if collection done via UI dialog)
- Specimen Type Temperature Requirements = Frozen (if order has specimen type specified)
- Schedule Order Parent
- Specimen/Data To Be Collected In Office Flag