Loading...

XML

Word

Printable

JSON

Specification:

US National Directory (FHIR)
Raised in Version:

1.0.0-ballot
Work Group:

Patient Administration
Related URL:
https://build.fhir.org/ig/HL7/fhir-directory-exchange/
Related Artifact(s):

National Directory Organization
National Directory OrganizationAffiliation
Related Page(s):

Profiles
Grouping:
- Block-Vote-2
Resolution Description:

Hide

See ~~FHIR-38301~~ for disposition regarding TIN

Current Address complex data type has sufficient flexibility to address vanity addresses – no need to modify either Location or Organization profiles (see R5 Organization description of use of organization and location)

Include guidance for use of location address vs Organization.address

Show
See FHIR-38301 for disposition regarding TIN Current Address complex data type has sufficient flexibility to address vanity addresses – no need to modify either Location or Organization profiles (see R5 Organization description of use of organization and location) Include guidance for use of location address vs Organization.address
Resolution Vote:
Bob Dieterle / Brian Postlethwaite: 8-0-0
Change Category:
Enhancement
Change Impact:
Compatible, substantive

Organization id make TIN required. Our company and many, many, others, use TIN as the key to a provider record. This also aligns with HIPAA transactions that require a TAXID. NPI is just an informational attribute.

We would like to nail down address content. Physical address is the most challenging attribute, we find. Are we going to enable reference IDs/GUIDs for address locations? For example, we build alternative address tables tied to a USPS address table that helps us navigate vanity addresses and then ties to a reference number. Also, unsure how the IG incorporates whatever ONC did on address standardization recently.