# Key Considerations in Matching *This module is in progress and open for Community review and feedback. You are invited to provide feedback in* [*the virtual forum*](https://forum.datausecommunity.org/c/patient-id-mgmt/26) *or as a comment in* [*the Google Document*](https://docs.google.com/document/d/1rkvE4ijYrzYQt4YSkqHA82wrakP-j5ta/edit?pli=1)*. Please provide your name comments.* **Purpose** This module outlines key steps for designing and implementing an effective approach for matching person-level records within and across health-related datasets. It is intended for health data analysts, IT systems managers, developers, and program implementers. **Learning Objectives** At the end of this module, readers should be able to: 1. Name the three key phases of a person-matching approach and describe what occurs in each phase. 2. Describe how data quality can affect person matching and state ways that identifier data can be assessed and improved. 3. Understand different types of matching strategies and the advantages and disadvantages of each. 4. Describe methods for evaluating the performance of the matching algorithm. 5. State rationale for ongoing monitoring and enhancement of the matching process. Module Moderators Dr. Toan Ong - Email: Dr. Shaun Grannis
Co-Authors If you are interested in partnering on the further development/refinement of this module, please connect with the module moderators. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guides.ohie.org/duc/patient-identity-management-toolkit/modules/key-considerations-in-matching.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.