Current Build

Переводит команда Health Samurai . Приглашаем поучаствовать в русификации стандарта FHIR: GitHub , Email.

Electronic Health Records Work Group Maturity Level: 1Trial Use Use Context: Any

Определения для профиля ehrsrle-auditevent.

AuditEvent
Element IdAuditEvent
Definition

A record of an event made for purposes of maintaining a security log. Typical uses include detection of intrusion attempts and monitoring for inappropriate usage.

Control0..*
Comments

Based on IHE-ATNA.

Invariants
Inherited by this element
dom-2RuleЕсли ресурс встроен в другой ресурс, он НЕ ДОЛЖЕН содержать описательной частиcontained.contained.empty()
dom-3RuleЕсли ресурс встроен в другой ресурс, где-то в родительском ресурсе на него ДОЛЖНА БЫТЬ дана ссылка or SHALL refer to the containing resourcecontained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4RuleЕсли ресурс встроен в другой ресурс, он НЕ ДОЛЖЕН иметь meta.versionId или meta.lastUpdatedcontained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5RuleIf a resource is contained in another resource, it SHALL NOT have a security labelcontained.meta.security.empty()
dom-6GuidelineA resource should have narrative for robust managementtext.div.exists()
This is (only) a best practice guideline because:

When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.

AuditEvent.id
Element IdAuditEvent.id
Definition

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Control0..1
Typeid
Comments

The only time that a resource does not have an id is when it is being submitted to the server using a create operation.

AuditEvent.meta
Element IdAuditEvent.meta
Definition

Метаданные ресурса. Это такая информация, которая поддерживается инфраструктурой. Изменения этой информации не всегда можно ассоциировать с версионными изменениями ресурса.

Control0..1
TypeMeta
AuditEvent.implicitRules
Element IdAuditEvent.implicitRules
Definition

Ссылка на свод правил, которым следовали при создании этого ресурса и которые необходимо понимать при обработке этого содержимого. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Control0..1
Typeuri
Is Modifiertrue (Reason: This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation)
Comments

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.

AuditEvent.language
Element IdAuditEvent.language
Definition

Основной язык, на котором написан ресурс.

Control0..1
Terminology BindingЕстественный язык.
The codes SHOULD be taken from Language
Typecode
Comments

Язык указывается для поддержки предварительной обработки текстов и доступности для понимания (например при преобразовании текста в речь используется языковой тег). HTML-тег language в описательной части применяется к этой описательной части. Языковой тег ресурса может использоваться для указания языков других представлений, генерируемых из данных ресурса

Не все содержание ресурса должно быть на указанном основном языке. Resource.language нельзя автоматически принимать за язык описательной части. Если язык указан, его также следует указать в элементе div в HTML (информацию о связи между xml:lang и HTML-атрибутом lang см. в правилах HTML5).

AuditEvent.text
Element IdAuditEvent.text
Definition

Человекочитаемая описательная часть, содержащая краткое изложение ресурса, которая может использоваться для представления содержимого ресурса человеку. От описательной части не требуется кодировать все структурированные данные, но она должна содержать достаточно сведений, чтобы простое её прочтение человеком было "клинически безопасным". Определения ресурсов могут описывать, какое содержимое должно быть представлено в описательной части для обеспечения клинической безопасной.

Control0..1
TypeNarrative
Alternate Namesnarrative, html, xhtml, display
Comments

Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

AuditEvent.contained
Element IdAuditEvent.contained
Definition

Эти ресурсы не обладают независимым существованием вне ресурса, который их содержит - их нельзя идентифицировать независимо, и они не могут иметь своей собственной независимой транзакционной области действия.

Control0..*
TypeResource
Alternate Namesinline resources, anonymous resources, contained resources
Comments

Этого не следует делать, когда содержимое может быть идентифицировано должным образом, поскольку, потеряв идентификацию, будет чрезвычайно сложно (и контекстно-зависимо) снова восстановить её. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.

