This page lists the roles the business processes of this guide name, and the example people and systems that play them. Every person is fictional.
Roles
| Role | Played by | Description |
|---|---|---|
| Holder | person | The person who holds a Personal Health Wallet, records consent, and presents verifiable health links and certificates. Specializes the ActorDefinition Holder (input/fsh/actors/actors.fsh). |
| Consent Recorder | person, system | The person or system that records a consent directive for the holder (IHE PCF Consent Recorder): the wallet itself, or a health worker on the holder’s behalf. |
| Consent Registry | system | Holds consent directives and answers IHE PCF [ITI-108] Access Consent. Specializes the ActorDefinition ConsentRegistry (input/fsh/actors/actors.fsh). |
| VHL Sharer | system | Holds the health information, generates verifiable health links, and enforces consent when a link is redeemed. Specializes the ActorDefinition Issuer (input/fsh/actors/actors.fsh). |
| Document Source | system | The system that assembles a document about the holder before it is signed: the VHL Sharer when a document is shared, the Certificate Issuance Service when a certificate is issued. Adds the consent directives to it (process M). |
| VHL Receiver | system | Receives a verifiable health link, checks its signature against the trust list, and retrieves the information. Specializes the ActorDefinition Receiver (input/fsh/actors/actors.fsh). |
| Trust Anchor | system | Publishes the trust list of keys that participants use to check signatures. GDHCN is one possible anchor among others. Specializes the ActorDefinition TrustNetworkAnchor (input/fsh/actors/actors.fsh). |
| Certificate Issuer | person, system | A health worker or issuing system that issues a verifiable digital health certificate. Specializes the ActorDefinition Issuer (input/fsh/actors/actors.fsh). |
| Verifier | person, system | Checks a certificate and its status, with or without a status checking application. Specializes the ActorDefinition Receiver (input/fsh/actors/actors.fsh). |
| Data Provider Administrator | person | The person at a data provider who registers clients under a data sharing agreement. |
| Data Recipient System | system | A server that accesses data under a data sharing agreement (OAuth client) and performs the agreement’s duties. |
| Provider Authorization Server | system | Registers clients and decides access under a data sharing agreement (policy decision and enforcement). |
| Auditor | person | The person who reviews audit and provenance records under a data sharing agreement. |
Example people
Ana (data provider administrator)
Persona: the administrator who registers partner servers under the data sharing agreements her health information exchange signs. Fictional.
Roles: Data Provider Administrator.
Goal. Register only the clients an agreement allows, and revoke them the moment it ends.
Needs
- The agreement’s terms in a form the server can check
- One place to suspend a client
Frustrations
- Agreements that exist only as PDFs
Dr Mei (receiving clinician)
Persona: an emergency physician who treats visitors from other countries and reads their records through verifiable health links. Fictional.
Roles: Verifier.
Goal. Read a visitor’s record quickly and know it is genuine and that she is allowed to read it.
Needs
- A clear answer: allowed, refused, or unknown
- A record she can trust, signed by a known issuer
Frustrations
- Links that fail without saying why
Kofi (auditor)
Persona: an auditor who checks that every access under a data sharing agreement was allowed and its duties were done. Fictional.
Roles: Auditor.
Goal. Show, for any access, which consent and which agreement allowed it.
Needs
- Provenance that cites the consent and its version
- Duty checks he can run himself
Frustrations
- Logs that say who, but not why
Lina (wallet holder)
Persona: a 34-year-old teacher who keeps her health records in a personal health wallet on her phone and travels for work. Fictional.
Roles: Holder, Consent Recorder.
Goal. Share her health information only with the people who need it, for as long as they need it.
Needs
- To see who can read her record, and to withdraw that at any time
- One link that works abroad as well as at home
- To know when her record was read, and by whom
Frustrations
- Consent forms she cannot read back later
- Not knowing whether a withdrawal took effect
Nurse Tomás (clinic nurse)
Persona: a nurse at a community clinic who vaccinates, issues certificates, and records consent for patients who ask for help with the wallet. Fictional.
Roles: Certificate Issuer, Consent Recorder.
Goal. Issue certificates that are accepted wherever his patients go, without extra paperwork.
Needs
- To record a patient’s consent in one step, and show it back to them
- To know a certificate was issued correctly
Frustrations
- Patients who were never asked what they agreed to
Example systems
| System | Roles | Description |
|---|---|---|
| Home health information exchange | VHL Sharer, Consent Registry, Document Source | The health information exchange that holds Lina’s record: it records her consent in its Consent Registry, generates her links and enforces consent when a link is redeemed. |
| Lina’s personal health wallet | Holder, Consent Recorder | The wallet app on Lina’s phone: records her consent, holds her verifiable health links and certificates, and presents them as QR codes. |
| Provider authorization service | Provider Authorization Server | The authorization server of the health information exchange: registers clients and decides access under data sharing agreements. |
| Receiving clinic’s record system | VHL Receiver, Data Recipient System | The record system of Dr Mei’s clinic: reads verifiable health links, and as a registered client accesses data under a data sharing agreement. |
| Trust anchor service | Trust Anchor | A trust anchor that publishes the trust list of participants’ keys; GDHCN or another accepted anchor. |