Stream: ihe
Topic: MHD Document Consumer(Client) testing
Dimitar (Oct 16 2017 at 13:25):
Hello, I am making a FHIR client which is also supposed to retrieve a specific patient document from a document sharing environment, such as XDS, through the MHD API. However, I am having difficulties, finding sample data, to test my requests. I am currently experimenting, with the XDStarClient, provided by the gazelle community, but I wanted to see if there is better alternatives, with synthetic document data, which I can query easily with the MHD API. Thank you in advance!
John Moehrke (Oct 17 2017 at 13:19):
I have never gotten time to work on creating them. IHE does intend to produce them in the coming months. I am very happy to receive help.
Dimitar (Oct 21 2017 at 15:47):
@John Moehrke I am intending to use the MHD API, within my internship project, which will be built entirely using FHIR REST API and I'll be posting in here how that's going and in case I run into some issues with it. Definitely a great API to have and I am looking forward to testing it out on practice!
John Moehrke (Oct 23 2017 at 14:41):
Note that there are now a set of StructureDefinitions for MHD that I have registered through Simplifier with registry.fhir.org. Thanks go to @Ardon Toonstra for writing the first draft. I welcome comments on improvement.
John Moehrke (Oct 23 2017 at 15:06):
I would like to have a minimal ImplementationGuide resource that links the MHD StructureDefinitions with the IHE wiki page for MHD http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents_(MHD) ... Anyone want to mock that up for me? or give me hints as to how I will fail?
Jose Costa Teixeira (Oct 23 2017 at 15:43):
Did you see Eric Haas's IG template? Might be a good point to start.
https://github.com/Healthedata1/IG-Template
John Moehrke (Oct 23 2017 at 16:10):
Jose, that is not what I am looking for. I am not looking to create YET-ANOTHER implementation guide. I already have the IHE wiki, and pdf. What I need is a minimal ImplementationGuide resource that I can register on registry.fhir.org; and it points at the IHE wiki, and the three StructureDefinitions. There is no good reason to start from scratch... at least not yet, that will be a task in a few months. Today I just want a way to associate a set of StructureDefinitions with an IHE published web-page (Profile ~~ Implementation Guide).
Jose Costa Teixeira (Oct 23 2017 at 16:16):
How do you see it?
Is this what you mean by having it on registry?
https://simplifier.net/IHEMMA2
Jose Costa Teixeira (Oct 23 2017 at 16:17):
i don't know how you see the link to the wiki page
John Moehrke (Oct 23 2017 at 16:19):
Jose, anytime you register something with Simplifier, it will get registered at registry.fhir.org... so your MMA IG is registered there (actually a few versions are there, and I don't know how to manage versions (deleting old). https://registry.fhir.org/search?q=ihe%20mma
John Moehrke (Oct 23 2017 at 16:22):
As we have discussed many times... using the HL7 toolings to produce an Implementation Guide (with a space) is a fine thing to do for an IHE profile, and eventually I want all IHE profiles of FHIR to do this. However that is additional work, and we have a list of issues. I want to just have an ImplementationGuide resource (no space). This is NOT the same thing. When you use the HL7 implementation guide tooling to produce your Implemenation Guide, it does produce an ImplementationGuide resource. but it also produces a bunch of HTML that is not part of the IHE governance and balloting process... The IHE governance and balloting process only cover the Supplement PDF file, thus that is all that is normative today.
Jose Costa Teixeira (Oct 23 2017 at 16:25):
I don't get it. Do you want a JSON with an ImplementationGuide resource?
Jose Costa Teixeira (Oct 23 2017 at 16:26):
there's one here:
https://simplifier.net/IHEMMA2/MMA/~json
Jose Costa Teixeira (Oct 23 2017 at 16:27):
this was made in Forge. not the IG Publisher
Jose Costa Teixeira (Oct 23 2017 at 16:28):
you mention want to link to a wiki page, it's not clear to me how you see this. You mean in the json? or you mean in the html that the json publishes?
John Moehrke (Oct 23 2017 at 16:36):
So I already have that kind of an ImplementationGuide resource.. but it is missing the .page element. I think the .page element can provide links to the html for humans to read, thus in my case the IHE wiki... Hence why I ask... because I don't see good examples of how the ImplementationGuide resource links to human readable stuff.. .and we (IHE) start with human readable stuff, so I want to have links (somehow) between the StructureDefinition and the human readable stuff that we have.
John Moehrke (Oct 23 2017 at 16:37):
see for PDQm https://simplifier.net/IHEPDQmimplementatio/PDQm/~json
John Moehrke (Oct 23 2017 at 16:39):
note, I noticed your URLs have \profile\ in them... that is not part of our current thinking of persistent identifer URLs ... So for example
John Moehrke (Oct 23 2017 at 16:39):
"url":"http://ihe.net/fhir/profile/StructureDefinition/MMA",
John Moehrke (Oct 23 2017 at 16:39):
should be
John Moehrke (Oct 23 2017 at 16:39):
"url":"http://ihe.net/fhir/StructureDefinition/MMA",
John Moehrke (Oct 23 2017 at 16:40):
please feel free to find my bugs... I am sure I have more than you... (for example, right now my new PDQm (with fixed URLs) is failing when I load it to simplifier).
Jose Costa Teixeira (Oct 23 2017 at 16:43):
the urls were just whatever-i-could-think-at-the-moment. But i will change AND capture this as a requirement :)
Jose Costa Teixeira (Oct 23 2017 at 16:44):
did you try to build it with forge? or are you manually entering data there?
Jose Costa Teixeira (Oct 23 2017 at 16:47):
later i will try to build one IG where the page.source points to one external url, to see how that works.
John Moehrke (Oct 23 2017 at 17:11):
yes that URL pattern is something we just determined.
John Moehrke (Oct 23 2017 at 17:12):
I don't want to be reliant on any specific tools, these FHIR conformance resources are 'standard' after all...
Michel Rutten (Oct 23 2017 at 19:57):
@John Moehrke Do you know why your profile fails to upload to simplifier? Maybe loading it in Forge shows validation errors?
Jose Costa Teixeira (Oct 24 2017 at 08:30):
@John Moehrke this is still a steep curve, but hopefully we can work to make it easy.
The url is for a page that is built with the IG, and it does not work for external pages. We can consider, as part of some templates, how we can have one html page in the IG that simply embeds a wiki page. Assuming that is a quick patch, could be worth the limited effort.
Jose Costa Teixeira (Oct 24 2017 at 08:31):
there was some difference between Forge editing and manual editing - that is not linked to the resources, which are standard, but with the flexibility of the IG Publishing mechanisms.
John Moehrke (Oct 24 2017 at 13:44):
Thanks for the intereste @Michel Rutten . I did fix my error, and now have it uploaded. But do get an error that it can't be displayed. I suspect this is because I am looking to just point at IHE profile, rather than build an IG in FHIR format... See https://simplifier.net/IHEPatientDemographi/PDQm-2/~overview
Michel Rutten (Oct 24 2017 at 14:08):
Hi @John Moehrke, Simplifier allows you to author and publish IGs as part of your project. However we're still working on the integration of the FHIR IG resource. Specifically, IG resource preview rendering hasn't been implemented yet.
John Moehrke (Oct 24 2017 at 23:43):
Thanks @Michel Rutten . So I should not think that I have invalid IG resource... Otherwise, does it look okay?
Michel Rutten (Oct 25 2017 at 09:47):
Hi @John Moehrke, the PDQm IG resource on Simplifier references the PDQM.Patient profile via a sourceUri:
<sourceUri value="http://ihe.net/fhir/StructureDefinition/IHE.PDQm.Patient" />
ImplementationGuide.package.source[x] is a choice type element:
https://www.hl7.org/fhir/implementationguide-definitions.html#ImplementationGuide.package.resource.source_x_
I think in this case, you'd want to use a sourceReference (based on canonical url of the target profile).
John Moehrke (Oct 25 2017 at 14:43):
Thanks... I fixed that
David Hay (Oct 25 2017 at 17:32):
@John Moehrke - that's exactly the approach I took with the CF IG viewer - using the IG almost like an index for the various artifacts of interest in some given context...
David Hay (Oct 25 2017 at 17:33):
Are you interested in building out the functionality in CF to make it easier to author an IG for this purpose?
John Moehrke (Oct 25 2017 at 17:38):
I am working on two phases for IHE. First phase is what I am looking to do now, with minimal ImplementationGuide resource that points at StructureDefinition (and somehow CapabilityStatements) -- and leveraging the IHE published wiki page, and thus PDF... Second phase is working with the IG tooling to move IHE away from PDF as the prime. This move will likely have multiple sub-phases. I do today recommend CF be used during early profiling, as a easy way to drive consensus. Have a bunch of functionality that IHE leverages in their Profile format that are not yet as mature in FHIR yet..... SO, YES, I want to work with you and the other IG tooling people to improve this. I have asked to be on the IG SIG...
David Hay (Oct 25 2017 at 19:21):
cool! I'll tidy up some stuff I started on and ping you when ready... I should go on the IG sig as well (unfortunately I missed the last call as I was travelling)...
Last updated: Apr 12 2022 at 19:14 UTC
