> For the complete documentation index, see [llms.txt](https://docs.nwrrp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nwrrp.com/fire-ems/medicbridge-user-guide.md).

# MedicBridge ALS User Guide

**Resource baseline:** `medic_bridge_als` v0.9.38-beta.1

MedicBridge supports BLS/ALS assessment, treatment, monitoring, ECG documentation, transport, and handoff for live players and ERS patient peds.

## Opening the monitor

1. Identify the correct patient.
2. Aim Third Eye (`R-ALT`) at the patient.
3. Select **Treat ERS Patient**.
4. Confirm the banner shows the expected BLS or ALS mode.

F4 and `/ersmedui` are disabled in the production configuration. Use `/ersmedbridge` only as a fallback.

## Care workflow

1. Confirm scene safety and patient identity.
2. Complete the primary assessment.
3. Obtain and monitor vitals.
4. Apply treatments appropriate to role, training, and SOP.
5. Reassess after major interventions.
6. Coordinate responding crews.
7. Decide transport priority and destination in roleplay.
8. Provide a clear handoff.

## ECG use

Consider a 12-lead for chest pain, shortness of breath, syncope, abnormal vitals, overdose complications, cardiac arrest, palpitations, or altered mental status with possible cardiac cause. Save a strip when it meaningfully supports documentation or training.

## Access and scope

Automatic role detection determines BLS/ALS access. Do not use advanced features outside your approved role. Treat ERS patients with the same roleplay quality as live players.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.nwrrp.com/fire-ems/medicbridge-user-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.