chargeToPracticeCode"This field is the charge to the ordering entity for the studies performed when applicable. The first component is a dollar amount when known by the filler. The second is a charge code when known by the filler (results only)" - HL7 Version 2.8, OBR-23. This property contains the charge code, if available.
chargeToPracticeCost"This field is the charge to the ordering entity for the studies performed when applicable. The first component is a dollar amount when known by the filler. The second is a charge code when known by the filler (results only)." - HL7 Version 2.8, OBR-23. This property contains the dollar amount, if available.
dateAcceptedThe date/time on which the ordered service was accepted by the filler. In other words, the creation date of the Promise record.
discontinueDate"This is the date the order was discontinued." - HL7 CIMI, Promise.orderDiscontinueDate
expectedAvailabilityDate"Specifies the date/time the filler expects the services to be available. For example when a prescription is ready for pickup or when a supply will be sent or picked up, or for when a laboratory result is expected to be available." - HL7 Version 2.8, ORC-27
fillerOrderIdA unique identifier of the order from the filling organization's point of view. Note that different terms have been historically been used for the filler order id in different domains. For example, in Pharmacy, the "filler order id" is typically called a "prescription number". Similarly in Lab, it is typically called an "accession number"."This field is the order number associated with the filling application...." - HL7 Version 2.8, ORC-3 and OBR-3."This field is equivalent in uniqueness to the pharmacy/treatment supplier filler order number. At some sites, this may be the pharmacy/treatment supplier (internal) sequential form. At other sites, this may be an external number." - HL7 Version 2.8, RXD-7.
fillerSupplementalInfo"Contains supplemental service information sent from the filler system to the placer system for the procedure code reported in OBR-4 Universal Service ID. This field will be used to report ordering information detail that is not available in other specific fields in the OBR segment. Typically it will reflect the same information as was sent to the filler system in OBR-46-Placer supplemental service information unless the order was modified, in which case the filler system will report what was actually performed using this field...." - HL7 Version 2.8, OBR-47.
orderPoints to the Healthcare Order in response to which the Healthcare Promise was created. Note that since both the HealthcareOrder and HealthcarePromise are abstract classes, this association is available to all subclasses, such that LabPromise would point to LabOrder, etc."The order that is partly or wholly enacted by the performance of this act." - HL7 CIMI, Promise.fulfillsOrder
orderModalityThe method by which the ordering clinician (or the ordering system on behalf of the ordering clinician) communicated the order to the fulfilling person or organization (or the fulfilling system on behalf of the fulfilling person or organization). Examples include: Duplicate (i.e., an error), Electronically Entered, Policy, Service Correction, Telephoned, Verbal, Written, etc."The method the provider used to communicate to the user to take action on the order. Examples include: written, telephoned, verbal, electronically entered, etc." - HL7 CIMI, Promise.orderModality"Code indicating the origin of the prescription." - NCPDP Telecommunication (Field 419-DJ, Data Dictionary 201104). Possible values include: Written; Telephone; Electronic; Facsimile; Pharmacy; Not Known.
precautionProtocolInvokedPointer to a list of zero-to-many procedures that is invoked as a precaution to prevent harm to the patient, guests, or healthcare workers in response to a known situation where a potential danger may exist.
priority"Describes the urgency of the request. If this field is blank, the default is [Routine]" - HL7 Version 2.8, TQ1-9. Possible values include (from HL7 Table 122): Stat; ASAP; Routine; Preop; Callback; Timing critical*; As needed. *Note that the Timing Critical has a syntax that allows more information, e.g., Timing Critical within 15 minutes.
promisingOrganizationIdentifies the Organization to which the Healthcare Order was sent for performance. Used to identify the performing organization, especially when the ordering organization is different than the performing organization. For example if the VA orders a lab test from Quest Diagnostics, this field would contain Quest Diagnostics.
promisingProvider"Information about who made the promise, when did they make it, how was it conveyed, etc..." - HL7 CIMI, Promise.promised
scheduledDateTime"The date/time the filler scheduled an observation, when applicable (e.g., action code in OBR-11-specimen action code = "S"). This is a result of a request to schedule a particular test and provides a way to inform the placer of the date/time a study is scheduled (result only)." - HL7 Version 2.8, OBR.36
status"Contains the status of results for this order." - HL7 Version 2.8, OBR-25
statusChangeDateTime"Specifies the date/time when the results were reported or status changed. This conditional field is required whenever [Report Status] is valued. This field is used to indicate the date and time that the results are composed into a report and released, or that [Healthcare Order status] is entered or changed." - HL7 Version 2.8, OBR-22.
statusModifier"This field is a modifier or refiner of the ORC-5-Order status field. This field may be used to provide additional levels of specificity or additional information for the defined order status codes." - HL7 Version 2.8, ORC-25
FHIM::Common::ActionStatement