{
  "resourceType": "CapabilityStatement",
  "id": "nexus-emr-server",
  "url": "https://fhir.apps.health/CapabilityStatement/nexus-emr-server",
  "name": "NexusEmrServer",
  "title": "Nexus EMR Server Capability Statement",
  "status": "draft",
  "experimental": true,
  "date": "2026-08-14",
  "publisher": "WELLSTAR Technologies Corp.",
  "kind": "requirements",
  "description": "The resource types, interactions and profiles a conformant Nexus EMR FHIR endpoint offers. The resource list is the set this IG marks smart-exposed; the interactions on each are the ones that extension declares. Types this IG profiles but does not expose are deliberately absent.",
  "fhirVersion": "4.0.1",
  "format": [
    "application/fhir+json",
    "application/fhir+xml"
  ],
  "rest": [
    {
      "mode": "server",
      "documentation": "Every interaction below is authorized. Authorization is by SMART-on-FHIR scope, and the scope\nvocabulary is generated from this IG: a scope naming a resource type this statement does not\nlist is not granted, and a scope asking for an interaction a type does not declare is dropped\nrather than honoured. Patient-compartment scoping is enforced separately, from the launch\ncontext, so a `patient/` scope does not by itself widen to the population.",
      "security": {
        "cors": true,
        "service": [
          {
            "coding": [
              {
                "code": "SMART-on-FHIR",
                "system": "http://terminology.hl7.org/CodeSystem/restful-security-service",
                "display": "SMART-on-FHIR"
              }
            ]
          }
        ],
        "description": "SMART on FHIR. Clinical scopes name a resource type from the list below; `*` expands over exactly that list and no further."
      },
      "resource": [
        {
          "type": "AllergyIntolerance",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-allergyintolerance"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Appointment",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-appointment"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "AppointmentResponse",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-appointment-response"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            }
          ],
          "documentation": "No delete: an answer to a booking is superseded by a newer answer rather than removed, and a consumer resolves the latest answer per appointment. Destroying one moves a booking's displayed confirmation state backwards with nothing recording that it moved. Create and update are both granted because the producer is an integrating system outside the EMR, reaching this type through the API rather than from inside it."
        },
        {
          "type": "Basic",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-appstate"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "CareTeam",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-careteam"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ],
          "searchParam": [
            {
              "name": "patient",
              "definition": "http://hl7.org/fhir/SearchParameter/clinical-patient",
              "type": "reference",
              "documentation": "A patient's own care team: `CareTeam?patient={id}`. NOT MEASURED against any store. The one surface issuing it re-filters the returned bundle by subject on the client, so a store that ignored the parameter would still look correct there -- and would look correct nowhere else."
            },
            {
              "name": "status",
              "definition": "http://hl7.org/fhir/SearchParameter/CareTeam-status",
              "type": "token",
              "documentation": "The standing-team query: `CareTeam?status=active` lists the teams work may be pooled to. NOT MEASURED against any store."
            }
          ],
          "documentation": "Two parameters, and they are the two the searching surfaces use: one patient's own team, and the active standing teams work is pooled to. NEITHER IS MEASURED. Nothing in this estate exercises a CareTeam search against a store and asserts that the filter ran, which is a weaker footing than the Task entry further down, and it is stated rather than smoothed over. `participant` is deliberately absent: who is on a team is read off the bundle the search already returned rather than asked for again. So is `subject:missing`, which would be the direct way to separate a practice-wide pool (no subject) from one patient's team (a subject). That separation is done on the client instead, because a modifier the store ignores answers with every team, looking exactly like a match -- see the Task entry for the measurement that established that failure mode here."
        },
        {
          "type": "ClinicalImpression",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-clinicalimpression"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Composition",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-composition"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Condition",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-condition"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Consent",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-app-consent",
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-item-consent",
            "https://fhir.apps.health/StructureDefinition/nexus-privacy-directive"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on Consent, so no scope grants them. THREE FAMILIES SHARE THIS TYPE and a scope cannot separate them -- an application granted `consent:read` reads app consents, item consents and privacy directives alike, because a SMART scope names a resource type rather than a profile. Read `Consent.category` to tell them apart before interpreting `status`, which means opposite things across families. Write is granted by no scope: an application able to write a Consent could post a permitting override for itself."
        },
        {
          "type": "DetectedIssue",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-detectedissue"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            }
          ],
          "documentation": "No delete: a DetectedIssue is the record of a prescribing-safety finding and, where `mitigation` is present, of a prescriber deciding to proceed in spite of it. That override is a medico-legal trail, so no scope grants its destruction."
        },
        {
          "type": "Device",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-appdevice",
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-emrdevice"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on Device, so no scope grants them."
        },
        {
          "type": "DiagnosticReport",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-diagnosticreport"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "DocumentReference",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-documentreference"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ],
          "searchParam": [
            {
              "name": "identifier",
              "definition": "http://hl7.org/fhir/SearchParameter/clinical-identifier",
              "type": "token",
              "documentation": "The form discovery query: `DocumentReference?patient={id}&identifier=https://fhir.apps.health/NamingSystem/nexus-form|` finds the patient's forms and nothing else (see the nexus-form NamingSystem). MEASURED against the NativeFHIR store (2026-08-21): the parameter is served and genuinely filtered -- the system-only token returns exactly the marked documents."
            },
            {
              "name": "description",
              "definition": "http://hl7.org/fhir/SearchParameter/DocumentReference-description",
              "type": "string",
              "documentation": "The template search query: `DocumentReference?identifier=https://fhir.apps.health/NamingSystem/nexus-form-template|&description:contains={text}` finds the templates whose title carries the text anywhere, case-insensitively -- the standard R4 string search with its `:contains` modifier (unmodified, a string search matches from the start of the value). MEASURED against the NativeFHIR store (2026-08-25): `:contains` matches the text anywhere in the title, case-insensitively (`SIB` and `orm` both find `WSIB Form 8`), and the unmodified search matches from the start of the value only (`SIB` finds nothing). A store that ignored the modifier would answer the start-of-value match, so a caller seeing prefix-only results should suspect that before suspecting the catalogue."
            }
          ]
        },
        {
          "type": "Encounter",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-encounter"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Flag",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-flag"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Immunization",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-immunization"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Invoice",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-invoice"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "List",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-template-list",
            "https://fhir.apps.health/StructureDefinition/nexus-attachment-packet"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            }
          ],
          "searchParam": [
            {
              "name": "identifier",
              "definition": "http://hl7.org/fhir/SearchParameter/clinical-identifier",
              "type": "token",
              "documentation": "The template discovery query: `List?identifier=https://fhir.apps.health/NamingSystem/nexus-template|` finds every template and nothing else. MEASURED against the NativeFHIR store (2026-08-19): the parameter is served and genuinely filtered -- a bogus identifier returns zero, not an unfiltered list."
            }
          ],
          "documentation": "Templates (the nexus-template profile). No delete: destroying a template is an administrative act, not an app workflow step, and no scope grants it. Matches the charting permission grant exactly (list:read + list:write)."
        },
        {
          "type": "Location",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-location"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on Location, so no scope grants them."
        },
        {
          "type": "MedicationDispense",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-medicationdispense"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "MedicationRequest",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-medicationrequest"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "MessageHeader",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-messageheader"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on MessageHeader, so no scope grants them. A MessageHeader is the ROUTING ENVELOPE of a message bundle, not chart content: it is read off the bundle to dispatch it and it carries no patient data of its own. Expect to meet it inside a bundle rather than to retrieve one by id -- a deployment need not file it as an independently addressable resource at all."
        },
        {
          "type": "Observation",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-observation"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Organization",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-organization"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on Organization, so no scope grants them."
        },
        {
          "type": "Patient",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-patient"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            }
          ],
          "documentation": "No delete: Patient may be created and amended, but destroying the compartment root is data loss rather than a workflow step, and no scope grants it."
        },
        {
          "type": "Practitioner",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-practitioner"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on Practitioner, so no scope grants them."
        },
        {
          "type": "PractitionerRole",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-practitionerrole"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on PractitionerRole, so no scope grants them."
        },
        {
          "type": "Procedure",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-procedure"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Provenance",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-provenance"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            }
          ],
          "documentation": "No delete, and the asymmetry is the point: a producer records its own attribution alongside the write it describes, but an audit trail a client can destroy is not an audit trail, so no scope grants a delete on any Provenance. Write it for what you produced; do not rewrite someone else's. A Provenance CONTAINED in another resource -- an AI-suggestion Task, for instance -- is not reached through this entry at all: it travels under the grant of the resource containing it. Read the ABSENCE of Provenance as inconclusive rather than as an assertion that no agent was involved; coverage is not universal."
        },
        {
          "type": "Questionnaire",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-questionnaire"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            }
          ]
        },
        {
          "type": "QuestionnaireResponse",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-questionnaireresponse"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on QuestionnaireResponse, so no scope grants them."
        },
        {
          "type": "RelatedPerson",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-relatedperson"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Schedule",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-schedule"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on Schedule, so no scope grants them."
        },
        {
          "type": "ServiceRequest",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-core-referral",
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-servicerequest"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ]
        },
        {
          "type": "Slot",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-slot"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "searchParam": [
            {
              "name": "end",
              "definition": "https://fhir.apps.health/SearchParameter/slot-end",
              "type": "date",
              "documentation": "When a slot finishes. NOT A BASE R4 PARAMETER: R4 defines `start` on Slot and no counterpart, so this is this estate's own definition, published as an artifact. A store that was never given that definition IGNORES the parameter rather than refusing it, and answers with everything -- so a test asserting `200` proves nothing here. What separates an applied parameter from a dropped one is a bound past every slot's end returning ZERO rather than the whole set."
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on Slot, so no scope grants them."
        },
        {
          "type": "Specimen",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-specimen"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            }
          ],
          "documentation": "Read-only: the IG declares no create, update or delete on Specimen, so no scope grants them. A Specimen arrives with the lab result it produced and is reached from `DiagnosticReport.specimen`; nothing in this estate authors one on its own."
        },
        {
          "type": "Task",
          "supportedProfile": [
            "https://fhir.apps.health/StructureDefinition/nexus-emr-core-clinical-task",
            "https://fhir.apps.health/StructureDefinition/nexus-correction-task"
          ],
          "interaction": [
            {
              "code": "read"
            },
            {
              "code": "vread"
            },
            {
              "code": "history-instance"
            },
            {
              "code": "search-type"
            },
            {
              "code": "create"
            },
            {
              "code": "update"
            },
            {
              "code": "delete"
            }
          ],
          "searchParam": [
            {
              "name": "_id",
              "definition": "http://hl7.org/fhir/SearchParameter/Resource-id",
              "type": "token",
              "documentation": "Fetch a known set in one request: `Task?_id={id},{id}`. This is load-bearing rather than a convenience -- a worklist whose question this surface cannot express as a filter computes the ids some other way and reads them back here. NOT MEASURED."
            },
            {
              "name": "_lastUpdated",
              "definition": "http://hl7.org/fhir/SearchParameter/Resource-lastUpdated",
              "type": "date",
              "documentation": "The delta re-read: a chart already holding a patient's tasks asks what changed with `_lastUpdated=gt{instant}` rather than reading the whole module again. NOT MEASURED."
            },
            {
              "name": "authored-on",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-authored-on",
              "type": "date",
              "documentation": "The received-date window on a worklist, sent as a pair: `authored-on=ge{date}&authored-on=lt{date}`. The bounds are the calendar days they fall on LOCALLY, so a task authored late in the local day is not reported against the following UTC one. NOT MEASURED."
            },
            {
              "name": "based-on",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-based-on",
              "type": "reference",
              "documentation": "The work raised for an order or a referral: `Task?based-on=ServiceRequest/{id}`. NOT MEASURED."
            },
            {
              "name": "business-status",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-business-status",
              "type": "token",
              "documentation": "The workflow state inside a lifecycle status -- a received task still awaiting review, for instance. The profile binds `businessStatus` REQUIRED as of 1.26.0, so the set of values a search can return is closed and known -- a code from outside it is an error rather than a local extension. Two vocabularies share that set and only one belongs on any given task: the correction lifecycle appears only on `privacy-request` tasks. NOT MEASURED."
            },
            {
              "name": "code",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-code",
              "type": "token",
              "documentation": "The task type, as a system-qualified token and usually as an OR-list: a worklist's type filter is this parameter and nothing else. NOT MEASURED."
            },
            {
              "name": "focus",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-focus",
              "type": "reference",
              "documentation": "The chart element the work is about: `Task?focus=DocumentReference/{id}` finds the tasks raised against a document. NOT MEASURED."
            },
            {
              "name": "identifier",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-identifier",
              "type": "token",
              "documentation": "The business key a producer minted: `Task?identifier={system}|{value}` retrieves that one task, and the system-only form `{system}|` sweeps every task from one producer. MEASURED: the request asserts an exact count of one, and a parameter the store dropped would answer with the tenant's whole task set."
            },
            {
              "name": "intent",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-intent",
              "type": "token",
              "documentation": "Assigned work versus a suggestion awaiting approval -- the distinction every worklist here is built on, since an inbox admits everything but `proposal` and a suggestions panel admits only it. MEASURED: the request asserts that an `intent=proposal` search returns no `option`-intent task, so a store collapsing the two fails it."
            },
            {
              "name": "location",
              "definition": "http://services.well.com/fhir/task/location",
              "type": "reference",
              "documentation": "Where the work is to happen. NOT A BASE R4 PARAMETER: it is declared by the estate over `Task.location` at the canonical above, on a host this guide does not own, and a store never given that definition ignores it. MEASURED: a reference naming nothing returns zero rather than everything, which is exactly what separates a parameter that was applied from one that was dropped."
            },
            {
              "name": "owner",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-owner",
              "type": "reference",
              "documentation": "Whose work it is, as an OR-list over the practitioner AND the roles work reaches them through -- stored data holds both forms, so naming only one of them under-reports. NOT MEASURED. Asking instead for the tasks nobody owns is not something this surface can express; see the entry note on `:missing`."
            },
            {
              "name": "patient",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-patient",
              "type": "reference",
              "documentation": "The patient the task is filed against, resolved from `Task.for`. MEASURED: the request asserts that EVERY task returned is filed against the patient asked for, because a parameter silently ignored answers with the whole tenant's tasks and a count alone would not say so."
            },
            {
              "name": "priority",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-priority",
              "type": "token",
              "documentation": "Urgency, as an OR-list of the priorities wanted. NOT MEASURED."
            },
            {
              "name": "requester",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-requester",
              "type": "reference",
              "documentation": "Who raised the work, as a reference to a practitioner or one of their roles. A created-by worklist is this parameter. NOT MEASURED."
            },
            {
              "name": "restriction-period-end",
              "definition": "http://services.well.com/fhir/task/restriction-period-end",
              "type": "date",
              "documentation": "The due date, from `Task.restriction.period.end`, used both to filter and as a sort key. NOT A BASE R4 PARAMETER: declared by the estate at the canonical above, on a host this guide does not own. MEASURED, on the same reasoning as `location` -- a date nothing falls on returns zero rather than everything."
            },
            {
              "name": "status",
              "definition": "http://hl7.org/fhir/SearchParameter/Task-status",
              "type": "token",
              "documentation": "The lifecycle status, sent as an OR-list of the statuses wanted rather than as an exclusion. NOT MEASURED ON ITS OWN: the request that carries it carries other filters too, so nothing isolates this one."
            }
          ],
          "searchInclude": [
            "Task:based-on",
            "Task:location",
            "Task:owner",
            "Task:patient",
            "Task:requester"
          ],
          "documentation": "Sixteen parameters and five includes: the set the searching surfaces reach for, which is a narrower claim than the set R4 defines on Task. FIVE ARE MEASURED and eleven are not, and every entry says which it is. A measured entry here rests on a STANDING conformance request against a seeded NativeFHIR store rather than on a one-off run, and each such request asserts what the filter must EXCLUDE rather than merely that a bundle came back. That shape is forced by how the store fails: an unsupported parameter is not an error to it -- it drops the parameter, answers with everything, and explains itself in an OperationOutcome entry inside an otherwise ordinary searchset. A test asserting 200 proves nothing at all here.\n\n`:missing` IS NOT DECLARED, AND TWO MEASUREMENTS DISAGREE ABOUT WHY. On 2026-08-25, against a store holding one patientless task among nine, `patient:missing` returned the unfiltered set for `true` and for `false` alike, indistinguishably from a parameter that does not exist. On 2026-09-08 the opposite was measured directly against the store image this estate runs: with one owned and one unowned Task present, `owner:missing=true` returned only the unowned one, `owner:missing=false` only the owned one, and an unfiltered control returned both. The store's own source agrees with the second result -- the modifier is parsed explicitly and compiled to a not-exists condition, unconditionally. Each hop between the client and the store was also checked in isolation and preserves the modifier. What has NOT been measured is the whole chain at once, which is the only thing that would settle it, so this surface still declares nothing. Until it does, a client wanting the tasks filed against nobody should narrow the result itself rather than trust the modifier -- the cost of being wrong is that every task in the tenant reads as a match, and that failure is silent. `:not` is likewise undeclared: nothing isolates it, and its semantics differ between servers, so an OR-list of the values wanted is the portable spelling of the same query.\n\nCHAINING AND REVERSE CHAINING ARE NOT DECLARED. `patient.name` and `patient.identifier` narrow a worklist by the patient a task is filed against, and `_has:Communication:based-on:recipient` answers addressed-to-me. All three go over this surface today and none has been measured. They are named here so that an implementer meeting one knows it is unverified, which is a different thing from knowing it works.\n\nRESULT PARAMETERS. `_count`, `_total=accurate` and `_sort` accompany every search these surfaces issue, and `-authored-on` is the sort the worklists use. `_include:iterate` takes a second hop off what the first one brought back -- the Practitioner behind an included PractitionerRole, the patient behind an included ServiceRequest. That hop leaves this resource type, so it is not listed in `searchInclude` above and its support is a question for the type it lands on. `Task:location` is an include over a parameter this guide does not define -- see that entry."
        }
      ],
      "interaction": [
        {
          "code": "transaction",
          "documentation": "All-or-nothing multi-resource write at the server root. Entries are applied as one unit and the bundle fails together, so a single nonconformant entry loses every other entry with it; read the returned OperationOutcome rather than retrying. Internal references between entries are resolved within the bundle."
        },
        {
          "code": "batch",
          "documentation": "Independent multi-resource write at the server root. Unlike `transaction`, each entry succeeds or fails on its own and the response carries one status per entry, so a caller MUST read every entry's status rather than the overall response code."
        }
      ],
      "operation": [
        {
          "name": "billing-launch",
          "definition": "https://fhir.apps.health/OperationDefinition/billing-launch",
          "documentation": "Open a signed-in ClinicAid session for a clinic, optionally prefilled from one appointment. Requires the billing-launch permission. Affects state: it spends a clinic credential and mints a single-use address."
        },
        {
          "name": "eligibility-check",
          "definition": "https://fhir.apps.health/OperationDefinition/eligibility-check",
          "documentation": "Ask a patient's province, through the clinic's own payer account, whether that patient may be billed. Affects state: it spends a payer account and is not safe to repeat blindly, because one of its two 503 endings means the check may already have run."
        },
        {
          "name": "indexing-status",
          "definition": "https://fhir.apps.health/OperationDefinition/indexing-status",
          "documentation": "Report which search parameters are defined and indexed on this tenant's store. ADMINISTRATIVE: the right is granted to an administrative role, not to an integration. This is how to find out whether a given tenant's store actually holds the non-base search parameters declared above. Reads only. Despite that, GET is refused; use POST."
        },
        {
          "name": "index-search-parameter",
          "definition": "https://fhir.apps.health/OperationDefinition/index-search-parameter",
          "documentation": "Start a background job that makes one search parameter usable for search on this tenant's store. ADMINISTRATIVE and heavy: for a custom parameter it WRITES the definition to the store before indexing begins, and a true reply is an acceptance rather than an outcome. Not a lever an integration should pull."
        }
      ]
    }
  ]
}