{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:38:21.804Z",
  "record_id": "VXI-EXT-PROCUREMENT-SMART-BACKEND-PREAUTHORIZATION-NOT-PATIENT-CONSENT-01-v1",
  "record_kind": "external_reference",
  "title": "SMART backend preauthorization boundary",
  "system": "HL7 SMART App Launch",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a SMART Backend Services access token establish patient consent for an administrative workflow?",
  "near_questions": [
    "Does SMART backend authentication include patient approval?",
    "What preauthorization bounds a SMART system client?",
    "Can a system access token replace patient-consent evidence?",
    "Which permissions must be checked before a backend FHIR export?"
  ],
  "supported_claims": [
    {
      "claim": "SMART Backend Services 2.2 uses preauthorized access: the client and server establish permitted scopes before runtime, and the client authenticates using asymmetric credentials to request a token. This flow does not require an end-user authorization interaction at runtime. Its token therefore documents a system grant rather than a patient consent decision.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Legal sufficiency of consent or authority for clinical decisions",
    "Actual consent, policy applicability and clinical purpose are unknown.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "SMART Backend Services 2.2 uses preauthorized access: the client and server establish permitted scopes before runtime, and the client authenticates using asymmetric credentials to request a token. This flow does not require an end-user authorization interaction at runtime. Its token therefore documents a system grant rather than a patient consent decision.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Backend Services - SMART App Launch v2.2.0",
    "source_url": "https://www.hl7.org/fhir/smart-app-launch/STU2.2/backend-services.html",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SMART-BACKEND-PREAUTHORIZATION-NOT-PATIENT-CONSENT-01-v1",
    "candidate_record_sha256": "25e096cbd8a07f071d71b2de83ff348dc6ecb4663b26cc94bf78ec9cb4c0c3c0",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "SMART Backend Services 2.2 uses preauthorized access: the client and server establish permitted scopes before runtime, and the client authenticates using asymmetric credentials to request a token. This flow does not require an end-user authorization interaction at runtime. Its token therefore documents a system grant rather than a patient consent decision.",
    "required_buyer_context": "Registered backend client and permitted system scopes; Applicable preauthorization agreement; Separate consent or other access-policy evidence required for the task. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "Does a SMART Backend Services access token establish patient consent for an administrative workflow?",
    "documented_statement": {
      "status": "documented",
      "statement": "SMART Backend Services 2.2 uses preauthorized access: the client and server establish permitted scopes before runtime, and the client authenticates using asymmetric credentials to request a token. This flow does not require an end-user authorization interaction at runtime. Its token therefore documents a system grant rather than a patient consent decision.",
      "source_ids": [
        "smart-backend-pinned"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Check the preauthorization arrangement and separately required patient or organisational permissions.",
      "source_ids": [
        "smart-backend-pinned"
      ]
    },
    "buyer_evidence_required": [
      "Registered backend client and permitted system scopes",
      "Applicable preauthorization agreement",
      "Separate consent or other access-policy evidence required for the task"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer patient consent solely from backend token issuance."
    },
    "unknowns": "Actual consent, policy applicability and clinical purpose are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Actual consent, policy applicability and clinical purpose are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "smart-backend-pinned",
        "url": "https://www.hl7.org/fhir/smart-app-launch/STU2.2/backend-services.html",
        "final_url": "https://www.hl7.org/fhir/smart-app-launch/STU2.2/backend-services.html",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:22:37.614Z",
        "sha256": "ccce6ea984ebc6a32ef2408d4bddb42050909364ca03ae5ee9dadd5410bc2ce1",
        "bytes": 36876,
        "title": "Backend Services - SMART App Launch v2.2.0",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Preauthorization",
          "Client authentication",
          "Obtaining access token"
        ],
        "version_context": "SMART App Launch STU2.2 (2.2.0), pinned published URL."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Separate technical backend access from the permissions needed for the buyer’s workflow.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Separate technical backend access from the permissions needed for the buyer’s workflow.",
    "refusal_conditions": [
      "Do not infer patient consent solely from backend token issuance."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "governance",
    "classification_label": "Agent Governance & Policy Boundaries",
    "topic_id": "governance",
    "buyer_intent": "Separate technical backend access from the permissions needed for the buyer’s workflow.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#smart-backend-preauthorization-not-patient-consent",
  "machine_readable_record": "/varexis-index/records/smart-backend-preauthorization-not-patient-consent.json"
}
