Skip to content

QuestionnaireResponse Profile

Canonical../StructureDefinition/nexus-emr-core-questionnaireresponse
Statusdraft (experimental) · 1.26.0
BaseQuestionnaireResponse (constraint)
SourceFSH · JSON

Nexus EMR profile for QuestionnaireResponse -- completed intake, screening and consent forms, including those passed through from external eReferral partners. Appears in the patient chart's journey timeline. First pass: dating and form linkage; item structure is deliberately unconstrained.

Access

What the endpoint offers

Declared for QuestionnaireResponse by the capability statements this IG publishes. One row per statement; follow it for the rest of what that statement says about this type.

Capability statement Interactions Search parameters
Server Capability Statement read vread history-instance search-type none declared

A cell reading none declared means that statement declares none, which is not the same as the endpoint having none. See how to read a capability statement for what a declared interaction and a declared search parameter do -- and do not -- promise.

SMART on FHIR scopes

QuestionnaireResponse is reachable by a SMART on FHIR app. These are the scopes an app can request, and the platform permission each one resolves to.

Request this scope Grants Permission required
user/QuestionnaireResponse.rs Read and search questionnaireresponse:read

QuestionnaireResponse is in the FHIR patient compartment, so every suffix above also works with the patient context (patient/QuestionnaireResponse.rs), which narrows the grant to the launch patient's records. The permission required is the same either way.

Narrowed exposure

QuestionnaireResponse declares no write or delete permission, so an app cannot create or update or delete it however the scope is written.

Reading the suffix

A clinical scope is <context>/<ResourceType>.<interactions>.

  • Context is patient (the launch patient's data only, and only for resource types in the FHIR patient compartment) or user (everything the authenticated user may see, valid for any type). There is no system context.
  • Interactions are the letters c create, r read, u update, d delete, s search, written in cruds order. Order does not matter on the way in: QuestionnaireResponse.sr and QuestionnaireResponse.rs are the same scope.
  • The older SMART v1 suffixes still work and fold on arrival: .read becomes .rs, .write becomes .cud, and .* becomes .cruds.
  • Wildcards (patient/*.rs) expand over the SMART-exposed resource types only, never over everything this IG profiles.

Ask for a whole permission, or none of it

The platform has one read permission covering both r and s, and one write permission covering both c and u. A scope asking for half of either could only be granted by handing over more than it asked for, so it is refused rather than quietly widened: request QuestionnaireResponse.rs, not QuestionnaireResponse.r.

An unrecognised or ungrantable scope is rejected outright. It never silently resolves to an empty grant, which a caller could mistake for "no narrowing needed".