Orion Health Amadeus Platform<\/a>, so we need to have a Portal login. Our user account also needs to have permissions to access the clinical data we need (we\u2019ll talk about this in the third post in this series).<\/p>\n\n\n\nOnce we\u2019ve logged in, the app will retrieve the worklists that have been defined for the logged in user. These worklists are lists of individuals\/patients that can be maintained by the user. The lists are displayed in the app.<\/p>\n\n\n\n
We select a worklist, and the app then displays all the patients in that worklist. We can select any patient, and the app will retrieve the data from the platform (via the API) and calculate the Cardiovascular Disease (CVD) risk. Both risk and the data used to calculate the risk are displayed on the screen. (Please don\u2019t rely on these figures from this app \u2013 this is a demonstration only!) Here\u2019s a screen shot:<\/p>\n\n\n\nWe can then save the assessment back to the platform using the green \u2018Save Risk Assessment\u2019 button, after which it can be viewed in Portal \u2013 or retrieved from the API again. In fact, we display the previous assessments on the screen over on the right hand side of the app.<\/p>\n\n\n\n
Here\u2019s a screen shot of the assessment being viewed from portal:<\/p>\n\n\n\nAnd because this is a demo app, we\u2019ve also provided the ability to generate random test data (using the red button).<\/p>\n\n\n\n
And that\u2019s really all the app is! There\u2019s a lot more we could do \u2013 for example we could allow the user to modify the data on screen and re-generate the risk to show someone how they could reduce their risk, or display a chart showing the risk changing over time, but this is only a demo after all!<\/p>\n\n\n\n
It\u2019s a Single-Page Application (SPA) using Angular on the client, communication with a Node.js application on the server. The node app makes the actual API calls to the platform (via the API Manager) and returns the results to the client. It also has the assessment algorithm. This approach was taken to avoid any Cross Origin Resource sharing (CORS) issues that can occur when the call is made directly from the browser to the server.<\/p>\n\n\n\n
In the next week\u2019s blog, we\u2019ll dig into the API in more detail.<\/p>\n\n\n\n
To learn more about FHIR for Clinicians download the white paper now.<\/p>\n\n\n\n
![\"\"](\"https:\/\/orionhealth.weareiceberg.co\/wp-content\/uploads\/2019\/05\/framingham.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/orionhealth.weareiceberg.co\/wp-content\/uploads\/2019\/05\/screen-shot-2017-10-10-at-103242-am-1440x619.png\")
<\/figure>\n\n\n\n![\"\"](\"https:\/\/orionhealth.weareiceberg.co\/wp-content\/uploads\/2019\/05\/screen-shot-2017-10-10-at-104620-am-1440x794.png\")
<\/figure>\n\n\n\n