logo
Insights

Medical software design: what really matters is not more features, but making every decision safer

Today, more and more healthcare services are being reorganized by software.

Appointments, visits, medical records, doctor's orders, care, examinations, follow-up, and even diagnosis and treatment decisions may be made through a digital interface. For ordinary software, a design error may only allow users to take one more step. However, in a medical scenario, a neglected abnormal data, a unit of measurement that is easy to confuse, and a wrong patient selection may have consequences far beyond the screen.

Therefore, to evaluate whether a medical software is excellent, one cannot only look at how many functions it has, nor can one only look at whether the interface is simple and the operation is smooth. The more important question is:

Can it help the right people make safer decisions at the right time and make the whole process verifiable, traceable and recoverable?

This should be the starting point for medical software design.

 

1. define boundaries before you start designing

 

"Medical software" is not a single category.

Hospital management systems focus on appointments, fees, inventory and scheduling; clinical work systems carry medical records, doctor's orders, care and examinations; patient-side product connection follow-up, health management and medication reminders; and clinical decision support systems may provide risk scores, diagnosis and treatment recommendations or early warnings. Further forward, there are auxiliary diagnosis, vital signs monitoring, treatment control and various medical AI products.

Different products seem to handle medical information, but bear completely different responsibilities.

A page that displays health knowledge and an algorithm that affects a doctor's diagnosis cannot use the same set of product standards. The closer the output of the software is to diagnosis, treatment and patient safety, the more stringent its design, validation, change and regulatory requirements.

Therefore, before discussing the page, function and technical architecture, the team must first clarify three questions: who the software serves, which medical process is involved in, and what consequences the error output may bring.

Once the product boundary is blurred, the subsequent experience design, authority system, risk control and compliance work will lose the accurate basis.

 

The starting point of 2. medical experience design is not a list of requirements, but a list of risks.

 

Traditional product design often starts from "what the user wants to accomplish. Medical software also needs to ask one more step: What happens when a user makes an error, a data anomaly, or a system failure?

For example:

  • Is it possible to choose the wrong patient?
  • Is it easy to confuse dose, unit, time, or left and right sides of the body?
  • Does the system still give conclusions when data is missing, delayed, or out of date?
  • Can critical work continue after a network outage or external interface failure?
  • Can the user undo the wrong operation and does the system keep the records before and after the modification?
  • When a AI gives wrong advice, does the person have a chance to spot it and stop it?

These issues are not additional checks that need to be added to the pre-launch testing phase, but should be directly involved in the formation of product structure and interaction logic.

Truly effective risk control also has a clear sequence: first try to eliminate the danger from the design; When it cannot be completely eliminated, reduce the risk through verification, interlocking, authority and protection mechanism. Warning text and personnel training should be the last line of defense, not the main solution.

For example, instead of prompting "please pay attention to patient information" in the corner of the page, it is better to keep the patient's name, identification, allergy history and current treatment status visible. Instead of frequently popping up "please operate with caution", it is better to confirm with context only at high-risk nodes.

Security is not adding a prompt icon to the page, but making errors more difficult to occur and making exceptions easier to find.

3. design should be around clinical workflows, not functional menus

One of the most common problems with medical software is the translation of organizational or functional modules directly into navigation menus, ignoring the user's real work process.

Doctors, nurses, inspectors and patients are never isolated functions. They are faced with a task that is contextual, time-stressed, and constantly interrupted.

A nurse may wear gloves and complete information verification during ward movement. An emergency doctor may need to read multi-source data in a very short time. Test results may come from LIS, images from PACS, patient identity and doctor's orders from HIS. Operating procedures established under normal conditions may not be available at all in emergency conditions.

As a result, medical UX can't just be done in a conference room relying on flowcharts. The design team needs to enter the real scene and observe what equipment users use, what environment they work in, where the information comes from, where they pause, what actions are repeated, and what information is easily missed.

The focus of design optimization is not to pursue "one click less" mechanically ". A meaningful check-up may be safer than a one-step direct. What should really be reduced is repeated entry, meaningless jump, repeated search and lack of context confirmation.

Good workflow design allows information to appear naturally when needed, allows key actions to occur at the right nodes, and allows different roles to maintain clear collaboration in the same medical link.

 

4. medical interfaces must make critical information more visible and less likely to be misunderstood

 

In ordinary consumer products, the interface can emphasize emotion, exploration and personality; in the medical system, visual expression first assumes the responsibility of identification, judgment and error prevention.

A piece of medical data should not be just a number. It also needs to explain the unit, reference range, collection time, data source and whether it has been audited. Anomaly results cannot rely solely on color, as color can be affected by the environment, the device, and the visual capabilities of the user. Similar drug names, similar patients, different dosage forms and units of measurement need to establish sufficiently clear differences through the information structure.

