Update NPI and participation date at a location-network
PUT/practitioners/:practitionerId/locations/:locationId/networks/:networkId/npi-par-date
As of CP-36570: updates only the practitioner-agnostic TenantGroupLocationNetwork addressType2Npi array (NPI + participation date, supports multiple NPIs per location-network) — no TenantGroupLocationPractitionerNetwork row is written by this endpoint anymore. {practitionerId} and the practitioner's association with the location/network are still validated for authorization/existence scoping, but the write itself is location-network scoped, not per-practitioner — NPI is a location-network attribute and cannot be edited at the practitioner-location level alone. Preferred: pass npiEntries with the location-network's complete NPI set — it REPLACES the stored addressType2Npi array, so an NPI omitted from the list is deleted (the only way to remove one) and an entry without npiParticipationDate is stored with no date. Deprecated: the scalar npi/npiParticipationDate fields still work — pass null for either to leave that value unchanged, repeat the call to add/update additional NPIs, npi is required to disambiguate npiParticipationDate when more than one NPI exists — but they are mutually exclusive with npiEntries in the same request. {practitionerId} is the certifyPractitionerId.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 500
The updated location-network assignment record.
Bad request - Invalid input or validation error
Unauthorized - Authentication required
Forbidden - Insufficient permissions
Practitioner, location, or network not found
Internal server error