Commissioned Research
Top 10 Best Respiratory Software of 2026

GITNUXSOFTWARE REVIEW

Medical Conditions & Disorders

Top 10 Best Respiratory Software of 2026

Top 10 respiratory software options for clinics, with clear tradeoffs, features, and use cases to guide software shortlisting.

20 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Respiratory software decides how clinical teams capture pulmonary function signals, score and interpret results, and produce audit-ready reports across sleep and cardiopulmonary workflows. This comparison helps operators weigh integration depth, API and data model fit, and deployment realities such as cloud monitoring versus on-prem test stations, including how Spirometry platforms like SpiroCloud handle throughput and interpretation support.

Somnoware is the best pick for respiratory teams that want protocol-led documentation and RT worklists without a heavy hospital EHR dependency, thanks to its predefined, episode-linked workflow steps that cut variation between staff, while MGC Diagnostics fits better when you need structured therapy documentation tied to reporting outputs for consistent review cycles.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Somnoware

Protocol-driven respiratory documentation steps that advance work through predefined RT workflows and episode-linked entries.

Best for: Fits when respiratory teams need protocol-led documentation and RT worklists without a full hospital EHR dependency.

2

MGC Diagnostics

Editor pick

RT documentation workflow that ties structured therapy events to reporting outputs without manual re-entry.

Best for: Fits when respiratory teams need consistent therapy documentation and reporting with controlled workflows.

3

ResMed AirView

Editor pick

AirView patient monitoring timelines that consolidate therapy status and adherence changes from connected devices.

Best for: Fits when sleep and home ventilation programs need centralized monitoring queues for ongoing clinician review.

Comparison Table

1
SomnowareBest overall
vertical specialist
9.1/10
Overall
2
enterprise
8.9/10
Overall
3
vertical specialist
8.8/10
Overall
4
vertical specialist
8.3/10
Overall
5
vertical specialist
8.2/10
Overall
6
vertical specialist
7.8/10
Overall
7
vertical specialist
7.5/10
Overall
8
vertical specialist
7.1/10
Overall
9
API-first
6.9/10
Overall
10
API-first
6.6/10
Overall
#1

Somnoware

vertical specialist

Sleep medicine software for diagnostic testing, scoring, reporting, and clinical workflow management.

9.1/10
Overall
Features9.1/10
Ease of Use9.0/10
Value9.2/10
Standout feature

Protocol-driven respiratory documentation steps that advance work through predefined RT workflows and episode-linked entries.

Somnoware targets respiratory care workflow and documentation needs for clinical teams using configurable forms and structured case data. The system supports RT-facing tasking and protocol-driven documentation so visits stay consistent across staff handoffs.

Integration options focus on importing and exporting study and measurement outputs while keeping care events tied to specific episodes. Automation centers on pre-defined respiratory documentation steps and rule-based work progression rather than open-ended free text.

Pros
  • +Configurable respiratory documentation flows reduce variation between RTs
  • +Worklist-style execution supports consistent protocol steps during routine care
  • +Structured episode linkage keeps measurements and events traceable
  • +Import and export interfaces support pulmonary study and measurement handoffs
Cons
  • –Protocol and form configuration requires governance discipline to stay aligned
  • –Waveform-level integrations depend on external device and format availability
  • –Advanced analytics require additional build effort instead of out-of-the-box dashboards
  • –Cross-service orchestration is limited compared with hospital enterprise suites
Use scenarios
  • Respiratory therapy teams

    Episode-based RT documentation during visits

    Consistent visit records

  • Clinical documentation specialists

    Standardize measurements into structured fields

    Lower manual re-entry

Show 1 more scenario
  • Hospital program managers

    Control handoffs across shift changes

    Fewer handoff gaps

    Uses rule-based work progression so tasks remain aligned for staff handoffs without freeform notes.

Best for: Fits when respiratory teams need protocol-led documentation and RT worklists without a full hospital EHR dependency.

#2

MGC Diagnostics

enterprise

Cardiopulmonary diagnostic software suite for complete pulmonary function testing workflows.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

RT documentation workflow that ties structured therapy events to reporting outputs without manual re-entry.

MGC Diagnostics provides respiratory care software designed to support clinical documentation and reporting workflows for respiratory teams. The system centers on structured charting that aligns therapy activities with downstream documentation needs, including study result handling for pulmonary diagnostics.

