Inbound Transaction Matching Preference in Profile

overview & requirements for inbound transactions, profile offers a flexible and customisable matching preference system, allowing organisations to define how records are automatically matched to patients, providers, or points of service (pos) while minimum best practice restrictions are enforced, organisations have the flexibility to tailor the matching logic to be as simple or stringent as needed use cases where matching logic is used in profile when assigning inbound lab & diagnostic results to a patient when assigning inbound documents to a provider and pos when assigning referrals to a provider and pos the following article will cover how to configure the matching settings, as well as provide details around the matching logic applied it is meant for system administrators and technical users requirements profile versions 9 0 11+ configuration process explained below how to configure the matching settings go to organisation / preferences / general / general / import tab under the fields that participate in matching section, matching conditions can be set for the following categories patient receiving provider pos matching logic the table below outlines how the matching logic is applied matching requirements logic patient the following patient attributes can be selected to enforce matching logic dob (date of birth) phn (personal health number) last name first name file number sex logic mandatory attribute dob is a required patient attribute for matching and cannot be deselected minimum combination requirements the system will validate that at least one of the following combinations is selected dob + phn dob + last name a warning will be displayed if the minimum standard combination is not selected additional attributes users can select additional attributes to make the matching logic more comprehensive name matching rules for last name and first name matching, spaces and non letter characters will be removed during the matching process unique identifier for canadian customers, the phn field will be utilised for non canadian organisations, the phn will be replaced with the applicable national unique identifier provider the following provider attributes can be selected to enforce matching logic logic surname id refers to the provider's license number issued by board such as cpso/cpsbc/cpsnb/msp or it refers to the provider's billing number like the msp practitioner id in bc mandatory attribute surname is a required provider attribute for matching and cannot be deselected name matching rules for surname matching, spaces and non letter characters will be removed during the matching process pos the following pos attributes can be selected to enforce matching logic use manual matching for pos logic there are no minimum requirements when the use manual matching for pos checkbox is checked, the transaction will appear in the manual matches log if they don't have a pos assigned (even if the provider and patient are matched successfully) in the manual matching log, a new pos column will be displayed this column is shown so that the result can be assigned to the correct pos when providers are working in a multi pos setting the manual matches log can be seen from organisation/control centre /manage /manual matches