(Note: (Numbers)
correspond to the numbers in the diagram above)
-
mcode/rems-admin
- REMS Administrator
(4)
- Node/TypeScript
(1.1)(3)
CDS Hooks (server) end points(1.4)
FHIR Server to support REMS SMART on FHIR App- Contains Questionnaire, Library (w/ CQL), ValueSets
- Retrieves and caches ValueSets from VSAC
(5)
Interface to check status of REMS- Stores data in MongoDB
- Docker scripts to launch the entire stack
- REMS Administrator
-
mcode/test-ehr
- Test EHR
(2)
- Java HAPI FHIR Server
- Contains test patient data
- Supports launching REMS SMART on FHIR app
- Test EHR
-
mcode/request-generator
- Request Generator
(2)
- Node/JavaScript
- Web Application mimicking the EHR frontend
- Requests
(1.1)(3)
Generates CDS Hooks order-sign (client) that is sent to the REMS Admin(1.2)(3)
Handles CARDS returned from REMS Admin to launch REMS SMART on FHIR App- Sends Rx to PIMS using NCPDP Script NewRx
- Communicates with REMS Admin and EHR to retrieve ETASU and prescription status
- Patient Portal allowing patient access to in-progress forms and information about their prescriptions
- Manages Tasks for deferring and relaunching in-progress forms
- Request Generator
-
mcode/pims
- Pharmacy Information System
(6)
- Node/TypeScript
- Receives Rx from Request Generator
(5)
Provides interface to monitor status of REMS- Allows pharmacist to mark Rx as dispensed
- Provides interface for querying status of Rx
- Non-standard, created for demo purposes only
- Stores data in MongoDB
- Pharmacy Information System
-
mcode/rems-smart-on-fhir
- REMS SMART on FHIR Application
- SMART on FHIR application to generate CDS Hooks interaction with REMS Admin for any EHR that does not support CDS Hooks
- Node/TypeScript
- Displays Questionnaire forms and allows filling them out
- SMART on FHIR application to generate CDS Hooks interaction with REMS Admin for any EHR that does not support CDS Hooks
- REMS SMART on FHIR Application
-
mcode/rems-cds-hooks
- Git submodule used by REMS SMART on FHIR Application and REMS Admin
- TypeScript
- Prefetch implementation
- Type definitions for CDS Hooks needed by TypeScript
- Git submodule used by REMS SMART on FHIR Application and REMS Admin
-
mcode/rems-intermediary
- REMS Intermediary
alternate (4)
- Node/TypeScript
aternate (1.1)(3)
CDS Hooks (server) end points- Forwards request to REMS Admin
aternate (5)
Interface to check status of REMS- Forwards request to REMS Admin
- Stores data in MongoDB
- Docker scripts to launch the entire stack
- REMS Intermediary
-
KeyCloak
- Authentication of users
- Docker config hosted in mcode/test-ehr
-
MongoDB
- Stores data for REMS Admin and PIMS in separate databases
- Docker config hosted and stored in mcode/rems-setup