AuditEvent.extension
Element IdAuditEvent.extension
Definition

Может использоваться для представления дополнительной информации, не являющейся частью базового определения ресурса. Чтобы сделать использование расширений надежным и управляемым, существует строгий набор управления применительно к определению и использованию расширений. Хотя каждому реализатору разрешается определять расширения, имеется набор требований, которые должны выполняться в рамках определения расширения.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

Не должно быть никаких предрассудков по использованию расширений любыми приложениями, проектами или стандартами - вне зависимости от учреждения или юрисдикции, которые используют или задают расширение. Именно использование расширений позволяет спецификации FHIR сохранять простоту для всех.

AuditEvent.modifierExtension
Element IdAuditEvent.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue (Reason: Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them)
Alternate Namesextensions, user content
Comments

Не должно быть никаких предрассудков по использованию расширений любыми приложениями, проектами или стандартами - вне зависимости от учреждения или юрисдикции, которые используют или задают расширение. Именно использование расширений позволяет спецификации FHIR сохранять простоту для всех.

AuditEvent.type
Element IdAuditEvent.type
Definition

Identifier for a family of the event. For example, a menu item, program, rule, policy, function code, application name or URL. It identifies the performed function.

Control1..1
Terminology BindingType of event.
The codes SHALL be taken from Audit Event ID; other codes may be used where these codes are not suitable
TypeCoding
Must Supporttrue
Requirements

This identifies the performed function. For "Execute" Event Action Code audit records, this identifies the application function performed.

AuditEvent.subtype
Element IdAuditEvent.subtype
Definition

Identifier for the category of event.

Control0..*
Terminology BindingSub-type of event.
The codes SHALL be taken from Audit Event Sub-Type; other codes may be used where these codes are not suitable
TypeCoding
Must Supporttrue
Requirements

This field enables queries of messages by implementation-defined event categories.

AuditEvent.action
Element IdAuditEvent.action
Definition

Indicator for type of action performed during the event that generated the audit.

Control0..1
Terminology BindingIndicator for type of action performed during the event that generated the event.
The codes SHALL be taken from AuditEventAction
Typecode
Must Supporttrue
Requirements

This broadly indicates what kind of action was done on the AuditEvent.entity by the AuditEvent.agent.

AuditEvent.period
Element IdAuditEvent.period
Definition

The period during which the activity occurred.

Control0..1
TypePeriod
Comments

The period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.

AuditEvent.recorded
Element IdAuditEvent.recorded
Definition

The time when the event was recorded.

Control1..1
Typeinstant
Must Supporttrue
Requirements

This ties an event to a specific date and time. Security audits typically require a consistent time base (e.g. UTC), to eliminate time-zone issues arising from geographical distribution.

Comments

In a distributed system, some sort of common time base (e.g. an NTP [RFC1305] server) is a good implementation tactic.

AuditEvent.outcome
Element IdAuditEvent.outcome
Definition

Indicates whether the event succeeded or failed.

Control0..1
Terminology BindingIndicates whether the event succeeded or failed.
The codes SHALL be taken from AuditEventOutcome
Typecode
Comments

In some cases a "success" may be partial, for example, an incomplete or interrupted transfer of a radiological study. For the purpose of establishing accountability, these distinctions are not relevant.

AuditEvent.outcomeDesc
Element IdAuditEvent.outcomeDesc
Definition

A free text description of the outcome of the event.

Control0..1
Typestring
AuditEvent.purposeOfEvent
Element IdAuditEvent.purposeOfEvent
Definition

The purposeOfUse (reason) that was used during the event being recorded.

Control0..*
Terminology BindingThe reason the activity took place.
The codes SHALL be taken from V3 Value SetPurposeOfUse; other codes may be used where these codes are not suitable
TypeCodeableConcept
Must Supporttrue
Comments

