Stream: IG creation
Topic: How to publish an IG
Apra (Sep 19 2019 at 15:10):
Good morning, good evening (depending on where you are)
Apra (Sep 19 2019 at 15:12):
I am new to FHIR and am trying to create an implementation guide
Apra (Sep 19 2019 at 15:21):
what I have: an app A that gives some readings. We also built a test app that integrates with this by sending an FHIR request (ServiceRequest and ObservationResponse). I am aware of the structure of the messages to be sent between the app A that we built and any 3rd party app that wants to integrate with app A.
Apra (Sep 19 2019 at 15:21):
Is that all that we need to fill in the implementation guide?
Grahame Grieve (Sep 19 2019 at 15:21):
do you know what profiles (StructureDefinitions) do?
Apra (Sep 19 2019 at 15:23):
what I have: an app A that gives some readings. We also built a test app that integrates with this by sending an FHIR request (ServiceRequest and ObservationResponse). I am aware of the structure of the messages to be sent between the app A that we built and any 3rd party app that wants to integrate with app A.
Where in implementation guide do we add these? Most sections do not seem to apply to our case at all. I do see a section titled: "ImplementationGuide.definition" and a subsection titled "ImplementationGuide.definition.resource" under that. Is this where the above data goes in?
Apra (Sep 19 2019 at 15:23):
There is a section called "ImplementationGuide.manifest.resource" which also looks similar. Not sure which one to use
Apra (Sep 19 2019 at 15:27):
Do we provide a skeleton structure of the ServiceRequest and ObservationResponse in one of the above sections? And give actual examples down below? I see a section for Examples.
David Pyke (Sep 19 2019 at 15:37):
The creation of an implementation guild is a set of resources, profiles and other components. This wiki entry will give you an idea of the process but creating one is not a small undertaking: https://wiki.hl7.org/index.php?title=FHIR_Implementation_Guides
Lloyd McKenzie (Sep 19 2019 at 21:43):
@Apra We're in the process of putting together a fair bit of documentation to support newcomers in defining their own IGs. Should be announced here in the next couple of weeks. In the meantime, suggest googling "FHIR DevDays Videos and look at those that deal with profiling and implementation guides.
Apra (Sep 20 2019 at 11:58):
Thanks for the inputs Lloyd.
Apra (Sep 20 2019 at 12:38):
So, I understand the key is to build documents - "CapabilityStatement","StructureDefinition","ValueSet" that define the messages passed between the apps I have and then reference these docs from the IG. I still have sme points that are a little unclear, but will read up on the above and get back if required.
Apra (Sep 20 2019 at 14:10):
do you know what profiles (StructureDefinitions) do?
Reading and trying to understand now. Looks like that may help my case.
Apra (Sep 20 2019 at 15:00):
Hey guys
Apra (Sep 20 2019 at 15:01):
I was reading about Capability statements
Apra (Sep 20 2019 at 15:02):
In my case, I have 2 apps sending FHIR messages to each other. Both are android apps and communicate via Android intent calls. Not via REST API. So, in a capability statement, I suppose I should use Messaging instead of rest
Apra (Sep 20 2019 at 15:03):
Now, there is an option "interactions" which is present under rest - looks like this is used to indicate what request/response can happen between the two apps. However, I do not see this under Messaging at all.
Apra (Sep 20 2019 at 15:03):
how do I do something similar with Messaging?
Grahame Grieve (Sep 20 2019 at 15:05):
messaging is under developed in capability statement. But there's a lot functionality in MessageDefinition - have you looked at that?
Apra (Sep 20 2019 at 15:06):
is it? let me see. I was also initially confused . in fact still am trying to understand what is the difference between these
Apra (Sep 20 2019 at 15:06):
let me check
Lloyd McKenzie (Sep 20 2019 at 15:08):
It may be that you'll be doing a custom transport rather than "true" FHIR messaging (transmitting a Bundle starting with a MessageHeader)
Apra (Sep 20 2019 at 15:15):
@Lloyd McKenzie , well - this is a type of "messaging". Both apps are on the same device and they use intent calls to work by sending a FHIR compliant request/response
Lloyd McKenzie (Sep 20 2019 at 15:17):
Understood. All FHIR exchanges can be thought of as "messaging", but the term Messaging means something specific in FHIR and has impacts on both what the exchanged data structure looks like and how it's defined.
Apra (Sep 23 2019 at 07:47):
Ok
Apra (Sep 23 2019 at 07:48):
@Lloyd McKenzie , are you suggesting using a custom tag - maybe I could call it "intent" instead
Apra (Sep 23 2019 at 07:49):
but that may not be recognized by all FHIR services, isnt it?
Apra (Sep 23 2019 at 10:24):
or I see something called "document". Not sure if that could be used.
Lloyd McKenzie (Sep 23 2019 at 13:01):
@Apra There are three primary mechanisms for sharing FHIR data - REST, messaging and documents. First, have you read through the pages in the FHIR spec that describe each of the approaches? (You can find links to each of the pages here under 'exchanging resources': http://build.fhir.org/documentation.html
Apra (Sep 23 2019 at 13:32):
(deleted)
Last updated: Apr 12 2022 at 19:14 UTC
