For questions about this archive, please contact webmaster@hl7.org.
Freida Hall (Jan 17 2020 at 21:55):(I’m reposting this question, previously posted to the General stream, trying to reach a wider audience)
In the US Realm you’ve probably seen advocacy for price transparency so a patient will know the price of a medical service in advance of committing to the treatment. Is there a preferred way to do this for existing V2 interfaces? I looked in the standards master grid but did not see any V2 implementation guides for this topic but found existing message segments that may suffice.
For example, a provider’s EHR system could send a general order message (ORM) to a laboratory requesting the price for a laboratory test for a specific patient, e.g. what would be charged. The ORM (general order message [event O01]) message structures contain repeating, optional FT1 (Financial Transaction) segments and at first look it seems these fields might be appropriate to return the test price from the laboratory to the provider’s EHR system (below extracted from the V2.5.1 standard):
FT1-4 (DR) Transaction Date (required)
FT1-6 (IS) Transaction Type (required), Table 0017 value CG-Charge
FT1-7 (CE) Transaction Code (required)
FT1-10 (NM) Transaction Quantity
FT1-11 (CP) Transaction Amount - Extended
FT1-12 (CP) Transaction Amount – Unit
When I posted this to the general stream Frank Oemig suggested using Chpt. 5 queries, but we’d prefer to leverage existing V2 functionality with Chapter 4 messages.
Daniel Rutz (Feb 20 2020 at 19:14):Maybe using the FT1 like that? It seems like we might still need something that's a "lite" query, like a new set of control codes in ORC-1, in order to indicate this wasn't actually an order to be performed and just a query for pricing.
Freida Hall (Feb 27 2020 at 19:42):Thanks Dan. My thought was for ORC-1 we could use "RE-Observations/Performed Service to follow" from Table 0119 Order Control Codes to return price info re: the tests ordered.
We'd still rather send an ORM from the filler (vs. a query), which (my opinion) V2 permits as an update, change to the order, in the ORM definition (from V2.5.1):
"The function of this message is to initiate the transmission of information about an order. This includes placing new orders, cancellation of existing orders, discontinuation, holding, etc. ORM messages can originate also with a placer, filler, or an interested third party.
The trigger event for this message is any change to an order. Such changes include submission of new orders, cancellations, updates, patient and non-patient specific orders, etc."
The change/update is returning the price (test code and charge amount) info using the FT1 segment.
Last updated: Mar 23 2020 at 00:02 UTC