Genomic Consent-Scoped Data Access Review

In biotechnology and genomics, a population cohort is often assembled from several hospital partners, and each participant's consent says what their data may be used for. This concept illustrates a data access committee view in SemanticFed where every request for cohort data is checked against that consent before anything is opened. The page sits under Policies, headed Data Access Requests and described as a population cohort whose consent is read where each hospital keeps it.

Consent is not uniform. Participants enrolled under different consent versions agreed to different things, some ruling out commercial use and others limiting it to one disease area, and some have since withdrawn. A committee weighing a partner's request for variant frequencies needs to know how many participants the request can actually reach, and a copied consent spreadsheet goes stale the day a withdrawal arrives. The concept is designed to resolve each request's stated use against the consent codes in each hospital partner's own register, or the consent extract it shares, rather than against a central copy.

Tabs separate requests pending review, approved and expired, with counts on the first two. The request table lists each request with its requester, stated use, eligible participants out of the whole cohort and a status; the sample rows show a pharma partner's commercial cardiometabolic target validation and a university group's academic disease research, both awaiting the committee. Expanding the first request opens Eligibility by consent version, giving each version's scope and participant count, marked included or excluded, with withdrawn participants in their own excluded group. Beside it, a Proposed policy pairs a row rule that allows only participants whose consent permits commercial use in this disease area with a column rule denying date of birth and hospital number, names the partner analyst role it would apply to, carries an end date and shows as inactive. Approve & activate and Reject sit beneath.

A Withdrawals this week panel shows how the design handles a change of mind. A withdrawal recorded by a hospital is designed to drop out of the eligible rows on the next request, and the sample withdrawal carries three markers: routed by FluidGrids as a consent withdrawal, flagged in two earlier releases, and a LabsOfScience sample hold placed. The design intent is that a FluidGrids workflow routes each withdrawal notice to the committee, flags the earlier releases that included the participant and requests a sample hold in LabsOfScience, while SemanticFed governs which rows any approved policy can reach. A Guardrails panel states that policies are created inactive, that approval needs a named committee member and that every decision is logged.