When do I need to use the Inventory Data Model?
The Inventory Data Model is used to track surgical supplies (scalpels, bandages, etc) between systems. The Inventory.Update transaction is an administrative message that is used to synchronize the lists between systems. Generally this data comes from the Enterprise Resource Planner into the EHR, including the types of items stocked and the specific locations in the hospital they might be found. The Inventory.Deplete event is a workflow-oriented message that sends information from the EHR to the ERP when a supply is used in a surgical procedure.
When and where can the Inventory Data Model be found?
You’ll find the Inventory Data Model most commonly when connecting to inpatient EHRs with robust interfacing capabilities and surgical specialty modules. Supplies are also often used in areas that function similarly to surgery, such as invasive cardiology or angiography. Typically ERPs will make Inventory.Update data available via an HL7v2 MFN format or a vendor-specific API. Inventory.Deplete is most commonly made available via an HL7v2 OMS or DFT format or a vendor-specific API.
How is the Inventory Data Model different from the Financial Data Model?
Financial is administrative information about what’s happened to a patient in regards to financial impact. Inventory.Deplete is also administrative information about what’s happened to a patient, mainly for the purposes of tracking when certain items might need to be re-ordered or restocked.
Can I receive preference card information via the Inventory Data Model?
Once the full list of supplies is created in the EHR via Inventory.Update, surgeons can create their preference cards, a list of supplies they commonly use and document in surgery. Preference cards are master data themselves, in that they are lists of surgical supply preferences, but they are not exchanged via a known standard.
When a surgeon uses a supply in surgery, they choose the supply from the preference card list and mark it as used or wasted. This sends the usage to the outside systems via Inventory.Deplete. Depending on use case, this usage information, as well as other relevant Data Models like SurgicalScheduling, are typically sufficient in supporting the needs of Redox applications that focus on surgical areas.