Integration and automation focus on connecting respiratory data into clinical records and work queues so teams can complete documentation with fewer manual handoffs. The product’s strongest fit is operational control for RT teams where repeatable protocols and consistent documentation flow matter more than custom UI changes.

Pros
  • +Structured therapy documentation reduces free text variability across respiratory staff
  • +Workflow support for respiratory documentation supports consistent completion and review cycles
  • +Automation of respiratory work queues helps minimize documentation lag after patient encounters
  • +Export-ready pulmonary outputs support reuse for clinical reporting and shared review
Cons
  • –Advanced automation depends on integration work to match local documentation structures
  • –Some respiratory-specific workflow screens can feel narrow versus broader enterprise EMR coverage
Use scenarios
  • Pulmonary diagnostics clinics

    Structured charting for therapy activities

    Reduced documentation drift

  • Respiratory care coordinators

    Work queue completion using protocols

    Faster queue turnaround

Show 2 more scenarios
  • RT documentation leads

    Standardize protocol-driven reporting outputs

    More consistent reports

    Aligns therapy and study result handling so reporting stays consistent across repeated pulmonary assessments.

  • Clinical data managers

    Integrate device results into records

    Fewer transcription errors

    Moves pulmonary diagnostics data into clinical records so teams avoid manual transcription into charts.

Best for: Fits when respiratory teams need consistent therapy documentation and reporting with controlled workflows.

#3

ResMed AirView

vertical specialist

Cloud-based remote monitoring platform for patients using ResMed respiratory and sleep therapy devices.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

AirView patient monitoring timelines that consolidate therapy status and adherence changes from connected devices.

ResMed AirView is differentiated by its focus on remote monitoring from connected respiratory devices and sleep workflows, which feeds repeatable clinical review processes for distributed patients. The monitoring experience is organized around patient-level histories and therapy status changes, which helps RT and sleep teams track outcomes over time. The system also supports exporting and structured review views intended for care coordination and follow-up documentation.

A tradeoff is that AirView’s most reliable results come when connected-device data coverage exists for the site’s equipment mix, since workflows depend on incoming device telemetry rather than manual chart entry alone. A good fit is a sleep or home ventilation program that needs centralized review queues for therapy follow-up, with consistent documentation and trend awareness across clinicians.

Pros
  • +Remote monitoring views built for sleep and home ventilation follow-ups
  • +Patient timelines make therapy changes and adherence patterns easy to review
  • +Clinical review tooling supports repeatable monitoring workflows
  • +Cohort provisioning helps keep monitored populations organized by role
Cons
  • –Workflow depth varies when connected-device data is incomplete for a site
  • –Integration breadth beyond AirView telemetry can require additional interface work
  • –Administrative setup takes discipline to keep roles and cohorts aligned
  • –Advanced automation needs tighter process mapping to match clinic review habits
Use scenarios
  • Sleep program managers

    Clinician review of therapy adherence trends

    More consistent follow-up documentation

  • Home ventilation teams

    Remote oversight of ventilator therapy

    Faster intervention decisions

Show 1 more scenario
  • Hospital case management

    Care coordination using monitoring timelines

    Better continuity across visits

    Therapy review context supports case handoffs and follow-up scheduling decisions.

Best for: Fits when sleep and home ventilation programs need centralized monitoring queues for ongoing clinician review.

#4

SpiroCloud

vertical specialist

Cloud-based spirometry software for test management, interpretation support, and reporting.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Spirometry import normalization that maps incoming measurements into consistent study fields for repeatable PFT reporting.

SpiroCloud is built around a cardiopulmonary documentation module that structures each pulmonary function study as a record with consistent measurement fields. Data import handles spirometry data import workflows so staff can move results from acquisition devices or external sources into a standardized format for interpretation. Reporting outputs support repeatable PFT reporting interface needs for review, sign-off, and study comparison across visits.

Pros
  • +Structured pulmonary function study records reduce manual reconciliation work
  • +API-driven integrations support automated transfer of study results
  • +Role-based access separates data entry from clinical review
Cons
  • –Ventilation waveform and ICU event tracking are not core capabilities
  • –Respiratory therapy worklists and RT protocol automation need external orchestration
