SMART Permission Tickets
0.1.0 - ci-build
SMART Permission Tickets, published by . This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/jmandel/smart-permission-tickets-wip/ and changes regularly. See the Directory of published versions
Every open design question in this specification is listed here with a stable ID. Questions live as callouts on the page where they matter; this registry exists so you can see them all and reference them in discussion. To weigh in, raise a question on an Argonaut call, in the Zulip stream, or as a GitHub issue, citing the ID. Settled design decisions are stated in the specification text where they apply, not tracked here.
| ID | Question | Where |
|---|---|---|
| OQ-UC2-VERIFY | Should each delegated-access ticket say how the issuer verified the authority, or are per-code issuer obligations plus framework audit enough? | Use Case Catalog |
| OQ-QUALITY-GAP | Who issues quality-gap-query tickets, against what relationship record, and for what lifetime? | Use Case Catalog |
| OQ-5D | What must be true (authorization UX, classification precision, framework rules) before a Data Holder honors release_authorized for a restricted category? |
Proposal 005 |