Connected Patient Monitor¶
Use this example for a distributed device connected to hospital systems.
- Model bedside monitor, gateway, and clinical data repository responsibilities.
- Define typed measurement and network exchanges.
- Mark the hospital-network trust boundary.
- Link assets, interfaces, and cybersecurity concerns without copying components.
Where this sits in MEMO¶
Every tutorial is one slice of the same structure. This example populates these layers:
| Layer | Element types it uses | Reference |
|---|---|---|
| Logical | Interface, LogicalComponent, LogicalExchange, LogicalExchangeItem |
Logical |
| Assurance | TrustBoundary |
Assurance |
| Views and methodology | MemoDiagramView |
Views and methodology |
| Core | TerminologyCode |
Core |
Typed links it uses: CrossesTrustBoundary, LogicalConnector — see Relationships for what each one claims and which ends are legal.
Layers it does not populate: operational, functional, implementation and realization. A MEMO project includes only the layers selected by its methodology. For a device modelled all the way through, see the GPCA Pump case study.
Narrative treatment: Requirements and Architecture · Risk, Cybersecurity, and Assurance.
Source model: examples/connected-patient-monitor