Use scenarios
  • Respiratory therapy coordinators

    Standardize lab spirometry study documentation

    Fewer transcription errors

  • Pulmonary function lab managers

    Enable study comparison across visits

    More reliable longitudinal review

Show 1 more scenario
  • Clinical informatics teams

    Automate handoff to EHR workflows

    Reduced manual data entry

    Use API endpoints to push study outputs into downstream clinical applications with controlled field mapping.

Best for: Fits when respiratory departments standardize lung function documentation and need interoperable, report-ready outputs.

#5

ndd EasyWarePro

vertical specialist

Pulmonary function testing software paired with ndd spirometry and diffusion capacity hardware.

8.2/10
Overall
Features8.2/10
Ease of Use8.3/10
Value8.1/10
Standout feature

Study template configuration that maps imported measurements into encounter-ready documentation and repeatable reports.

ndd EasyWarePro fits clinical teams that need consistent respiratory documentation across multiple measurement sessions and care teams. The workflow structure supports respiratory therapy documentation, repeatable study capture, and report generation from imported measurements. Configuration controls allow site-specific mapping of data capture fields into the encounter documentation used by therapists and clinicians.

Pros
  • +Structured respiratory documentation reduces variation across measurement sessions
  • +Automated respiratory therapy worklists match recurring therapy scheduling patterns
  • +Configurable study templates keep imported device data aligned to reports
  • +Report outputs support fast review during patient encounters
Cons
  • –Workflow automation relies on template and step configuration discipline
  • –Ventilator waveform integration coverage is limited compared with broader ICU platforms
  • –Cross-department governance controls are less granular than enterprise EHR overlays
  • –Complex multi-device pipelines require careful field mapping
Use scenarios
  • Respiratory therapy teams

    Daily therapy worklist documentation

    More consistent care records

  • Pulmonary function labs

    Spirometry study result reporting

    Quicker turnaround for reviews

Show 1 more scenario
  • Clinical informatics analysts

    Interoperability field mapping

    Lower rework after imports

    Configuration supports mapping imported measurement attributes into the local documentation layout.

Best for: Fits when respiratory programs need consistent documentation and worklist automation across recurring measurement sessions.

#6

NuvoAir

vertical specialist

Digital respiratory care software for remote monitoring, spirometry, and chronic disease management.

7.8/10
Overall
Features7.8/10
Ease of Use7.9/10
Value7.7/10
Standout feature

Episode-centric respiratory documentation that ties therapy activity to protocol-linked review and shift handoff checks.

NuvoAir focuses on respiratory care workflows with a documentation and review layer built around therapy episodes rather than generic note capture. The system targets cardiopulmonary documentation needs like oxygen therapy, nebulization records, and protocol-linked therapy activity. NuvoAir also supports analytics and worklist-driven operations so teams can track care completion and exceptions across shifts.

Pros
  • +Therapy-episode documentation aligns to RT workflow patterns
  • +Worklist views support shift handoff and task completion tracking
  • +Protocol-linked documentation reduces omission risk during rounds
  • +Analytics surfaces care completion and exception patterns by unit
Cons
  • –Ventilator waveform integration is not positioned as a native focus
  • –Integration options rely on external connectivity rather than turnkey EHR mapping
  • –Protocol configuration requires careful governance to avoid inconsistent rules
  • –Some cardiopulmonary reporting tasks may require manual export steps
Use scenarios
  • ICU respiratory teams

    Oxygen therapy and nebulization tracking

    Clear therapy timelines

  • Unit charge nurses

    Monitor care completion across shifts

    Fewer missed entries

Show 1 more scenario
  • Pulmonary program coordinators

    Analyze episode outcomes and exceptions

    Actionable quality insights

    Runs analytics over therapy episodes to identify patterns in completion gaps and protocol deviations.

Best for: Fits when respiratory therapy teams need episode-based documentation, worklists, and unit-level tracking without heavy waveform integration requirements.

#7

Cosmed

vertical specialist

Pulmonary function and metabolic measurement software for clinical and research applications.

7.5/10
Overall
Features7.5/10
Ease of Use7.4/10
Value7.6/10
Standout feature

RT protocol engine that ties worklist tasks to documented therapy steps and handoff context across ongoing care.

Cosmed supports respiratory care workflows by coordinating documentation, therapy orders, and clinical follow-up in one environment. It is built around care-team worklists and structured capture for therapy activities, including measurements and administration events.

