# health.hats.institution.public

> Referrals, transfers, and consults between two institutions: the requester's ServiceRequest and the receiver's Task. Authority is the requesting institution's DID; the skey is the partner institution's DID.

- Kind: space
- Authority: institution.hats.health
- Lexicon: 1
- Published by [hats.health](https://lexicon.garden/identity/did:plc:uvvhtareovj2oaregs7vsibv), the NSID's authority

## Links

- [Documentation](https://lexicon.garden/lexicon/did:plc:uvvhtareovj2oaregs7vsibv/health.hats.institution.public)
- [Schema JSON](https://lexicon.garden/lexicon/did:plc:uvvhtareovj2oaregs7vsibv/health.hats.institution.public/schema.json)
- [Analytics](https://lexicon.garden/lexicon/did:plc:uvvhtareovj2oaregs7vsibv/health.hats.institution.public/analytics)

## Space (`health.hats.institution.public`)

Type: space · key any

### Shown at sign-in

- `name` (string): Referrals and transfers

### Collections

- `collections` (array · nsid): The record collections clients of this space type use. A space: scope covers these unless it names its own.
  - Collections: `health.hats.fhir.serviceRequest`, `health.hats.fhir.task`, `health.hats.fhir.communication`, `health.hats.fhir.documentReference`

### Asking for it (OAuth scope)

- `space:health.hats.institution.public` (scope): A client asks for access to spaces of this type with this scope. On its own it covers your own spaces, with any key, and reading, creating, updating and deleting records in the collections above; authority, skey, collection, action and manage narrow or widen that. From the Atproto Spaces proposal (0016).
  - Scope builder: `Open in the scope builder`

## Schema

```json
{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "collections": [
        "health.hats.fhir.serviceRequest",
        "health.hats.fhir.task",
        "health.hats.fhir.communication",
        "health.hats.fhir.documentReference"
      ],
      "description": "Referrals, transfers, and consults between two institutions: the requester's ServiceRequest and the receiver's Task. Authority is the requesting institution's DID; the skey is the partner institution's DID.",
      "key": "any",
      "name": "Referrals and transfers",
      "type": "space"
    }
  },
  "id": "health.hats.institution.public",
  "lexicon": 1
}
```