DISA Healthcare Technology and the paperwork that opens the ward

At Northern Michigan University, the instructions for becoming a nursing student include a rather precise purchase. The Winter 2026 checklist lists a minimum of $147.74 for a DISA Healthcare Technology package. There are documents to upload, a drug-screen window to observe, and health requirements to keep current. Admission, it turns out, comes with an administrative sequel.

The price is a useful entrance to this company’s story. Nursing education needs clinical experience; clinical sites need evidence that incoming students satisfy their requirements. Between those two needs sits a collection of records that must be gathered, checked, updated and shared. A student can understand the coursework perfectly and still have unfinished business with an upload button.

The second admission test

DISA Healthcare Technology works with colleges, universities and healthcare institutions. Its territory includes student background checks, drug testing, fingerprinting, occupational health services, immunization records and clinical rotation management. Faculty and staff screening extends the same operation into campus employment, with education, employment and professional-license verification among the available services.

The problems are wonderfully unglamorous. Has the evidence been submitted? Does it meet this institution’s rules? Is it still current? Can the receiving hospital see it? These questions matter because the school and the clinical site are separate organizations, each with its own obligations and instructions. A record stored in one place is not automatically useful in another.

DISA’s LinkedIn profile reports more than one million active students across over 2,200 colleges and universities. Its homepage reports support for more than 9,000 educational programs. Those are company figures, and programs are not the same unit as institutions. Even with that distinction, the scale explains why a business might devote serious attention to the humble requirement checklist.

A new name with two old businesses inside

The company’s history requires care with the nouns. DISA Global Solutions acquired CastleBranch’s screening and compliance services in a deal effective March 1, 2024. CastleBranch had been established in 1997. Founder Brett Martin endorsed the sale, saying, “We believe the business is in great hands.” DISA’s announcement promised investment in technology, security and customer experience.

One conspicuous piece stayed outside the sale: CB Bridges, CastleBranch’s clinical experience platform. It remained separate and was to operate as Bridges EXP. That detail prevents a familiar acquisition error, in which every product wearing the old company’s badge is assumed to have travelled together.

“We believe the business is in great hands.”Brett Martin, CastleBranch founder, March 2024

On February 4, 2025, DISA announced its acquisition of American DataBank, founded in 1998 by Toshi Akiyama. At the same time, it launched a dedicated Healthcare Technology division under David Dickson. American DataBank brought immunization, compliance and rotation-tracking capabilities. The combination gave the division a second established route into healthcare education, including Complio.

DISA’s parent business dates to 1986; the dedicated division dates to 2025. The current CastleBranch rebrand page tells existing users their credentials, records and day-to-day workflows continue. The login page still offers myCB, Complio and Stargate. A unified brand, in other words, does not require pretending that every customer woke up on the same software.

The calendar is part of the product

Complio’s interesting feature is its treatment of requirements as rules rather than mere attachments. Institutions configure the criteria. Users upload evidence, associate it with a requirement and enter the relevant information. The company describes a review process combining its team’s knowledge with a rules engine. The system can then monitor and share compliance status.

That distinction becomes visible when a document expires. Complio supports standard, fixed-date and calculated expirations. Its default reminders arrive 60, 30, 15 and seven days beforehand, with schedules configurable by the school. A tidy digital folder could preserve yesterday’s evidence indefinitely; readiness tracking needs to notice when yesterday’s evidence stops answering today’s question.

Rotation management adds another layer. A clinical agency can specify requirements that differ from the school’s. DISA describes automatic mapping of identical requirements, profile sharing, digitally signed attestations and contract-expiration notices. The point of mapping is straightforward: where two organizations request the same evidence, a student should not have to perform the same administrative dance twice.

The hospital’s view also matters. DISA’s rotation tools are designed to make student, instructor and preceptor information available for reporting and audit preparation. The product’s practical value lies in the handoff: administrators can check readiness before a rotation and see the status of the people coming into a facility.

A school chooses. A student pays.

The business model has an unusual triangle. Institutions configure or select the service, students use it, and clinical sites receive the evidence. Complio’s public FAQ says students are typically responsible for paying for their orders; reimbursement is at the school’s discretion. It also explains that previous addresses, prior names and third-party or court fees can affect charges.

The Northern Michigan example gives that arrangement a number. Its Winter 2026 BSN checklist lists a minimum package cost of $147.74, alongside separate responsibility for CPR and immunization or health requirements. That figure belongs to a particular school and cohort. It is not a DISA-wide tariff, and it does not turn the whole cost of clinical readiness into one convenient receipt.

For institutions, the website offers demonstrations and an RFP/RFI sales route, rather than a universal public price sheet. Screening orders and compliance subscriptions form part of the commercial relationship. The buyer needs to examine the actual package: what gets checked, what gets reviewed, which renewals apply and who carries each expense.

The acquisitions have their own economics. The CastleBranch announcement explicitly left deal terms undisclosed. Public announcements establish the transactions and their purpose; they do not support a tidy purchase-price calculation. The strategic direction is clearer: combine established screening and compliance operations, then extend their connections to schools and hospitals.

The integration is the argument

DISA is operating in an existing market. Exxat Approve collects and reviews student compliance documents within the Exxat ecosystem, with screening integrations and administrative reporting. Verified Credentials Scholar also combines student screening with requirement management. Document uploads, reminders and dashboards are available from other vendors. A useful comparison must go deeper than counting boxes on a feature sheet.

DISA’s case rests on its healthcare education experience, screening operation and links to placement systems. It markets PBSA-accredited screening and says much of its screening process is managed in-house. Its partner list includes InPlace, Typhon Group, Trajecsys, CORE, myClinicalExchange and ProjectConcert. Some are neighbours in the workflow rather than substitutes for the entire business.

InPlace illustrates the division of labour. Its university software manages workplace experiences; its healthcare-side network supports placement capacity and allocation. DISA supplies compliance and screening capabilities that can connect to that placement machinery. Schools can therefore examine how the proposed setup fits their current system before deciding to replace anything.

The service layer deserves equal attention. DISA advertises dedicated migration teams, data transfer, onboarding, training and continuing support. Its leadership roster includes customer success, operations, product, engineering and compliance responsibilities. In this market, the apparently small question of who answers a student’s problem can affect whether a placement starts on time.

The lesson hiding in the checklist

The first thing likely to go wrong in this kind of handoff is agreement: two parties believe they have the same requirements until a specific document proves otherwise. That is an interpretation of the workflow, not a documented DISA outage. The company’s tools address the discrepancy by making requirements, evidence and current status visible.

There is a lesson here that any program can copy. Define the receiving site’s requirements before collecting documents. Give exceptions an owner. Put renewals on the calendar. Tell students which package to order and what costs sit outside it. Software becomes more useful when the institution has already decided what a satisfactory answer looks like.

Limits remain quite concrete. DISA’s FAQ says the institution makes admission decisions; the screening provider supplies information. A background report reflects its completion date, and the institution determines how recent it must be. A compliant profile cannot create hospital capacity, provide a preceptor or settle a disagreement about a placement rule. If those are the constraints, a cleaner dashboard alone will not resolve them.

For students, the sensible starting point is their program’s instructions and the correct myCB or Complio support route. For administrators, it is a demonstration using their own requirements and clinical-site handoffs. The result worth purchasing is a student whose evidence reaches the right people in time. Paperwork is rarely the reason someone enters nursing. It can still decide when they enter the ward.