Stream: social
Topic: National FHIR projects
Simone Heckmann (Jan 10 2018 at 16:40):
Hi all,
I'm trying to put together a comprehensive list of FHIR projects on national /regional scale,
here's what I've got so far:
http://wiki.hl7.de/index.php?title=FHIR-Markt%C3%BCbersicht&stable=0#FHIR-Projekte_International
Does anyone find a wrong or obsolete entry, can provide details on the status (in production/in developement) or know of additional projects?
Igor Sirkovich (Jan 10 2018 at 16:59):
Hi Simone, in Canada, in addition to "Digital Health Immunization Repository - Ontario", we also have "Digital Health Drug Repository - Ontario" in production.
Fernando Portilla (Jan 10 2018 at 17:01):
Hi all,
I'm trying to put together a comprehensive list of FHIR projects on national /regional scale,
here's what I've got so far:
http://wiki.hl7.de/index.php?title=FHIR-Markt%C3%BCbersicht&stable=0#FHIR-Projekte_International
Does anyone find a wrong or obsolete entry, can provide details on the status (in production/in developement) or know of additional projects?
Fernando Portilla (Jan 10 2018 at 17:08):
Hello Simone, in Uruguay with the Salud.uy Program, we are using the Resources CodeSystem and ValueSet to publish the Catalogues for our National Electronic Health Record Project. We used vue.js to program the front end of a dynamic searcher in : https://hcen.salud.uy/web/pub/catalogos ; the web site of the program is : hcen.salud.uy; Other field of interest is in relation with the resources related with e-prescription for medication for our national project. Kind regards!
Simone Heckmann (Jan 10 2018 at 17:27):
@Igor Sirkovich @Fernando Portilla Thank you so much!
I added your projects to the list.
Lloyd McKenzie (Jan 10 2018 at 17:36):
Love the list. Any chance we could migrate it to the HL7 International wiki and have the German page link to it? (That might make it more discoverable for the rest of the community.) I'm sure there are a lot more national-scale projects to add to the list. The Lithuania EHR? (Is that still in production?)
Simone Heckmann (Jan 10 2018 at 17:37):
Sure, I'll just c&p as soon as it's halfway stable!
Simone Heckmann (Jan 10 2018 at 17:38):
@Patrick Werner: What's going on in Chile?
Simone Heckmann (Jan 10 2018 at 17:38):
The NHS should have more stuff than is currently on the list...
Simone Heckmann (Jan 10 2018 at 17:39):
@Lloyd McKenzie : what's the best place to put it in the Wiki?
Simone Heckmann (Jan 10 2018 at 17:40):
Separate page or subsection of this: http://wiki.hl7.org/index.php?title=Organizations_interested_in_FHIR
Lloyd McKenzie (Jan 10 2018 at 18:02):
Might be worth having its own page - though a link from Organizations interested would be good.
Simone Heckmann (Jan 10 2018 at 18:25):
How about this format: http://wiki.hl7.org/index.php?title=National_FHIR_Projects
Lloyd McKenzie (Jan 10 2018 at 18:48):
I like it - though right now it give the illusion that Canada is much further ahead than I think we really are :)
Simone Heckmann (Jan 10 2018 at 18:49):
That'll motivate others :D
Simone Heckmann (Jan 10 2018 at 18:51):
@Brian Postlethwaite : I'm sure you'll find something to add/correct: http://wiki.hl7.org/index.php?title=National_FHIR_Projects#Australia :)
Patrick Werner (Jan 12 2018 at 15:16):
This and the next week we are building protypes for a national health provider directory and a prototype of a national pharmaceutical terminology service. Both realised in FHIR.
Dion McMurtrie (Jan 15 2018 at 02:53):
To add to the list, in Australia we have the National Clinical Terminology service https://www.healthterminologies.gov.au, which has a FHIR endpoint as the main set of terminology services at https://api.healthterminologies.gov.au/integration/v2/fhir.
Dion McMurtrie (Jan 15 2018 at 02:57):
@Patrick Werner I'm interested in the pharmaceutical terminology service you mention. We have AMT exposed as part of SNOMED CT-AU in the National Clinical Terminology service though CodeSystem and implicit ValueSet resources and operations - normal FHIR terminology service.
I'm also experimenting with the concept of exposing our medications terminology, AMT, as a set of Medication resources to provide a richer API to the drug content than is available through the FHIR terminology service API. This is explained at more detail with a running example at https://medserve.online
Is the pharmaceutical terminology service similar to one of these things or something different?
Melva Peters (Jan 17 2018 at 14:54):
@Patrick Werner The Pharmacy Work Group would be interested in learning more about your pharmaceutical terminology service. We are working on change to the Medication resource and your input would be very useful.
Jose Costa Teixeira (Jan 17 2018 at 17:36):
@Melva Peters i think the meeting is scheduled - Tuesday starting in Q2, this specific matter on Q4
Jose Costa Teixeira (Jan 17 2018 at 17:39):
@Dion McMurtrie @Patrick Werner can you join?
Jose Costa Teixeira (Jan 17 2018 at 17:42):
perhaps we can start with "how a product is identified" and then we simply let the topic explode into HealthProduct, Catalog, ... But co-chairs may have better guidance to structure the meeting.
Dion McMurtrie (Jan 17 2018 at 21:04):
Sure, I'd love to. Where can I get the details? i.e. date/time, call in details etc?
Melva Peters (Jan 18 2018 at 22:42):
@Dion McMurtrie The joint meeting is Tuesday Q4 with Pharmacy and BR&R. Pharmacy will be discussing requirements on Monday Q4 and throughout the week. If you aren't going to be in New Orleans for the Working Group Meeting, you can dial in to a Pharmacy call at 4pm Eastern US every Monday. Next week is our last teleconference before the Working Group Meeting and we will resume on February 11th. Dial in information is Dial-in Number (United States): (515) 604-9344
Access Code: 443497
International Dial-in Numbers: https://www.freeconferencecall.com/wall/pharmacy8#international
Dion McMurtrie (Jan 19 2018 at 02:30):
Excellent, thanks @Melva Peters I'll join you next week. Unfortunately I was unable to get approval to travel for the WG meeting in New Orleans, but I'll try to get to the next one.
Jose Costa Teixeira (Jan 19 2018 at 08:57):
Actually, the meeting starts on Q2. Seems we have a conflict of agenda- We start discussing product definition on Q2, with everyone in the same room. then it seems that OO discusses product catalog and Pharmacy discussed the "medicationKnowledge" in Q4 separately
Jose Costa Teixeira (Jan 19 2018 at 08:58):
The stuff where we talk about Catalog (the thing where we are trying to support @Dion McMurtrie 's and similar terminologies) is on Tuesday Q4
Jose Costa Teixeira (Jan 19 2018 at 09:03):
@Hans Buitendijk @Melva Peters @Lorraine Constable how do we resolve this?
Seems silly that the two discussions on product Catalog are competing in the same slot. Should we combine efforts?
Melva Peters (Jan 19 2018 at 15:54):
We have a joint meeting with BR&R on Tuesday Q4 to discuss the two projects that have been proposed that overlap - MedicationKnowledge and MedicinalProduct. I personally do not believe that catalog should overlap with this discussion. A catalog will include references medication or medicationknowledge resources but should not be duplicating the same content.
Jose Costa Teixeira (Jan 19 2018 at 16:10):
@Melva Peters not knowing what is MedicationKnowledge, i am not so sure there is an overlap, so i am playing it safe - we have long agreed that Catalog will not replicate the content, but Catalog will contain the relations between entities. Things like "this device contains that product" or "this medication needs that device" or "this product requires that other product".
Jose Costa Teixeira (Jan 19 2018 at 16:11):
in other words,
Catalog does not define MP, MPP, PhP, etc.
But a Catalog will say "in this hospital, the following "brand products" correspond to the following "generic products"
Jose Costa Teixeira (Jan 19 2018 at 16:12):
If that polyhierarchy / graph is outside of the scope of medicationKnowledge, then yes we are good.
However, that is the only thing I saw in Dion's work that made me bring this up.
Jean Duteau (Jan 19 2018 at 16:23):
@Jose Costa Teixeira I certainly hope that Catalog DOES NOT try to represent that inherent relationships between medicinal products. That seems to me to be totally outside the scope of a Catalog since these inherent relationships are not context-specific. All of your examples are characteristics of the product itself and are not catalog-specific. I specifically don't understand your "in this hospital, the following brand products correspond to the following generic products" example. Maybe we can touch base in NOLA so you can explain this to me.
Lloyd McKenzie (Jan 19 2018 at 16:24):
I don't think it's totally agreed that catalog will contain any relationships. That's proposed. But we don't even have agreement that Catalogue will exist at all. And I'm quite leary of relationships being defined outside of the resource that the relationships are to.
Jose Costa Teixeira (Jan 19 2018 at 16:24):
Aha, so there is overlap. Yes, they can be context-specific (will gladly explain that example).
Lloyd McKenzie (Jan 19 2018 at 16:24):
Containment relationships, requires relationships, etc. I'd expect to be found on the Medication/Device/Product/whatever - NOT on a wrapper.
Lloyd McKenzie (Jan 19 2018 at 16:25):
And I wouldn't be in favor of catalog entry or whatever duplicating any of that information
Jose Costa Teixeira (Jan 19 2018 at 16:25):
Catalog is proposed indeed, with the intent of eliciting requirements and showing commonalities.
Jean Duteau (Jan 19 2018 at 16:25):
Containment relationships, requires relationships, etc. I'd expect to be found on the Medication/Device/Product/whatever - NOT on a wrapper.
+1
Lloyd McKenzie (Jan 19 2018 at 16:25):
Commonalities are generally handled via patterns, not resources
Jose Costa Teixeira (Jan 19 2018 at 16:26):
Good, that is the Q2 discussion.
Lloyd McKenzie (Jan 19 2018 at 16:26):
Q2 where?
Lloyd McKenzie (Jan 19 2018 at 16:26):
(and which day?) - not that I can likely make it...
Jose Costa Teixeira (Jan 19 2018 at 16:26):
ah Tuesday Q2, health Products thing
Jean Duteau (Jan 19 2018 at 16:27):
Good, that is the Q2 discussion.
I don't see how that is a discussion at all. Catalog entries CAN'T contain relationships that are inherent to the underlying thing being referenced.
Jose Costa Teixeira (Jan 19 2018 at 16:27):
@Jean Duteau Q2 is for Lloyd's question.
Lloyd McKenzie (Jan 19 2018 at 16:28):
Anyhow, we've hijacked a social discussion - this should continue on the implementers stream
Jens Villadsen (Jan 21 2018 at 20:28):
Hopefully, I'll be able to add Denmark within the next couple of weeks
Patrick Werner (Jan 22 2018 at 14:13):
@Melva Peters @Jose Costa Teixeira i just joined the pharmacy List. I also will be attending the WGM in New Orleans with a colleage from Chile also involved in the project.
Melva Peters (Jan 22 2018 at 16:25):
@Patrick Werner Great! If you are able to join Pharmacy in New Orleans, we'd very much like to hear about your work
vilas mamidyala (Feb 07 2018 at 20:34):
Hi Everyone,
I have a question about FHIR framework. FHIR is grown in recent time and it is apparently the ONC Standard these days and is included in the 21^st Century Cures Act. So I was just curious, do we need to migrate to FHIR for my project where we currently using hl7 v2 for communication between the clinic and my organization.
I currently see no issues in using HL7 v2, i would like to know whether moving to FHIR has any better advantage over HL7 V2. Is FHIR is now public following standard or it still in development stage in the market.
Thanks
Grahame Grieve (Feb 07 2018 at 20:45):
FHIR has a number of structural advantages over v2 even for things where v2 is well established. However none of these advantages are enough for the market to start ripping and replacing v2 interfaces with FHIR, except in a few corner cases. If you tried to replace it right now, you'd most likely find that your partners were not ready for it, and don't even have any plans to be ready soon
Lloyd McKenzie (Feb 07 2018 at 20:58):
FHIR is most likely to show up in v2 environments first as a parallel interface - to support SMART on FHIR apps, government reporting or other interfaces (quite likely mediated through existing interface engines). It will be a good while before FHIR becomes a preferred interface for things like ADT - if that happens at all.
Kevin Shekleton (Feb 07 2018 at 22:35):
Small bit of clarification - FHIR is actually not mandated in the 21st Century Cures Act or other US based regulation. Yet. What did happen was language that says APIs must be made available for a certain set of data. Many vendors have satisfied that API requirement via FHIR.
Simone Heckmann (Feb 08 2018 at 10:03):
Needless to add that V2 will not satisfy any language that says "API" :)
René Spronk (Feb 08 2018 at 10:41):
v2 is not an "API" ? Depends on ones definition I guess. Having a MLLP v2 interface is a pretty basic API, but why not?
Simone Heckmann (Apr 25 2018 at 10:21):
Reminder: please remember to update http://wiki.hl7.org/index.php?title=National_FHIR_Projects with information about planned/implemented/productive FHIR projects on a national level. This is very helpful information for people who are trying to promote FHIR all over the world! Thanks!
Last updated: Apr 12 2022 at 19:14 UTC
