Polysomnography and Home Sleep Test Device Imports, Scoring Workflow Queues, CPAP Adherence Data Downloads and DME Referral Handoff for a Custom US Sleep Medicine Platform

This article is part of our series on Custom Sleep Clinic Management Software Development for US Sleep Medicine Providers: Building a Study Scheduling, Scoring and CPAP Adherence Platform

Introduction: Three Vendors’ Data and One Queue You  Build 

Four pieces decide whether a sleep medicine platform actually works, and only one of them gets built from scratch. Study data lives in acquisition systems from a small number of manufacturers, each with its own formats and its own openness to outside connections. Adherence data lives in manufacturer cloud platforms designed around suppliers rather than prescribers. The supplier handoff is a business relationship with no standard behind it, and the scoring queue is the one component a team designs from the ground up.

Sleep medicine software integrations split cleanly along that line, and the split tells a technical decision-maker where the risk actually sits. Getting acquisition and adherence data flowing usually calls for custom software development, since the connections involved rarely come packaged as an off-the-shelf integration. The portals that make referring providers and patients part of the workflow depend on web application development built around how each group actually works. One boundary holds throughout every piece covered here: nothing in the platform scores a study, interprets a result, or determines clinical benefit.

Polysomnography and Home Sleep Test Device Imports

A sleep center runs on two very different kinds of studies, and each arrives through its own equipment. In-lab polysomnography comes off acquisition systems tethered to the bed. Home sleep tests come back on a device the patient carried out the door and returned. Both eventually need to reach the same platform, but neither integration looks like the other, and neither looks like connecting to a typical piece of medical software. 

A Small Market With Its Own Formats

Sleep acquisition and analysis systems come from a limited number of manufacturers, and each stores data in a proprietary format alongside varying support for the interchange standards common in physiological recording. What can actually be exported, and whether scoring travels with the signal data or sits separately, differs by system and by version. That variation makes integration a per-vendor question rather than a general one, and a team scoping the work needs to confirm specifics against the acquisition system already in place, not against the category.

What Actually Needs to Move

In most designs, raw signal data stays in the acquisition system, where scoring already happens on calibrated displays built for exactly that purpose. What moves into the management platform is narrower: the study’s existence, its status, the scored summary, and the final report. Pulling multichannel raw recordings into a separate platform creates a large storage and display problem for little practical benefit, since nobody scores from a management dashboard.

Home Devices Add a Download Step

Home testing devices get downloaded at the point of return, and that download is when the study enters the scoring queue. The physical return, the reprocessing gate, and the data import function as one workflow rather than three separate steps. A device that comes back but never gets downloaded produces a study nobody in the system knows exists, and that gap is worth designing a specific check around rather than trusting staff to catch it manually.

Scoring Workflow Queues

A scoring queue should show what needs attention and why. Each study should include its acquisition date, type, priority, and any clinical urgency.

Study count alone can hide the real workload. A full attended study may require far more scorer time than a home test, making scoring hours a better measure of capacity.

Studies can then be assigned based on scorer qualifications, workload, and study type. Easy reassignment keeps work moving when availability changes. Studies waiting the longest should also surface automatically, helping teams spot capacity issues before they affect turnaround.

Automation can reduce workload but should not replace clinical review. Automated results should enter as drafts for qualified scorers to review. Nothing should be released based on automated output alone.

The same approach applies to interpretation. A separate queue can make physician workload and pending studies visible while keeping assignments clear.

Quality assurance should remain part of the workflow. Reference cases can help maintain consistency and support ongoing scorer education.

Together, these workflows give centers a clearer view of capacity. Tracking scoring hours, throughput, and queue age also helps teams understand how additional volume could affect turnaround.

CPAP Adherence Data Downloads

CPAP adherence data downloads get assumed to be simple more often than any other integration in this list, and they turn out to be the hardest. The data belongs to the device manufacturer, and the access model was built around the supplier furnishing the device, not around the prescriber trying to monitor a patient.

Devices report usage to manufacturer cloud platforms, and a handful of manufacturers dominate the market, each running its own platform with its own access model and its own data structure. Access typically gets arranged for the supplier who furnished the device, with prescriber access available under terms that vary considerably by manufacturer and by agreement. In practice, a single center’s patients end up on devices from several manufacturers, supplied by several DME companies, with access credentials set up per clinician rather than per organization.

