Argonaut Provider Directory Implementation Guide Version 1.0.0

This page is part of the Argonaut Provider Directory Guide (v1.0.0: Release) based on FHIR R3. This is the current published version. For a full list of available versions, see the Directory of published versions

Provider Directory

The Argonaut project Provider Directory guide is based upon the FHIR STU3 API and contains the foundation for a robust provider directory. It describes the use cases and search expectations for finding a practitioner or organization. It outlines the key data elements for any provider directory and basic query guidance. The components developed in this guide are intended to provide a foundation for a central or distributed Provider or Healthcare Directory. Additional work flow components and elements may be required for a particular implementation.

The requirements for the Argonaut Provider Directory data model were drawn from IHE Healthcare Provider Directory and the ONC Provider Directory Workshop.

Use Cases

  1. Search for Practitioner by demographics
    • Name
    • Specialty
  2. Search for Practitioner within a region (city, state)
    • Practitioner or specialty within a specified distance - 10 miles from patient home
    • Show me every one of this specialty in the city
  3. Search for Organization and facility by:
    • Name
    • Address
  4. Search for Practitioner by organizational relationships
    • Practitioner in a specific health organization (e.g. Baptist Health Organization)
    • Practitioner in a specific clinic (e.g. West Clinic)

Example Searches

  1. Locate a Provider’s Direct address
    1. Search Practitioner by Name or Specialty
    2. Select appropriate Practitioner
    3. Retrieve Direct address from PractitionerRole.endpoint
  2. Locate a Provider’s phone or fax number at a location
    1. Search Practitioner by Name or Specialty
    2. Select appropriate Practitioner
    3. Retrieve PractitionerRole.telecom with PractitionerRole.telecom.system=phone|fax

Assumptions and Preconditions

Electronic service information will be available when the Practitioner or Organization is returned

Additional implementation guidance on the use cases and core data elements will be required. For example:

  • Pushing updates to central directory
  • Bulk registry download


  • Argonaut Provider Directory Endpoint
  • Argonaut Provider Directory Location
  • Argonaut Provider Directory Organization
  • Argonaut Provider Directory Practitioner
  • Argonaut Provider Directory PractitionerRole
  • Value Sets

  • Argonaut Provider Directory Provider Speciality (NUCC)
  • Argonaut Provider Directory Provider Role (NUCC)

  • Author: Brett Marquard

    Author: Eric Haas