{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T17:38:21.804Z",
  "record_id": "VXI-EXT-PROCUREMENT-FHIR-CAPABILITYSTATEMENT-KIND-DEPLOYMENT-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "FHIR capability declarations and deployed instances",
  "system": "HL7 FHIR",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does every FHIR CapabilityStatement describe the controls enforced by a deployed endpoint?",
  "near_questions": [
    "What does CapabilityStatement.kind mean for a FHIR integration?",
    "Can FHIR requirements metadata describe an undeployed capability?",
    "How do instance and software capability statements differ?",
    "What evidence binds a FHIR conformance declaration to an endpoint?"
  ],
  "supported_claims": [
    {
      "claim": "FHIR R5 distinguishes instance, capability and requirements statements. An instance statement describes a deployed configured solution; a capability statement describes software capabilities independently of a particular installation; a requirements statement describes desired capabilities. The statement kind and implementation reference therefore matter when assessing a concrete endpoint.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Certification from publishing a CapabilityStatement",
    "The buyer endpoint’s actual conformance and enforcement are untested.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "FHIR R5 distinguishes instance, capability and requirements statements. An instance statement describes a deployed configured solution; a capability statement describes software capabilities independently of a particular installation; a requirements statement describes desired capabilities. The statement kind and implementation reference therefore matter when assessing a concrete endpoint.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "CapabilityStatement - FHIR v5.0.0",
    "source_url": "https://hl7.org/fhir/R5/capabilitystatement.html",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-FHIR-CAPABILITYSTATEMENT-KIND-DEPLOYMENT-BOUNDARY-01-v1",
    "candidate_record_sha256": "6a605f8bee81c57f33e00f58c610776fa3f9f2877e074f31e318852438376df4",
    "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": "FHIR R5 distinguishes instance, capability and requirements statements. An instance statement describes a deployed configured solution; a capability statement describes software capabilities independently of a particular installation; a requirements statement describes desired capabilities. The statement kind and implementation reference therefore matter when assessing a concrete endpoint.",
    "required_buyer_context": "CapabilityStatement kind and implementation URL; Software version and endpoint identity; Observed authorization and interaction results. 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 every FHIR CapabilityStatement describe the controls enforced by a deployed endpoint?",
    "documented_statement": {
      "status": "documented",
      "statement": "FHIR R5 distinguishes instance, capability and requirements statements. An instance statement describes a deployed configured solution; a capability statement describes software capabilities independently of a particular installation; a requirements statement describes desired capabilities. The statement kind and implementation reference therefore matter when assessing a concrete endpoint.",
      "source_ids": [
        "fhir-capability"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Bind the statement to the deployed instance and verify the relevant behaviour separately.",
      "source_ids": [
        "fhir-capability"
      ]
    },
    "buyer_evidence_required": [
      "CapabilityStatement kind and implementation URL",
      "Software version and endpoint identity",
      "Observed authorization and interaction results"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Reject deployed-control conclusions based on a requirements or generic capability statement alone."
    },
    "unknowns": "The buyer endpoint’s actual conformance and enforcement are untested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer endpoint’s actual conformance and enforcement are untested."
    },
    "evidence_sources": [
      {
        "source_id": "fhir-capability",
        "url": "https://hl7.org/fhir/R5/capabilitystatement.html",
        "final_url": "https://hl7.org/fhir/R5/capabilitystatement.html",
        "status": 200,
        "captured_at_utc": "2026-10-24T17:21:12.798Z",
        "sha256": "c82badd3b7888d542472c6a2385ad40e1270df2b48ce5cfa2bd8a8b66747d0a9",
        "bytes": 969532,
        "title": "CapabilityStatement - FHIR v5.0.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": [
          "5.3.1.1 Instance",
          "5.3.1.2 Capability",
          "Requirements kind"
        ],
        "version_context": "HL7 FHIR R5 (5.0.0), pinned URL; resource status and implementation support require separate checks."
      }
    ],
    "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": "Avoid accepting a deployment on the basis of generic feature declarations.",
      "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": "Avoid accepting a deployment on the basis of generic feature declarations.",
    "refusal_conditions": [
      "Reject deployed-control conclusions based on a requirements or generic capability statement alone."
    ]
  },
  "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": "Avoid accepting a deployment on the basis of generic feature declarations.",
    "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#fhir-capabilitystatement-kind-deployment-boundary",
  "machine_readable_record": "/varexis-index/records/fhir-capabilitystatement-kind-deployment-boundary.json"
}