This reality makes the integration plural rather than singular, and the first real work is establishing what access actually exists today, not what a manufacturer’s marketing page claims is available. What needs to arrive in the platform is usage data by night across the reporting period, plus the summary figures required for documentation, tied to the patient’s record in the center’s own system rather than sitting in a portal someone has to remember to log into.

Timing carries clinical weight here. Data visible in week two lets a care team catch a struggling patient early and adjust the mask or the humidification settings before the patient gives up. A patient portal, built through web application development, should show adherence data as it comes in, and not wait until the clinical visit to reveal it. If a clinician only sees the numbers during the encounter, they’re just reading about what already happened. By then, it’s too late to help.  Any arrangement permitting this data flow is a privacy matter requiring proper agreements between the parties involved, convenient access is never the same thing as permitted access.

DME Referral Handoff

The handoff to an equipment supplier is a business process with no industry standard behind it, which in practice means fax, a supplier portal, or email. The design question worth solving is reliability, not elegance. What goes out to the supplier includes the order with its prescription, the documentation the supplier needs to bill correctly, the study results establishing medical qualification, and the patient’s details.

What has to come back is where most designs fall short: confirmation the patient was set up, the date it happened, which specific device was issued, and an identifier that lets adherence data get matched to that device later. That return path is the piece most often missing from a first build. A center that does not know which device its patient actually received cannot match the usage data when it eventually needs to.

Multiple suppliers are the norm rather than the exception, since patients have preferences, insurance networks differ, and referring physicians carry their own supplier relationships. The handoff needs to work as something configurable per supplier, not something built once and assumed universal. Status tracking through setup matters just as much, since a patient who was never actually set up is a patient whose coverage window is running down with nothing happening on the ground. Where the center also supplies equipment directly, the handoff becomes an internal process carrying legal considerations that belong with healthcare counsel rather than with a workflow diagram.

Systems a Sleep Center Connects To

Beyond these four core areas, several other systems complete the connection map. The electronic health record (EHR), whether used by the center or an affiliated health system, typically connects through standard clinical messaging for patient details, orders, and results. Referring practices use their own systems to send referrals and receive reports.

Eligibility and prior authorization come into play early in the workflow. Billing and clearinghouse systems handle claims later in the process, covering both professional and facility services. Patient communication tools, including apps built through mobile app development, support reminders, preparation instructions, and therapy follow-up. Electronic signature tools manage consent forms and other intake documents.

Several operational systems run alongside the clinical workflow. Accounting and payroll support the business side of the center, while shipping systems become important when home devices are delivered to patients. Inventory systems track equipment, sensors, and other supplies so teams know when to reorder.

Telehealth also plays a role, particularly when follow-up visits are conducted remotely. Together, these connections support the full patient journey, from referral and scheduling through testing, treatment, billing, and follow-up.

Reconciliation and Failure Handling

Two categories of failure run through everything covered so far: one costs a patient their therapy, and the other costs a referrer relationship. A device returned and never downloaded. A study scored and never interpreted. A report completed and never delivered. A patient handed to a supplier with no setup confirmation on record. A patient sitting inside the coverage window with no adherence data available. A device dispatched and never returned.

Each of these needs a queue with an age attached and an owner responsible for clearing it. Two checks earn a permanent place in daily operations. A daily study reconciliation confirms every acquired study made it into the scoring queue and every returned device actually got downloaded, since a study nobody knows exists stays invisible until a referrer calls asking about it. A coverage window review, sorted by days remaining, catches patients before that clock runs out, because a patient discovered late has already lost the option to act.

Device imports and adherence downloads drive the budget are covered in: Budgeting Custom Sleep Clinic Management Software.

Final Thoughts

A well-designed platform should reflect how the center actually works. Raw signal data can stay in the acquisition system, while the platform brings in the status and results teams need. Measuring the scoring queue in hours rather than study counts gives a clearer view of workload. Understanding what adherence data is actually available prevents teams from designing around assumptions. Closing the supplier loop also makes it easier to connect devices to patients later.

If adherence data is driving the need for a custom platform, start by identifying which manufacturer platforms your patients use today. That inventory can then shape the right integration approach. New Age Sys IT can help turn those requirements into a practical integration plan. Learn more about digital transformation solutions from one of the leading AI software companies in the United States.