Skip to main contentWorkspaces
A Stenoa Workspace is the container for your organization’s activity on Stenoa, and represents your healthcare organization. As a user, you can have accounts on one or many Workspaces on Stenoa (if you are affiliated to multiple healthcare organizations) and can switch between these accounts using the dropdown menu in the top left-hand corner of the web application, or top bar of the mobile application. When you log into Stenoa, you’re logging into a specific Workspace.
Organizational Trees
Stenoa creates a digital organizational tree of your healthcare organization, seamlessly modelling its natural hierarchy, and enabling intuitive care coordination. Health networks are modeled with hierarchical, nested levels in Stenoa.
Nodes
Each unit within a Network’s organizational tree is called a Node. When a user is invited to join your Network, they are assigned affiliations to the various Nodes within your Network. Users can be affiliated to Nodes at any level of the org tree.
Networks
A network represents the highest level of your healthcare organization’s tree. It is normally named after your health network, and is functionally equivalent to your Workspace on Stenoa. When users log into a workspace on Stenoa, they are logging into that Network’s workspace. In order for Networks to coordinate care and communicate between each other on Stenoa, a Connection needs to be established between them.
Sites
A Site represents a physical establishment within a Network where care is provided. This can be a tertiary or quaternary hospital, community hospital, outpatient clinic, or EMS unit. Networks must have a minimum of one Site.
Departments
A Department represents an organizational unit within a Site. This is usually the highest clinically recognizable entity (e.g. Department of Medicine). Sites must have a minimum of one Department.
Divisions
A Division represents an organizational unit within a Department. A Department does not need to have a Division.
Services
A service represents an organizational unit within a division. For larger Divisions, services can be used to represent specific treating teams or tasks (e.g. clinical teaching unit-1, clinical teaching unit-2, echocardiography lab, heart failure, etc.). A Division does not need to have a service.
Connections
Establishing a connection between workspaces allows team members across networks to coordinate care together. Connections allow network admins to manage inbound and outbound Flows.
Schedules
A Schedule can be created for any organizational unit within Stenoa at the Department level or below, and can be created for any user role. Schedules allow users to be set on-call. Schedules can be linked to Flows to manage escalation policies for a given Flow.
Flows
A flow is the most basic structural unit within Stenoa. Flows can be directly affiliated to a Department, Division, or Service. They enable users from within a Network or an affiliated network (via Connections) to create cases and coordinate care.
Cases
The most basic concept in Stenoa is a Case. A Case represents a structured consultation from one consulting team to another. Pending or active Cases appear in Home on the mobile app or web app. Completed or cancelled Cases appear in the Archive.
Cases can be manually created from within a Network and across authorized Networks, or automatically triggered by third-party event sources.
Lists
A List is a structural unit linked to a Service. Lists allow teams within a Service to keep track of their patients, and review the Archive for patients discharged from their Service. 
