### 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. Top navigation bar with a :speech\_balloon: message icon that leads to a 3-way chat interface between Sender, Receiver and Transporter.
2. One tap access to :map: navigation directions on Google maps.
3. Speed dial option to call the Receiver in case of an :exclamation:emergency.
4. 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".
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://www.neoport.org/screenshots.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.