The interface should also answer several questions on an ongoing basis:

  • Which patient's data are you currently seeing?
  • Is the data complete, up-to-date and credible?
  • Is this a fact recorded by the system, an inference generated by the model, or a judgment made by the medical staff?
  • Who created or modified this content and when?
  • If a commit fails, information conflicts, or the system goes offline, what should be done next?

This means that the medical interface cannot be designed only to be "ideal". Loads, failures, offline, insufficient permissions, data conflicts, and degraded runs are also part of the complete experience.

This is especially true of alarm design. More alerts do not necessarily lead to higher security. A large number of low-value, recurring reminders can create alarm fatigue, causing users to gradually ignore the really important information. A high-quality alert system should be stratified according to risk level, clinical context and enforceability, and clearly tell the user what happened, why it is important, and what actions can be taken now.

 

5. medical AI should not be just a chat window

 

AI are entering scenarios such as medical record generation, image recognition, risk prediction, knowledge retrieval, and clinical decision-making. But the big model into a dialog box, does not mean that the completion of the medical AI product design.

A medical AI should first be a system component that can be identified, limited, and supervised.

Users need to know what input data the model uses, when the data comes from, what the conclusions are based on, what scope they apply to, and what are the known limitations. When the input is incomplete or the model has insufficient confidence, the system should explicitly prompt uncertainty instead of continuing to output seemingly complete answers.

At the same time, the model version, knowledge base version, call records, manual confirmation and modification should be retained. After the AI-generated content enters the medical record, it should also be clearly distinguished from the manual content to avoid the machine inferring the clinical facts that have been mistaken for confirmation in the circulation.

For high-risk results such as diagnosis, doctor's orders, dosage, etc., the generation ability cannot be directly connected to the execution ability. Structured rule verification, indications and contraindications, authority control, and clear manual approval are all necessary safety boundaries.

In other words, the core competitiveness of the medical AI is not just "whether the answer is like an expert", but whether the system can correctly express its ability boundaries and maintain control in human-computer cooperation.

 

6. privacy and security is not a back-office issue, but part of the product experience

 

Healthcare information is highly sensitive. Once the data is abused or leaked, the impact is not only the account security, but also the dignity of patients, social relations and real rights and interests.

Therefore, privacy and security cannot be handed over to technology or legal supplement after the product is completed, but must enter the product architecture and service process.

The system should minimize unnecessary data collection, assign permissions based on position, institution, and patient relationships, protect transmission and storage procedures, and set stricter controls on export, sharing, batch query, and sensitive field access. Data retention, deletion, backup, disaster recovery and security incident response also need to be specified during the product design phase.

Audit ability is an important basis for the credibility of the medical system. A complete set of records should be able to answer: who viewed or modified what data for which patient when; What changes before and after the modification; What permissions are based on this behavior; Can the process be restored after a problem occurs.

For users, security does not mean barriers. Good permissions and security design should make unreasonable access more difficult and leave clear evidence of high-risk behavior without interrupting normal work.

7. move from "delivery function" to "delivery evidence"

Ordinary software often uses "whether the function is completed" to judge the progress of the project. Medical software must also demonstrate why it is trustworthy.

The team needs to establish a chain of evidence throughout the product life cycle:

Clinical demand → product demand → risk → design → implementation → testing → release version → online monitoring

Each high-risk requirement should have corresponding control measures, and each control measure should be verified. Key algorithms need to demonstrate expected performance, target users need to complete key tasks in a near-real-world environment, and each feature or model change needs to assess what processes, risks, and validation results it may affect.

This will change the team’s understanding of the design deliverables. Prototypes are not only used to render pages, but also to verify key tasks. Design specifications not only unify vision, but also explain status, permissions and exception rules. User testing not only focuses on "whether you like it", but also confirms whether users can correctly understand information, complete tasks and safely recover from errors.

For medical software, design is not a beautification before development, but a core process that connects clinical needs, risk management, technology implementation and validation evidence.

 

Conclusion: Security comes from a visible order.

 

Medical digitization is advancing rapidly, but the truly outstanding products often do not win by the number of functions.

It can keep the identity clear, keep the data with time and source, and separate the system facts from the model inference. It can prevent errors before they occur, help users detect anomalies when they occur, and provide a safe retreat after system failure. It also allows every important decision to be explained, traced and verified.

Ultimately, we can revisit a medical software with five questions:

  1. Does it improve definitive clinical outcomes or productivity?
  2. When a user makes a mistake, can the system prevent it, detect it, or help it recover safely?
  3. Is each important conclusion explainable and traceable?
  4. Can medical work continue safely when systems or AI fail?
  5. Does the product have sufficient evidence that it is safe, effective and continuously controlled?

In STOYARD view, the value of medical software design is to establish a clear order between complex technology, clinical tasks and human judgment. Vision, interaction, content and technology are not independent links. They together determine whether information can be accurately understood, risks can be identified in time, and trust can be truly established.

Really good medical software doesn't just help people get things done.

 

 

It should also help people do important things right.


References