Quick-start Guide

The purpose of this guide is to assist new users in performing basic functions in Mirth Match, including adding entities (e.g. patients) and observing matches that occur.

Once Mirth Match has been deployed, you should now be able to access the Mirth Match Admin Console. To do this:

1. Open a web browser, and navigate to http://localhost:8888/MirthMatch. This should bring up a log in page.
2. Log in with user admin and password admin 
3. Once here, go to the Administration page and change the password for admin if you are so inclined.

Domain Selection Screen

In order to get started in registering patients, you first need to create a domain (a.k.a., entity domain) by clicking "New". Give it a name and make sure the MHSIP matching module is selected.

Once the domain has been created, it will return you to the domain selection screen. Double-click on it to proceed.

Adding Patients

1. Now that you've entered the domain, click on the "Entities" tab to start adding patients.
2. Click on "Register New Entity" on the left side under "Entity Actions."
3. Fill in the information for a fictitious patient like the one displayed in the figure below.
4. Once you click "Submit", you'll need to search for the entity to get it to display (because all searches are audited). Simply type "john" into the search box near the upper right and hit enter to view the newly created patient.

Observing Entity Merges

You've just created your first patient. Every time you add new patients, Mirth Match will try to determine if the newly added patient potentially matches an existing one (based on the similarity of the traits). If the two patients are in the same Identifier Domain, a merge relation will be triggered. Let's see it in action:

1. Create a new patient with the same data as the first except make these changes:
   1. Change the Entity Identifier to 2
   2. Change the DATEOFBIRTH from 19911212 to 19921212 (you can enter other formats such as MM/dd/yyyy or yyyy-MM-dd, etc.).
2. Once you refresh the entities list (by rerunning the search on "john"), you should observe a "1" under the "Work Queue" column for both patients.
3. Clicking on the "Work Queue" tab will show a "Potential Merge Review" between those two patients.
4. If you mouse-over the item, you'll see a comparison between the two entities.
5. If you double-click the item, you'll bring up the "Edit Work Item" screen.
6. If you feel these two entities are a match, click on "Approve Item" under "Work Item Actions" on the left. The entity that was merged still exists in the system, but is marked as inactive. This is so that the entities can be unmerged at a later time.

Tip: You can also access the "Edit Work Item" screen by clicking on the "1" under the "Work Queue" column for one of the patients on the Entities tab.

Observing Entity Linkages

As depicted here, merges occur within an identifier domain, but links occur across identifier domains. So, in order to proceed, we need to create a new identifier domain.

1. Click on the "Identifier Domains" tab.
2. Click on "New Identifier Domain" under "Identifier Domain Actions" on the left.
3. Give it a label and identifier, e.g. "LAB."
4. Click "Submit Changes"
5. Now click on the "Entities" tab
6. Create two new patients:
   1. Identifier Domain: TEST_ID, Entity Identifier: 3, FIRSTNAME: Jane, LASTNAME: Doe, GENDER: F, DATEOFBIRTH: 19801015
   2. Identifier Domain: LAB, Entity Identifier: 4, FIRSTNAME: Jane, LASTNAME: Doe, GENDER: F, DATEOFBIRTH: 19811015
7. You should now observe a "Potential Link Review" in the work queue.

Observing Automatic Entity Linkages

If a match score is high enough, a link will automatically occur. Try it with:

• Identifier Domain: TEST_ID, Entity Identifier: 8, FIRSTNAME: Homer, LASTNAME: Simpson, MIDDLENAME: S, GENDER: M, DATEOFBIRTH: 19701212, SSN: 111223333, POSTALCODE: 12345
• Same as above except: Identifier Domain: LAB, Entity Identifier: 9, SSN: 111223334

Other Ways of Adding Entities

Besides adding entities through the UI, you can also import them from a file, or add them via a remote Web Service API via the Mirth Match client. More to come on that soon.