# What is Signals

Canonical page: https://docs.ovok.com/signals

Actimi Signals judges vital-sign readings against patient-specific rules and raises alerts when a reading needs a clinician's attention. It returns those decisions through an API: your app shows them and runs the care workflow.

Signals is MDR Class IIa medical-device software; Ovok is not. See [Regulatory status](#regulatory-status) before you ship an app that shows Signals results.

## Two ways to use Signals through Ovok [#two-ways-to-use-signals-through-ovok]

| | [Standalone](/signals/standalone) | [With Ovok](/signals/connected-ovok) |
| --- | --- | --- |
| What you call | Signals' own API, at `/v1/signals/api/*` | Ovok's FHIR API and Slim APIs |
| Where patients and readings live | In Signals, under your own ids (`refId`) | In FHIR (`Patient`, `Observation`); Ovok forwards readings to Signals |
| Where alerts come back | Signals' alert and episode routes, and webhooks | FHIR `DetectedIssue`, `Flag` and `Observation.interpretation`, and the Slim notification feeds |
| Credentials | A Manager or Submitter application, or any caller whose policy holds the `signals_*` capabilities | Any project credential with the FHIR access it needs |
| Good for | A product with its own data store that only needs alert decisions | A product built on Ovok's FHIR data |

Both need your project to have its own Signals tenant. You can use both at once: a patient created in FHIR and enrolled in Signals is also visible through the standalone API.

## Start here [#start-here]

| Goal | Start with |
| --- | --- |
| Raise your first alert in five calls | [Standalone quickstart](/signals/standalone#quickstart) |
| Build an alert feed with webhooks, end to end | [Build an alert feed](/signals/tutorial) |
| Let Ovok send FHIR readings to Signals | [Signals with Ovok](/signals/connected-ovok) |
| Receive alerts as they happen | [Webhooks](/signals/standalone/webhooks) |
| Look up a route | [API reference](/api/signals-api---alerts/list-alerts-or-the-episodes-they-were-folded-into) |

## What Signals does [#what-signals-does]

<Recording name="signals-console-overview" alt="The Console's Signals overview showing a synthetic project's tenant and mutual TLS status" />

- Judges each reading against bands and rules set for the whole tenant or for one patient.
- Raises an alert when a reading breaches a rule, and groups the breaches of one clinical event into an episode. See [Alerts and episodes](/signals/alerts-and-episodes).
- Flags patients who go quiet, send empty readings or leave a note.

Signals never shows anything to clinicians itself. Your app, or Ovok's FHIR resources, carry its results to them. If you build a non-clinical product, you don't need Signals: Ovok's FHIR APIs work without it.

## Regulatory status [#regulatory-status]

### Product details [#product-details]

| Detail | Information |
| --- | --- |
| UDI-DI | `42700031203-API-XG` |
| Security contact | [security@actimi.com](mailto:security@actimi.com) |

### What MDR Class IIa means [#what-mdr-class-iia-means]

**Class IIa** is one of the medical-device risk classes defined by the EU Medical Device Regulation (MDR). The MDR's Annex VIII sets out classification rules based on a device's intended purpose and risk. Rule 11 addresses software that provides information used for diagnostic or therapeutic decisions and software intended to monitor physiological processes; it also sets out circumstances that can result in a higher class. See the [MDR, Annex VIII, Rule 11](https://eur-lex.europa.eu/eli/reg/2017/745/oj/eng) and the European Commission's [software qualification and classification guidance, MDCG 2019-11 rev.1](https://health.ec.europa.eu/document/download/b45335c5-1679-4c71-a91c-fc7a4d37f12b_en?filename=md_mdcg_2019_11_guidance_qualification_classification_software_en.pdf&prefLang=en).

Actimi Signals' Class IIa status applies to Signals as a medical-device software product. It does not certify Ovok or automatically give the same status to an application that integrates with Signals. Ovok is a backend platform, not a certified medical device.

### What this means for your app [#what-this-means-for-your-app]

**Showing a Signals alert does not, by itself, decide whether your app is a medical device.** The MDR assessment is based on the app's own intended purpose and what it is designed and presented to do. The intended purpose is informed by the manufacturer's statements in product materials, instructions for use, promotional or sales content, and clinical evaluation—not just by a disclaimer or the fact that the app uses a certified service.

The boundary depends on the complete workflow. Software limited to storing, transferring, or simply displaying information may be treated differently from software intended to interpret or prioritize patient data, monitor a condition, recommend an intervention, or provide information used for diagnosis or treatment. A user interface can still be part of medical-device software when its intended purpose is to support clinical decisions. There is no blanket exemption for an app described as “display only.”

For an Ovok-powered app, assess these points together:

- **Purpose:** What medical purpose, if any, do you claim for the app, and who is it intended to help—clinicians, patients, or both?
- **Role of the alert:** Does the app pass through the Signals result, or does it add interpretation, ranking, recommendations, escalation logic, or actions that influence care?
- **Use in care:** Is the information intended to support diagnosis or treatment decisions, or to monitor a physiological process? What does the user understand they should do with an alert?
- **Product claims:** Do the app's name, interface, documentation, instructions, and marketing describe a clinical function, even if the code only displays a result produced elsewhere?

If your app has a medical intended purpose, assess it as its own software product under the MDR. Rule 11 may apply when software provides information used for diagnostic or therapeutic decisions, or is intended to monitor physiological processes. The resulting class depends on the intended purpose and the Rule 11 criteria; Signals' Class IIa classification does not set your app's class. The same assessment applies whether the software runs on a phone, server, or in the cloud.

#### A practical review before release [#a-practical-review-before-release]

1. Write down the app's intended purpose, intended users, and the role of Signals results in the care workflow.
2. Compare that statement with the app's actual behavior and all user-facing claims, including alert labels, prioritization, notifications, and recommended next steps.
3. Document your qualification and, if applicable, classification rationale against MDR Annex VIII Rule 11 and the European Commission's software guidance.
4. Get a product-specific assessment from a qualified EU medical-device regulatory professional before placing the app on the market. Do not infer the answer from Ovok's status, Signals' class, or a UI disclaimer alone.

This is a practical summary of public EU guidance, not a legal determination for your product. See the [MDR definition of intended purpose and medical device](https://eur-lex.europa.eu/eli/reg/2017/745/oj/eng) and the European Commission's [MDCG 2019-11 rev.1 software qualification and classification guidance](https://health.ec.europa.eu/document/download/b45335c5-1679-4c71-a91c-fc7a4d37f12b_en?filename=md_mdcg_2019_11_guidance_qualification_classification_software_en.pdf&prefLang=en).

### Official intended purpose [#official-intended-purpose]

> Actimi Signals is a medical device stand alone cloud-based software intended to analyze clinical data captured by compatible medical devices or supplied by other software via the API. Based on the input, Actimi Signals generates patient-specific alerts and creates prioritized lists of patients based on pre-configured rules, using several validated algorithms, based on the recommendations of international societies, or based on a patient-specific rules set by an individual medical practitioner for a specific patient. Therefore, Actimi signals can bring to the clinician's attention those monitored patients potentially in need of clinical intervention or can be used for regular data collection, monitoring and trends reporting. Actimi Signals is not intended to directly present the output to the user, instead, it communicates the results via API and supplies them to a compatible software (i.e. software using adequate API), which can further process the data or provide a graphic user interface to a user.

## Related [#related]

- [Signals route policies](/access-policies/signals)
- [Data Ingestion](/data-ingestion)
