Security label system · FHIR · JupyterHealth

jupyterhealth scope system

The scopes a patient grants through the BioFS Lab Connector, written as security labels on the Consent resource.

https://genobank.io/jupyterhealth/scope
Status. Namespace defined 8 November 2026 for the BioFS Lab Connector. This page defines the identifier system; a machine-readable resolver is not yet published.

Use

The Consent resource the Connector publishes carries 1 security label per scope granted, under provision.securityLabel. The scopes map onto the study scopes of the receiving JupyterHealth Exchange, so a scope is granted or withdrawn in both systems by 1 signature.

{
  "provision": {
    "type": "permit",
    "securityLabel": [
      { "system": "https://genobank.io/jupyterhealth/scope", "code": "genomic-results" }
    ]
  }
}

Codes

CodeCovers
ehr-record-bundleHospital record imports obtained through Patient Access.
genomic-resultsLaboratory and genomic result files, such as variant reports and sequencing files.
imaging-studiesDICOM imaging studies.

Meaning

A label names a class of files the patient allows readers to open. Withdrawing the scope stops later reads of the files themselves, because every attachment is a biocid served by a gated stream that checks the consent on each request.

Part of the BioFS Lab Connector specification. Published by GenoBank.io, 8 November 2026. Technical documentation, not legal or medical advice.