Intertween.*

Which data may be used, and for what?

We use fictional examples to explore how sources and conditions of use can be described for a recipient.

THE PROBLEM

Can origin and conditions be described so that another organisation understands what a dataset may be used for?

When data may be used for different purposes, conditions and time limits need to be clear. A technical connection between systems cannot determine what may be disclosed.

Fictional scenario

What if a dataset could be understood before access was requested?

A researcher is looking for material for a study. What if a description showed how a dataset was produced, its limitations and who assesses requests to use it — without showing patient information? Fictional data helps us explore what that description would need to contain. Access would still require a separate assessment.

CONNECTIONS TO EXPLORE

What can we understand before requesting access?

A fictional miniature example. Choose a connection and read its evidence. All texts and events below are illustrative.

EVIDENCE IN THE FICTIONAL SOURCE

Synthetic dataset D

Dataset D was produced through transformation M.
Read the complete miniature record and connected sources

Synthetic dataset D

Dataset D was produced through transformation M. Its contents are subject to conditions V.

Illustrative record · halsodata:D · v1

Transformation description M

M aggregates fictional observations for a defined study purpose.

Illustrative record · halsodata:M · v1

Conditions record V

Every use request requires a separate assessment. The dataset description can be shown without its contents.

Illustrative record · halsodata:V · v1

Try your own document against the parliamentary material ↗

LET’S EXPLORE

What we want to explore with the framework

Using synthetic data, we explore descriptions of purpose, consent where relevant and other conditions. What evidence would a future Mediator need to assess a request? The current demo does not perform that assessment.

Possible source material

Synthetic health records, consent records and datasets for a defined purpose.

An illustrative example

A synthetic dataset has a stated purpose and an expiry date. An illustrative recipient view shows which fields might be disclosed after a separate assessment of permissions and conditions.

What we need to learn

Which local conditions, responsibilities and human judgments are missing from the example? A real case may change both the problem framing and the proposed response.

What should remain useful, and on whose terms?

Could timestamps, locations and relationships identify a patient even without a name? How should changed conditions reach recipients, and how would an inability to comply become visible?

Questions to test. The examples do not establish that these protections or decision rules are implemented. Read about responsibility and conditions ↗

Test the question together

Do you recognise the problem, or see it differently? Bring a real case, source material or a challenge. Together, we can examine the assumptions and decide whether a focused demo or pilot is the right next step. We would test what becomes easier, what still needs human judgment and what Intertween needs to change.

Start a conversation about this path ↗