Stream: implementers
Topic: Spark FHIR non-default profiles
Teun Pronk (Apr 18 2019 at 06:19):
Hi all, I posted a question on Reddit and there was suggested i'd ask it here.
Since its quite a long message i will just post the link here
https://www.reddit.com/r/fhir/comments/be7rv1/fhir_server_using_nondefault_profiles/
Any ideas? You can just reply here
Thanks in advance.
Lloyd McKenzie (Apr 18 2019 at 06:32):
What the specification is asking for should be fully supported using Spark. The profile defined seems compliant with the FHIR specification - they're just indicating specific elements that you're expected to support and/or that must always be included.
Teun Pronk (Apr 18 2019 at 06:34):
Yes, but thats regarding receiving these profiles. But what if I have to respond using that ZD Organization profile? How can I make spark do that, that's something I can't figure out.
Lloyd McKenzie (Apr 18 2019 at 14:08):
Just make sure you include the elements the profile is asking for.
Martijn Harthoorn (Apr 19 2019 at 10:33):
@Kenneth Myhra is currently the maintainer of the OS Spark FHIR server.
Martijn Harthoorn (Apr 19 2019 at 10:35):
If you post a resource that server that conforms to zd-organization, it will return the same resource on request.
Martijn Harthoorn (Apr 19 2019 at 10:35):
that's the case for most FHIR servers
Kenneth Myhra (Apr 19 2019 at 11:49):
As is being said above by Martijn and Lloyd, Spark will give you the exact same resource back as you posted. You can test it out at http://spark.kufu.no it's currently running R4
Martijn Harthoorn (Apr 19 2019 at 11:50):
Teun is implementing ZorgDomein profiles - which I think are STU3.
Martijn Harthoorn (Apr 19 2019 at 11:52):
If that's true - he can checkout stu3/master. Right?
Kenneth Myhra (Apr 19 2019 at 12:53):
Yep
Teun Pronk (Apr 24 2019 at 05:50):
Thanks a lot guys, this info allowed me to progress on the project. Sorry for the late response, had some time off.
Appreciate the input :)
Last updated: Apr 12 2022 at 19:14 UTC
