# How it works

<figure><img src="/files/jp6DIej6YFOffhshiSGl" alt=""><figcaption><p>NeoPORT Workflow</p></figcaption></figure>

Once a Sender creates a transport request, they assign it to a Receiver, and then a Transporter — either of whom can accept or decline the request. Once all parties accept, the transport starts.

The Sender can track the inbound movement of the Transporter to their location. Once the Sender hands over the infant to the Transporter, they can see the outbound trip to the Receiver. This data is also visible to the Receiver. When outbound, the Transporter has to measure infant vitals — based on rules set up by the Sender. If the Transporter misses a measurement, they receive an alert.&#x20;

The Transporter’s location is tracked and used to notify the Sender and the Receiver. All three participants also have access to a group chat.&#x20;

Once the transporter arrives at the Receiver’s location, they handover the infant. The Receiver then closes the transport episode by entering infant vitals into the system. Based on these vitals, the system calculates a Ca-TRIPS score, a clinically-validated scoring system of infant transport quality. The difference in scores between the start and end of the transport provides a measure of transport quality. NeoPORT has been used to generate scientific literature about transport quality and its impact on clinical outcomes.

The entire system is managed by a System Administrator, who managers the network of users.


---

# 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/how-it-works.md?ask=<question>
```

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.