Use AuditEvent.agent.purposeOfUse when you know that it is specific to the agent, otherwise use AuditEvent.purposeOfEvent. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.

AuditEvent.agent
Element IdAuditEvent.agent
Definition

An actor taking an active role in the event or activity that is logged.

Control1..*
TypeBackboneElement
Must Supporttrue
Requirements

An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility.

Alternate NamesActiveParticipant
Comments

Several agents may be associated (i.e. have some responsibility for an activity) with an event or activity.

For example, an activity may be initiated by one user for other users or involve more than one user. However, only one user may be the initiator/requestor for the activity.

Invariants
Inherited by this element
ele-1RuleAll FHIR elements must have a @value or childrenhasValue() or (children().count() > id.count())
AuditEvent.agent.id
Element IdAuditEvent.agent.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
AuditEvent.agent.extension
Element IdAuditEvent.agent.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.agent.modifierExtension
Element IdAuditEvent.agent.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue (Reason: Modifier extensions are expected to modify the meaning or interpretation of the element that contains them)
Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.agent.type
Element IdAuditEvent.agent.type
Definition

Specification of the participation type the user plays when performing the event.

Control0..1
Terminology BindingThe Participation type of the agent to the event.
The codes SHALL be taken from ParticipationRoleType; other codes may be used where these codes are not suitable
TypeCodeableConcept
AuditEvent.agent.role
Element IdAuditEvent.agent.role
Definition

The security role that the user was acting under, that come from local codes defined by the access control security system (e.g. RBAC, ABAC) used in the local context.

Control0..*
Terminology BindingWhat security role enabled the agent to participate in the event.
For example codes, see SecurityRoleType
TypeCodeableConcept
Must Supporttrue
Requirements

This value ties an audited event to a user's role(s). It is an optional value that might be used to group events for analysis by user functional role categories.

Comments

Should be roles relevant to the event. Should not be an exhaustive list of roles.

AuditEvent.agent.who
Element IdAuditEvent.agent.who
Definition

Reference to who this agent is that was involved in the event.

Control0..1
TypeReference(PractitionerRole)
Must Supporttrue
Requirements

This field ties an audit event to a specific resource or identifier.

Alternate NamesuserId
Comments

Where a User ID is available it will go into who.identifier.

AuditEvent.agent.altId
Element IdAuditEvent.agent.altId
Definition

Alternative agent Identifier. For a human, this should be a user identifier text string from authentication system. This identifier would be one known to a common authentication system (e.g. single sign-on), if available.

Control0..1
Typestring
Requirements

In some situations, a human user may authenticate with one identity but, to access a specific application system, may use a synonymous identify. For example, some "single sign on" implementations will do this. The alternative identifier would then be the original identify used for authentication, and the User ID is the one known to and used by the application.

AuditEvent.agent.name
Element IdAuditEvent.agent.name
Definition

Human-meaningful name for the agent.

Control0..1
Typestring
Requirements

The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.

AuditEvent.agent.requestor
Element IdAuditEvent.agent.requestor
Definition

Indicator that the user is or is not the requestor, or initiator, for the event being audited.

Control1..1
Typeboolean
Must Supporttrue
Requirements

This value is used to distinguish between requestor-users and recipient-users. For example, one person may initiate a report-output to be sent to another user.

Comments

There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.

AuditEvent.agent.location
Element IdAuditEvent.agent.location
Definition

Where the event occurred.

Control0..1
TypeReference(Location)
Must Supporttrue
AuditEvent.agent.policy
Element IdAuditEvent.agent.policy
Definition

The policy or plan that authorized the activity being recorded. Typically, a single activity may have multiple applicable policies, such as patient consent, guarantor funding, etc. The policy would also indicate the security token used.

Control0..*
Typeuri
Must Supporttrue
Requirements

This value is used retrospectively to determine the authorization policies.

Comments

For example: Where an OAuth token authorizes, the unique identifier from the OAuth token is placed into the policy element Where a policy engine (e.g. XACML) holds policy logic, the unique policy identifier is placed into the policy element.

AuditEvent.agent.media
Element IdAuditEvent.agent.media
Definition

Type of media involved. Used when the event is about exporting/importing onto media.

Control0..1
Terminology BindingUsed when the event is about exporting/importing onto media.
The codes SHALL be taken from Media Type Code; other codes may be used where these codes are not suitable
TypeCoding
Requirements

Usually, this is used instead of specifying a network address. This field is not used for Media Id (i.e. the serial number of a CD).

AuditEvent.agent.network
Element IdAuditEvent.agent.network
Definition

Logical network location for application activity, if the activity has a network location.

Control0..1
TypeBackboneElement
Must Supporttrue
Invariants
Inherited by this element
ele-1RuleAll FHIR elements must have a @value or childrenhasValue() or (children().count() > id.count())
AuditEvent.agent.network.id
Element IdAuditEvent.agent.network.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
AuditEvent.agent.network.extension
Element IdAuditEvent.agent.network.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.agent.network.modifierExtension
Element IdAuditEvent.agent.network.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue (Reason: Modifier extensions are expected to modify the meaning or interpretation of the element that contains them)
Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.agent.network.address
Element IdAuditEvent.agent.network.address
Definition

An identifier for the network access point of the user device for the audit event.

Control0..1
Typestring
Must Supporttrue
Requirements

This datum identifies the user's network access point, which may be distinct from the server that performed the action. It is an optional value that may be used to group events recorded on separate servers for analysis of a specific network access point's data access across all servers.

Comments

This could be a device id, IP address or some other identifier associated with a device.

AuditEvent.agent.network.type
Element IdAuditEvent.agent.network.type
Definition

An identifier for the type of network access point that originated the audit event.

Control0..1
Terminology BindingThe type of network access point of this agent in the audit event.
The codes SHALL be taken from AuditEventAgentNetworkType
Typecode
Must Supporttrue
Requirements

This datum identifies the type of network access point identifier of the user device for the audit event. It is an optional value that may be used to group events recorded on separate servers for analysis of access according to a network access point's type.

AuditEvent.agent.purposeOfUse
Element IdAuditEvent.agent.purposeOfUse
Definition

The reason (purpose of use), specific to this agent, that was used during the event being recorded.

Control0..*
Terminology BindingThe reason the activity took place.
The codes SHALL be taken from V3 Value SetPurposeOfUse; other codes may be used where these codes are not suitable
TypeCodeableConcept
Must Supporttrue
Comments

Use AuditEvent.agent.purposeOfUse when you know that is specific to the agent, otherwise use AuditEvent.purposeOfEvent. For example, during a machine-to-machine transfer it might not be obvious to the audit system who caused the event, but it does know why.

AuditEvent.source
Element IdAuditEvent.source
Definition

The system that is reporting the event.

Control1..1
TypeBackboneElement
Must Supporttrue
Requirements

The event is reported by one source.

Comments

Since multi-tier, distributed, or composite applications make source identification ambiguous, this collection of fields may repeat for each application or process actively involved in the event. For example, multiple value-sets can identify participating web servers, application processes, and database server threads in an n-tier distributed application. Passive event participants (e.g. low-level network transports) need not be identified.

Invariants
Inherited by this element
ele-1RuleAll FHIR elements must have a @value or childrenhasValue() or (children().count() > id.count())
AuditEvent.source.id
Element IdAuditEvent.source.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
AuditEvent.source.extension
Element IdAuditEvent.source.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.source.modifierExtension
Element IdAuditEvent.source.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue (Reason: Modifier extensions are expected to modify the meaning or interpretation of the element that contains them)
Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.source.site
Element IdAuditEvent.source.site
Definition

Logical source location within the healthcare enterprise network. For example, a hospital or other provider location within a multi-entity provider group.

Control0..1
Typestring
Must Supporttrue
Requirements

This value differentiates among the sites in a multi-site enterprise health information system.

AuditEvent.source.observer
Element IdAuditEvent.source.observer
Definition

Identifier of the source where the event was detected.

Control1..1
TypeReference(PractitionerRole)
Must Supporttrue
Requirements

This field ties the event to a specific source system. It may be used to group events for analysis according to where the event was detected.

Alternate NamesSourceId
AuditEvent.source.type
Element IdAuditEvent.source.type
Definition

Code specifying the type of source where event originated.

Control0..*
Terminology BindingCode specifying the type of system that detected and recorded the event.
The codes SHALL be taken from Audit Event Source Type; other codes may be used where these codes are not suitable
TypeCoding
Must Supporttrue
Requirements

This field indicates which type of source is identified by the Audit Source ID. It is an optional value that may be used to group events for analysis according to the type of source where the event occurred.

AuditEvent.entity
Element IdAuditEvent.entity
Definition

Specific instances of data or objects that have been accessed.

Control0..*
TypeBackboneElement
Must Supporttrue
Requirements

The event may have other entities involved.

Alternate NamesParticipantObject
Comments

Required unless the values for event identification, agent identification, and audit source identification are sufficient to document the entire auditable event. Because events may have more than one entity, this group can be a repeating set of values.

Invariants
Inherited by this element
ele-1RuleAll FHIR elements must have a @value or childrenhasValue() or (children().count() > id.count())
sev-1RuleEither a name or a query (NOT both)name.empty() or query.empty()
AuditEvent.entity.id
Element IdAuditEvent.entity.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
AuditEvent.entity.extension
Element IdAuditEvent.entity.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.entity.modifierExtension
Element IdAuditEvent.entity.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue (Reason: Modifier extensions are expected to modify the meaning or interpretation of the element that contains them)
Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.entity.what
Element IdAuditEvent.entity.what
Definition

Identifies a specific instance of the entity. The reference should be version specific.

Control0..1
TypeReference(Resource)
Must Supporttrue
AuditEvent.entity.type
Element IdAuditEvent.entity.type
Definition

The type of the object that was involved in this audit event.

Control0..1
Terminology BindingCode for the entity type involved in the audit event.
The codes SHALL be taken from Audit event entity type; other codes may be used where these codes are not suitable
TypeCoding
Must Supporttrue
Requirements

To describe the object being acted upon. In addition to queries on the subject of the action in an auditable event, it is also important to be able to query on the object type for the action.

Comments

This value is distinct from the user's role or any user relationship to the entity.

AuditEvent.entity.role
Element IdAuditEvent.entity.role
Definition

Code representing the role the entity played in the event being audited.

Control0..1
Terminology BindingCode representing the role the entity played in the audit event.
The codes SHALL be taken from AuditEventEntityRole; other codes may be used where these codes are not suitable
TypeCoding
Must Supporttrue
Requirements

For some detailed audit analysis it may be necessary to indicate a more granular type of entity, based on the application role it serves.

AuditEvent.entity.lifecycle
Element IdAuditEvent.entity.lifecycle
Definition

Identifier for the data life-cycle stage for the entity.

Control0..1
Terminology BindingIdentifier for the data life-cycle stage for the entity.
The codes SHALL be taken from http://hl7.org/fhir/ValueSet/object-lifecycle-events ; other codes may be used where these codes are not suitable
TypeCoding
Must Supporttrue
Requirements

Institutional policies for privacy and security may optionally fall under different accountability rules based on data life cycle. This provides a differentiating value for those cases.

Comments

This can be used to provide an audit trail for data, over time, as it passes through the system.

AuditEvent.entity.securityLabel
Element IdAuditEvent.entity.securityLabel
Definition

Security labels for the identified entity.

Control0..*
Terminology BindingSecurity Labels from the Healthcare Privacy and Security Classification System.
The codes SHALL be taken from SecurityLabels; other codes may be used where these codes are not suitable
TypeCoding
Must Supporttrue
Requirements

This field identifies the security labels for a specific instance of an object, such as a patient, to detect/track privacy and security issues.

Comments

Copied from entity meta security tags.

AuditEvent.entity.name
Element IdAuditEvent.entity.name
Definition

A name of the entity in the audit event.

Control0..1 This element is affected by the following invariants: sev-1
Typestring
Requirements

Use only where entity can't be identified with an identifier.

Comments

This field may be used in a query/report to identify audit events for a specific person. For example, where multiple synonymous entity identifiers (patient number, medical record number, encounter number, etc.) have been used.

AuditEvent.entity.description
Element IdAuditEvent.entity.description
Definition

Text that describes the entity in more detail.

Control0..1
Typestring
Requirements

Use only where entity can't be identified with an identifier.

AuditEvent.entity.query
Element IdAuditEvent.entity.query
Definition

The query parameters for a query-type entities.

Control0..1 This element is affected by the following invariants: sev-1
Typebase64Binary
Requirements

For query events, it may be necessary to capture the actual query input to the query process in order to identify the specific event. Because of differences among query implementations and data encoding for them, this is a base 64 encoded data blob. It may be subsequently decoded or interpreted by downstream audit analysis processing.

Comments

The meaning and secondary-encoding of the content of base64 encoded blob is specific to the AuditEvent.type, AuditEvent.subtype, AuditEvent.entity.type, and AuditEvent.entity.role. The base64 is a general-use and safe container for event specific data blobs regardless of the encoding used by the transaction being recorded. An AuditEvent consuming application must understand the event it is consuming and the formats used by the event. For example, if auditing an Oracle network database access, the Oracle formats must be understood as they will be simply encoded in the base64binary blob.

AuditEvent.entity.detail
Element IdAuditEvent.entity.detail
Definition

Tagged value pairs for conveying additional information about the entity.

Control0..*
TypeBackboneElement
Requirements

Implementation-defined data about specific details of the object accessed or used.

Invariants
Inherited by this element
ele-1RuleAll FHIR elements must have a @value or childrenhasValue() or (children().count() > id.count())
AuditEvent.entity.detail.id
Element IdAuditEvent.entity.detail.id
Definition

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

Control0..1
Typestring
AuditEvent.entity.detail.extension
Element IdAuditEvent.entity.detail.extension
Definition

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

Control0..*
TypeExtension
Alternate Namesextensions, user content
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.entity.detail.modifierExtension
Element IdAuditEvent.entity.detail.modifierExtension
Definition

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

Control0..*
TypeExtension
Is Modifiertrue (Reason: Modifier extensions are expected to modify the meaning or interpretation of the element that contains them)
Alternate Namesextensions, user content, modifiers
Comments

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

AuditEvent.entity.detail.type
Element IdAuditEvent.entity.detail.type
Definition

The type of extra detail provided in the value.

Control1..1
Typestring
AuditEvent.entity.detail.value[x]
Element IdAuditEvent.entity.detail.value[x]
Definition

The value of the extra detail.

Control1..1
TypeChoice of: string, base64Binary
[x] NoteSee Choice of Data Types for further information about how to use [x]
Requirements

Should not duplicate the entity value unless absolutely necessary.

Comments

The value can be string when known to be a string, else base64 encoding should be used to protect binary or undefined content. The meaning and secondary-encoding of the content of base64 encoded blob is specific to the AuditEvent.type, AuditEvent.subtype, AuditEvent.entity.type, and AuditEvent.entity.role. The base64 is a general-use and safe container for event specific data blobs regardless of the encoding used by the transaction being recorded. An AuditEvent consuming application must understand the event it is consuming and the formats used by the event. For example if auditing an Oracle network database access, the Oracle formats must be understood as they will be simply encoded in the base64binary blob.