The person’s context
A task can feel very different under time pressure or on a shared device. Begin with the circumstances around the interaction.
A person can encounter several systems while trying to answer one simple question. The health perspective starts with that experience: what someone needs to understand, what they can do next and where a careful connection could reduce effort.
Health work can involve people receiving care, people coordinating it and the systems that hold the information. The challenge is to preserve meaning as the question moves between them. NRTH Health explores that experience alongside the software and research questions around it.
Open a context to see the connections it brings into focus.
A health question connects a person, understandable information and an appropriately supported next step.
Context in viewSomeone needs to understand what comes next
A map of the questions around the work. It illustrates relationships rather than a live service or an existing product integration.
A person has information in front of them, but the terminology, order or navigation makes the next practical step difficult to find.
Define the question in the person’s own terms before deciding what an interface should show.
Bring the question, the setting in which it arises and a sample of the information. The objective is comprehension, not more content.
Several people are involved in a coordination task. A handoff can lose its purpose when ownership and the outstanding question are unclear.
Identify what must remain visible when the task changes hands, including who can resolve it.
Map one real handoff, including the exceptional case. That reveals more than a generic diagram of an ideal care journey.
Someone encounters a device, language, navigation or permissions barrier before reaching the information they need.
Distinguish the access requirement from assumptions about how someone will interact with it.
Describe the access conditions and test them early. Accessibility and appropriate permissions affect the shape of the whole experience.
A task can feel very different under time pressure or on a shared device. Begin with the circumstances around the interaction.
Information is useful when the reader can interpret it. Study vocabulary, hierarchy and the relationship to the next decision.
Information boundaries and role responsibilities need to be understood before a workflow is connected.
Distinguish an interface study from a clinical application. Intended use determines the evidence and review that would be needed.
These venture directions bring distinct perspectives to health questions. Their relationship is a way to frame the conversation; current scope is confirmed separately.
Considers the person’s question, the information around it and the coordination involved in everyday care.
Explore the ventureBrings a perspective on access boundaries, information exchange and workflows that span several tools.
Explore the ventureOffers a research perspective on testing assumptions about comprehension, navigation and interaction.
Explore the ventureThis page describes NRTH’s area of inquiry. It does not provide care, medical advice or a claim about clinical performance. Any clinical application would need its own defined scope, evidence and appropriate review.
Yes. Describe the task, the people involved and the point where understanding or responsibility becomes difficult. An anonymized example can support an initial conversation.
A process description, intended audience and constraints are useful. Avoid sending personal health information through the general contact form.
A possibility you see.
A problem worth solving.
We would like to hear it.