Criteria Requirements Library Profile¶
| Canonical | ../StructureDefinition/nexus-criteria-requirements |
|---|---|
| Status | draft · 1.26.0 |
| Base | Library (constraint) |
| Source | FSH · JSON |
The data-requirements manifest generated for a compiled clinical criterion: a FHIR R4 Library with type = module-definition, declaring the resource types the logic retrieves, the profiles they must satisfy, the code and value-set filters applied, and the elements read. Derived from the compiled logic rather than authored beside it, so it cannot drift from the criteria it describes. A deployment artifact verified when a consuming host starts, not an API surface an application reaches.
Access
What the endpoint offers¶
Library is modelled by this IG but is not offered as an API surface.
No capability statement in this IG names Library, so there are no interactions and no search parameters declared for it. This IG publishes Server Capability Statement; profiling a resource and offering it are two different decisions, and each statement's own description says which types it covers and which it deliberately leaves out.
SMART on FHIR scopes¶
A SMART on FHIR app cannot reach Library.
This is the default, not an omission. A resource is unreachable unless its profile declares smart-exposed, because profiling a resource and exposing it to a third-party app are two different decisions: the first is modelling, the second is authorization. No scope naming Library will be granted, and a wildcard scope (patient/*.rs) does not expand over it.