You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TestEnvironmentUsage.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,19 +18,19 @@ After registering an app, we get a client id, which is the client id of the SMAR
18
18
The SMART app must be made aware of the client id in order to launch correctly. In the case of the REMS SMART app, registration is handled at the time of launch if the app doesn’t already know which client id to use, which should make the process seamless.
19
19
20
20
When launching an app, you are connecting it to Meld’s EHR system.
21
-
The data can be uploaded manually using the data manager as described in the [Test Environment Usage Document](TestEnvironmentSetup.md). Our default patient, Jon Snow, and all of his related resources should be loaded
21
+
The data can be uploaded manually using the data manager as described in the [Test Environment Usage Document](TestEnvironmentSetup.md). Our default patient, John Snow, and all of his related resources should be loaded
22
22
23
23
24
24
25
-
For most purposes, Jon Snow will work just fine as our default patient.
25
+
For most purposes, John Snow will work just fine as our default patient.
26
26
27
27
28
28
29
-
When launching any app, Meld will ask you to select a persona. Jon Snow’s resources all reference Rita Abrams, so ideally pick her as the practitioner when launching the REMS SMART app or request generator.
29
+
When launching any app, Meld will ask you to select a persona. John Snow’s resources all reference Rita Abrams, so ideally pick her as the practitioner when launching the REMS SMART app or request generator.
After selecting a practitioner, you can select a patient. Selecting Jon Snow will properly allow the REMS SMART on FHIR app to function. If you are launching the Request Generator, you can launch without a patient.
33
+
After selecting a practitioner, you can select a patient. Selecting John Snow will properly allow the REMS SMART on FHIR app to function. If you are launching the Request Generator, you can launch without a patient.
Copy file name to clipboardExpand all lines: Verify-REMS-Integration-Prototype-Works.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,9 @@
3
3
1. Access the EHR gateway at <http://localhost:3000>. Click Launch with the default FHIR Server Endpoint, Client ID, and Scope values.
4
4
2. You'll be redirected to <http://localhost:8180>. Authenticate with `alice` as the username and password. You'll then be redirected back to the EHR UI at <http://localhost:3000> to play the role of a prescriber.
5
5
3. Click **Select a Patient** in the middle of the page.
6
-
4. Locate **Jon Snow** in the list of patients and click the "Select a medication request" dropdown.
6
+
4. Locate **John Snow** in the list of patients and click the "Select a medication request" dropdown.
6. Click **Select** to assign Jon Snow as the medication request recipient.
8
+
6. Click **Select** to assign John Snow as the medication request recipient.
9
9
7. Click **Send Rx to Pharmacy** to dispatch the prescription.
10
10
8. Click **Sign Order**, which demonstrates the case where an EHR has CDS Hooks natively.
11
11
9. Await the arrival of two **CDS cards**.
@@ -14,17 +14,17 @@
14
14
12. Complete and submit the questionnaire via **Submit REMS Bundle**.
15
15
- 12a. For demonstrating an asynchronous workflow, partially complete the questionnaire and click **Save to EHR**.
16
16
- 12b. Visit the Patient Portal at <http://localhost:3000/#/patient-portal> as the patient.
17
-
- 12c. Login with **JonSnow** as the username and **jon** for the password.
17
+
- 12c. Login with **johnsnow** as the username and **john** for the password.
18
18
- 12d. Select the saved Questionnaire, complete it, and click **Save to EHR**.
19
19
- 12e. Return to the EHR UI at <http://localhost:3000>, select the latest saved questionnaire from the second
20
-
dropdown next to Jon Snow's name, and continue as the prescriber.
20
+
dropdown next to John Snow's name, and continue as the prescriber.
21
21
- 12f. Click **Launch SMART on FHIR App** and fill out the remainder of the questionnaire, including the prescriber signature, then click **Submit REMS Bundle**.
22
22
13. A new UI will appear with REMS Admin Status and Medication Status.
23
23
14. Visit the Pharmacy Information Management System at <http://localhost:5050> to play the role of a pharmacist.
24
24
15. Click **Doctor Orders** in the top navigation.
25
25
16. View the Doctor Order that was sent to the pharmacist from the prescriber and use the **Verify ETASU** button to get
26
26
a status update of the REMS requirements submitted.
27
-
17. Return to the EHR UI at <http://localhost:3000> and play the role of the prescriber again. Select patient Jon Snow
27
+
17. Return to the EHR UI at <http://localhost:3000> and play the role of the prescriber again. Select patient John Snow
28
28
from the patient select UI and click **Launch SMART on FHIR App**, which will open the SMART on FHIR App in its own
29
29
view and demonstrate the case where an EHR does not have CDS Hooks implemented natively.
30
30
18. From the medications dropdown select **Turalio 200 MG Oral Capsule**, which should populate the screen with cards
0 commit comments