Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIR Core (FHIR)
-
R5
-
Security
-
Provenance
-
-
Kathleen Connor / Alexander Mense: 6-0-0
-
Clarification
-
Non-substantive
-
R5
Description
type should be clearly the functional role that is used with respect to the activity. Other functional roles are not relevant. the .role should be structural roles only, not including functional role. Thus need better separation of the valueSets between these two. Not clear where we have a valueSet of structural roles, might need to invent an example valueSet showing examples of structural roles.
Provenance.agent.type | |
Element Id | Provenance.agent.type |
Definition | The primary act of participation of the agent with respect to the activity. |
Cardinality | 0..1 |
Terminology Binding | ParticipationRoleType (Extensible) |
Type | CodeableConcept |
Requirements | Note: The .type of author could be .role of primary author. Note there are overlapping codes to be used in specific circumstances. See ISO 21298:2018 - Health Informatics - Functional and structural roles. |
Summary | true |
Comments | For example: assembler, author, doctor, nurse, clerk, etc. |
Provenance.agent.role | |
Element Id | Provenance.agent.role |
Definition | The functional or structural roles of the agent indicating the agent's competency. The security role enabling the agent with respect to the activity. |
Cardinality | 0..* |
Terminology Binding | SecurityRoleType (Example) |
Type | CodeableConcept |
Requirements | Note: The .type of author could be .role of primary author. Note there are overlapping codes to be used in specific circumstances. See ISO 21298:2018 - Health Informatics - Functional and structural roles. |
Comments | For example: PRIMAUTH, REVIEWER, VERF, etc. |