Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Home

Jump to bottom
mcconville edited this page Mar 29, 2019 · 1 revision

Short title

Summit Health Patient Records

Long title

Build a Node.JS analytics web application that connects to a zOS Mainframe.

Author

URLs

Github repo

Other URLs

Summary

Summit Health is a conceptual healthcare/insurance type company. This part of Summit Health is a conceptual Node.JS analytics web application for a health records system, designed to showcase best in class integration of modern cloud technology, in collaboration with legacy mainframe code.

Technologies

  • Data Visualization
  • API Management
  • Cloud Foundry
  • JavaScript
  • Node.js
  • HTML5 Canvas

Description

Summit Health is a conceptual healthcare/insurance type company. It has been around a long time, and has 100s of thousands of patient records in a SQL database connected to a zOS mainframe. Summit's health records look very similar to the health records of most insurance companies.

Summit has recently started understanding that their patients are increasingly data and design literate. They're used to using fast, modern looking apps on their phones, and tablets. Summit has to compete not just on integrity of data, but ease and style of access. Summit has also heard a lot about cloud computing, as the key to being nimble and creative.

This project is a conceptual Node.JS web application for a health records system, designed to showcase best in class integration of modern cloud technology, in collaboration with legacy mainframe code.

Flow

  1. Data Service API acts as a data pipeline and is triggered for updating data lake with updated health records data by calling API Connect APIs associated with the zOS Mainframe.
  2. API Connect APIs process relevant health records data from zOS Mainframe data warehouse and send the data through the data pipeline.
  3. The Data Service data pipeline processes zOS Mainframe data warehouse data and updates MongoDB data lake.
  4. User interacts with the UI to view and analyze analytics.
  5. The functionality of the App UI that the User interacts with is handled by Node.JS. Node.JS is where the API calls are initialized.
  6. The API calls are processed in the Node.JS data service on Kubernetes and are handled accordingly.
  7. The data is gathered from the MongoDB data lake from API calls.
  8. The responses from the API calls are handled accordingly by the App UI.

Instructions

Find the detailed steps for this pattern in the readme file. The steps will show you how to:

  1. Clone the repo
  2. Get Mapbox Access Token
  3. Run the application
  4. Deploy to IBM Cloud

Components and services

  • Docker

  • IBM Cloud

  • Kubernetes

  • Node Package Manager

  • Synthea

  • Mapbox

  • FCC

  • Kubernetes Service

Runtimes

  • javascript/node

Related IBM Developer content

List any IBM Developer resources that are closely related to this pattern, such as other patterns, blog posts, tutorials, etc..

Related links

Provide any non-IBM Developer resources that you need to link to that are NOT components or services

Announcement

Every pattern must have an announcement post that introduces it. The announcement should explain why the pattern is important or useful. The announcement is an invitation to try the pattern; you can expand on why you created the pattern, discuss any challenges that you overcame, or expand on the technologies that you're using.

Announcements should be at least 2-3 paragraphs

Clone this wiki locally