A directory entry is a promise worth checking

When a list becomes an access question

CMS’s April 2024 Medicaid and CHIP managed-care final rule (opens in a new tab) included provisions for independent surveys examining appointment access and:

“the accuracy of provider directories”

— Centers for Medicare & Medicaid Services, April 2024

These requirements had staged applicability. They were not a promise that every directory or appointment process had changed by June. The practical point is nonetheless clear: an entry can exist without giving someone enough reliable information to use it.

Try the number with a real question in mind

Imagine a hypothetical community program helping a participant locate a nearby service. The directory has a telephone number and address. It does not say whether the service accepts new participants, offers the relevant program, or can accommodate the person’s communication needs.

A colleague calls and discovers that the number now reaches another office. The original entry still looks complete on the page.

At genus, this is the kind of small detail we take seriously. A directory can be beautifully organized while leaving the person to do all the checking that makes a connection possible.

Define what an entry can honestly promise

A listing should distinguish confirmed information from information that needs a direct conversation. A current address does not establish available capacity. Participation in a network does not settle an individual’s coverage or eligibility.

Use clear labels and a review date. Name the source of the information when that helps staff judge whether it needs checking again.

Avoid writing a confident service description from an old brochure alone. Ask the organization how it wants inquiries routed and what a prospective participant should know before making contact. A good description can save unnecessary calls without pretending to answer every personal question.

Give maintenance an actual place in the work

Directory upkeep often falls between teams. One colleague adds resources, another shares them, and nobody is sure who removes an outdated entry.

Assign responsibility for reviewing the most-used listings and handling reported errors. The review schedule can reflect how frequently the information changes and what happens if it is wrong.

A simple correction route matters too. If a participant reports a disconnected number, staff should know where to send that finding. Thanking the person is appropriate; leaving them to solve the organization's information problem is not.

Check the details that change someone’s decision

Ask what would make the option usable for the particular person. It may be opening hours, a language arrangement, an accessible entrance, or a way to speak privately.

These questions should inform the inquiry without becoming assumptions about what the participant needs. Let the person identify the details that matter to them.

Where specialist advice is necessary, connect them with the appropriate qualified source. A community directory should not quietly become an insurance recommendation, a clinical assessment, or a guarantee that a provider will accept a referral.

Make room for an unsuccessful connection

Sometimes a listing is accurate and the service still cannot help. Ask whether the person wants another option, and be clear about who will look for it.

For leaders, keep these situations distinct from inaccurate information. A wrong number needs correction. A lack of suitable capacity may need a different planning conversation.

Both deserve attention, but combining them under “referral failure” can hide the response required. People seeking support should not have to repeat the same unsuccessful call because the organization never learned what happened.

How genus can support a maintained resource

Today, genus content and pathways can bring prepared resources and links into an audience-appropriate experience. A configured care wall can make selected community information easier to discover.

The organization must still verify and maintain what it publishes. genus does not certify a provider directory or determine network participation, availability, or eligibility. We see the practical opportunity as connecting a resource with a named content owner and a human route for questions.

That combination matters more than the length of the list. Ten dependable starting points may serve a person better than a hundred entries nobody has checked.

For a reception team, the practical test might be reviewing one frequently shared resource together. Compare the public entry with the questions callers actually ask, then decide which detail needs checking before it is shared again.

A question for the next directory review

If someone follows this entry today, what can they reasonably expect—and which important details still need confirmation?