Skip to main content
Ready Health provides a convenient method to searching multiple registries at the same time, saving time during the credentialing process and reducing errors.

​
Matching Types

Registry searches can be performed using two different matching strategies:

​
Partial Matching

Partial matching searches for individuals using flexible name matching algorithms. This method:
  • Matches names even when there are slight variations or differences
  • Takes into account aliases that an individual might have
  • Provides broader search results that may catch matches that exact matching might miss

​
Exact Matching

Exact matching requires precise name matches with the registry data. This method:
  • Only returns results when names match exactly as provided
  • Provides more precise results with fewer false positives
  • Useful when you have complete and accurate name information

​
Configuring Matching Type

The matching type can be configured in two ways:

​
Partner Configuration

You can set the default matching type in your partner configuration. This will be used for all searches unless overridden in the API call.

​
API Call Override

You can specify the matching type directly in the API request by including the match_type attribute: 
{
  "external_id": "uuid-here",
  "context": {
    "first_name": "John",
    "last_name": "Doe",
    "date_of_birth": "1990-01-01"
  },
  "registries": ["oig-exclusions", "ofac"],
  "match_type": "PARTIAL"
}
Or for exact matching: 
{
  "external_id": "uuid-here",
  "context": {
    "first_name": "John",
    "last_name": "Doe",
    "date_of_birth": "1990-01-01"
  },
  "registries": ["oig-exclusions", "ofac"],
  "match_type": "EXACT"
}
The match_type parameter accepts either "PARTIAL" or "EXACT" as values. If no match_type is specified in the API call, the system will use the default matching type configured for the partner ID (specified in external_id).

​
Registry Configuration Requirements

The external_id field in the request corresponds to the partner ID. Important: If the partner ID does not have a requested registry configured in the partner configuration, the request will fail. Ensure that all registries specified in the registries array are enabled for your partner ID before making the request.

​
Additional Context

You can include additional context fields in the request to improve search accuracy:
  • date_of_birth: Helps narrow down results by matching individuals with the same birth date. Format: YYYY-MM-DD
  • zip: Provides geographic context to help filter and match results more accurately
These fields are optional but recommended when available, as they help reduce false positives and improve match quality. Example with additional context: 
{
  "external_id": "uuid-here",
  "context": {
    "first_name": "John",
    "last_name": "Doe",
    "date_of_birth": "1990-01-01",
    "zip": "10001"
  },
  "registries": ["oig-exclusions", "ofac"],
  "match_type": "PARTIAL"
}

​
Federal Registries

RegistryStatus
OIG ExclusionsAvailable
OFACAvailable
SAM ExclusionsAvailable
NSOPWAvailable
NursysComing soon

​
State Registries

New registry searches are being added continuously. For specific sites, please get in touch to discuss the use case.