Stream: implementers
Topic: Fhir Resources format
Lakshmi Thrivarna (Oct 24 2018 at 13:57):
Hi All, We have different formats in the fhir resources. I want the below resource format to specify in my application.
{
"resourceType" : "Bundle",
"identifier" : {
"use" : "${identifier.use}",
"type" : "${identifier.type}",
"system" : "${identifier.system}",
"value" : "${identifier.value}",
.
.
.
.
etc
Is there any way??
Vadim Peretokin (Oct 24 2018 at 14:00):
What is the question you're asking?
Steve Munini (Oct 24 2018 at 14:03):
I'm a little confused about your question. Bundle Resources are collections of other FHIR Resources. Each separate Resource can be found in Bundle.entry.resource.
Lakshmi Thrivarna (Oct 25 2018 at 12:02):
I want to submit the fhir resource builder for any resource(patient,practitioner,Account........). I want the below format to submit in my application.
{
"resourceType": "Patient",
"id": "${id}",
"identifier": [
{
"use": "${use}",
"type": {
"text": "${text}"
},
"value": "${value}",
"assigner": {
"display": "${display}"
}
}
],
}
Can anyone suggest.
Thank you
John Silva (Oct 25 2018 at 12:34):
Not sure what you're trying to do; it appears that you are trying to have some template mechanism in your app's client code, which makes sense. One thing to watch out for -- the Medication resource does NOT have an identifier property unfortunately!! (Have discussed this in other threads here and there's some reason behind it but it would be nice if it could conform to the same pattern as every other FHIR resource.)
Lloyd McKenzie (Oct 25 2018 at 15:12):
Not sure what you mean by "the fhir resource builder" - what software are you referring to? A use value of "${use}" isn't going to be a valid FHIR instance going over the wire. Internally you could certainly use a framework like that to allow population of an instance though if you wanted.
Jean Duteau (Oct 25 2018 at 16:16):
One thing to watch out for -- the Medication resource does NOT have an identifier property unfortunately!!
Actually, that is no longer true.
John Silva (Oct 25 2018 at 18:28):
Yeh, that made it into R4; hooray!! (but folks that are not yet on R4 will not see it for a while, I suppose)
Lloyd McKenzie (Oct 25 2018 at 20:24):
They should have a standard extension they can use...
BTW: @Grahame Grieve as part of the transformation work, are you defining extensions for new R4 elements that can be used in R3?
Grahame Grieve (Oct 26 2018 at 13:13):
we defined how they will be generated, and I will generate them and publish them as part of the final publication process
Lloyd McKenzie (Oct 26 2018 at 14:53):
Do the transforms use them?
Grahame Grieve (Oct 26 2018 at 14:56):
not at the moment.
Lloyd McKenzie (Oct 26 2018 at 15:11):
Will they by the time we publish?
Grahame Grieve (Oct 26 2018 at 15:19):
I plan so, yes.
Grahame Grieve (Oct 26 2018 at 15:19):
that is, if the transforms are ready.... it's a big piece of work....
Last updated: Apr 12 2022 at 19:14 UTC
