Stream: implementers
Topic: Representing apps in FHIR
Josh Mandel (Apr 20 2021 at 18:52):
Do folks have experience describing software tools (e.g., consumer- or provider-facing apps) in FHIR? Some combination of Device and Endpoint resources, or perhaps HealthcareServices for apps that are in this domain? The idea here is to explain what the app is and does (and I wouldn't necessarily assume the app uses FHIR in any way; just that at FHIR-based system might want to keep a list of apps). I'm curious what ideas are out there before I go too deep on this ;-)
Patrick Werner (Apr 20 2021 at 19:33):
@Simone Heckmann was involved in creating the german register for reimbursable apps:
https://simplifier.net/guide/diga/fhir-profile
Simone Heckmann (Apr 21 2021 at 10:55):
Yes, we used DeviceDefinition to represent the App. Not many attributes were usable however and a lot ended up in Extensions. In our specific case we even ended up putting most of the descriptive information, such as indication, into the ChargeItemDefinition resource, because these properties turned out to be dependent on where these apps were listed/who approved them...
Apparently in our scenario the same app can be prescribed for different indications for a different price, so... :shrug:
Last updated: Apr 12 2022 at 19:14 UTC
