UNC moves SARHAchat to OpenShift AI and cuts its model from 500B-plus to 20B parameters

The University of North Carolina has moved its Sexual and Reproductive Health Assistant, SARHAchat, onto Red Hat OpenShift AI and reduced the model behind the service from more than 500 billion parameters to 20 billion, according to a Red Hat case study published September 16.

Red Hat says the university team and the vendor established a working prototype on OpenShift AI in two weeks. The result is a concrete example of an enterprise AI migration in which the operational change is not simply a lift-and-shift: the team also replaced a much larger general-purpose model with a smaller model intended to improve efficiency and response time.

A smaller model, with platform controls

The case study says OpenShift AI gives the project greater stability, scalability and control over data as the service expands. It also says the architecture includes safety measures and supports uninterrupted transitions between informational and consultative modes, a behavior the team had previously found difficult to implement.

That distinction matters for a healthcare assistant. A conversational interface that supplies general information and one that moves into more consultative interaction do not carry the same expectations or risk. The published material does not provide enough detail to independently assess those safeguards, and Red Hat presents the performance and maintainability outcomes as customer and vendor claims rather than independently benchmarked results.

Still, the reported parameter reduction is substantial. Model size alone does not determine quality, latency or cost, but moving from a model above 500 billion parameters to one at 20 billion changes the infrastructure envelope and can make inference easier to operate. Red Hat says the smaller foundation increased efficiency and response speed while making the system easier and more cost-effective to maintain.

What platform teams can take from it

For platform teams, the useful signal is the combination of model selection and deployment controls. The case study describes a migration that paired a smaller model with a managed AI platform, data-control requirements and application-level safety behavior rather than treating model choice as an isolated decision.

The public case study does not disclose measured latency, throughput, accuracy, hardware use or production traffic, so it should not be read as a benchmark. It does show, however, that a university healthcare project was able to turn an OpenShift AI migration into a working prototype in two weeks and narrow its model footprint at the same time.