Stream: implementers
Topic: ResourceItem has been dropped in R4
vania manzelli (Jan 31 2019 at 15:04):
Hi, based on HL7GForge items [#16947], I realised that ResourceItem has been dropped from FHIR data model in 2018-May. I already started a new topic in http://community.fhir.org about the opportunity to reintroduce the specific resource.
We started last year developing a clinical collaboration platform based on FHIR and we cover several IHE transactions including pharmacy-logistics use cases and we based the development on the “ResourceItem” that was available in FHIR 3.5. Now we are moving the platform to support FHIR R4 and this resource is no more available.
We agree on the fact that for closed loop medication management is much better to use the real resource specific (medication/device) and not an abstract one and we definitely already do like that.
Indeed, despite of our CPOE module regularly adopts catalogs, medication and device resources, the aim of the logistic one is to track all the items inside the hospital till the effective administration to the patient and needs a more generic approach. The abstraction provided by the resource “ItemInstance” itself is great for this use case because it can easily manage not only devices, medications, specimens, etc, but also the container such as Rolls, Boxes and Packages that are used to delivery these items among locations (pharmacy, wards [Fridges],[Cabinets],[shelves] and [carts]).
John Moehrke (Jan 31 2019 at 15:07):
@Jose Costa Teixeira
Jose Costa Teixeira (Feb 01 2019 at 07:14):
Hi @vania manzelli good point and good timing.
We are now having discussions on "Healthcare Product" which should the same purpose, and it is great that you are looking at this from a broader operations perspective. So let me ping @Hans Buitendijk @Eric Haas, @Lorraine Constable and @Lloyd McKenzie who have taken part of the discussion. We also looked at Catalogs and Lorraine and I believe @François Macary and myself are having the same approach as you indicate - while specific resources are good for staying within a workflow, when it comes to distribution and catalogs, that specificity brings issues.
Jose Costa Teixeira (Feb 01 2019 at 07:17):
btw, IHE Pharmacy is preparing a white paper for Supply and the approach is to "supply an item, and we don't really care about defining when an item is called a medication or a device, or if it is a consumable or printer paper". The Supply profiles are looking at GS1 transactions because the GS1 model is established and is very simple - you can have an item which is inside a box which is another item, which is inside a carton which is another item...
vania manzelli (Feb 01 2019 at 14:34):
Hi @Jose Costa Teixeira , good to know, I see that you are in the IHE Pharmacy's technical committe, may I expect that the white paper will suggest the usage of a generic "ResourceItem"? is there any draft version of the document? may me and my team contribute somehow?
Jose Costa Teixeira (Feb 03 2019 at 20:57):
Hi Vania. In the white paper we will only describe the requirements and flows - but we will mention clearly that "supply" can be for medication, devices or other products.
Jose Costa Teixeira (Feb 03 2019 at 20:57):
the IHE white paper is only the analysis, then the IHE Profiles will specify a solution.
Jose Costa Teixeira (Feb 03 2019 at 20:58):
There, we will start with GS1, which has a generic "tradeItem" resource. We look forward to have the health product discussion handled in FHIR when we want to support intra-institutional supply (all aspects related to supply inside hospital, not only delivery, but also inventory, etc.)
Jose Costa Teixeira (Feb 03 2019 at 21:00):
that is a requirement that we can bring up - when supplying stuff, it is important NOT to force the implementers to choose between a device or medication.
John Moehrke (Feb 04 2019 at 13:19):
See the IHE Uniform Barcode Processing profile that @Jose Costa Teixeira has written. It shows GS1 use with FHIR https://wiki.ihe.net/index.php/Uniform_Barcode_Processing
Last updated: Apr 12 2022 at 19:14 UTC