Pros
  • +Worklists align RT-driven documentation with daily therapy sequencing
  • +Structured capture for therapy events supports consistent charting
  • +Integration support covers HL7 result feeds and import paths for studies
  • +Protocol configuration supports standardized therapy steps and handoff context
Cons
  • –Protocol behavior depends on careful configuration and release management
  • –Some advanced device workflows require tighter integration effort than expected
  • –Dashboard depth is limited compared with enterprise EHR-integrated respiration modules
  • –Clinician-facing views can feel heavier when many fields are required
Use scenarios
  • Respiratory therapy departments

    Therapy orders with structured administration capture

    Tighter order-to-chart flow

  • Clinical informatics teams

    HL7 result feeds into clinical records

    Less manual data movement

Show 2 more scenarios
  • Respiratory leaders

    Protocol configuration for consistent handoffs

    More uniform charting

    Configures respiratory protocols so RT documentation and handoffs follow the same structure across care teams.

  • Research coordinators

    Device and study file ingestion for reporting

    More traceable study data

    Brings in study artifacts for downstream reporting while keeping care events tied to episodes.

Best for: Fits when respiratory therapy teams need protocol-based worklists, structured documentation, and configurable handoffs.

#8

IngMar Medical RespiSim

vertical specialist

Respiratory simulation software for ventilator training and device testing.

7.1/10
Overall
Features7.1/10
Ease of Use7.1/10
Value7.1/10
Standout feature

Scenario-based respiratory physiology simulation with session workflow control for standardized training and evaluation.

IngMar Medical RespiSim is built for respiratory simulation workflows where clinicians need repeatable test conditions, not just documentation screens. It supports scenario-based sessions that generate standardized respiratory physiology behaviors for training and evaluation.

Pros
  • +Scenario-driven respiratory simulation supports repeatable training sessions
  • +Structured run workflow keeps tasks aligned to session phases
  • +Clear observation capture helps standardize learning or evaluation
  • +Simulation-first design reduces the need to adapt documentation workflows
Cons
  • –Not a cardiopulmonary documentation module for EHR-first work
  • –Ventilator waveform integration and HL7 ORU feeds are not its focus
  • –Protocol engine coverage for weaning and ARDSnet style rules is limited
  • –Requires scenario design effort to match local training objectives
Use scenarios
  • Respiratory educators

    Repeatable simulation sessions for training

    More consistent training

  • Clinical skills assessors

    Guided tasks during simulation runs

    More comparable assessments

Show 1 more scenario
  • Biomedical training administrators

    Protocol exercise with standardized conditions

    Higher scenario fidelity

    Controls workflow around simulation runs so teams rehearse respiratory protocols under repeatable test conditions.

Best for: Fits when simulation centers need controlled respiratory training runs with consistent task sequences.

#9

EnsoData

API-first

Software for automated sleep study analysis, scoring, interpretation, and report generation.

6.9/10
Overall
Features6.9/10
Ease of Use6.9/10
Value6.9/10
Standout feature

Configurable measurement intake and field mapping that drives structured exports for respiratory documentation and reporting flows.

EnsoData positions itself for respiratory workflows by focusing on data integration from clinical devices and exports into downstream reporting. It supports structured intake of measurements, mapping of incoming values to documentation fields, and repeatable exports for study and care coordination use cases.

Pros
  • +Device and measurement ingestion designed for repeatable documentation workflows
  • +Integration-first approach reduces manual transcription across respiratory episodes
  • +Export outputs support downstream reporting and research-style study pulls
  • +Configuration emphasizes repeatable mappings for incoming measurement fields
Cons
  • –Respiratory therapy specific worklists need more workflow wiring than generic templates
  • –Automation depth depends on integration setup effort and data field mapping discipline
Use scenarios
  • Pulmonary function testing teams

    Map PFT measurements into documentation fields

    Faster chart population

  • Clinical data integration teams

    Export repeatable study outputs for reporting

    More consistent exports

Show 1 more scenario
  • Quality and operations leads

    Controlled rollout for measurement throughput

    More predictable throughput

    Supports implementation focused on integration and automation so sites reach consistent measurement to documentation throughput.

Best for: Fits when respiratory teams need consistent measurement intake and structured exports into downstream reports.

#10

Lenus Health

API-first

