SDK interface to non FHIR server systems #1962
dennisbrox
started this conversation in
General
Replies: 4 comments 4 replies
-
If you use the Fhir[Json/Xml]Serializer, you can serialize your POCO's to correct FHIR json/xml. This is how FHIR data is usually communicated between two systems. If the receiving system cannot work with that, you will have to implement extra code to align with their API, or you would have to create an extra layer on the receiving end to convert the FHIR data to the format it can work with. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I am not communicating between 2 systems. I'm using the create and update
methods that take resources and which would seem the obvious way to do it.
I'd rather pass them serialized data so I could see what they are doing and
force the server to get what I wanted to send it.
…On Wed, Feb 16, 2022 at 4:01 AM Mirjam Baltus ***@***.***> wrote:
If you use the Fhir[Json/Xml]Serializer, you can serialize your POCO's to
correct FHIR json/xml. This is how FHIR data is usually communicated
between two systems. If the receiving system cannot work with that, you
will have to implement extra code to align with their API, or you would
have to create an extra layer on the receiving end to convert the FHIR data
to the format it can work with.
—
Reply to this email directly, view it on GitHub
<#1962 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANJYAKE4VA54X5VFTEI7VZLU3OGY5ANCNFSM5NV7RZUQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
2 replies
-
It's encrypted on the way I presume so seeing it seems impossible and I
actually know what's in it anyway. It's the AWS Lambda service that is not
handling it properly and it's virtually impossible to modify that without a
fleet of programmers.
…On Wed, Feb 16, 2022 at 9:54 AM Mirjam Baltus ***@***.***> wrote:
The FhirClient does send out the serialized data by the way. So it should
be possible to inspect that on the HTTP call.
—
Reply to this email directly, view it on GitHub
<#1962 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANJYAKCUOG6RSYMKHOCIKFLU3PQELANCNFSM5NV7RZUQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Interesting. Their "open source" FHIR server is what they call a Lambda
function. A user can create a Lambda function their handle whatever
service function they want . The FHIR server is generated automatically
when you set up an account and it has some configuration parameters you can
set but nothing related to actual functionality. It is a node js program
that is very large. If you don't like what it does, you can change it
yourself if you can hire a fleet of programmers to do it. Tech support I
buy does not know anything about it and do not support it in any way.
Obviously they have someone who put it together who knows what they are
doing but they are more inaccessible than God. I may go back to Mongo DB
and deal with the problem that SDK classes are not FHIR compatible, same
problem that Cosmos DB seems to have, and find a way to store serialized
data.
…On Thu, Feb 17, 2022 at 7:04 AM Mirjam Baltus ***@***.***> wrote:
Sounds like AWS still has some work to do before they can call themselves
FHIR compliant. I know you've tried to reach out to their support, but
maybe you can file tickets on their github repos to try and get this
improved.
—
Reply to this email directly, view it on GitHub
<#1962 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANJYAKCLH72ENOXP7HEF6A3U3UE6PANCNFSM5NV7RZUQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
SDK capitalizes class properties in a C# appropriate way that is not FHIR standard. Going to a FHIR server through a client is not a problem but writing a resource class directly to Mongodb or the AWS FHIR api is. How do you get around that? Or is there a Python type FHIR library for C# from someone that does work?
Beta Was this translation helpful? Give feedback.
All reactions