diff --git a/docs/loop-3/dana.md b/docs/loop-3/dana.md
new file mode 100644
index 00000000000..31b36d99a6c
--- /dev/null
+++ b/docs/loop-3/dana.md
@@ -0,0 +1,30 @@
+!!! warning "🚧 Documentation Under Construction 🚧"
+
+ This page is under development.
+
+ The addition of the Dana-i and DanaRS-v3 pump to iOS Open-Source Automated Insulin Delivery systems is new.
+
+ Please review the [DanaKit Issues](https://github.com/bastiaanv/DanaKit/issues) page for open issues reported for the DanaKit Pump Manager.
+
+
+!!! important
+ This Issue is very important:
+
+ * [When Bluetooth communication is interrupted during a bolus, cannot cancel, bolus finalized while in progress](https://github.com/bastiaanv/DanaKit/issues/34)
+ * This issue prevents you from cancelling a bolus from inside the OS-AID app if Bluetooth communication with the pump is lost during a bolus
+
+
+### Testing Dana with the *Loop* App
+
+* The branch needed to get Dana in *Loop* is: `feat/dev-dana-medtrum`
+ * This branch is subject to rapid updates
+ * If you also want to use the Eversense CGM, the `feat/eversense` branch provides support for Dana and Medtrum along with the Eversense CGM
+
+* Please refer to the [zulipchat Loop-dev development channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop-dev.20Status/with/515372445) before building this branch.
+
+
+
+Most of the information needed for the Dana pump can be found here:
+
+* [How to add a Dana Pump](add-pump.md#dana-i-danars-v3){: target="_blank" }
+* [Dana Troubleshooting](../troubleshooting/dana-faq.md){: target="_blank" }
diff --git a/docs/loop-3/eversense.md b/docs/loop-3/eversense.md
new file mode 100644
index 00000000000..ee33afdf7dd
--- /dev/null
+++ b/docs/loop-3/eversense.md
@@ -0,0 +1,45 @@
+!!! warning "🚧 Documentation Under Construction 🚧"
+
+ This page is under development.
+
+ The addition of the Eversense CGM to iOS Open-Source Automated Insulin Delivery systems is new.
+
+ Please review the [EversenseKit Issues](https://github.com/bastiaanv/EversenseKit/issues) page for open issues reported for the EversenseKit CGM Manager.
+
+## Testing Eversense with the *Loop* App
+
+* The branch needed to get Eversense in *Loop* is: `feat/eversense`
+ * This branch is subject to rapid updates
+ * This branch provides support for Dana and Medtrum along with the Eversense CGM
+
+* Please refer to the [zulipchat Loop-dev development channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop-dev.20Status/with/515372445) before building this branch.
+
+## Eversense 365 Screen
+
+The user interface for the 365 sensor is shown below.
+
+{width="300"}
+{align="center"}
+
+## Calibration and Battery Indicators
+
+* Once stabilized, the Eversense Transmitter requires weekly calibrations
+ * The Eversense will stop reporting glucose readings if the required calibration is more than 24 hours late
+* The Eversense Transmitter requires charging every 2 to 3 days
+
+The calibration status and battery level is highlighted at the top of the Eversense screen.
+
+
+{width="600"}
+{align="center"}
+
+* The left screenshot shows an orange line indicating a calibration is due in less than 24 hours
+* The right screenshot is after calibration
+
+## *Loop* Main Screen
+
+When calibration required is within 24 hours, the orange line is echoed on the top of the *Loop* main screen under the CGM icon to serve as a reminder to calibrate soon.
+
+Once the calibration is due, there is a 24-hour grace period before transmitter stops reporting glucose values. During that time, the "Next calibration in" line is red. This red line is also echoed on the top of the *Loop* main screen under the CGM icon.
+
+As usual for calibrating a CGM, choose a time when glucose is stable to measure glucose with a finger-stick and enter the value into the user interface. The calibration takes 15 minutes to process.
\ No newline at end of file
diff --git a/docs/loop-3/img/eversense-calibration-required.png b/docs/loop-3/img/eversense-calibration-required.png
new file mode 100644
index 00000000000..a948e1f8e50
Binary files /dev/null and b/docs/loop-3/img/eversense-calibration-required.png differ
diff --git a/docs/loop-3/img/eversense-user-interface.svg b/docs/loop-3/img/eversense-user-interface.svg
new file mode 100644
index 00000000000..9200fb6434a
--- /dev/null
+++ b/docs/loop-3/img/eversense-user-interface.svg
@@ -0,0 +1,116 @@
+
+
+
+
diff --git a/docs/loop-3/img/medtrum-connected.svg b/docs/loop-3/img/medtrum-connected.svg
new file mode 100644
index 00000000000..e29ca3fedf7
--- /dev/null
+++ b/docs/loop-3/img/medtrum-connected.svg
@@ -0,0 +1,338 @@
+
+
diff --git a/docs/loop-3/img/medtrum-device-details.svg b/docs/loop-3/img/medtrum-device-details.svg
new file mode 100644
index 00000000000..ec432052f98
--- /dev/null
+++ b/docs/loop-3/img/medtrum-device-details.svg
@@ -0,0 +1,15384 @@
+
+
diff --git a/docs/loop-3/img/medtrum-disconnected.svg b/docs/loop-3/img/medtrum-disconnected.svg
new file mode 100644
index 00000000000..8bffc817d00
--- /dev/null
+++ b/docs/loop-3/img/medtrum-disconnected.svg
@@ -0,0 +1,311 @@
+
+
diff --git a/docs/loop-3/img/medtrum-extended.svg b/docs/loop-3/img/medtrum-extended.svg
new file mode 100644
index 00000000000..460875f490a
--- /dev/null
+++ b/docs/loop-3/img/medtrum-extended.svg
@@ -0,0 +1,262 @@
+
+
diff --git a/docs/loop-3/img/medtrum-screen.svg b/docs/loop-3/img/medtrum-screen.svg
new file mode 100644
index 00000000000..c7d88d57a3d
--- /dev/null
+++ b/docs/loop-3/img/medtrum-screen.svg
@@ -0,0 +1,330 @@
+
+
diff --git a/docs/loop-3/img/patch-activation-flow.svg b/docs/loop-3/img/patch-activation-flow.svg
new file mode 100644
index 00000000000..2b8ad36e083
--- /dev/null
+++ b/docs/loop-3/img/patch-activation-flow.svg
@@ -0,0 +1,303 @@
+
+
diff --git a/docs/loop-3/img/patch-status-details.svg b/docs/loop-3/img/patch-status-details.svg
new file mode 100644
index 00000000000..b34fbd00237
--- /dev/null
+++ b/docs/loop-3/img/patch-status-details.svg
@@ -0,0 +1,322 @@
+
+
diff --git a/docs/loop-3/medtrum.md b/docs/loop-3/medtrum.md
new file mode 100644
index 00000000000..42773ccfadf
--- /dev/null
+++ b/docs/loop-3/medtrum.md
@@ -0,0 +1,344 @@
+!!! warning "🚧 Documentation Under Construction 🚧"
+
+ This page is under development.
+
+ The addition of the Medtrum Nano pump to iOS Open-Source Automated Insulin Delivery systems is new.
+
+ Please review the [MedtrumKit Issues](https://github.com/jbr7rr/MedtrumKit/issues) page for open issues reported for the MedtrumKit Pump Manager. In a few cases, the documentation on this page may anticipate some of the fixes planned for those minor issues.
+
+## Medtrum Nano Pump
+
+The Medtrum Nano Pump is supported using the *Loop* app built with a feature branch. See [Feature Branches](../version/development.md#how-to-build-feature-branches){: target="_blank" } for building instructions.
+
+* The pump patch is designed to be changed every 3 days
+* The pump base is reusable - do not accidentally discard the base after removing the patch
+* Versions 200U (MD0201 & MD8201) and 300U (MD8301) are supported
+
+### Testing Medtrum with the *Loop* App
+
+* The branch needed to get Medtrum in *Loop* is: `feat/dev-dana-medtrum`
+ * This branch is subject to rapid updates
+ * If you also want to use the Eversense CGM, the `feat/eversense` branch provides support for Dana and Medtrum along with the Eversense CGM
+
+* Please refer to the [zulipchat Loop-dev development channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Loop-dev.20Status/with/515372445) before building this branch.
+
+- - -
+
+## Medtrum Nano Screen
+
+The Medtrum Nano screen, shown in the graphic below, displays the patch status along with various options for adjusting settings.
+
+{width="300"}
+{align="center"}
+
+### Patch Life
+
+There is an 8-hour grace period following expiration.
+
+* Normal Life
+ * Patch expires at 72 hours
+ * Patch stops delivery at 80 hours
+
+!!! important ""
+ The patch can be operated with the [Extended Lifetime Setting](#extended-lifetime-setting), but this is not recommended.
+
+### Patch Summary
+
+There is a summary of the patch status at the top of the screen.
+
+* Just below the graphic of a Nano pump is an "Expires in:" line showing a graphical representaion of how long the patch has been operating and includes a text string reporting duration until expiration
+ * The solid bar is proportional to patch hours from activation through expiration
+ * It is blue for at least the first 48 hours
+ * The line turns orange to warn the patch is within 24 hours of expiration
+ * When the patch expires, the line turns red and the text indicates how much time until No Delivery
+ * The warning orange and red lifecycle lines also appear in the [HUD Pump Status](displays-v3.md#pump-status-icon){: target="_blank" } icon at the top of the *Loop* main screen
+* The left side of the next row reports the current (absolute) basal rate
+* The right side of the next row reports the reservoir level
+
+### Patch Alerts
+
+If [Patch Errors and Alerts](#patch-error-messages) occur, they will show up just below the Patch Summary.
+
+## Actions
+
+### Suspend Delivery
+
+Tapping on `Suspend Delivery` halts all insulin delivery from the patch for a duration of 2 hours. You can resume insulin delivery before that by tapping on resume delivery.
+
+* The user is alerted that pump is suspended by an icon on the OS-AID main screen header.
+* The patch itself might vibrate or beep every 15 minutes
+
+{width="150"}
+{align="center"}
+
+* For the *Loop* app, the [HUD Status Row](displays-v3.md#hud-status-row){: target="_blank" } message can be tapped to resume delivery.
+
+{width="300"}
+{align="center"}
+
+#### No Manual Bolus While Patch is Suspended
+
+If you request a manual bolus with *Loop* while a patch is suspended, *Loop* will send a notification that Bolus Failed with instructions that Pump is Suspended, Resume Delivery. In other words, you must resume delivery before you will be allowed to bolus with pods.
+
+### Stop Temp Basal
+
+If a temporary basal rate is currently active, the Stop Temp Basal button is provided to immediately cancel that temporary basal and restore scheduled basal delivery.
+
+The graphic below shows a nominal display with scheduled basal running on the left and temporary basal running on the right.
+
+{width="600"}
+{align="center"}
+
+### Sync Patch Data
+
+If the last sync was in the far past, you can force an immediate sync by tapping on Sync patch data.
+
+!!! info "Items Updated by Sync"
+ * Patch state (active, reservoir empty, fault, etc)
+ * Patch datetime
+ * Reservoir levels
+ * Bolus/basal state
+ * Patch battery voltage
+ * Patch starttime
+
+
+### Disconnect or Reconnect
+
+The Nano pump is normally always connected to the phone with Bluetooth. The action button will show Disconnect and the Status will report Connected with a green dot. (See [Stop Temp Basal](#stop-temp-basal) for example screenshots.)
+
+If you wanted to disconnect Bluetooth, tap on Disconnect and the display modifies as shown below. The action button will show Reconnect and the Status will report Disconnected with a red dot.
+
+{width="400"}
+{align="center"}
+
+If the phone and pump are within Bluetooth range, the app will reconnect them almost immediately.
+
+When the phone and pump are separated, the app will report Bluetooth is disconnected. It should reconnect promptly when the phone and pump are within range again. The Reconnect row allows you to hurry the process if desired.
+
+### Deactivate Patch
+
+The Deactivate Patch should only be tapped when you are ready to halt insulin permanently and remove the patch. Once you select this row, you are asked if you want to deactivate and then you must provide authentication to do so.
+
+Once the patch is deactivated, use the Medtrum-provided tool to retract the needle before removing the patch. Remove the patch and then promptly remove the pump base (brain) from the patch and put it in a safe place. The easiest way to remove the base is to turn the patch upside down and gently press on the plastic tab to release the base.
+
+### Patch State
+
+The Patch State refers to the patch itself, whereas [Status](#status) refers to the Bluetooth status.
+
+The icon shown in the *Loop* main screen may not be as specific as the string in the Patch State row. So if you see Patch Error with the stop sign on the main screen, tap on the icon to determine the exact issue.
+
+* **Active** (normal operation)
+* **Fault**
+* **Occlusion**
+* **Battery Empty**
+* **Suspended** (usually a manual action)
+* **Suspended - Hourly max** (insulin delivered in the last hour exceeds patch setting)
+* **Suspended - Daily max** (insulin delivered since midnight exceeds patch setting)
+* **Expired**
+
+The Suspended states can be updated by resuming, or modifying the hourly or daily maximum values in [Patch Settings](#patch-settings) and then clearing the alert.
+
+
+### Status
+
+The Status row reports the Bluetooth status:
+
+* **Connected** (normal configuration)
+* **Disconnected** (out of Bluetooth range)
+* **Reconnecting...** (after tap on Reconnect)
+
+- - -
+
+## Configuration
+
+The configuration section displays:
+
+* [**Insulin Type**](#insulin-type) shows the Insulin Brand selected; be sure to modify this between patches if you change your insulin
+* [**Patch Settings**](#patch-settings) tap on this row to modify settings for the patch
+
+
+### Insulin Type
+
+You selected [Insulin Type](add-pump.md#insulin-type){: target="_blank"} when connecting to this pump.
+
+Tap on this row if you switch to a different type of insulin.
+
+* The model used by *Loop* for all the rapid insulin brands are the same, but it's a good idea to record if you change brands - some people notice differences
+* If you switch between rapid and ultra-rapid insulin, you need to let *Loop* know so it will use the appropriate model
+
+### Patch Settings
+
+Typically the default Patch Settings are selected during onboarding of the Medtrum Nano pump. However, you can modify these setting during or between pods.
+
+Any changes made to Patch Settings after onboarding requires authentication to be saved.
+
+1. **Max hourly insulin** & **Max daily insulin**: Medtrum Nano does not work with max bolus and max basal settings, it uses max hourly & max daily insulin. Just like the names suggests, it controls the maximum amount of insulin per hour or per day (measured since midnight).
+1. **Alarm setting**: The Medtrum Nano has the ability to make a beep if there is an occlusion, patch fault, empty battery, etc. These alarms can also be silenced using this setting.
+1. **Patch lifetime**: Normally, the Medtrum Nano runs for 3 days and 8 hours. This is recommended to ensures the functioning of the patch and cannula. You can disable this limit but it is not recommended. See [Extended Lifetime Setting](#extended-lifetime-setting) for more information.
+1. **Notification for expiration**: If the **Patch lifetime** setting is set to normal lifetime, you have the ability to update this setting. You can control at what point the patch will alert you that patch is nearing expiration.
+1. **Notification for low reservoir**: You can select the reservoir level at which you want to be notified or disable the notification.
+
+
+- - -
+
+## Information
+
+The next section on the Medtrum Nano screen reports information about the current patch and the previous patch:
+
+* **Cannula Age**: Time since the cannula was inserted (coming soon)
+* **Activation**: Time at which patch was Activated
+* **Expiration:** Time at which patch will Expire (8 hours before No Delivery time)
+* **No Delivery**: Time at which patch will stop delivering insulin
+ * If using extended life, please read [Extended Lifetime Setting](#extended-lifetime-setting)
+ * If a Patch Fault was detected, this will give the time at which the fault was detected
+* Access to [**Patch Details**](#patch-details)
+* Access to [**Previous Patch Details**](#previous-patch-details)
+
+#### Patch Details
+
+Some additional details for the most recent patch are provided by tapping on this row.
+
+Some items reported:
+
+* Pump base serial number
+* Pump base firmware version
+* Pump base model
+* Battery level (V)
+* Insulin used (U)
+
+#### Previous Patch Details
+
+When you tap on the `Previous Patch Details` row, summary information is displayed about the patch before the one currently in use.
+
+## Patch Time
+
+Click on [Time Zone](displays-v3.md#time-zone){: target="_blank" } to understand how *Loop* treats "pump" time for pods.
+
+When the Pump time zone matches the phone time zone, the Pump Time is displayed with black font.
+
+When the phone time zone and pump time zone do not match, there is a clock icon on the main screen in the Pump Status Icon of the HUD.
+
+* Tap on the Pump Status Icon in the HUD (top red rectangle in graphic below)
+* Information about Time Change is provided on the Nano screen
+* The Pump Time displays the clock icon and yellow font
+ * The `Sync to Current Time` row appears
+ * Tap on the `Sync to Current Time` row to choose whether to make Pump Time match Phone Time or not (bottom red rectangle in graphic below)
+
+🚧 TODO: The graphic below will be prepared later 🚧
+
+{width="600"}
+{align="center"}
+
+### Other Time Changes
+
+What about other time changes? Suppose the iOS -> General -> Time & Date is modified to manually change the time, but the time zone is not adjusted. (Sometimes this is done to defeat limits on games. **Do Not** do this on an OS-AID phone. If you have an "old" glucose reading in the "future" - *Loop* will not predict correctly which may have dangerous consequences.) There will not be an obvious display in the main display or Nano screen (which keys off time zone) but you will get regular warnings that phone does not have automatic time set.
+
+> When automatic time is disabled on the iPhone settings, *Loop* will not automatically modify insulin delivery and the pump will revert to scheduled basal after the last temporary basal rate duration completes.
+
+The *Loop* app will display this warning modal screen if it detects a problem with the Phone time. It leaves it up the user to decide what action should be taken. To make this warning stop, go to iOS -> General -> Time & Date and enable Set Automatically.
+
+{width="300"}
+{align="center"}
+
+- - -
+
+## Prepare Patch
+
+!!! danger "Attach Pump Base Before Filling the Pump Patch with Insulin"
+ Make sure the pump base matches the patch.
+
+ * Before connecting your pump base with your patch, always check the REF on your patch with the REF on your pump base
+ * The first 3 digits should always match, the patch always ends with 0, while the pump base always ends with 1
+ * Do not use the patch with that base if they do not match
+
+ {width="450"}
+ {align="center"}
+
+
+### Activation flow
+
+!!! warning "IMPORTANT"
+ Connect your pump base to the patch before adding insulin to your patch.
+ Otherwise, you might corrupt the activation flow.
+
+
+!!! abstract ""
+ The graphics walk you through each step of the filling, pairing, priming, attaching and insertion process.
+
+ You will probably need to scroll up or down to see all the instructions on your phone.
+
+{width="500"}
+{align="center"}
+
+After the serial number prompt:
+
+1. Attach the base to the patch and then tap on Continue
+2. Follow the visual guide in the *OS-AID* app to pull out air and fill the patch with insulin
+3. Press "Start priming" to start priming the patch
+
+It is important to not attach the patch on your body before the priming process completes.
+
+!!! warning "IMPORTANT"
+ While the priming is running, DO NOT USE THE CANCEL BUTTON.
+ This might corrupt the activation flow, so please be patient while the priming process is running.
+
+After priming, follow the rest of the visual guide in the *OS-AID* app .
+From here, you can attach the patch to your body and complete the activation process.
+
+* Do not forget to insert the cannula manually
+* Press firmly until you feel and hear a click - make sure the cannula stays inserted when you let go
+* Tap on activate and in a few seconds you will see the nominal [Medtrum Nano Screen](#medtrum-nano-screen)
+
+- - -
+
+## Patch Error Messages
+
+🚧 TODO: This section is under construction 🚧
+
+Most Patch Error messages are for information and there is no action that can be taken other than to replace the patch. (This statement needs review)
+
+There are two states that can be handled by taking the appropriate action.
+
+### Alert: Suspended - Hourly Max
+
+The patch has an internal setting for the maximum amount of total insulin that can be delivered per hour. If this is exceeded then the patch indicates an alert and suspends insulin delivery.
+
+* Consider if there might be a cannula issue if your **Max hourly insulin** is reasonable and you do not think you should exceed that amount
+ * Remember to include scheduled basal rate, temporary basal rate and any boluses for that hour
+* Go to the [Patch Settings](#patch-settings)
+ * Examine the current value for **Max hourly insulin**
+ * You can modify that value to a larger amount and save it
+ * Once a larger amount is saved, you can then return to the Nano screen and clear the alert at the top of the screen
+ * Insulin Delivery should resume providing normal close-loop operation
+
+
+### Alert: Suspended - Daily max
+
+The patch has an internal setting for the maximum amount of total insulin that can be delivered in a day. If this is exceeded then the patch indicates an alert and suspends insulin delivery. Note that the insulin delivery is calculated from midnight local time.
+
+* Consider if there might be a cannula issue if your **Max daily insulin** is reasonable and you do not think you should exceed that amount
+ * Remember to include scheduled basal rate, temporary basal rate and any boluses for that day
+* Go to the [Patch Settings](#patch-settings)
+ * Examine the current value for **Max daily insulin**
+ * You can modify that value to a larger amount and save it
+ * Once a larger amount is saved, you can then return to the Nano screen and clear the alert at the top of the screen
+ * Insulin Delivery should resume providing normal close-loop operation
+
+- - -
+
+## Extended Lifetime Setting
+
+!!! warning "Extended Life"
+ The Medtrum Nano allows operation using Extended Life, although this is not recommended.
+
+ New firmware stictly limits delivery after 120 hours. After 120 hours, the patch will continue delivering scheduled basal rates until the batteries die.
+
+ The OS-AID pump manager assumes this 120-hour limit is enforced and provides suitable messages. Older Medtrum brains might allow full operation to continue. Please be exceedly cautious if you choose to extend your pump operation past the recommended 80 hours.
+
+
+* Exended Life
+ * Patch expires at 112 hours (this is an OS-AID notation)
+ * Patch might stop accepting bolus or temporary basal rate commands at 120 hours
+
+{width="300"}
+{align="center"}
diff --git a/docs/loop-3/omnipod.md b/docs/loop-3/omnipod.md
index d6ef640458b..678199a61b6 100644
--- a/docs/loop-3/omnipod.md
+++ b/docs/loop-3/omnipod.md
@@ -110,7 +110,7 @@ Pods start reporting reservoir values when 50 U are left.
| 0 U|Pod will attempt to deliver up to 4 U after it reports 0 U.
This is not guaranteed. The pod senses when it is not successful delivering pulses and that can happen before 4 U have been delivered.|
-## Activity
+## Actions
### Suspend Delivery
diff --git a/mkdocs.yml b/mkdocs.yml
index ad555dd366a..a72e1f5350d 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -189,8 +189,11 @@ nav:
- 'Optional: Services': 'loop-3/services.md'
- 'Displays': 'loop-3/displays-v3.md'
- 'RileyLink Display': 'loop-3/rileylink.md'
+ - 'Eversense CGM': loop-3/eversense.md
+ - 'Dana Pump': loop-3/dana.md
- 'Omnipod Pump': loop-3/omnipod.md
- 'Medtronic Pump': loop-3/medtronic.md
+ - 'Medtrum Pump': loop-3/medtrum.md
- 'Features': 'loop-3/features.md'
- Operate:
- 'Open Loop': 'operation/loop/open-loop.md'