Interoperable software for remote monitoring and pathway management in chronic respiratory disease.

6.6/10
Overall
Features6.6/10
Ease of Use6.6/10
Value6.6/10
Standout feature

RT worklist execution tied to respiratory documentation that preserves context across handoffs and therapy events.

Lenus Health provides respiratory care documentation and workflow tooling for clinical teams that need structured charting across encounters and settings. The system organizes respiratory-specific observations, orders, and therapy events into a consistent record that supports care handoff and worklist-driven delivery.

Pros
  • +Respiratory-specific documentation stays structured across encounters and settings
  • +Worklist-oriented workflows match RT-driven task handling
  • +API integration supports connecting respiratory workflows to external clinical systems
  • +Admin controls include governed access and audit visibility for documentation
Cons
  • –Respiratory reporting depth depends on the available export and analytics configuration
  • –Complex protocol logic needs careful configuration to avoid workflow gaps
  • –Ventilator waveform and device-level integration coverage may be limited
  • –Large multi-site deployments may require stronger governance rollout planning
Use scenarios
  • Respiratory care documentation teams

    Structured charting across encounter settings

    Uniform respiratory documentation

  • Hospital respiratory program managers

    Worklist-driven delivery with care handoffs

    Fewer handoff delays

Show 2 more scenarios
  • Clinical operations administrators

    Govern access with audit trails

    Improved traceability

    Uses user permissions and audit trails to support governed access to respiratory documentation and protocol execution.

  • Health IT integration engineers

    Connect respiratory data via API

    Simpler system integration

    Provides an API surface and integration pathways to connect respiratory data capture into surrounding clinical systems.

Best for: Fits when respiratory teams need structured RT documentation with governed access and integrable workflows.

Conclusion

After evaluating 10 respiratory software, Somnoware stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Somnoware

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Respiratory Software

How do respiratory software tools handle spirometry data normalization from different device outputs?
SpiroCloud normalizes spirometry imports by mapping incoming measurements into consistent study fields for repeatable PFT reporting. ndd EasyWarePro uses study template configuration to map imported measurements into encounter-ready documentation and standardized reports. EnsoData focuses on configurable measurement intake and field mapping to drive structured exports from device inputs into respiratory documentation fields.
Which platforms integrate respiratory measurements into existing clinical records using an API or a structured feed?
SpiroCloud provides API-driven data exchange for sending results to downstream clinical systems. Cosmed supports integration patterns that include HL7 result feeds and device or study file imports for downstream reporting. Lenus Health includes an API surface intended for connecting respiratory documentation workflows to surrounding clinical systems.
How do respiratory therapy worklists and protocol engines reduce manual re-entry across visits and shifts?
Cosmed ties worklist tasks to documented therapy steps and handoff context using an RT protocol engine. MGC Diagnostics uses structured charting tied to RT reporting outputs so therapy activities flow into documentation with fewer manual handoffs. NuvoAir drives episode-linked therapy documentation and review checks through worklist-driven operations across shifts.
What breaks if an organization needs episode-based documentation instead of charting tied to a single patient encounter?
NuvoAir is built around therapy episodes, so episode-centric tracking and shift handoff checks fit its documentation model. Somnoware organizes RT documentation steps and rule-based work progression around episode-linked entries, so encounter-only note patterns do not match its workflow. In contrast, SpiroCloud centers on lung function study import and PFT-ready output, so episode workflow requirements may require additional operational layering outside the core study pipeline.
How is single sign-on and governed access handled for respiratory documentation and monitored cohorts?
ResMed AirView supports health system provisioning for monitored cohorts managed by role, which reduces manual account administration for large programs. Lenus Health includes user permission controls and audit trails for governed access to respiratory documentation and protocol execution. SpiroCloud also supports role-based access for who can enter data, review studies, and manage configurations.
How should data migration be approached when moving legacy respiratory results into a new documentation and reporting system?
SpiroCloud expects lung function study imports and metadata normalization, so migration requires mapping legacy study metadata into its normalized study fields. ndd EasyWarePro expects device outputs into study result structures tied to patient encounters, so migration should convert legacy exports into its study template mapping model. EnsoData supports structured intake and repeatable exports, so migration works best when legacy values can be mapped into the configuration-driven field mapping that powers its exports.
When is an RT workflow control tool better suited than an EHR-centric documentation interface for respiratory teams?
MGC Diagnostics targets operational control for RT teams where repeatable protocols and consistent documentation flow matter more than custom UI changes. Cosmed focuses on protocol-based worklists, structured documentation, and configurable handoffs, which fits teams that standardize therapy steps without heavy EHR dependency. IngMar Medical RespiSim targets scenario-based respiratory physiology simulation with workflow control, so it does not function as an EHR documentation layer for routine clinical charting.
Which systems support ventilation or sleep-adjacent monitoring timelines rather than only bedside documentation?
ResMed AirView centralizes patient monitoring timelines that consolidate therapy status and adherence changes from connected devices. Lenus Health concentrates on respiratory-specific observations, orders, and therapy events for handoff and worklist-driven delivery rather than device-driven sleep timelines. NuvoAir focuses on episode-based respiratory therapy documentation and unit-level tracking, so it targets documentation workflows more than connected sleep monitoring views.
What is the tradeoff between scenario-based respiratory simulation and clinical documentation workflows?
IngMar Medical RespiSim is optimized for training and evaluation because scenario-based sessions generate standardized respiratory physiology behaviors with guided tasks. MGC Diagnostics is optimized for structured RT documentation workflow tied to reporting outputs, so it does not replace simulation fidelity for controlled physiology exercises. SpiroCloud and ndd EasyWarePro focus on study import and PFT-ready or encounter-ready reporting, so they do not provide the session workflow control required for repeatable simulation conditions.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Respiratory Software

