<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Data &#8211; BES International | Better Health Through Emerging Technologies</title>
	<atom:link href="https://www.bes.au/tag/data/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.bes.au</link>
	<description></description>
	<lastBuildDate>Thu, 20 Aug 2026 05:24:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.7</generator>
	<item>
		<title>Unifying health data across the four Federated States of Micronesia</title>
		<link>https://www.bes.au/unifying-health-data-across-the-four-federated-states-of-micronesia/</link>
		
		<dc:creator><![CDATA[communications@bes.au]]></dc:creator>
		<pubDate>Fri, 07 Aug 2026 04:42:24 +0000</pubDate>
				<category><![CDATA[Our impact]]></category>
		<category><![CDATA[Data]]></category>
		<guid isPermaLink="false">https://www.bes.au/?p=5986</guid>

					<description><![CDATA[The Federated States of Micronesia are based in the western Pacific Ocean, spread across more than 600 islands and four states - Pohnpei, Kosrae, Chuuk, and Yap - with a population of 114,000 people. Health data was siloed to each of these states. What was needed  FSM had four separate instances of an [...]]]></description>
										<content:encoded><![CDATA[<div class="fusion-fullwidth fullwidth-box fusion-builder-row-1 fusion-flex-container nonhundred-percent-fullwidth non-hundred-percent-height-scrolling" style="--awb-border-radius-top-left:0px;--awb-border-radius-top-right:0px;--awb-border-radius-bottom-right:0px;--awb-border-radius-bottom-left:0px;--awb-flex-wrap:wrap;" ><div class="fusion-builder-row fusion-row fusion-flex-align-items-center fusion-flex-justify-content-center fusion-flex-content-wrap" style="max-width:1456px;margin-left: calc(-4% / 2 );margin-right: calc(-4% / 2 );"><div class="fusion-layout-column fusion_builder_column fusion-builder-column-0 fusion_builder_column_1_1 1_1 fusion-flex-column" style="--awb-bg-blend:overlay;--awb-bg-size:cover;--awb-width-large:100%;--awb-margin-top-large:0px;--awb-spacing-right-large:1.92%;--awb-margin-bottom-large:0px;--awb-spacing-left-large:1.92%;--awb-width-medium:100%;--awb-spacing-right-medium:1.92%;--awb-spacing-left-medium:1.92%;--awb-width-small:100%;--awb-spacing-right-small:1.92%;--awb-spacing-left-small:1.92%;"><div class="fusion-column-wrapper fusion-flex-justify-content-flex-start fusion-content-layout-column"><div class="fusion-text fusion-text-1" style="--awb-content-alignment:center;--awb-margin-right:40px;--awb-margin-left:40px;"><h2>The Federated States of Micronesia are based in the western Pacific Ocean, spread across more than 600 islands and four states &#8211; Pohnpei, Kosrae, Chuuk, and Yap &#8211; with a population of 114,000 people. Health data was siloed to each of these states.</h2>
</div><div class="fusion-title title fusion-title-1 fusion-sep-none fusion-title-text fusion-title-size-four" style="--awb-margin-top:50px;"><h4 class="fusion-title-heading title-heading-left fusion-responsive-typography-calculated" style="margin:0;--fontSize:28;line-height:1.36;">What was needed</h4></div><div class="fusion-text fusion-text-2"><p>FSM had four separate instances of an electronic health record (EHR) system. Built on MySQL, patient&#8217;s health data flowed between the main hospital on-island, and with clinics and dispensaries on outer islands. What was needed was a unified health record to support continuity of care across the vast geographic region. A patient’s health data would not follow them if they transferred to another state’s hospital. BES worked closely with FSM&#8217;s Ministry of Health and Social Affairs to implement a complete migration from FSM’s legacy EHR to <a href="https://www.bes.au/products/tamanu/">Tamanu</a> (PostgreSQL).</p>
</div><div class="fusion-image-element awb-imageframe-style awb-imageframe-style-below awb-imageframe-style-1" style="text-align:center;--awb-aspect-ratio:2 / 1;--awb-margin-top:50px;--awb-caption-title-font-family:var(--body_typography-font-family);--awb-caption-title-font-weight:var(--body_typography-font-weight);--awb-caption-title-font-style:var(--body_typography-font-style);--awb-caption-title-size:var(--body_typography-font-size);--awb-caption-title-transform:var(--body_typography-text-transform);--awb-caption-title-line-height:var(--body_typography-line-height);--awb-caption-title-letter-spacing:var(--body_typography-letter-spacing);"><span class=" fusion-imageframe imageframe-none imageframe-1 hover-type-none has-aspect-ratio"><img fetchpriority="high" fetchpriority="high" decoding="async" width="1024" height="683" alt="health data" title="A clinician using the new national EMR Tamanu at the Pohnpei State Hospital" src="https://www.bes.au/wp-content/uploads/2026/08/A-clinician-using-Tamanu-at-the-Pohnpei-State-Hospital-1024x683.jpg" class="img-responsive wp-image-6007 img-with-aspect-ratio" srcset="https://www.bes.au/wp-content/uploads/2026/08/A-clinician-using-Tamanu-at-the-Pohnpei-State-Hospital-200x133.jpg 200w, https://www.bes.au/wp-content/uploads/2026/08/A-clinician-using-Tamanu-at-the-Pohnpei-State-Hospital-400x267.jpg 400w, https://www.bes.au/wp-content/uploads/2026/08/A-clinician-using-Tamanu-at-the-Pohnpei-State-Hospital-600x400.jpg 600w, https://www.bes.au/wp-content/uploads/2026/08/A-clinician-using-Tamanu-at-the-Pohnpei-State-Hospital-800x533.jpg 800w, https://www.bes.au/wp-content/uploads/2026/08/A-clinician-using-Tamanu-at-the-Pohnpei-State-Hospital-1200x800.jpg 1200w" sizes="(max-width: 640px) 100vw, 1024px" /></span><div class="awb-imageframe-caption-container"><div class="awb-imageframe-caption"><div class="awb-imageframe-caption-title">A clinician using the new national EMR Tamanu at the Pohnpei State Hospital</div></div></div></div><div class="fusion-builder-row fusion-builder-row-inner fusion-row fusion-flex-align-items-center fusion-flex-justify-content-center fusion-flex-content-wrap" style="width:104% !important;max-width:104% !important;margin-left: calc(-4% / 2 );margin-right: calc(-4% / 2 );"><div class="fusion-layout-column fusion_builder_column_inner fusion-builder-nested-column-0 fusion_builder_column_inner_2_3 2_3 fusion-flex-column" style="--awb-bg-size:cover;--awb-width-large:66.666666666667%;--awb-margin-top-large:0px;--awb-spacing-right-large:2.88%;--awb-margin-bottom-large:20px;--awb-spacing-left-large:2.88%;--awb-width-medium:66.666666666667%;--awb-order-medium:0;--awb-spacing-right-medium:2.88%;--awb-spacing-left-medium:2.88%;--awb-width-small:100%;--awb-order-small:0;--awb-spacing-right-small:1.92%;--awb-spacing-left-small:1.92%;"><div class="fusion-column-wrapper fusion-column-has-shadow fusion-flex-justify-content-flex-start fusion-content-layout-column"><div class="fusion-text fusion-text-3" style="--awb-margin-top:40px;"><h4>What we did</h4>
<p>The migration needed to be deliberately staged: state by state, and dataset by dataset. Starting with three of FSM&#8217;s four states (Yap, Pohnpei, Kosrae), Chuuk is the remaining state that is now underway.</p>
<p>The datasets were staged by core clinical records first, then procedures, labs, medications and imaging.</p>
<h4>How we did it</h4>
<p>First we extracted the data and reviewed it internally with no database writes. Next we migrated to a clone of the FSM environment for the MoH to verify. They say the devil is in the detail and this is where it starts to get complex. We used a record tracker to map every legacy record to its Tamanu record, solving the go-live problem: snapshot and migrate before go-live, snapshot again after, and migrate only what changed in the gap. Nothing lost, nothing duplicated.</p>
<p><span style="background-color: rgba(0, 0, 0, 0);">The tracker also lets us keep building, attaching labs, medications and imaging onto patients and encounters migrated months earlier.</span></p>
<p style="text-align: left;">Finally we migrate to production after sign off, with two independent review gates. We profiled the source data for quality before and after transformation. AI also assisted matching mapped legacy free text procedures and medications onto standard code lists followed by human reviews.</p>
</div></div></div><div class="fusion-layout-column fusion_builder_column_inner fusion-builder-nested-column-1 fusion_builder_column_inner_1_3 1_3 fusion-flex-column" style="--awb-bg-size:cover;--awb-width-large:33.333333333333%;--awb-margin-top-large:31px;--awb-spacing-right-large:5.76%;--awb-margin-bottom-large:0px;--awb-spacing-left-large:5.76%;--awb-width-medium:33.333333333333%;--awb-order-medium:0;--awb-spacing-right-medium:5.76%;--awb-spacing-left-medium:5.76%;--awb-width-small:100%;--awb-order-small:0;--awb-spacing-right-small:1.92%;--awb-spacing-left-small:1.92%;"><div class="fusion-column-wrapper fusion-column-has-shadow fusion-flex-justify-content-flex-start fusion-content-layout-column"><div class="fusion-text fusion-text-4"><h2 style="text-align: center;">Around 128,000 patients and 530,000 clinical encounters migrated across the three completed states, with records dating back to 2018.</h2>
</div></div></div></div><div class="fusion-image-element awb-imageframe-style awb-imageframe-style-below awb-imageframe-style-2" style="text-align:center;--awb-margin-top:50px;--awb-caption-title-font-family:var(--h2_typography-font-family);--awb-caption-title-font-weight:var(--h2_typography-font-weight);--awb-caption-title-font-style:var(--h2_typography-font-style);--awb-caption-title-size:var(--h2_typography-font-size);--awb-caption-title-transform:var(--h2_typography-text-transform);--awb-caption-title-line-height:var(--h2_typography-line-height);--awb-caption-title-letter-spacing:var(--h2_typography-letter-spacing);"><span class=" fusion-imageframe imageframe-none imageframe-2 hover-type-none"><img decoding="async" width="1024" height="751" alt="health data" src="https://www.bes.au/wp-content/uploads/2026/08/DSCF0475-1-1024x751.jpg" class="img-responsive wp-image-5999" srcset="https://www.bes.au/wp-content/uploads/2026/08/DSCF0475-1-200x147.jpg 200w, https://www.bes.au/wp-content/uploads/2026/08/DSCF0475-1-400x293.jpg 400w, https://www.bes.au/wp-content/uploads/2026/08/DSCF0475-1-600x440.jpg 600w, https://www.bes.au/wp-content/uploads/2026/08/DSCF0475-1-800x587.jpg 800w, https://www.bes.au/wp-content/uploads/2026/08/DSCF0475-1-1200x880.jpg 1200w" sizes="(max-width: 640px) 100vw, 1024px" /></span><div class="awb-imageframe-caption-container"><div class="awb-imageframe-caption"><p class="awb-imageframe-caption-text">Two thumbs up! A dental technician from the dental clinic at Pohnpei State Hospital rates Tamanu.</p></div></div></div><div class="fusion-title title fusion-title-2 fusion-sep-none fusion-title-text fusion-title-size-four"><h4 class="fusion-title-heading title-heading-left fusion-responsive-typography-calculated" style="margin:0;--fontSize:28;line-height:1.36;">Outcomes in health data migration</h4></div><div class="fusion-builder-row fusion-builder-row-inner fusion-row fusion-flex-align-items-center fusion-flex-justify-content-center fusion-flex-content-wrap" style="width:104% !important;max-width:104% !important;margin-left: calc(-4% / 2 );margin-right: calc(-4% / 2 );"><div class="fusion-layout-column fusion_builder_column_inner fusion-builder-nested-column-2 fusion_builder_column_inner_1_1 1_1 fusion-flex-column" style="--awb-bg-size:cover;--awb-width-large:100%;--awb-margin-top-large:26.9805px;--awb-spacing-right-large:1.92%;--awb-margin-bottom-large:20px;--awb-spacing-left-large:1.92%;--awb-width-medium:100%;--awb-order-medium:0;--awb-spacing-right-medium:1.92%;--awb-spacing-left-medium:1.92%;--awb-width-small:100%;--awb-order-small:0;--awb-spacing-right-small:1.92%;--awb-spacing-left-small:1.92%;"><div class="fusion-column-wrapper fusion-column-has-shadow fusion-flex-justify-content-flex-start fusion-content-layout-column"><div class="fusion-text fusion-text-5"><p><b style="background-color: rgba(0, 0, 0, 0);">Continuity of care:</b></p>
<p>A clinician can open Tamanu from any state, with any patient’s history in place. This allows for a greater continuity of care from day one, strengthening the delivery of, and resulting in improved health outcomes of FSM’s public healthcare.</p>
<p><b>Data quality:</b></p>
<p>The aim was to leave data in better shape than we found it, and that has been achieved. Questionable records are now flagged to be addressed. There is also now eight-plus years of history available in Tamanu, including its in-product reporting. Every mapping and import is audited, enabling safe re-runs and targeted fixes.</p>
<p><b>Operational efficiency:</b></p>
<p>Change detection means each re-run only touches the records that have actually changed, so revisiting a state does not mean repeating the whole migration. Because this is one codebase with per-state configuration, each new state costs less to bring on than the last, and the pattern itself now doubles as a reusable playbook for future full EMR migrations.</p>
<p><b>No interruption to care:</b></p>
<p>Migrations of this size usually mean a maintenance window. Neither the legacy systems nor Tamanu was taken offline here. Extraction was read-only, so the legacy systems kept serving clinicians while we worked. On the Tamanu side, our importer was built to understand how Tamanu distributes data between its central server and each facility. Rather than loading records in one place and waiting for them to propagate across island internet links, we wrote to the central server and the state facility server together, marking each record so that Tamanu&#8217;s synchronisation treats it as already settled. Batches were small enough to keep the system responsive, and every import is repeatable.</p>
</div></div></div></div><div class="fusion-text fusion-text-6"><h4>What the future holds</h4>
</div><div class="fusion-text fusion-text-7"><p><span style="background-color: rgba(0, 0, 0, 0);">Now that the health data is unified in a central database, we can expand into automated data analysis. This includes bringing in Tupaia, a health data visualisation tool, for visualising the health data, which updates regularly using an automated data pipeline.</span></p>
</div><div class="fusion-text fusion-text-8" style="--awb-margin-top:20px;"><p><strong>Thank you</strong></p>
<p>None of this would be possible without our donors and partners, including the <a href="https://www.dfat.gov.au/" rel="nofollow noopener" target="_blank">Australian Department of Foreign Affairs and Trade</a> through the Global Health Division and <a href="https://indopacifichealthsecurity.dfat.gov.au/partnerships-healthy-region" rel="nofollow noopener" target="_blank">Partnerships for a Healthy Region (PHR)</a> and the <a href="https://hsa.gov.fm/" rel="nofollow noopener" target="_blank">Federated States of Micronesia&#8217;s Department of Health and Social Affairs.</a></p>
<p>Congratulations to the local health information and IT teams in FSM who are leading the broader project, and to everyone at BES across FSM, Fiji, New Zealand, and Australia who supported them to get here.</p>
</div></div></div></div></div>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Anatomy of a digital health Go-Live</title>
		<link>https://www.bes.au/anatomy-of-a-digital-health-go-live/</link>
		
		<dc:creator><![CDATA[Michael]]></dc:creator>
		<pubDate>Tue, 14 Jul 2026 11:24:58 +0000</pubDate>
				<category><![CDATA[Our impact]]></category>
		<category><![CDATA[Data]]></category>
		<category><![CDATA[Tamanu]]></category>
		<guid isPermaLink="false">https://www.bes.au/?p=5888</guid>

					<description><![CDATA[Anatomy of a Go-Live Last week, Tamanu EMR went live across all inpatient departments at TTM Hospital in Samoa. Nineteen wards and departments came online on the same day, across more than 300 staff, with usage increasing for workflows across the week. It was the biggest single-day go-live for a digital health project in the [...]]]></description>
										<content:encoded><![CDATA[<p><strong>Anatomy of a Go-Live</strong></p>
<p>Last week, Tamanu EMR went live across all inpatient departments at TTM Hospital in Samoa. Nineteen wards and departments came online on the same day, across more than 300 staff, with usage increasing for workflows across the week. It was the biggest single-day go-live for a digital health project in the Pacific this year, and the culmination of 12 months of work.</p>
<p>For anyone outside the digital health sector, a &#8220;go-live&#8221; might sound like flipping a switch. In reality, it is closer to a small, carefully choreographed operation, and one that looks very different depending on where in the world it happens.</p>
<p><strong>The basics</strong></p>
<p>The formula we aim for is always the same… after months of build-up, the Go-Live team arrives at the hospital in the week leading up to the big day. This is comprised of an international team from BES, put together with a local team of Change Champions from (in this case) Samoa. The team will wear high-vis vests throughout the week and be stationed throughout the hospital supporting staff, answering questions and identifying issues. Any problems are shared via messaging apps with the control room, staffed by a senior Project Manager and local IT staff. In Samoa, we supplemented this with a ‘virtual’ control room based in Suva, who were on rotation with one staff member allocated full-time to Samoa throughout the entire week.</p>
<p>The night before, the team meets for pizza and a final walk-through of the hospital, testing equipment and network access. Ribbons and balloons go up, the final ‘thumbs up’ decision is taken, senior staff are informed and at 6am on the day of Go-Live, Tamanu blinks to life.</p>
<p>Smooth sailing? Never! But with the right resourcing, calm staff and a lot of laughter, everything is manageable.</p>
<p><strong>Go-lives are not the same everywhere</strong></p>
<p>In a very highly-resourced hospital system, a go-live might come with a budget in the millions, a dedicated project office, and months of parallel running between old and new systems. In the Pacific, that model simply does not exist, and trying to force it rarely works.</p>
<p>At TTM, the same outcome – that is, a safe, complete transition to digital records across a 200-bed tertiary hospital – has to be achieved with a fraction of the resourcing. Every hour of planning has to count, every risk has to be understood in context and anticipated in advance and the people on the ground have to be trusted to make real-time decisions when something doesn&#8217;t go to plan. Lower-resourced does not mean lower-standard. It means different, and it means smarter.</p>
<p><strong>People who understand context matter more than credentials</strong></p>
<p>One of our clearest lessons from years of Pacific go-lives is that technical skill alone does not get you through the experience. The staff who make the biggest difference during a go-live are the ones who have worked in similar clinical and public health environments before, and who understand what it means to run a busy ward with limited staff, intermittent power, or a shared laptop between three nurses. Air conditioners leak, members of the public might have greater access to sensitive areas of the hospital, family priorities can pull crucial staff away at inopportune times, rain sometimes falls inside the building, rats chew through cables in the ceiling… none of those are a crisis, that’s just a normal Monday.</p>
<p>Placing people with that lived experience alongside local teams changes the dynamic of a go-live entirely. It is the difference between a support person who can only follow a script and one who can look at a ward at 7am and immediately understand what is about to go wrong, keep their sense of humour, roll up their sleeves and just help.</p>
<p><img decoding="async" class="aligncenter size-full wp-image-5895" src="https://www.bes.au/wp-content/uploads/2026/07/IMG_8937.jpg" alt="" width="2100" height="1576" srcset="https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-200x150.jpg 200w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-300x225.jpg 300w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-400x300.jpg 400w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-600x450.jpg 600w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-768x576.jpg 768w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-800x600.jpg 800w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-1024x768.jpg 1024w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-1200x901.jpg 1200w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937-1536x1153.jpg 1536w, https://www.bes.au/wp-content/uploads/2026/07/IMG_8937.jpg 2100w" sizes="(max-width: 2100px) 100vw, 2100px" /></p>
<p><strong>Local teams lead, we support</strong></p>
<p>It is easy to frame a go-live around the visiting support staff. But the truth is that these projects are led by local health information and IT teams, not by BES. Our staff are there to back them up, not to run the show.</p>
<p>That distinction matters throughout the months of preparation before a go-live, and just as much on the day itself. The relationship with local teams, built over months of requirements gathering, configuration, testing, and training, is what allows a go-live to hold together under pressure. Without that trust, no amount of external support can make up the difference.</p>
<p><strong>No half measures</strong></p>
<p>Perhaps the hardest lesson to apply, and the easiest to get wrong, is that a go-live has to be all-in. If clinical data is allowed to move back and forth between paper and digital systems, even temporarily, the project is in trouble. Staff quickly learn which system is &#8220;real,&#8221; duplicate records creep in, and the continuity of care the system was meant to improve starts to break down instead.</p>
<p>At TTM, that meant a genuine cut-over. By the end of week one, every incoming patient had a fully digital experience, with handovers, triage, bed management, clinical care, and clinical administration all running through Tamanu. There is no fallback to paper.</p>
<p>Of course, there are still paper workflows in the hospital – forms that were missed, practices which are hard to break, departments which are more complex than others. That’s why the Go-Live isn’t the end of the story, it’s just the start. There are still months of work ahead, making sure that the new systems adapt to the workflows (and vice versa) until everything works seamlessly.</p>
<p><strong>A genuinely regional effort</strong></p>
<p>Last week’s go-live was also a reminder of how connected the Pacific digital health workforce has become. Staff from New Zealand, Fiji, Australia, and Samoa worked together on the ground and remotely, including through a virtual control room based at our regional support centre in Suva, supporting the Samoa Ministry of Health IT team in Apia.</p>
<p>This regional model matters. It means expertise built in one country&#8217;s health system can be shared with another. TTM becomes the sixth national hospital in the Pacific to implement Tamanu across all departments, and the second largest hospital to use the system. The cohort of staff that is building are mutually supporting and represent a very real peer-to-peer network which can eventually take BES out of the loop.</p>
<p><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-5891" src="https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-scaled.jpg" alt="" width="2560" height="1920" srcset="https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-200x150.jpg 200w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-300x225.jpg 300w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-400x300.jpg 400w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-600x450.jpg 600w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-768x576.jpg 768w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-800x600.jpg 800w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-1024x768.jpg 1024w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-1200x900.jpg 1200w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-1536x1152.jpg 1536w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5467-scaled.jpg 2560w" sizes="(max-width: 2560px) 100vw, 2560px" /></p>
<p><strong>Twelve months in the making</strong></p>
<p>Last week did not happen overnight. It followed 12 months of preparation, with the last four in particular given over to intensive requirements gathering, configuration, testing, and training, all underpinned by a broader change management strategy. Over the same period, the team also delivered go-lives at more than ten smaller facilities and outpatient departments across Samoa, each one building the experience and confidence that made today possible.</p>
<p>On the ground in Apia, the day itself scaled up gradually. Final hardware inspections were completed on Sunday night. On Monday morning, staff worked side by side with local teams to migrate current inpatients ahead of each critical shift change, and ward rounds were digitised progressively across the first 48 hours. Support will continue through July, starting with five BES staff on the ground and reducing progressively to one project manager as the local team takes full ownership.</p>
<p>After that, the focus shifts from go-live support to something arguably more important: using the data now being captured for evidence-based decision making and improved clinical care.</p>
<p><strong>What the data already shows</strong></p>
<p>Even before today, Tamanu&#8217;s impact in Samoa was measurable. Since the system was first introduced in 2021, more than 1.2 million encounters and 4.6 million clinical events have been recorded across Samoa&#8217;s public health facilities. More than 210,000 patients have had more than one encounter in the system, and for 74,000 of those patients, encounters spanned different facilities, a strong signal that longitudinal, connected care is genuinely happening.</p>
<p>More than 900 users now work using Tamanu, from clinicians to public health and health information staff. TTM&#8217;s go-live adds a national tertiary hospital to that picture, with 24/7 digital records now underpinning emergency care, paediatrics, ICU, and surgical theatres.</p>
<p><strong>Thank you</strong></p>
<p>None of this would be possible without our donors and partners, including the Australian Department of Foreign Affairs and Trade through the Global Health Division and Partnerships for a Healthy Region (PHR), the World Bank Group, and the Tautua Human Development for All Program, delivered by Palladium.</p>
<p>Congratulations to the local health information and IT teams in Samoa who led this project, and to everyone across Samoa, Fiji, New Zealand, and Australia who supported them to get here.</p>
<p><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-5896" src="https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-scaled.jpg" alt="" width="2560" height="1920" srcset="https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-200x150.jpg 200w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-300x225.jpg 300w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-400x300.jpg 400w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-600x450.jpg 600w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-768x576.jpg 768w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-800x600.jpg 800w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-1024x768.jpg 1024w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-1200x900.jpg 1200w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-1536x1152.jpg 1536w, https://www.bes.au/wp-content/uploads/2026/07/IMG_5560-scaled.jpg 2560w" sizes="(max-width: 2560px) 100vw, 2560px" /></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Managing patient duplicates: A comprehensive approach to data integrity</title>
		<link>https://www.bes.au/managing-patient-duplicates-with-tamanu-a-comprehensive-approach-to-data-integrity/</link>
					<comments>https://www.bes.au/managing-patient-duplicates-with-tamanu-a-comprehensive-approach-to-data-integrity/#respond</comments>
		
		<dc:creator><![CDATA[Michael]]></dc:creator>
		<pubDate>Wed, 30 Jul 2025 07:19:56 +0000</pubDate>
				<category><![CDATA[Our impact]]></category>
		<category><![CDATA[Data]]></category>
		<category><![CDATA[Tamanu]]></category>
		<guid isPermaLink="false">https://www.bes.au/?p=5146</guid>

					<description><![CDATA[Patient duplicates and data integrity in Electronic Medical Records represent far more than an administrative inconvenience—they constitute a genuine threat to patient safety and healthcare quality. When the same individual exists multiple times within a healthcare system, their medical history becomes fragmented across different records, creating dangerous gaps in clinical understanding. Healthcare providers may unknowingly [...]]]></description>
										<content:encoded><![CDATA[<p>Patient duplicates and data integrity in Electronic Medical Records represent far more than an administrative inconvenience—they constitute a genuine threat to patient safety and healthcare quality. When the same individual exists multiple times within a healthcare system, their medical history becomes fragmented across different records, creating dangerous gaps in clinical understanding. Healthcare providers may unknowingly duplicate treatments, miss critical allergies or contraindications, or fail to recognize patterns in a patient&#8217;s care history. These scenarios can lead to medication errors, unnecessary procedures, and compromised treatment decisions that directly impact patient outcomes.</p>
<p>The financial implications are equally significant. Duplicate records inflate administrative costs, create billing complications, and reduce operational efficiency across healthcare organizations. Staff spend valuable time reconciling conflicting information, while the integrity of health data analytics and population health initiatives suffers from inaccurate patient counts and scattered clinical data.</p>
<p>Recognizing these challenges, <a href="https://www.bes.au/products/tamanu">the Tamanu EMR</a> has developed a comprehensive, multi-layered approach to patient deduplication that addresses both prevention and remediation. This systematic strategy ensures that healthcare providers can maintain clean, accurate patient databases while delivering safe, coordinated care.</p>
<p>At the centre of any patient management strategy of course, are good processes and procedures, implemented by diligent staff. Tamanu can only help – we recognise though that it is the people at the heart of the system who determine its success.</p>
<p>&nbsp;</p>
<p><img loading="lazy" decoding="async" class="aligncenter wp-image-5156 size-large" src="https://www.bes.au/wp-content/uploads/2025/07/Tamanu-duplicates-683x1024.png" alt="Tackling data integrity in Tamanu" width="683" height="1024" srcset="https://www.bes.au/wp-content/uploads/2025/07/Tamanu-duplicates-200x300.png 200w, https://www.bes.au/wp-content/uploads/2025/07/Tamanu-duplicates-400x600.png 400w, https://www.bes.au/wp-content/uploads/2025/07/Tamanu-duplicates-600x900.png 600w, https://www.bes.au/wp-content/uploads/2025/07/Tamanu-duplicates-683x1024.png 683w, https://www.bes.au/wp-content/uploads/2025/07/Tamanu-duplicates-768x1152.png 768w, https://www.bes.au/wp-content/uploads/2025/07/Tamanu-duplicates-800x1200.png 800w, https://www.bes.au/wp-content/uploads/2025/07/Tamanu-duplicates.png 1024w" sizes="(max-width: 683px) 100vw, 683px" /></p>
<h4></h4>
<h4>The five Tamanu strategies for de-duplication</h4>
<p><strong>Strategy 1: Patient Master Index Integration</strong></p>
<p>The foundation of effective duplicate prevention lies in establishing a unified patient identity management system through a Patient Master Index (PMI) integration. A PMI serves as the authoritative source for patient identities across an entire healthcare network, maintaining a single, comprehensive registry of all patients served by the organization.</p>
<p>Tamanu&#8217;s PMI integration offers remarkable flexibility to accommodate diverse healthcare environments. In small to medium sized healthcare systems or those starting fresh, Tamanu can function as the primary PMI, becoming the central repository for patient identities across all connected systems and departments. This approach ensures seamless coordination between different clinical areas, from emergency departments to specialty clinics or allied health, with each patient maintaining a single, consistent identity throughout their care journey.</p>
<p>For larger healthcare networks or those with existing infrastructure investments, Tamanu can consume data from external PMI systems already in operation. This integration capability means organizations don&#8217;t need to abandon their current patient identity management investments. Instead, Tamanu synchronizes with these existing systems, ensuring consistency while leveraging established workflows and data governance practices.</p>
<p>Whether consuming data or making it available to other systems, Tamanu achieves this through an HL7 FHIR compliant API, which defines the resources and the business rules around which the data is exchanged.</p>
<p>The PMI approach creates a robust foundation for preventing duplicates at the source. By establishing unique patient identifiers that persist across all systems and encounters, healthcare organizations can eliminate the confusion that arises when patients are known by different identifiers in different departments or facilities.</p>
<p><strong>Strategy 2: ID Card System</strong></p>
<p>Physical patient identification represents a practical, user-friendly solution to many duplicate creation scenarios. Tamanu&#8217;s ID card system addresses the common registration challenges that lead to duplicate records—misspelled names, forgotten dates of birth, or variations in how patients provide their personal information.</p>
<p>The system supports both basic ID cards containing essential patient identifiers and more sophisticated photo ID cards that provide visual verification. When patients present their ID cards during registration or subsequent visits, healthcare staff can quickly and accurately retrieve their existing records without relying on potentially inconsistent verbal information. Each ID card contains a barcode, which is scanned in seconds across any part of the health system and all points of care.</p>
<p>This approach proves particularly valuable in busy clinical environments where registration staff may be working under time pressure or dealing with patients who may be distressed, confused, or unable to clearly communicate their details. The ID card system also benefits patients who frequently interact with the healthcare system, creating a streamlined experience that reduces wait times and administrative friction.</p>
<p>Furthermore, the physical ID card serves as a tangible connection between patients and their healthcare records, encouraging patients to maintain and present their identification consistently across different healthcare encounters and providers within the network.</p>
<p>&nbsp;</p>
<div id="attachment_5154" style="width: 610px" class="wp-caption aligncenter"><img loading="lazy" decoding="async" aria-describedby="caption-attachment-5154" class="wp-image-5154 size-fusion-600" src="https://www.bes.au/wp-content/uploads/2025/07/image-31-600x386.png" alt="" width="600" height="386" srcset="https://www.bes.au/wp-content/uploads/2025/07/image-31-200x129.png 200w, https://www.bes.au/wp-content/uploads/2025/07/image-31-300x193.png 300w, https://www.bes.au/wp-content/uploads/2025/07/image-31-400x257.png 400w, https://www.bes.au/wp-content/uploads/2025/07/image-31-460x295.png 460w, https://www.bes.au/wp-content/uploads/2025/07/image-31-600x386.png 600w, https://www.bes.au/wp-content/uploads/2025/07/image-31-768x494.png 768w, https://www.bes.au/wp-content/uploads/2025/07/image-31-800x514.png 800w, https://www.bes.au/wp-content/uploads/2025/07/image-31-1024x658.png 1024w, https://www.bes.au/wp-content/uploads/2025/07/image-31.png 1196w" sizes="(max-width: 600px) 100vw, 600px" /><p id="caption-attachment-5154" class="wp-caption-text">ID cards can be configured for local context and printed directly from Tamanu</p></div>
<p>&nbsp;</p>
<p><strong>Strategy 3: Real-Time Duplicate Detection</strong></p>
<p>Tamanu&#8217;s newly released real-time duplicate detection represents a significant advancement in proactive duplicate prevention. This intelligent system operates at the point of patient registration, analyzing incoming patient data against existing records using sophisticated matching algorithms that consider multiple data points simultaneously.</p>
<p>The system evaluates various criteria including name similarities (accounting for common spelling variations and phonetic matches), birth dates, contact information, and other identifying characteristics. This multi-factor analysis helps identify potential duplicates even when exact matches aren&#8217;t present, recognizing that patient information may be provided differently across various encounters.</p>
<p>One of the system&#8217;s most significant advantages is its offline capability. Many healthcare facilities, particularly in rural or resource-limited settings, face connectivity challenges that can interrupt their workflows. Tamanu&#8217;s offline duplicate detection ensures that patient safety measures remain active regardless of internet availability, making it an ideal solution for diverse healthcare environments.</p>
<p>When potential duplicates are identified, the system presents them to registration staff for review, enabling informed decisions about whether to link to an existing record or proceed with creating a new patient entry. This human-in-the-loop approach combines the efficiency of automated detection with the nuanced judgment that healthcare professionals bring to patient identity verification.</p>
<p><strong>Strategy 4: Patient Merge Tool</strong></p>
<p>Despite the best prevention efforts, duplicate records sometimes occur, particularly when integrating legacy data or managing complex patient populations. Tamanu&#8217;s patient merge tool provides a secure, comprehensive solution for consolidating duplicate records while preserving the integrity of all associated clinical data.</p>
<p>The merge process is designed with both safety and usability in mind. Authorized administrators can access the merge functionality easily through Tamanu&#8217;s admin panel, using a simple user interface. Here they can review duplicate records and complete the consolidation process. The system preserves all medical history, appointment records, clinical notes, laboratory results, and other patient data, ensuring that no information is lost during the merge operation.</p>
<p>This comprehensive data preservation is crucial for maintaining clinical continuity and meeting regulatory requirements for medical record retention. The merged record provides clinicians with a complete, unified view of the patient&#8217;s healthcare history, enabling more informed clinical decision-making and better care coordination.</p>
<p>The merge tool also maintains an audit trail of the consolidation process, documenting which records were merged and when, supporting quality assurance efforts and regulatory compliance requirements.</p>
<p><strong>Strategy 5: Database-Wide Reporting</strong></p>
<p>Maintaining long-term database integrity requires periodic assessment and cleanup of existing patient data. Tamanu&#8217;s comprehensive reporting tool addresses this need by analyzing entire patient databases to identify potential duplicates that may exist within legacy data or have been missed by real-time detection systems.</p>
<p>The reporting system employs advanced pattern recognition algorithms to examine patient data across multiple dimensions, identifying subtle similarities that might indicate duplicate records. Like the real-time duplicate detection, this analysis goes beyond simple name matching to consider combinations of demographic information, contact details, and other identifying characteristics that could suggest the same individual is represented multiple times in the database. The system is also designed to improve as it goes. We leverage machine learning to enhance the identification of potential duplicate patient records. Our models are trained to account for regional naming variations and cultural nuances—for instance, recognizing that “Jenny” and “Jennifer” may refer to the same individual. This is done by labelling pairs of potential matches as duplicate, different or unsure. This approach improves accuracy across diverse datasets and geographies.</p>
<p>The reports provide actionable insights, presenting suspected duplicates in a format that enables efficient review and decision-making by administrative staff. This systematic approach to database maintenance helps healthcare organizations conduct regular data hygiene audits, ensuring ongoing database quality and supporting accurate healthcare analytics and reporting.</p>
<p>These periodic cleanups are particularly valuable for organizations transitioning from paper-based systems or consolidating data from multiple legacy electronicsystems, where duplicate creation may have occurred during data migration processes.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><img loading="lazy" decoding="async" class="aligncenter size-full wp-image-5147" src="https://www.bes.au/wp-content/uploads/2025/07/029-scaled.jpg" alt="" width="2560" height="1707" srcset="https://www.bes.au/wp-content/uploads/2025/07/029-200x133.jpg 200w, https://www.bes.au/wp-content/uploads/2025/07/029-300x200.jpg 300w, https://www.bes.au/wp-content/uploads/2025/07/029-400x267.jpg 400w, https://www.bes.au/wp-content/uploads/2025/07/029-600x400.jpg 600w, https://www.bes.au/wp-content/uploads/2025/07/029-768x512.jpg 768w, https://www.bes.au/wp-content/uploads/2025/07/029-800x533.jpg 800w, https://www.bes.au/wp-content/uploads/2025/07/029-1024x683.jpg 1024w, https://www.bes.au/wp-content/uploads/2025/07/029-1200x800.jpg 1200w, https://www.bes.au/wp-content/uploads/2025/07/029-1536x1024.jpg 1536w, https://www.bes.au/wp-content/uploads/2025/07/029-scaled.jpg 2560w" sizes="(max-width: 2560px) 100vw, 2560px" /></p>
<p>&nbsp;</p>
<h4><strong>The Importance of Integrated Systems and Processes</strong></h4>
<p>While Tamanu&#8217;s built-in deduplication strategies provide robust protection against patient duplicates, the most effective approach to patient identity management can involve integration with complementary systems and processes that strengthen identification accuracy from multiple angles.</p>
<p><strong>Biometric Identification Systems</strong></p>
<p>Biometric identification represents a powerful complement to traditional patient identification methods, offering unique advantages in accurately distinguishing between individuals. <a href="https://www.simprints.com/" rel="nofollow noopener" target="_blank">Simprints</a>, an open-source biometric identification platform, is one such example which exemplifies how these technologies can enhance patient identity management in healthcare settings.</p>
<p>Biometric systems capture unique physiological characteristics—such as fingerprints, iris patterns, or facial features—that remain consistent throughout an individual&#8217;s lifetime. When integrated with EMR systems like Tamanu, biometric identification can provide definitive patient verification that transcends the limitations of traditional identifiers like names, addresses, or even identity documents, which can be forgotten, lost, or shared between family members.</p>
<p>Simprints has demonstrated particular effectiveness in challenging healthcare environments, including refugee settings, rural communities, and populations with limited documentation. The system&#8217;s open-source nature makes it accessible to healthcare organizations with varying resource levels, while its offline capabilities ensure functionality in areas with limited connectivity—a critical consideration for many healthcare deployments.</p>
<p>Biometric identification is not a panacea – in larger populations across broad age and ethnic spectrums, biometrics can help to massively reduce patient duplication and improve patient identification, but the systems still need to be backed by strong patient management systems and high quality policies and procedures.</p>
<p><strong>Civil Registration and Vital Statistics (CRVS) Integration</strong></p>
<p>Civil Registration and Vital Statistics systems provide another crucial layer of patient identity verification and lifecycle management. These systems maintain authoritative records of births, deaths, marriages, and other vital life events that establish and track individual identities throughout their lives. EMRs should interact with CRVS systems at moments including birth and death to ensure that people have official identities that benefit them throughout all facets of their lives, not just healthcare. The integration of CRVS systems with EMRs like Tamanu creates a comprehensive identity ecosystem where healthcare records are anchored to officially recognized vital events.</p>
<p>Birth registration data helps establish definitive patient identities from the earliest stages of life, providing healthcare systems with authoritative information about patient demographics and family relationships. Death registration integration ensures that deceased patients are appropriately flagged in healthcare systems, preventing inappropriate record creation and supporting accurate population health statistics</p>
<p><a href="https://www.opencrvs.org/" rel="nofollow noopener" target="_blank">OpenCRVS</a> represents a leading example of modern CRVS implementation, working globally to improve the management of vital events and strengthen the foundation of identity management systems. Also a free and open-source platform, OpenCRVS are working in the Indo-Pacific region with partners including BES and agencies such as SPC. When integrated with healthcare systems, CRVS data provides several critical benefits for patient identity management.</p>
<p>&nbsp;</p>
<h4><strong>Conclusion</strong></h4>
<p>Effective patient duplicate management requires a comprehensive, multi-layered approach that addresses both prevention and remediation while integrating with broader identity management ecosystems. Tamanu EMR&#8217;s five-strategy framework—PMI integration, ID card systems, real-time detection, merge tools, and database-wide reporting—provides healthcare organizations with robust tools for maintaining clean, accurate patient databases.</p>
<p>By combining Tamanu&#8217;s built-in deduplication strategies with thoughtful integration of complementary identification systems, healthcare organizations can achieve the highest levels of patient data integrity. This comprehensive approach ensures that every patient record is unique, accurate, and complete—supporting the delivery of safe, coordinated, and effective healthcare services.</p>
<p>Tamanu EMR&#8217;s comprehensive approach to duplicate management provides healthcare organizations with the tools and strategies needed to achieve and maintain this essential data quality standard. Come and chat with us about how our Project Management and Data teams can help your health ecosystem achieve its goals.</p>
<p>&nbsp;</p>
<p><strong>Watch our video on the five Tamanu deduplication strategies here:</strong></p>
<div class="video-shortcode"><iframe title="Managing duplicate patients in Tamanu" width="1400" height="788" src="https://www.youtube.com/embed/GjUFRbZZO0s?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bes.au/managing-patient-duplicates-with-tamanu-a-comprehensive-approach-to-data-integrity/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Behind the dashboards &#8211; making data useful</title>
		<link>https://www.bes.au/behind-the-dashboards-making-data-useful/</link>
					<comments>https://www.bes.au/behind-the-dashboards-making-data-useful/#respond</comments>
		
		<dc:creator><![CDATA[Michael]]></dc:creator>
		<pubDate>Mon, 21 Jul 2025 01:54:49 +0000</pubDate>
				<category><![CDATA[Our impact]]></category>
		<category><![CDATA[Data]]></category>
		<category><![CDATA[Tupaia]]></category>
		<guid isPermaLink="false">https://www.bes.au/?p=5092</guid>

					<description><![CDATA[How BES makes health data useful - and the team that does it. Every day, digital health systems built by BES help visualise thousands of data points across the Pacific and beyond. But data isn’t useful just because it exists. It has to be structured, validated, and presented in a way that helps people make [...]]]></description>
										<content:encoded><![CDATA[<h3 class="Header-module__header--Jux6H" data-anchor-id="hk65e-behind-the-dashboards-how-bes-makes-health-data-useful">How BES makes health data useful &#8211; and the team that does it.</h3>
<p>Every day, digital health systems built by BES help visualise thousands of data points across the Pacific and beyond. But data isn’t useful just because it exists. It has to be structured, validated, and presented in a way that helps people make real-world decisions. That’s the job of our data team.</p>
<p>In this post, we share a bit about how that happens – the people behind it, the processes that keep it running, and the work we do to turn raw data into something that matters. Our data team spans Melbourne, Sydney and Canberra, and brings together a mix of backgrounds across analytics, software engineering, and biomedical research.</p>
<p>&nbsp;</p>
<hr contenteditable="false" />
<p>&nbsp;</p>
<div class="fusion-content-boxes content-boxes columns row fusion-columns-2 fusion-columns-total-2 fusion-content-boxes-1 content-boxes-icon-with-title content-left" style="--awb-backgroundcolor:#9ed8e5;--awb-hover-accent-color:#65bc7b;--awb-circle-hover-accent-color:#65bc7b;--awb-box-shadow: 0px 0px ;;" data-animationOffset="top-into-view"><div style="--awb-backgroundcolor:#9ed8e5;" class="fusion-column content-box-column content-box-column content-box-column-1 col-lg-6 col-md-6 col-sm-6 fusion-content-box-hover content-box-column-first-in-row"><div class="col content-box-wrapper content-wrapper-background link-area-link-icon content-icon-wrapper-yes icon-hover-animation-fade" data-animationOffset="top-into-view"><div class="heading icon-left"><h2 class="content-box-heading fusion-responsive-typography-calculated" style="--h2_typography-font-size:24px;--fontSize:24;line-height:1.2;">Meet the team</h2></div><div class="fusion-clearfix"></div><div class="content-container">
<p><strong>Juliana Mitchell-Wong</strong> leads the team. With a background in biomedical and computer engineering, she brings both deep technical knowledge and practical experience leading the evolution of our data systems over the past four years.</p>
<p><img loading="lazy" decoding="async" class="alignleft wp-image-1217 size-fusion-400" src="https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-400x400.jpg" alt="" width="400" height="400" srcset="https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-66x66.jpg 66w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-150x150.jpg 150w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-200x200.jpg 200w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-300x300.jpg 300w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-400x400.jpg 400w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-600x600.jpg 600w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-768x768.jpg 768w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-800x800.jpg 800w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-1024x1024.jpg 1024w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-1200x1200.jpg 1200w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382-1536x1536.jpg 1536w, https://www.bes.au/wp-content/uploads/2022/03/Juliana-Pic-1-scaled-e1753068537382.jpg 1920w" sizes="(max-width: 400px) 100vw, 400px" /></p>
</div></div></div><div style="--awb-backgroundcolor:#9ed8e5;" class="fusion-column content-box-column content-box-column content-box-column-2 col-lg-6 col-md-6 col-sm-6 fusion-content-box-hover content-box-column-last content-box-column-last-in-row"><div class="col content-box-wrapper content-wrapper-background link-area-link-icon content-icon-wrapper-yes icon-hover-animation-fade" data-animationOffset="top-into-view"><div class="heading icon-left"><h2 class="content-box-heading fusion-responsive-typography-calculated" style="--h2_typography-font-size:24px;--fontSize:24;line-height:1.2;">Meet the team</h2></div><div class="fusion-clearfix"></div><div class="content-container">
<p><strong>Salman Hussain Raza</strong> first joined BES in our Fiji office and is now based in NSW. His background in software engineering means he has a sharp focus on automation and process design.</p>
<p><img loading="lazy" decoding="async" class="alignleft wp-image-2292 size-fusion-400" src="https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-400x400.jpg" alt="" width="400" height="400" srcset="https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-66x66.jpg 66w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-150x150.jpg 150w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-200x200.jpg 200w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-300x300.jpg 300w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-400x400.jpg 400w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-600x600.jpg 600w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-768x768.jpg 768w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-800x800.jpg 800w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599-1024x1024.jpg 1024w, https://www.bes.au/wp-content/uploads/2023/03/Salman-Raza-e1679887567599.jpg 1200w" sizes="(max-width: 400px) 100vw, 400px" /></p>
</div></div></div><div class="fusion-clearfix"></div></div>
<hr contenteditable="false" />
<p>&nbsp;</p>
<h3 class="Header-module__header--Jux6H" data-anchor-id="ho1gc-from-point-of-care-to-point-of-impact">From point of care to point of impact</h3>
<p>Data in Tupaia comes from many sources. Our own data collection tools — MediTrak on Android and DataTrak in the browser — are widely used, especially for surveys and field reporting. But we also pull data from other systems including Tamanu, DHIS2, mSupply, Kobo, and Google Drive, among others. These integrations are designed to be flexible: we can ingest data through APIs, database exports, backups, or spreadsheets, depending on the context.</p>
<p>But just ingesting data isn’t enough. Once we have it, we need to make sure it’s clean, consistent, and safe to report on. That’s where our processing pipelines come in.</p>
<p>&nbsp;</p>
<h3 class="Header-module__header--Jux6H" data-anchor-id="h6w8a-built-in-checks-and-balances">Built-in checks and balances</h3>
<p><span class="comment-m01b7cif">Our data pipelines process over 30 million data points every single day</span>. For that to work reliably, we use automated checks to detect issues in real time, before they impact reports.</p>
<p>When new data arrives, it goes through a series of steps that automatically:</p>
<ul>
<li>Remove any deleted, outdated, or otherwise unneeded records</li>
<li>Check for issues like missing values, data integrity failures, etc.</li>
<li>Flag inconsistencies for our team to review</li>
</ul>
<p>If something looks off, it doesn&#8217;t just sit there quietly. A validation error is raised and the team is notified. These early alerts are often what allow us to catch issues before they make it into a report or dashboard. It also means we can go back to the original data source, and make sure it doesn&#8217;t happen again &#8211; whether that&#8217;s through user training, or requesting a bug fix in the source system.</p>
<p>&nbsp;</p>
<hr contenteditable="false" />
<div class="fusion-content-boxes content-boxes columns row fusion-columns-2 fusion-columns-total-2 fusion-content-boxes-2 content-boxes-icon-with-title content-left" style="--awb-backgroundcolor:#9ed8e5;--awb-hover-accent-color:#65bc7b;--awb-circle-hover-accent-color:#65bc7b;--awb-box-shadow: 0px 0px ;;" data-animationOffset="top-into-view"><div style="--awb-backgroundcolor:#9ed8e5;" class="fusion-column content-box-column content-box-column content-box-column-1 col-lg-6 col-md-6 col-sm-6 fusion-content-box-hover content-box-column-first-in-row"><div class="col content-box-wrapper content-wrapper-background link-area-link-icon content-icon-wrapper-yes icon-hover-animation-fade" data-animationOffset="top-into-view"><div class="heading icon-left"><h2 class="content-box-heading fusion-responsive-typography-calculated" style="--h2_typography-font-size:24px;--fontSize:24;line-height:1.2;">Meet the team</h2></div><div class="fusion-clearfix"></div><div class="content-container">
<p><strong>Gagandeep Kaur</strong>, based in Canberra, brings a strong interest in how data is interpreted and communicated. She works closely with our product and implementation teams to ensure what we visualise is not just accurate, but also meaningful to the people using it.</p>
<p><img loading="lazy" decoding="async" class="wp-image-1722 size-fusion-400 alignleft" src="https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-400x400.jpeg" alt="" width="400" height="400" srcset="https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-66x66.jpeg 66w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-150x150.jpeg 150w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-200x200.jpeg 200w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-300x300.jpeg 300w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-400x400.jpeg 400w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-600x600.jpeg 600w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-768x768.jpeg 768w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-800x800.jpeg 800w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-1024x1024.jpeg 1024w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573-1200x1200.jpeg 1200w, https://www.bes.au/wp-content/uploads/2022/12/Gagan-Kaur-square-photo-e1670533320573.jpeg 1429w" sizes="(max-width: 400px) 100vw, 400px" /></p>
</div></div></div><div style="--awb-backgroundcolor:#9ed8e5;" class="fusion-column content-box-column content-box-column content-box-column-2 col-lg-6 col-md-6 col-sm-6 fusion-content-box-hover content-box-column-last content-box-column-last-in-row"><div class="col content-box-wrapper content-wrapper-background link-area-link-icon content-icon-wrapper-yes icon-hover-animation-fade" data-animationOffset="top-into-view"><div class="heading icon-left"><h2 class="content-box-heading fusion-responsive-typography-calculated" style="--h2_typography-font-size:24px;--fontSize:24;line-height:1.2;">Meet the team</h2></div><div class="fusion-clearfix"></div><div class="content-container">
<p><strong>Georgia Lack </strong>is our Head of Impact and Partnerships and has a public health background, rather than data engineering. She works on the &#8216;country&#8217; side with our partners to understand what data they are collecting, what data outputs they need, and how they can use that data to improve decision making.</p>
<p><img loading="lazy" decoding="async" class="wp-image-2108 size-fusion-400 alignleft" src="https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-400x400.jpg" alt="" width="400" height="400" srcset="https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-66x66.jpg 66w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-150x150.jpg 150w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-200x200.jpg 200w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-300x300.jpg 300w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-400x400.jpg 400w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-600x600.jpg 600w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-768x768.jpg 768w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-800x800.jpg 800w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-1024x1024.jpg 1024w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484-1200x1200.jpg 1200w, https://www.bes.au/wp-content/uploads/2023/03/333388077_168461189284945_1119742294805025917_n-e1753068868484.jpg 1536w" sizes="(max-width: 400px) 100vw, 400px" /></p>
</div></div></div><div class="fusion-clearfix"></div></div>
<hr contenteditable="false" />
<p>&nbsp;</p>
<h3 class="Header-module__header--Jux6H" data-anchor-id="hecgs-making-it-easy-to-report-on-what-matters">Making it easy to report on what matters</h3>
<p>As data is ingested, validated, and cleaned, we simultaneously structure it into reporting-friendly database views. We also apply standard calculations at this database view layer, so that metrics are consistent from one visualisation to another. This helps ensure dashboards are fast and reliable, while also keeping the reporting logic clear and easy to follow. Tamanu reports use straightforward queries on these views, and the data from them flows through the rest of our data pipelines. Once in <strong>Tupaia’s Viz Builder</strong>, they can be combined, filtered, and visualised however needed.</p>
<p>&nbsp;</p>
<hr contenteditable="false" />
<p>&nbsp;</p>
<blockquote>
<h3 class="Header-module__header--Jux6H" data-anchor-id="hjesv-a-real-world-example-forecasting-medication-shortages">A real-world example: forecasting medication shortages</h3>
<p>In September 2023, the Samoan Ministry of Health carried out a mass drug administration for lymphatic filariasis and scabies. Doses were weight-based, and recorded each evening in Tamanu. These were visualised immediately in Tupaia.</p>
<p>After a few days, the dashboards showed something unexpected: stock levels were dropping faster than anticipated. Because of how we model and visualise data, the Ministry was able to quickly spot the trend and take action — placing an emergency order for more medication to ensure the campaign could continue.</p>
<p>That’s the kind of impact we want our data systems to have: helping people see the issue early, and act on it.</p>
<p>To read more about this case study and others like it, visit <a class="ql-link" href="https://www.bes.au/data-for-decision-making-case-studies-from-the-pacific/" target="_blank" rel="nofollow noopener noreferrer ugc" data-slab-linktype="text">Data for decision making case studies from the Pacific</a>.</p></blockquote>
<p>&nbsp;</p>
<h3 data-anchor-id="hfot8-why-it-matters"></h3>
<h3 class="Header-module__header--Jux6H" data-anchor-id="hfot8-why-it-matters">Why it matters</h3>
<p>Whether it’s a national outbreak dashboard, a forecasting tool, or a facility-level report, our goal is always the same: to make health data useful. Only then can it be <em>used </em>to improve patient safety, make better policy decisions, or strengthen public health programming.</p>
<p>It takes a solid system, a clear process, and a good team to get there. Fortunately, we have all three.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bes.au/behind-the-dashboards-making-data-useful/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
