For AI agents: the documentation index is at /docs/payerbox/llms.txt. A Markdown version of this page is available at /docs/payerbox/data-integration/uscdi/care-team.md or by requesting it with the Accept: text/markdown header.
Payerbox Docs

Care Team Members

Datasets

US Core 6.1.0 maps each USCDI data element onto a FHIR element.

DatasetUS Core 6.1.0 target profile(s)
practitionersUS Core Practitioner, US Core PractitionerRole
organizationsUS Core Organization
care_teamUS Core CareTeam

practitioners

One row per practitioner, organization, and location: each row becomes one PractitionerRole, so a clinician practising at two locations produces two rows. Multiple specialties at the same location share a row.

If you already send the Provider Directory feed, list here only the clinicians missing from it, such as an external ordering physician.

practitioners.csv Data template with example rows
ColumnRequiredFormat / valuesExample
npiYes10 digits, Luhn-valid over the 80840 prefix9999999995
last_nameYestextRoe
first_nameRecommendedtextRichard
specialty_nuccRecommendedNUCC taxonomy code(s), ;-separated Healthcare Provider Taxonomy207R00000X
primary_org_npiRecommended10 digits, Luhn-valid over the 80840 prefix9999999979
practitioner_role_codeRecommendedSNOMED CT or v3 participation-function code Care Team Member FunctionPCP primary care physician
location_idRecommendedlocations keyLOC-221
phoneRecommended10 digits5551234567
emailIf availableemail address
role_period_startIf availabledate2021-04-01
role_period_endIf availabledate
is_deletedIf retractingtrue retracts this rowtrue
  • A row is keyed by npi, location_id and practitioner_role_code together — the roster has no key of its own, so do not mint one. Keep those three stable and the role updates in place.

organizations

One row per organization: a practice, hospital, pharmacy, or payer that other rows reference by NPI — practitioners via primary_org_npi, encounters via service_provider_npi, medication_dispenses via pharmacy_org_npi.

If you already send the Provider Directory feed, list here only the organizations missing from it.

organizations.csv Data template with example rows
ColumnRequiredFormat / valuesExample
org_npiYes10 digits, Luhn-valid over the 80840 prefix, or another stable id with org_identifier_system9999999979
org_identifier_systemIf org_npi is not an NPIURI of the issuing system, a URL you control or an OID; NPI (http://hl7.org/fhir/sid/us-npi) assumed when emptyhttp://acme.org/org-ids
org_nameYestextFamily Medical Group
activeRecommendedtrue / false (true assumed when empty); false retires an organization without deleting ittrue
org_type_codeIf availableprov provider, pay payer, ins insurance company, dept hospital department, bus non-healthcare business organization-typeprov
telecom_codeRecommendedphone, fax, email, pager, url, sms, other contact-point-systemphone
telecom_valueRecommendedthe number, address, or URL itself5551234567
address_line1Recommendedtext225 Broadway
cityRecommendedtextNew York
stateRecommended2-letter USPS USPS statesNY
zipRecommended5 or 9 digits, as a string10007
is_deletedIf retractingtrue retracts this rowtrue
  • org_npi is the key every other dataset uses to point at an organization. Send the NPI whenever the organization has one — US Core requires systems to support NPIs on organizations. An organization without an NPI, such as a community group a referral points to, may use another identifier that stays stable across deliveries; then org_identifier_system names who issued it, the same way patient_identifier_system does for members.
  • telecom_code and telecom_value travel together: FHIR requires the system code whenever a contact value is sent, so a telecom_value with an empty telecom_code is rejected.
  • FHIR requires name and active on every Organization, so a row without org_name is rejected, and an empty active is taken as true.

care_team

One row per patient and team member.

care_team.csv Data template with example rows
ColumnRequiredFormat / valuesExample
patient_identifierYespatient keyMRN-4471903
member_npiYes, unless member_related_person_id is sent10 digits, Luhn-valid over the 80840 prefix9999999995
member_related_person_idYes, unless member_npi is sentrecord_id of the related_persons row, for non-cliniciansRP-3310
role_codeYesSNOMED CT or v3 participation-function code Care Team Member Function446050000 primary care physician
statusRecommendedproposed, active, suspended, inactive, entered-in-error care-team-statusactive
is_deletedIf retractingtrue retracts this rowtrue
  • A row is keyed by patient_identifier, the member (member_npi or member_related_person_id) and role_code together — a roster has no key of its own for a membership, so do not mint one. Keep those stable and the membership updates in place.

These resources are served by Patient Access, Provider Access, and Payer-to-Payer.

Last updated: