Skip to content

Discrepancies in the AuditEvent mappings #469

Closed
@qligier

Description

@qligier

A few things I saw when working with AuditRecordTranslator and AbstractFhirAuditSerializationStrategy.

In AuditRecordTranslator, the ActiveParticipant/RoleIDCode is mapped to agent.role. In IHE FHIR profiles (and in AbstractFhirAuditSerializationStrategy), it is mapped to agent.type.
There's a slight issue with the IHE mapping: RoleIDCode and agent.role can be multivalued, but not agent.type. Still, since a single RoleIDCode value is specified in IHE profiles, we should expect only one value.

In AbstractFhirAuditSerializationStrategy, when the AuditMessage comes from a non-FHIR transaction, the subtype.system is "IHE Transactions" instead of the valid urn:ihe:event-type-code.

Still in AbstractFhirAuditSerializationStrategy, the ParticipantObjectID is only mapped to entity.what if it refers to a patient.

PR: #470.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions