Class TbsOVR_271
Unit
BSHL7DT271
Declaration
type TbsOVR_271 = class(TbsHL7Segment)
Description
Override Segment This segment allows a sender to override specific receiving application's business rules to allow for processing of a message that would normally be rejected or ignored. In many instances, business rules will be set as guidelines relative to patient care. In some instances it is in the patient's better interest to circumvent these guidelines. In other cases, business rules may exist to support normal process flow, but which may be bypassed or ignored under certain special circumstances. This segment is linked to the proposed ERR segment changes in that the first attempt to process a transaction that violates a business rule may result in an error that must be overridden. The ERR provides a mechanism to identify errors that may be overridden, as well as the allowed override codes. Use case #1: A patient has received a prescription with a duration of 30 days and receives the full amount at their pharmacy. While at home the patient accidentally spills the container and spoils a significant proportion of the prescription. The patient returns to their pharmacy and explains the situation to the pharmacy technician. The technician consults with their supervising pharmacist. Knowing the patient, thepharmacist decides to override the business rule stating that the dispensed amount for a prescription may not exceed the prescribed amount. In recording the decision, the pharmacy technician specifies that the Override Type is a "Compassionate Refill" and that the Override Code, or reason for the override, is "Spoilage". The technician also provides Override Comments to provide an explanation of the situation for future reference. While recording the decision, the technician's user ID is automatically stored in an Override Recorded By field. The pharmacist's ID is stored in the Override Responsible Provider field. Use case #2:A hospital wishes to submit an invoice to an insurer who is providing secondary coverage. The invoice is being submitted over a week after the service was performed, which is outside the insurer's normal accept time window. The insurer would normally reject the invoice. However, the submitter includes an Override Type of "late submission" as well as an Override Code indicating that the invoice is late due to delays with the primary payor. The secondary insurer examines the override reason and accepts the invoice. Usage Note: The override segment should be included in messages adjacent to the segment(s) containing the information that would trigger the business rule(s) that needs to be overridden. The segment should be optional (you shouldn't always need to override business rules), and should be allowed to repeat in circumstances where there may be more than one business rule overridden at the same time. Committees may wish to provide suggested values for override types or codes for use with the OVR segment in different messages.
Hierarchy
Overview
Properties
Description
Properties
|
property BusinessRuleOverrideType : TbsCWE_271 read GetBusinessRuleOverrideType write SetBusinessRuleOverrideType; |
Business Rule Override Type, Min : 0, Max : 1
|
|
property BusinessRuleOverrideCode : TbsCWE_271 read GetBusinessRuleOverrideCode write SetBusinessRuleOverrideCode; |
Business Rule Override Code, Min : 0, Max : 1
|
|
property OverrideComments : TbsTX_271 read GetOverrideComments write SetOverrideComments; |
Override Comments, Min : 0, Max : 1
|
|
property OverrideEnteredBy : TbsXCN_271 read GetOverrideEnteredBy write SetOverrideEnteredBy; |
Override Entered By, Min : 0, Max : 1
|
|
property OverrideAuthorizedBy : TbsXCN_271 read GetOverrideAuthorizedBy write SetOverrideAuthorizedBy; |
Override Authorized By, Min : 0, Max : 1
|
Generated by PasDoc 0.14.0.
|