Clinical Viewer for SMART Apps

HealthShare, FHIR

The product I'm using is HealthConnect ( this installation HSAP-2017.1.1.111.0.17521-hscore15.03-b8382-win_x64.exe). Do I have access to the Information Exchange Clinical Viewer ? Is there a way to install this and connect it up to my HealthShare FHIR repository?

  • 0
  • 0
  • 461
  • 4
  • 1

Answers

Ideally the responses by Jenny Ames and [@Matthew Spielman] would have been posted in the "Your Answer" area of DC rather that using the "Add new comment" link. That way  the OP, [@Conor Browne], could accept one of the answers by clicking on the grey checkmark at the top of the answer to turn it green. Doing this helps with DC housekeeping by removing the question from the "unanswered" list.

If Jenny and/or Matthew were to re-post their responses using the "Your Answer" field then Conor will be able to credit one of them with answering his question. Even them posting "See my answer in comments above" would be sufficient to give Conor somewhere to set a checkmark.

Alternatively Conor could either accept my answer (though it's not actually answering his question), or he could post an answer of his own, then accept it.

Comments

Hi Conor,

The Clinical Viewer is only available if you have Information Exchange (Information Exchange includes Health Connect but if you have Health Connect, you don't necessary have Information Exchange). You can, however, still use the HealthShare FHIR respository to store FHIR resources, and then use REST calls to retrieve each resource. What exactly are you trying to do?

If you would like Information Exchange and the Clinical Viewer, I recommend reaching out to your Sales Engineer or Sales Rep.

Ok thanks for the info. Just seeing what possibilities are out there right now. Was looking at installing SMART apps ( with OAuth2) to view content inside the FHIR repository I configured.

Doing the following: do ##class(HS.Util.Installer.FHIRServices).OAuthServer()

Threw the following error: "Information Exchange Registry namespace not found in this instance.
OAuth Server must be in the same instance as the Registry."

Hi Conor,

The FHIR Gateway as well as the associated setup methods including OAuthServer() are Information Exchange features and not available in Health Connect. The FHIR Repository which is a Health Connect component can be used as a building block to create your own FHIR based solutions but it requires some assembly, including the authentication components. If you need some help on working with the OAuth capabilities of Caché/Health Connect, please refer to the documentation and contact your Sales Engineer or WRC for assistance. 

 

Regards,
Matt Spielman
Product Manager, Information Exchange