Schemas / Record
rig.record.concerns
v1.0.0 · stable maturity: draft 2 fields 0 required
Fields
| Field | Type | Meaning | |
|---|---|---|---|
case |
entity | optional | Optional. The rig.record.case |
incident |
entity | optional | Optional. The rig.record.incident |
This fact belongs to a file. Format when present.
The member points at the file - the same rail rule as rig.circuit.net. The case and the incident hold no arrays.
At least one of case or incident is required. Compose onto the payment, claim, encounter, event, or sensor that belongs to the file. One case and one incident on this component. Do not invent a files array here.
JSON Schema
Resolves at https://rig.works/schemas/rig.record.concerns.schema.json —
raw file.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://rig.works/schemas/rig.record.concerns.schema.json",
"title": "rig.record.concerns",
"type": "object",
"additionalProperties": false,
"properties": {
"case": {
"$ref": "./_defs.schema.json#/$defs/entity"
},
"incident": {
"$ref": "./_defs.schema.json#/$defs/entity"
}
},
"description": "This fact belongs to a case and/or an incident. The file holds no member array.",
"minProperties": 1,
"x-rig-maturity": "draft"
}