We separate respiratory software by how it connects day-to-day respiratory documentation to usable outputs and safeguards. Prioritize criteria like integration depth, audit log, and RBAC to see whether the product can move data the way your workflows already demand.

Data integration across devices and records

Why it matters

For respiratory software, data integration across devices and records reduces double entry and keeps labs, treatments, and notes aligned. When it’s thin, users end up rebuilding timelines in spreadsheets.

How to check

During the demo, ask for a sample patient chart that includes device readings and therapy documentation. Then show where those items appear without manual retyping, and confirm what fields are mapped correctly.

API and workflow automation surface

Why it matters

API and workflow automation surface matters because respiratory teams often repeat the same documentation patterns. Better automation and extensibility reduce delays between orders, observations, and signed notes.

How to check

Ask what actions can be triggered via API (create/update notes, attach results, update orders). Request a demo workflow that auto-populates fields, then verify whether it supports a sandbox or test environment for real trial data.

Configurable data model for respiratory tasks

Why it matters

A configurable data model for respiratory tasks lets teams represent their work without contorting names and timestamps. If it’s rigid, respiratory-specific steps become generic notes.

How to check

Request an example configuration for common events like therapy sessions and measurement entries. Confirm you can adjust fields, required inputs, and how results are stored without custom code.

Provisioning, RBAC, and audit trail

Why it matters

Provisioning, RBAC, and audit trail protects clinical integrity and supports safe delegation in respiratory workflows. Without it, changes are hard to trace and permissions become guesswork.

How to check

In the admin view, review roles and what each role can edit or sign. Then open an example record and show the audit trail for changes, including who changed what and when.

Therapy and measurement reporting outputs

Why it matters

Therapy and measurement reporting outputs are what turns documentation into usable clinical and operational views. If exports are incomplete or inconsistent, your reports break downstream.

How to check

Ask to generate a report that pulls therapy events plus measurements for a single patient and a date range. Then check whether the output includes timestamps, units, and status, and whether users can export in a standard format.

Extensibility via configuration, not rewrites

Why it matters

Extensibility via configuration keeps respiratory workflows adaptable when policies or templates change. If every change needs rewrites, teams fall behind and documentation quality drops.

How to check

Ask how the product handles a change to a form field or required item. Confirm whether admins can update templates, approvals, or documentation rules and see the change reflected immediately in existing workflows.

Red flags

  • Fields that should map from records still require frequent manual retyping
  • Audit trail is present but doesn’t clearly show what changed and by whom
  • Reporting omits units or timestamps, making outputs unreliable

Fit by situation

  • If you need to reduce duplicate documentation between devices and notes, prioritize Data integration across devices and records.
  • If your team relies on repeated order-to-document steps, prioritize API and workflow automation surface.
  • If multiple roles edit respiratory notes, prioritize Provisioning, RBAC, and audit trail.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.