health.hats.fhir.practitionerRole
A FHIR R4 PractitionerRole resource. The record is the resource itself: its JSON fields as FHIR defines them, plus $type and the HATS integrity fields. Decimals are strings, since atproto has no floats; codes keep their code system's case. Published by an institution, one per person who works there, keyed by that person's DID: the coordinator reads a role by key. Forwards are contained Endpoints (docs/institution/people.md#when-someone-leaves).
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | fhir.hats.health |
| Indexed |
Record
record · key anyProperties
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
health.hats.fhir.patient
recordA FHIR R4 Patient resource. The record is the resource itself: its JSON fields as FHIR defines them, plus $type and the HATS integrity fields. Decimals are strings, since atproto has no floats; codes keep their code system's case.
-
A FHIR R4 Procedure resource. The record is the resource itself: its JSON fields as FHIR defines them, plus $type and the HATS integrity fields. Decimals are strings, since atproto has no floats; codes keep their code system's case.
-
A FHIR R4 DocumentReference resource. The record is the resource itself: its JSON fields as FHIR defines them, plus $type and the HATS integrity fields. Decimals are strings, since atproto has no floats; codes keep their code system's case.
-
health.hats.fhir.provenance
recordA FHIR R4 Provenance resource. The record is the resource itself: its JSON fields as FHIR defines them, plus $type and the HATS integrity fields. Decimals are strings, since atproto has no floats; codes keep their code system's case.
-
A FHIR R4 Organization resource. The record is the resource itself: its JSON fields as FHIR defines them, plus $type and the HATS integrity fields. Decimals are strings, since atproto has no floats; codes keep their code system's case. An institution's own description of itself, one per account: its NUCC taxonomy type, its endpoints, and its contacts.