ah well, in our case IRIS is acting as an ESB. Data doesn't live in IRIS. We are calling out to other systems to get the data e.g. Patient Administration System or Health Provider Directory.  In this case the other systems may or may not support APIs in which case we would query them using ODBC Adaptor, transform data to FHIR compliant json schema in IRIS and return to the client.

Hi Dmitry,

Thank you for reply :)

>>>Speaking about HealthCare application, why would you even decide to implement some own way, when FHIR already covers most of the things you would need?

Would you mind elaborating on this last statement please? I am not sure what you mean. 

We are writing specifications for our API following the FHIR standard. 

Utsavi

Hi Eduard,

Firstly, thank you for sharing this article. Great information !

I am trying to work out best way of Error Handling within a REST Business Operation and Business Process. My Business Operation makes a call to the third party API to do certain things. I need to return the response I get back from the third party to the clinet.  Possible repsonses are, 

- 200 in which case I return requested data e.g. Patient demographics 

- 404 Patient not found 

- 500 - Internal Server Error

This is what my Business Operation currently looks like,

 
Code

Now, when the BO gets any sort of error, the operation shows an error and so does the process and same error goes back to the clinet e.g. in event of 503 client sees,

 
JSON

I need to catch this exception and modify the json response that goes back to the client.  But I am not sure what is the best way to do that. Is it something that is best done in BO or BP ? 
 

Any help or guidance on this will be much appreciated!

Utsavi

Hi Eduard,

I am looking for some examples of REST API served through production. Would you be able to point me to some, please? 

I am trying to implement a business service,  process and operation that serves bundle of apis related to a domain and resource e.g Patient , Patient alerts, patient status . These will be 3 api urls served by single business service,  process and operation.  

I am also looking for best practice to handle various http responses in BP and BO.

Would greatly appreciate if you can direct me to relevant examples. 

Thank you,

Utsavi

Thanks Vitaly Furman

We enabled logging on receiving PACS and figured out that Ensemble was sending same ID for 2 different SOP classes. I had been using the "CreateAssociation" command with third argument as blank to create associations.  When doing so , Ensemble adds all Abstract Syntaxes it knows about with default TransferSyntax of Implicit VR. I believe the receiving PACS didn't cater for one of the Abstract Syntax. 

To solve the problem, I removed the association. Created it using GUI so no default Presentation COntext is added. I then manually added a few Abstract Syntax with Basic Transfer syntax of Implicit VR and retested and this time the communication worked.

I then created an Import file for the PACS based on Conformation Statement provided by PACS and imported in Ensmeble using the ImportAssociation command.

Regards,

Utsavi