<div class="xblock xblock-public_view xblock-public_view-vertical" data-block-type="vertical" data-runtime-class="LmsRuntime" data-usage-id="block-v1:MITx+HST.936x+1T2019+type@vertical+block@9fa31600ec1f4f9d9b738fd0a2961b24" data-course-id="course-v1:MITx+HST.936x+1T2019" data-has-score="False" data-graded="True" data-runtime-version="1" data-init="VerticalStudentView" data-request-token="78d7f9e2023f11efa4fd0afff417eba9">
<h2 class="hd hd-2 unit-title">The Global Health Informatics Project Lifecycle</h2>
<div class="vert-mod">
<div class="vert vert-0" data-id="block-v1:MITx+HST.936x+1T2019+type@html+block@3aa892e1a38246a18312ef34cc694f22">
<div class="xblock xblock-public_view xblock-public_view-html xmodule_display xmodule_HtmlBlock" data-block-type="html" data-runtime-class="LmsRuntime" data-usage-id="block-v1:MITx+HST.936x+1T2019+type@html+block@3aa892e1a38246a18312ef34cc694f22" data-course-id="course-v1:MITx+HST.936x+1T2019" data-has-score="False" data-graded="True" data-runtime-version="1" data-init="XBlockToXModuleShim" data-request-token="78d7f9e2023f11efa4fd0afff417eba9">
<script type="json/xblock-args" class="xblock-json-init-args">
{"xmodule-type": "HTMLModule"}
</script>
<p>In this section, we introduce a global health informatics project life cycle as a framework for developing a technology solution. This is not intended as a comprehensive, step-by-step guide, but rather to provide a high-level understanding of key considerations and practical insights toward a successful implementation. Incorporating technology into global health is complicated and requires a holistic approach to address unique challenges. Technology is only a small part of any global health informatics project, since existing resources, workflows, regulatory environments, and so on are necessary to consider for the successful implementation of any technical solution. An underlying theme throughout the process is to bring together many diverse perspectives to engage situational specificities and complex clinical scenarios.</p>
</div>
</div>
<div class="vert vert-1" data-id="block-v1:MITx+HST.936x+1T2019+type@html+block@f843fcdc003f41daa578b32e2a64c00e">
<div class="xblock xblock-public_view xblock-public_view-html xmodule_display xmodule_HtmlBlock" data-block-type="html" data-runtime-class="LmsRuntime" data-usage-id="block-v1:MITx+HST.936x+1T2019+type@html+block@f843fcdc003f41daa578b32e2a64c00e" data-course-id="course-v1:MITx+HST.936x+1T2019" data-has-score="False" data-graded="True" data-runtime-version="1" data-init="XBlockToXModuleShim" data-request-token="78d7f9e2023f11efa4fd0afff417eba9">
<script type="json/xblock-args" class="xblock-json-init-args">
{"xmodule-type": "HTMLModule"}
</script>
<p><img src="/assets/courseware/v1/ba27c12abd7f370bb895155fe4a6cda8/asset-v1:MITx+HST.936x+1T2019+type@asset+block/figure_16_01.png" alt="" type="saveimage" target="[object Object]" preventdefault="function (){r.isDefaultPrevented=n}" stoppropagation="function (){r.isPropagationStopped=n}" stopimmediatepropagation="function (){r.isImmediatePropagationStopped=n}" isdefaultprevented="function t(){return!1}" ispropagationstopped="function t(){return!1}" isimmediatepropagationstopped="function t(){return!1}" width="934" height="489" /></p>
<p>While there are many ways to generalize and sequence a project life cycle, in this overview, we will be describing a conceptual three-phase system comprising design, development, and deployment. While we present these stages as largely flowing in order, it is important to note that most projects do not move linearly forward and may have work going on in multiple stages at the same time, since there is substantial crossover and overlap across any phase. Furthermore, following a process of testing and validation within constantly changing environments, we often find that projects call for adaptation, so certain steps may need to be repeated or revised to adjust to changing requirements.</p>
<p>We will begin section 3.1 on the Health Informatics Design Process</p>
</div>
</div>
<div class="vert vert-2" data-id="block-v1:MITx+HST.936x+1T2019+type@html+block@d6ee0f7fd2fe45efaa5a0f4aef1df113">
<div class="xblock xblock-public_view xblock-public_view-html xmodule_display xmodule_HtmlBlock" data-block-type="html" data-runtime-class="LmsRuntime" data-usage-id="block-v1:MITx+HST.936x+1T2019+type@html+block@d6ee0f7fd2fe45efaa5a0f4aef1df113" data-course-id="course-v1:MITx+HST.936x+1T2019" data-has-score="False" data-graded="True" data-runtime-version="1" data-init="XBlockToXModuleShim" data-request-token="78d7f9e2023f11efa4fd0afff417eba9">
<script type="json/xblock-args" class="xblock-json-init-args">
{"xmodule-type": "HTMLModule"}
</script>
<h4>Sources of Failure</h4>
<p>There are many factors that could potentially lead to the failure of a health informatics project; however, a common breakdown from the outset is the design of the project. One common mistake is presumptively applying the blueprints from a previous project to a new situation. Unfortunately, what works in one area does not necessarily translate to another, particularly when entering a different cultural or socioeconomic environment. Maintaining a social awareness of the characteristic patients and health workers is crucial to implementing a usable application, while understanding and navigating the political and regulatory habitat is pivotal to avoiding insurmountable barriers.</p>
<p>Other failures derive from errors in process, without appropriately considering dependencies. Projects can be too compartmentalized, segregating the clinical design from the technology development. Too often, principal investigators simply hand off design specifications to developers to produce the software. This amplifies errors on both ends, as the clinical investigators fall into traps of feasibility and the engineers make flawed assumptions of implementation, resulting in buggy software nobody wants to use.</p>
</div>
</div>
</div>
</div>
© All Rights Reserved