The SimpleHealth Medical Records application allows us to retrieve the medical history for former SimpleHealth patients. After entering their email and date of birth, you'll be prompted to download a PDF which includes their basic patient info (name, address, telephone etc), prescription history, any insurance policies we have on file and their consultation questions and answers.
This application uses
React
Typescript
Tailwind
eslint
axios
Google Oauth
Node.js
Express
.
Note: User tokens are stored in Session Storage
and are verified on the local Node
server.
- Download or clone the repository
- Run
npm install
- Make sure you have a copy of the .env file. If not, you'll need to create one and fill in the following variables
REACT_APP_MEDICAL_RECORDS_API_CLIENT_ID
: client id for the medical records APIREACT_APP_MEDICAL_RECORDS_API_CLIENT_SECRET
: client secret for the medical records APIREACT_APP_GOOGLE_OAUTH_CLIENT_ID
: client id for Google OauthREACT_APP_GOOGLE_OAUTH_CLIENT_SECRET
: client id for Google Oauth
- Run
npm start
- In development, go to
localhost:3000/login
. You'll be prompted to login in using a gmail account. You must have a user account to access the application. In development, you can do this by simply adding your user account to the database connected to the Medical Records API. Once this application is deployed in production, another admin can add your email on the/users
page and that will create your user's account. - As long as the Medical Records API is running and the database is running (and hydrated), you should be able to search for SimpleHealth patient's medical records using their email and date of birth. If you are in development, the database has been seeded with one user: Alice Liddel. Her email is [email protected] and date of birth is
01/12/1992
.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000/login to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.