A little space to think about making care better.

Meet Aroha. Her cancer journey unfolds over months: treatment planning, chemotherapy, recovery and follow-up. This fictional story uses real PulseMD screens at Te Awa Health. At hospital, Aroha can start with something as simple as a QR code. This is an existing patient feedback code for the Oncology Day Unit. Scanning it opens the hospital's feedback experience in a phone browser. There is no app to download. The public feedback code is an entry point for service feedback. It does not unlock a private patient record or enrol someone in identified care. The provider chooses the capabilities relevant to its services: real-time feedback, scheduled Heartbeat check-ins, care-team follow-up and requests for contact. Aroha encounters these through the appropriate patient experience or care invitation. During treatment, Aroha wants to explain a mixed experience. The nurses have been wonderful, but she was unsure who to contact when her treatment appointment changed. She types the observation in her own words. She continues, chooses anonymous and shares the signal. Here is the recorded submission and its receipt from our fictional demo. Her name is not attached through this pathway, and the comment does not become an entry in her identified Care record. People should still avoid putting identifying details in the words they submit; choosing anonymous cannot make identifying content anonymous. This existing oncology theme brings together concerns about waiting for chemotherapy. This is a separate example; we are not claiming Aroha's comment has already joined it. PulseMD supports AI-assisted themes with human review. This curated demonstration uses reviewed theme wording. Now follow Aroha home between visits. Her chemotherapy programme offers a Heartbeat every seven days. Before taking part, the patient can see the purpose, who reads the answers, the team's review hours and urgent-help instructions. Saying no does not change her care. Let's complete the questionnaire using the product's patient preview. We are replaying Aroha's existing week-one answers, without saving another response. First: how much has nausea affected her this week? Aroha chooses somewhat, then moves on. Next: how tired has she felt? She chooses a little tired. Then she answers the third question: how is she managing eating and drinking? This week, the answer is well. Before completing the check-in, Aroha reviews all three answers. She sends the check-in to the team and sees a receipt explaining when it should be reviewed. Several weeks later, the same questions tell a different story. In week four, nausea is affecting Aroha a lot. She selects very tired, and says eating and drinking are okay. She reviews those answers, asks for contact and completes the preview check-in. For the authorised care team, Aroha's actual record brings her answers together over time. Week one and week four can be compared directly. The missed check-in in week two remains visible as well. Staff can consider the sequence rather than treating each questionnaire as an isolated response. Aroha's record already includes a follow-up owned by Aisha Rahman. Staff can review the concern, record a contact attempt and its outcome, and keep the next step visible. Here we open that workflow without saving a new attempt. The team decides what follow-up is appropriate. Aroha can also ask for help with a practical concern. In this separate patient-preview example, she requests an afternoon call and explains that she feels overwhelmed and is unsure who to speak to about her next appointment. The working request form and confirmation show how she can ask the team for contact. This illustration is separate from her saved check-in history. For urgent symptoms or emergencies, Aroha still follows her provider's established clinical pathways. PulseMD complements clinical records, assessment and monitoring. Patient Experience leaders need a wider perspective. Across participating services, themes and trends help them explore recurring concerns, positive experiences and changes over time. In this separate existing example, an equipment issue has owners, tasks and a review, making the organisational response visible. The regional view brings Te Awa's participating hospitals and services into one organisational picture. This is a view within one fictional organisation, not unrestricted sharing of identified patient histories. It can complement surveys, complaints and other feedback processes with a more continuous source of experience information. Return to Aroha. Three perspectives now fit together: her voice, captured simply; her care team's understanding of how her experience changes; and the organisation's ability to learn across services. From feedback at the point of care to check-ins between visits, PulseMD helps teams listen throughout the journey and turn what they hear into meaningful action.

Between appointments, a person's experience can change. A care team needs a clear way to review what they share and keep the next step visible. This is a demonstration of PulseMD Care using fictional people and illustrative data. Start with the heart failure team's caseload. It brings together the reason someone needs attention, the person responsible, the due time and their check-in history. The team's review hours are shown here too. These are patient-reported check-ins, reviewed through the service's arrangements. Wiremu's response has triggered an urgent follow-up under a configured rule. Open his record and the context stays with him: who answers, his programme, the responsible clinician and the review hours. Ben is responsible, and the follow-up is already in progress. In Check-ins and scores, we can read the actual answers. Wiremu says he feels worse and reports breathlessness lying flat or at night. The screen preserves his response to the contact question as well. A rule helps route the response for human review; it does not make a diagnosis or decide treatment. Now open Follow-ups. Ben has recorded a phone call with no answer, and a note that he will try the landline next. That distinction matters. An attempted call is part of the record, while the follow-up remains in progress. The contact form gives the team a place to record what happened and the next step. Here we are previewing that workflow. We are not making a call or recording a new clinical outcome. Back on the person record, responsibility and the outstanding follow-up remain visible. The team can return to the same context instead of reconstructing it from separate notes and messages. PulseMD Care supports that continuing relationship: hear what the person reports, review it in context and organise follow-up. The service sets its response process and coverage. Stay connected between visits.

