Stream: implementers
Topic: Profile registry defined in hl7.org
redixint (Sep 21 2017 at 13:38):
Previously, I asked a question about how to retrieve extension definitions from hl7.org. The question was well answered. Now, I have a similar question for profile. I would like to retrieve the profile definitions for a resource as well as the profile lists defined in hl7.org via REST API.
I have tried the following REST API to get the profiles defined in the resource observation.
https://www.hl7.org/fhir/STU3/observation-profiles.json
I also tried the following to get the profile lists.
http://hl7.org/fhir/profilelist.json
Both do not work. Can someone point me in the right direction to get the profile registry for a resource and the profile lists defined in hl7.org?
Lloyd McKenzie (Sep 21 2017 at 17:53):
The HL7 website doesn't actually expose a REST API. It's just a static website. We don't provide files that list profiles (or extensions) by resource, but there are files that list all profiles and extensions: profiles-others.json (or .xml) and extension-definitions.json (or .xml). You could then figure out what resource(s) they apply to.
Mirjam Baltus (Sep 22 2017 at 12:33):
You could use the Simplifier.net registry. Simplifier exposes its data through a REST API, and has all of the core profiles and extensions stored, plus lots of other profiles from multiple organizations. Query https://stu3.simplifier.net/open/StructureDefinition?url=<canonical url you're looking for>, or use any of the other search parameters on StructureDefinition.
redixint (Sep 22 2017 at 12:35):
@Mirjam Baltus
redixint (Sep 22 2017 at 12:38):
I have tried the following: https://stu3.simplifier.net/open/StructureDefinition?name=OptumPractitioner. It does not seem to work. It always returns all of the results.
Mirjam Baltus (Sep 22 2017 at 12:54):
Ah, sorry about that! I thought we had implemented all standard search parameters, but I was wrong. I did get the right result using url=http://fhirtest.uhn.ca/baseDstu3/StructureDefinition/OptumPractitioner
Mirjam Baltus (Sep 22 2017 at 12:55):
And searching on publisher=optum works as well.
redixint (Sep 22 2017 at 13:05):
Yes, publisher works. But several other search parameters, e.g., date, kind, name, title, url, etc do not work.
Mirjam Baltus (Sep 22 2017 at 13:22):
The url parameter does work, but only if you fill in the complete canonical url. The other parameters you mention are planned to be supported in a future release.
Another search parameter you can use is the _content parameter, that does quite a broad search through the resource content.
redixint (Sep 22 2017 at 13:27):
Interesting. Is "_content" specific to Simplifier.net since hl7.org does not have this parameter? Can you share some examples on how to use the "_content'?
Mirjam Baltus (Sep 22 2017 at 13:35):
This is one of the standard parameters that can be available on all resource types (see http://www.hl7.org/fhir/search.html#content). Implementations can vary, but with Simplifier I could find your profile with ?_content=OptumPractitioner.
Mirjam Baltus (Sep 22 2017 at 13:35):
I'm not completely sure which fields Simplifier indexes for this parameter though.
Last updated: Apr 12 2022 at 19:14 UTC
