NeoPORT
  • Introduction
  • How it works
  • Screenshots
  • Platforms and roles
  • The future: CritiPORT
  • Install NeoPORT
Powered by GitBook
On this page
  • Left screen: Sender UI
  • Right screen: Transporter UI

Was this helpful?

Screenshots

PreviousHow it worksNextPlatforms and roles

Last updated 8 months ago

Was this helpful?

Left screen: Sender UI

This screenshot is that of a Sender's app, after their request has been accepted by a Receiver. The app converts form responses into a clinical summary β€” an identical view is presented to the Receiver.

Images and free-text notes, if any, can be seen on a secondary page.

The screen highlights primary action pending for the Sender β€” that of assigning a Transporter.

Right screen: Transporter UI

This is what the Transporter sees when en route to the Receiver. Some of the highlights of this screen are:

  1. Vitals dashboard, with overdue vitals highlighted. For example, the screen shows that temperature was recorded 53 minutes ago, and is overdue. The frequency with which vitals have to be recorded are defined by the Sender. Their choices are β€” "monitor half-hourly", "monitor hourly", or "do not monitor".

Top navigation bar with a message icon that leads to a 3-way chat interface between Sender, Receiver and Transporter.

One tap access to navigation directions on Google maps.

Speed dial option to call the Receiver in case of an emergency.

πŸ’¬
πŸ—ΊοΈ
❗
NeoPORT screenshots with synthetic data