New post

#FHIR

26

Fast Healthcare Interoperability Resources (FHIR, pronounced "fire") is a draft standard describing data formats and elements (known as "resources") and an application programming interface (API) for exchanging electronic health records

Official site

I have been successfully able to transform hand-written medical test results documents to HL7 ORU_R01 v2.x, then to SDA, which will be trasformed to FHIR or C-CDA.

However, I have a category of documents which contains reference range in multiple date formats, which are measured for each gestation period.
For example, below is one of the documents.

Analyte: HCG, Value: 1968, Unit: mlU/mL

0 4
0 179
Question
· Jul 6, 2023
REST Documentation Confusion

I had attempted to create a REST Operation before but did not have success. As I am going through the Tutorials and Documentation everything references REST services, but I have a case where I want to create a REST Operation that makes Epic API calls against Interconnect. I have done SOAP operations before and we currently have one in our Production Namespace, but from what I understand SOAP has the wsdl which defines al the structures and etc, where REST does not.

0 1
1 204

Hi Community,

I would like to know how I can query a list of patients that were revoked on HealthShare for the month of April and May.

Messages are sent using FHIR and a revoke is handled with active:false as seen below. A non-revocation will have active: true on the patient resource.

I wanted to check SQL tables but I am not sure which one to check if so. Please advise on how to go about getting this report.

Regards,

0 0
0 120

Hi all,

I am looking for a way to serialize fhir content received via interoperability adapter into it´s corresponding ISC model class (e.g. HS.FHIR.DTL.vR4.Model.Resource.DiagnosticReport) for later use. In my opinion the outline to accomplish this would be something like

1) Receive the FHIR data
2) Get quick stream containing the JSON data
3) Examine if bundle or single ressource
4) For resource serialize to coressponding model class (HS.FHIR.DTL.vR4.Model.Resource.*)
5) further use of newly created object of type HS.FHIR.DTL.vR4.Model.Resource.*

0 3
0 209