Vitals
See the nodeVISTA Demo posting to setup the nodeVISTA management client and CPRS.
A discussion on nodeVISTA emulation statistics can be found below in the Emulation Statistics section below.
Demo Procedures
Create a Vital
- From the CPRS patient chart, click on visit box, you will then be prompted with the visit context dialog. Choose Alexander,Robert as the provider and clinicD as the location and click ok.
- Then click on one of the entries in the vitals pane. This will bring up the vitals dialog. If no vital is present, click on ‘No data found’.
- Then click on the ‘Enter Vitals’ button at the top right-hand side of the dialog. This will bring up the vitals entry dialog.
After clicking on ‘Exp. View’, also on the top right-hand side of the top menu bar, a side menu appears. There, select ‘System’ Folder > ‘DEMO.NODEVISTA’ > Daily Vitals. At this point, you can enter values for blood pressure, temperature, and height.
-
You may also want to enter qualifiers, like cuff size and position for blood pressure.
Click on save and exit when you are done. You may be prompted with a dialog that says the vitals data differs by 10 percent, just click ok.
- The main vitals dialog now displays the entered data.
- Navigate to the nodeVISTA client and open the RPC Events tab. Notice the three GMV ADD VM RPC Event line items. Each RPC calls has its own transaction ID associated with the call.
- Clicking on one of the RPC Events will bring up a details modal. Observe the RPC request parameters. The response pane is empty per the RPC spec.
- Navigate to the MVDM Events tab. Observe the three MVDM create events that are associated, by transaction ID, with the GMV ADD VM RPC Events.
- Clicking on one of the MVDM create events will bring up a details modal.
Mark as Entered in Error
- In CPRS, bring up the vitals dialog and click the ‘Entered in Error’ button in the top right-hand side of the vitals dialog.
- This will bring up the ‘Entered in Error’ dialog. Select the height vital. The reason section will now be enabled. Select the ‘Incorrect Reading’ radio button then click the ‘Mark as Entered in Error’ button.
- Go over to the nodeVISTA client. Under RPC Events, observe the GMV MARK ERROR RPC Event line item.
- Clicking on the RPC event line item will bring up the details modal.
- Click on the MVDM Events. Observe the corresponding MVDM remove event, note that the transaction ID is the same as the corresponding RPC Event.
- Clicking on the MVDM remove event line item will bring up the details modal.
Emulation Statistics
Upon successful completion of the Vitals demo trail, the nodeVISTA system will have processed close to 240 individual RPCs from CPRS, using a combination of RPC emulations and pass-through native RPC implementations.The table below contains a breakdown of nodeVISTA’s RPC emulation capabilities as a series of percentages against native and overall RPC processing as of v1.3 (8/2/2017):
All RPCs | Unique RPCs |
---|---|
Total RPCs: 240Total RPCs By Category Server: 1 (0.42%) Native: 47 (19.58%) Emulated: 192 (80.00%) Total RPCs By Sub-Category UNKNOWN: 2 Server: 1 (50.00%) Native: 1 (50.00%) AUTHENTICATION: 11 Native: 10 (90.91%) Emulated: 1 (9.09%) NON CLINICAL: 171 Emulated: 166 (97.08%) Native: 5 (2.92%) OUT OF SCOPE: 5 Emulated: 5 (100.00%) CLINICAL: 51 Native: 31 (60.78%) Emulated: 20 (39.22%) |
Total Unique RPCs: 93Total Unique RPCs By Category Server: 1 (1.08%) Native: 28 (30.11%) Emulated: 64 (68.82%) Total Unique RPCs By Sub-Category UNKNOWN: 2 Server: 1 (50.00%) Native: 1 (50.00%) AUTHENTICATION: 5 Native: 4 (80.00%) Emulated: 1 (20.00%) NON CLINICAL: 49 Emulated: 45 (91.84%) Native: 4 (8.16%) OUT OF SCOPE: 5 Emulated: 5 (100.00%) CLINICAL: 32 Native: 19 (59.38%) Emulated: 13 (40.63%) |