<aside> 🇵🇭 In this section we will be presenting some of the best practices from open source solutions that were deployed locally.

</aside>

Start with Pilots for Scalable Solutions

Piloting a solution is important for several reasons, the largest being the success of the project. Pilots can narrow down specific bottlenecks or preliminary problems early on. By pinpointing potential problem areas in the pilot phase, it allows the engineers and architects to make necessary adjustments promptly before implementing the solution at scale. Pilots are helpful to validate requirements and even test to push the limits of the solution to its breaking point, allowing your company to understand any possible limitations in the future. If your company has regulations, compliance standards, or legal commitments that need to be documented, pilots are a great way to determine pass/fail within your actual working environment and specific processes.

<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/d42fb937-6826-4627-b05f-3bb82b355b9f/download_(12).jpeg" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/d42fb937-6826-4627-b05f-3bb82b355b9f/download_(12).jpeg" width="40px" /> The goal of the eHatid project is to deploy a local health information exchange to various LGUs. Given the varying realities per LGU, the strategy employed by the eHatid project is to work on small pilots. Rather than deploying their technologies to various LGUs they started with working with a municipality (Pulilan) first, then the used the learnings obtained to move to a city (Cagayan de Oro) and to a province (Pangasinan). The process they employed is iterative to ensure that the learnings learned in one implementation can be used in the next implementations.

</aside>

Community of Practice

“Communities of Practice” is a phrase that refers to the ways in which people naturally work together. It acknowledges and celebrates the power of informal communities of peers, their creativity and resourcefulness in solving work problems, and inventing better and easier ways to meet their commitments.

A Community of Practice (CoP) is a special type of informal network that emerges from a desire to work more effectively, or to understand work more deeply among members of a particular specialty or work group. At the simplest level, CoPs are small groups of people who've worked together over a period of time to develop a common sense of purpose, and a desire to share work-related knowledge and experience through extensive communication.

CoPs emerge in the social space between project teams and knowledge networks. When multiple project teams are engaged in similar tasks, the need to share what they know will often lead to community formation.

<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/ef84a313-274d-45aa-aa71-2a91d56f9b58/download_(12).jpeg" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/ef84a313-274d-45aa-aa71-2a91d56f9b58/download_(12).jpeg" width="40px" /> The eHatid Project is engaged on deploying the Local Health Information Exchange (LHIE) locally. Given that there are thousands of LGUs who can be potential users of the system, the eHatid group is looking at establishing communities of practice locally to develop local teams that can actually support the eHatid system. This is crucial in the scalability of the system as the eHatid group will not have enough people to support all the LGUs so it is really important that a community of practice is able to support this initiative.

</aside>

Reuse

Software Reuse is the systematic use of existing software assets to construct new or modified assets. Software assets in this view may be source code or executables, design templates, freestanding Commercial-Off-The-Shelf (COTS) or Open Source System (OSS) components, or entire software architectures and their components forming a product line (PL) or product family. One advantage of software reuse is that it minimizes the risk of using and developing new components for software systems.

<aside> <img src="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/b5e9527e-5fa9-4aa6-9519-719c7d4c68f9/fassster-logo.png" alt="https://s3-us-west-2.amazonaws.com/secure.notion-static.com/b5e9527e-5fa9-4aa6-9519-719c7d4c68f9/fassster-logo.png" width="40px" /> FASSSTER was originally a system used to monitor existing epidemics in the Philippines like Dengue. However during the COVID-19 pandemic, FASSSTER was reused and modified to used for surveillance monitoring. Since there is a need to integrate other systems to FASSSTER, it needed to have an integration layer. Rather than developing a new system, the FASSSTER technical team have decided to use a HAPI FHIR Server (a DPG nominated tool) as the data warehouse where data from other systems can be placed. This enabled the development of an integration layer within weeks (rather than months) and since HAPI FHIR is already using global standards it was easier for software systems to connect to it

</aside>

Continued Support and Capacity Building