A care programme needs more than a set of questions. It needs a purpose, a schedule, people who will review the answers, and a clear account of what its results mean. This walkthrough uses Te Awa Health’s fictional heart failure recovery programme. Its symptom score and results are illustrative, not a claim about a validated clinical measure or customer outcomes. The programme page brings participation and current work together. People remain on the version they joined. A published version can be in use while changes are being prepared in a draft. The cohort shows check-in history and any reason for attention, linking the programme design to the team’s everyday work. Open the existing draft to see the design steps. The programme begins with a template, then covers who joins, anchors and timepoints, measures, review rules, messages and review hours. The participant preview sits alongside the configuration. That lets the team connect each design decision with what a person will actually see. The published schedule uses discharge as its anchor. It asks at discharge, six weeks, three months and six months. Each point has an answer window, and the primary comparison is identified. The table shows which measure, heartbeat and custom questions are included, together with the expected effort. Timing is part of the meaning of the result, not just a reminder setting. Review and rules define how the team handles responses. Here the mode is every response read. The configured rules include a request for contact, breathlessness at night, and a change in the symptom score. Clinical rules show a named approver and a review date. An operational rule covers repeated closed windows without an answer. These rules create work for people; they do not replace clinical judgement. Review hours and routing belong to the care team. The programme’s participant wording explains who reads answers, while urgent-help information remains visible. A service needs a workable review commitment, including what happens outside those hours. The software makes that arrangement explicit, rather than implying that an online answer is monitored continuously. Before reading outcomes, look at response. The table separates answered, missed, not sent and skipped check-ins. In this example, the six-week and three-month windows each have fourteen answers from sixteen closed windows. A skipped check-in is excluded from the rate. A check-in that was never sent is a team-side gap, rather than a failure attributed to the person. The outcomes view starts with the funnel. Seventeen people have an in-window baseline, sixteen have reached a closed primary window, and fourteen have a paired result. That is the group the comparison describes. The chart keeps the full score scale and shows separate timepoint groups. It does not draw a continuous line that implies every point contains exactly the same people. The paired comparison shows a mean change and an uncertainty interval. The page also warns that people who answer at follow-up may differ from those who do not, and that these figures are not adjusted for case mix. Small groups are suppressed. In this demo, the numbers illustrate how a result is presented; they do not establish that the service caused a clinical benefit. Return to the cohort and the design has a practical purpose. Questions arrive at meaningful points, review arrangements are visible, and the team can see outstanding follow-up alongside participation. A programme can be refined without silently rewriting the version that existing people joined. PulseMD brings programme design, everyday response and measurement into one connected workflow. The value is a clearer account of what was asked, who was heard, what the team did, and what the resulting evidence can support.

An equipment problem may start as one observation. When it keeps happening across shifts, a team needs to see the pattern and decide what to do next. This is a demonstration of PulseMD using fictional people and illustrative data. Here, the issue is infusion pumps faulting and giving false alarms. The theme brings related observations into one place. We can see the issue, the people who raised it, and the work already under way. Open the supporting signals to hear the detail. Staff describe pumps stopping during infusions, equipment that is difficult to find in working order, and faults that need attention. Those words give the team context for a decision. In this showcase, theme naming uses a curated demonstration assist. The useful story is how people review the issue and follow it through. On the overview, responsibility is visible. Priya owns the work. The intended result is specific: infusions running without false alarms or failures. The completed tasks record the practical steps, including agreeing the swap with biomedical engineering and training charge nurses on the new pumps. Next, look at the improvement work and its review. Finishing a task and checking its effect are separate steps. The record keeps the change, evidence and review together, so another person can understand what happened and what still needs attention. The timeline also includes a frontline update. It connects what staff reported with the team's response. These are illustrative results, rather than evidence of customer impact. A fall in signals still needs interpretation: fewer reports can reflect a change in the service, or a change in who is speaking up. That is the path PulseMD makes visible: a shared observation, a reviewable theme, owned work and a considered update. Hear what matters. Follow through on care.