SocialWelfareAuditEvent
SocialWelfareAuditEvent -profiililla siirretään sosiaalihuollon luovutusilmoituksen tiedot lokirekisterien säilytyspalveluun. Profiilista viitataan agent-ja entity-rakenteilla muihin luovutusilmoituksen tietojen välittämisessä tarvittaviin profiileihin ja laajennoksiin.
Yhdestä asiakastietojen luovutustapahtumasta tehdään yksi (1) luovutusilmoitus, johon kootaan kyseisessä luovutustapahtumassa luovutettujen asiakastietojen tiedot. SocialWelfareAuditEvent -resurssin agent-rakenteessa ilmoitetaan luovutustapahtumaan osallistuneiden toimijoiden tiedot. Asiakastiedot luovuttaneen rekisterinpitäjän tiedot ovat pakollisia rakenteessa. Lisäksi rakenteessa ilmoitetaan luovutuksen vastaanottajan tiedot. Luovutuksen vastaanottajan tietojen ilmoittamista on kuvattu tarkemmin soveltamisoppaan luvussa Tallenna luovutusilmoitus.
Jos luovutustapahtumassa luovutetaan erillisiä tietokokonaisuuksia (esimerkiksi kaksi asiakirjaa), jokaisen tietokokonaisuuden tiedot ilmoitetaan resurssissa omassa entity-rakenteessaan. Luovutetusta tietokokonaisuudesta on aina ilmoitettava ainakin joko asiakirjan yleinen asiakirjatyyppi, tarkennettu asiakirjatyyppi tai luovutetun asiakastiedon selite.
SocialWelfareAuditEvent (AuditEvent) | I | AuditEvent | Element idAuditEvent Sosiaalihuollon luovutusilmoitus DefinitionSocialWelfareAuditEvent -profiililla siirretään sosiaalihuollon luovutusilmoituksen tiedot valtakunnalliseen lokirekisterien säilytyspalveluun. Profiilista viitataan Agent-ja Entity-rakenteilla muihin luovutusilmoituksen tietojen välittämisessä tarvittaviin profiileihin ja laajennoksiin. Based on IHE-ATNA.
| |
id | Σ | 1..1 | string | Element idAuditEvent.id Luovutusilmoituksen yksilöivä tunnus DefinitionLuovutusilmoituksen globaalisti yksilöivä tunnus. Lähettävän järjestelmän on tuotettava luovutusilmoituksen tallennusta varten yksilöivä tunnus, joka on voimassa tiedonsiirron ajan. Luovutusilmoituksen tallennuksen yhteydessä Kanta-palvelut tuottaa luovutusilmoitukselle uuden yksilöivän tunnuksen. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idAuditEvent.meta Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
|
id | 0..1 | string | There are no (further) constraints on this element Element idAuditEvent.meta.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.meta.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
versionId | Σ | 0..1 | id | There are no (further) constraints on this element Element idAuditEvent.meta.versionId Version specific identifier DefinitionThe version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted. The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
|
lastUpdated | Σ | 0..1 | instant | There are no (further) constraints on this element Element idAuditEvent.meta.lastUpdated When the resource version last changed DefinitionWhen the resource last changed - e.g. when the version changed. This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a read interaction.
|
source | Σ | 0..1 | uri | There are no (further) constraints on this element Element idAuditEvent.meta.source Identifies where the resource comes from DefinitionA uri that identifies the source system of the resource. This provides a minimal amount of Provenance information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc. In the provenance resource, this corresponds to Provenance.entity.what[x]. The exact use of the source (and the implied Provenance.entity.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
|
profile | Σ | 1..1 | canonical(StructureDefinition)Fixed Value | Element idAuditEvent.meta.profile Profiles this resource claims to conform to DefinitionA list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. canonical(StructureDefinition) Constraints
https://shark.kanta.fi/fhir/StructureDefinition/SocialWelfareAuditEvent |
security | Σ | 0..* | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.meta.security Security Labels applied to this resource DefinitionSecurity labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Security Labels from the Healthcare Privacy and Security Classification System.
|
tag | Σ | 0..* | Coding | There are no (further) constraints on this element Element idAuditEvent.meta.tag Tags applied to this resource DefinitionTags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
|
implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idAuditEvent.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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.
|
language | 0..1 | codeBinding | There are no (further) constraints on this element Element idAuditEvent.language Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
| |
text | 0..1 | Narrative | There are no (further) constraints on this element Element idAuditEvent.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. 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.
| |
contained | 0..* | Resource | There are no (further) constraints on this element Element idAuditEvent.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.
| |
extension | I | 2..* | Extension | Element idAuditEvent.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. 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. 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. Unordered, Open, by url(Value) Constraints
|
StatuteOfDisclosure | I | 0..1 | Extension(string) | Element idAuditEvent.extension:StatuteOfDisclosure Luovutuksen perusteena oleva säädös Alternate namesextensions, user content DefinitionLaajennoksella ilmoitetaan laki tai asetus, johon luovutustapahtumassa luovutettujen asiakastietojen luovuttaminen perustuu. Laajennos on pakollinen, jos asiakastietojen luovuttaminen perustuu lakiin, asetukseen tai tietopyyntöön. Laajennos liitetään SocialWelfareAuditEvent -profiiliin. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/StatuteOfDisclosure Constraints
|
Consent | I | 0..1 | Extension(Reference()) | Element idAuditEvent.extension:Consent Luovutusluvan tai suostumuksen tiedot Alternate namesextensions, user content DefinitionLaajennoksella ilmoitetaan asiakkaan tai hänen laillisen edustajansa antaman luovutusluvan tai suostumuksen tiedot, johon asiakastietojen luovuttaminen luovutustapahtumassa on perustunut. Luovutusluvan tai suostumuksen tiedot ovat pakollisia, jos luovutustapahtumassa luovutettujen asiakastietojen luovuttaminen perustuu asiakkaan tai hänen laillisen edustajansa antamaan luovutuslupaan tai suostumukseen. Laajennos liitetään SocialWelfareAuditEvent -profiiliin. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/Consent Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. https://shark.kanta.fi/fhir/StructureDefinition/extension/Consent
| |
value[x] | 1..1 | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.value[x] Luovutusluvan tai suostumuksen tiedot DefinitionAsiakkaan tai hänen laillisen edustajansa antaman luovutusluvan tai suostumuksen tiedot on kuvattu profiilissa SocialWelfareConsent.
| ||
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.value[x].id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.value[x].extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 0..1 | string | Element idAuditEvent.extension:Consent.value[x].reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.value[x].type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.value[x].identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.extension:Consent.value[x].display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
valueReference | Reference(SocialWelfareConsent) | Data type Reference(SocialWelfareConsent) Allowed aggregation: contained | ||
TypeOfDisclosure | I | 1..1 | Extension(Coding) | Element idAuditEvent.extension:TypeOfDisclosure Asiakastietojen luovutustapa Alternate namesextensions, user content DefinitionLaajennoksella ilmoitetaan miten luovutustapahtumassa luovutetut asiakastiedot on luovutettu. Laajennos liitetään SocialWelfareAuditEvent -profiiliin. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/TypeOfDisclosure Constraints
|
BusinessIdentifier | I | 1..1 | Extension(Identifier) | Element idAuditEvent.extension:BusinessIdentifier Luovutusilmoituksen yksilöivä tunnus organisaatiossa Alternate namesextensions, user content DefinitionOrganisaation käyttämä luovutusilmoituksen yksilöivä tunnus. Yksilöivän tunnuksen on oltava globaalisti yksilöivä. Lähettävä järjestelmä voi tuottaa organisaation käyttämän yksilöivän tunnuksen luovutusilmoitukselle, jota voidaan hyödyntää esimerkiksi virhetilanteiden selvittämisessä. 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. https://gen.kanta.fi/fhir/StructureDefinition/extension/BusinessIdentifier Constraints
|
modifierExtension | ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | Σ | 1..1 | CodingBinding | Element idAuditEvent.type Type/identifier of event DefinitionIdentifier 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. This identifies the performed function. For "Execute" Event Action Code audit records, this identifies the application function performed. Type of event.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.type.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.type.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.type.code Disclose Record Lifecycle Event DefinitionOccurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content. Need to refer to a particular code in the system.
disclose
|
display | Σ | 1..1 | stringFixed Value | Element idAuditEvent.type.display Disclose Record Lifecycle Event DefinitionOccurs when an agent causes the system to release, transfer, provision access to, or otherwise divulge record entry content. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
Disclose Record Lifecycle Event
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.type.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
subtype | Σ | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.subtype More specific type/id for the event DefinitionIdentifier for the category of event. This field enables queries of messages by implementation-defined event categories. Sub-type of event.
|
action | Σ | 0..0 | codeBinding | There are no (further) constraints on this element Element idAuditEvent.action Type of action performed during the event DefinitionIndicator for type of action performed during the event that generated the audit. This broadly indicates what kind of action was done on the AuditEvent.entity by the AuditEvent.agent. Indicator for type of action performed during the event that generated the event.
|
period | 1..1 | Period | Element idAuditEvent.period Tapahtuma-aika DefinitionLokimerkinnän aiheuttaneen luovutuksen päivämäärä tai aikaleima (pvm + aika). The period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.period.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.period.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
start | Σ I | 1..1 | dateTime | There are no (further) constraints on this element Element idAuditEvent.period.start Starting time with inclusive boundary DefinitionThe start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.
|
end | Σ I | 0..0 | dateTime | There are no (further) constraints on this element Element idAuditEvent.period.end End time with inclusive boundary, if not ongoing DefinitionThe end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03. If the end of the period is missing, it means that the period is ongoing
|
recorded | Σ | 1..1 | instant | Element idAuditEvent.recorded Laatimisaika DefinitionAjankohta, jolloin luovutusilmoitus on valmistunut eikä siihen tehdä enää muutoksia. Jos luovutusilmoitus koostetaan samaan luovutustapahtumaan kuuluvista asiakastietojen luovutuksista, laatimisaika tarkoittaa luovutusilmoituksen muodostamisen ajankohtaa. 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. In a distributed system, some sort of common time base (e.g. an NTP [RFC1305] server) is a good implementation tactic.
|
outcome | Σ | 0..0 | codeBinding | There are no (further) constraints on this element Element idAuditEvent.outcome Whether the event succeeded or failed DefinitionIndicates whether the event succeeded or failed. 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. Indicates whether the event succeeded or failed.
|
outcomeDesc | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.outcomeDesc Description of the event outcome DefinitionA free text description of the outcome of the event.
|
purposeOfEvent | Σ | 1..1 | CodeableConceptBinding | Element idAuditEvent.purposeOfEvent Asiakastietojen käyttötarkoitus DefinitionKäyttötarkoitus, johon asiakastiedot on luovutettu. Ilmoitetaan koodistolla THL - Asiakastietojen käyttötarkoitus (1.2.246.537.6.3300.202201). Yhdessä tietojen luovutuksessa on aina yksi asiakastietojen käyttötarkoitus. Jos asiakastietoja luovutetaan samalle vastaanottajalle eri käyttötarkoituksiin, katsotaan luovutukset omiksi luovutuksikseen ja niistä tehdään omat luovutusilmoituksensa. 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. Asiakastietojen käyttötarkoitus
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | code | Element idAuditEvent.purposeOfEvent.coding.code Käyttötarkoituksen koodiarvo DefinitionValuesetin Social Welfare Purpose Of Use mukainen käyttötarkoituksen koodiarvo. Need to refer to a particular code in the system.
|
display | Σ | 1..1 | string | Element idAuditEvent.purposeOfEvent.coding.display Käyttötarkoituksen nimi DefinitionValuesetin Social Welfare Purpose Of Use mukainen käyttötarkoituksen arvo. Arvon nimen on vastattava annettua koodiarvoa. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.purposeOfEvent.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
agent | 1..* | BackboneElement | Element idAuditEvent.agent Luovutustapahtumaan osallistuneet toimijat Alternate namesActiveParticipant DefinitionAgent-rakenteessa ilmoitetaan luovutustapahtumaan osallistuneiden toimijoiden tiedot. Asiakastietojen luovutuksesta on ilmoitettava aina tiedot luovuttanut rekisterinpitäjä. Lisäksi on aina ilmoitettava luovutuksen vastaanottaja, joka on organisaatio, ammattihenkilö, asiakas tai asiakkaan laillinen edustaja. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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. Unordered, Closed, by role.coding.code(Value) Constraints
| |
(All Slices) | There are no (further) constraints on this element | |||
id | 0..1 | string | There are no (further) constraints on this element Element idAuditEvent.agent.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent.type How agent participated DefinitionSpecification of the participation type the user plays when performing the event. The Participation type of the agent to the event.
| |
role | 0..* | CodeableConcept | There are no (further) constraints on this element Element idAuditEvent.agent.role Agent role in the event DefinitionThe 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. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
who | Σ | 1..1 | Reference(SocialWelfareRelatedPerson | SocialWelfareAuditEventOrganization | SocialWelfarePatient | KantaDevice | SocialWelfarePractitionerRole | SocialWelfarePractitioner) | Element idAuditEvent.agent.who Identifier of who Alternate namesuserId DefinitionReference to who this agent is that was involved in the event. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Reference(SocialWelfareRelatedPerson | SocialWelfareAuditEventOrganization | SocialWelfarePatient | KantaDevice | SocialWelfarePractitionerRole | SocialWelfarePractitioner) Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..1 | string | There are no (further) constraints on this element Element idAuditEvent.agent.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..1 | string | There are no (further) constraints on this element Element idAuditEvent.agent.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent.requestor Whether user is initiator DefinitionIndicator that the user is or is not the requestor, or initiator, for the event being audited. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
|
location | 0..1 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent.location Where DefinitionWhere the event occurred.
| |
policy | 0..* | uri | There are no (further) constraints on this element Element idAuditEvent.agent.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..1 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..1 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
id | 0..1 | string | There are no (further) constraints on this element Element idAuditEvent.agent.network.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent.network.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent.network.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
address | 0..1 | string | There are no (further) constraints on this element Element idAuditEvent.agent.network.address Identifier for the network access point of the user device DefinitionAn identifier for the network access point of the user device for the audit event. 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. This could be a device id, IP address or some other identifier associated with a device.
| |
type | 0..1 | codeBinding | There are no (further) constraints on this element Element idAuditEvent.agent.network.type The type of network access point DefinitionAn identifier for the type of network access point that originated the audit event. 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. The type of network access point of this agent in the audit event.
| |
purposeOfUse | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
OrganizationReceivingDisclosure | 0..1 | BackboneElement | Element idAuditEvent.agent:OrganizationReceivingDisclosure Asiakastiedot vastaanottanut organisaatio Alternate namesActiveParticipant DefinitionSen organisaation tiedot, jolle asiakastietojen rekisterinpitäjä on luovuttanut asiakkaan asiakastiedot luovutustapahtumassa. Vastaanottaneen organisaation tiedot ovat pakolliset, jos asiakastiedot on luovutettu organisaatioille. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.type How agent participated DefinitionSpecification of the participation type the user plays when performing the event. The Participation type of the agent to the event.
| |
role | 1..1 | CodeableConceptBinding | Element idAuditEvent.agent:OrganizationReceivingDisclosure.role Asiakastiedot vastaanottanut organisaatio DefinitionOrganisaatio on osallistunut luovutustapahtumaan ottamalla vastaan luovutetut asiakastiedot. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.coding Social Welfare AuditEvent Role Category DefinitionKoodiston arvoilla ilmoitetaan mikä on toimijan (organisaatio, henkilö tai tietojärjestelmä) rooli luovutustapahtumassa, josta luovutusilmoitus tehdään. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.coding.code Roolin koodiarvo DefinitionKoodiarvo, joka kertoo luovutustapahtumaan osallistuneen toimijan roolin luovutustapahtumassa. Need to refer to a particular code in the system.
2
|
display | Σ | 1..1 | string | Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.coding.display Asiakastiedot vastaanottanut organisaatio DefinitionOrganisaatio, joka on ottanut vastaan luovutustapahtumassa luovutetut sosiaalihuollon asiakkaan asiakastiedot. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.role.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
who | Σ | 1..1 | Reference(SocialWelfareAuditEventOrganization) | Element idAuditEvent.agent:OrganizationReceivingDisclosure.who Identifier of who Alternate namesuserId DefinitionReference to who this agent is that was involved in the event. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Reference(SocialWelfareAuditEventOrganization) Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent:OrganizationReceivingDisclosure.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | booleanFixed Value | Element idAuditEvent.agent:OrganizationReceivingDisclosure.requestor False DefinitionIlmoitetaan arvo False. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
false
|
location | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.location Where DefinitionWhere the event occurred.
| |
policy | 0..0 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
purposeOfUse | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:OrganizationReceivingDisclosure.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
DisclosingDevice | 0..1 | BackboneElement | Element idAuditEvent.agent:DisclosingDevice Asiakastiedot luovuttanut tietojärjestelmä Alternate namesActiveParticipant DefinitionSen tietojärjestelmän tiedot, josta asiakkaan asiakastiedot on luovutettu luovutustapahtumassa. Asiakastiedot luovuttaneen tietojärjestelmän tiedot ovat pakollisia, jos asiakastietojen luovutus tapahtuu teknisen rajapinnan tai katseluyhteyden kautta. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..0 | CodeableConceptBinding | Element idAuditEvent.agent:DisclosingDevice.type Asiakastiedot luovuttanut tietojärjestelmä DefinitionTietojärjestelmä on osallistunut luovutustapahtumaan luovuttamalla asiakastiedot. The Participation type of the agent to the event.
| |
role | 1..1 | CodeableConceptBinding | Element idAuditEvent.agent:DisclosingDevice.role Asiakastiedot luovuttanut tietojärjestelmä DefinitionTietojärjestelmä on osallistunut luovutustapahtumaan luovuttamalla asiakastiedot. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | Element idAuditEvent.agent:DisclosingDevice.role.coding Social Welfare AuditEvent Role Category DefinitionKoodiston arvoilla ilmoitetaan mikä on toimijan (organisaatio, henkilö tai tietojärjestelmä) rooli luovutustapahtumassa, josta luovutusilmoitus tehdään. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.role.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.role.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.role.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.role.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.agent:DisclosingDevice.role.coding.code Roolin koodiarvo DefinitionKoodiarvo, joka kertoo luovutustapahtumaan osallistuneen toimijan roolin luovutustapahtumassa. Need to refer to a particular code in the system.
3
|
display | Σ | 1..1 | string | Element idAuditEvent.agent:DisclosingDevice.role.coding.display Asiakastiedot luovuttanut tietojärjestelmä DefinitionTietojärjestelmä on osallistunut luovutustapahtumaan luovuttamalla asiakastiedot. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.role.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.role.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
who | Σ | 1..1 | Reference(KantaDevice) | Element idAuditEvent.agent:DisclosingDevice.who Identifier of who Alternate namesuserId DefinitionReference to who this agent is that was involved in the event. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent:DisclosingDevice.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | booleanFixed Value | Element idAuditEvent.agent:DisclosingDevice.requestor False DefinitionIlmoitetaan arvo False. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
false
|
location | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.location Where DefinitionWhere the event occurred.
| |
policy | 0..0 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
purposeOfUse | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingDevice.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
DeviceReceivingDisclosure | 0..1 | BackboneElement | Element idAuditEvent.agent:DeviceReceivingDisclosure Asiakastiedot vastaanottanut tietojärjestelmä Alternate namesActiveParticipant DefinitionSen tietojärjestelmän tiedot, joka on ottanut vastaan luovutetut asiakkaan asiakastiedot luovutustapahtumassa. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.type How agent participated DefinitionSpecification of the participation type the user plays when performing the event. The Participation type of the agent to the event.
| |
role | 1..1 | CodeableConceptBinding | Element idAuditEvent.agent:DeviceReceivingDisclosure.role Asiakastiedot vastaanottanut tietojärjestelmä DefinitionTietojärjestelmä on osallistunut luovutustapahtumaan ottamalla vastaan luovutetut asiakastiedot. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | Element idAuditEvent.agent:DeviceReceivingDisclosure.role.coding Social Welfare AuditEvent Role Category DefinitionKoodiston arvoilla ilmoitetaan mikä on toimijan (organisaatio, henkilö tai tietojärjestelmä) rooli luovutustapahtumassa, josta luovutusilmoitus tehdään. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.role.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.role.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.role.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.role.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.agent:DeviceReceivingDisclosure.role.coding.code Roolin koodiarvo DefinitionKoodiarvo, joka kertoo luovutustapahtumaan osallistuneen toimijan roolin luovutustapahtumassa. Need to refer to a particular code in the system.
4
|
display | Σ | 1..1 | string | Element idAuditEvent.agent:DeviceReceivingDisclosure.role.coding.display Asiakastiedot vastaanottanut tietojärjestelmä DefinitionTietojärjestelmä on osallistunut luovutustapahtumaan ottamalla vastaan luovutetut asiakastiedot. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.role.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.role.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
who | Σ | 1..1 | Reference(KantaDevice) | Element idAuditEvent.agent:DeviceReceivingDisclosure.who Identifier of who Alternate namesuserId DefinitionReference to who this agent is that was involved in the event. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent:DeviceReceivingDisclosure.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | booleanFixed Value | Element idAuditEvent.agent:DeviceReceivingDisclosure.requestor False DefinitionIlmoitetaan arvo False. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
false
|
location | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.location Where DefinitionWhere the event occurred.
| |
policy | 0..0 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
purposeOfUse | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DeviceReceivingDisclosure.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
DisclosingPractitioner | 0..1 | BackboneElement | Element idAuditEvent.agent:DisclosingPractitioner Asiakastiedot luovuttanut ammattihenkilö Alternate namesActiveParticipant DefinitionSen rekisterinpitäjän palveluksessa olevan ammattihenkilön tiedot, joka on luovuttanut asiakkaan asiakastiedot luovutustapahtumassa. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.type How agent participated DefinitionSpecification of the participation type the user plays when performing the event. The Participation type of the agent to the event.
| |
role | 1..1 | CodeableConceptBinding | Element idAuditEvent.agent:DisclosingPractitioner.role Asiakastiedot luovuttanut ammattihenkilö DefinitionAmmattihenkilö on osallistunut luovutustapahtumaan luovuttamalla asiakkaan asiakastiedot. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | Element idAuditEvent.agent:DisclosingPractitioner.role.coding Social Welfare AuditEvent Role Category DefinitionKoodiston arvoilla ilmoitetaan mikä on toimijan (organisaatio, henkilö tai tietojärjestelmä) rooli luovutustapahtumassa, josta luovutusilmoitus tehdään. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.role.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.role.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.role.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.role.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.agent:DisclosingPractitioner.role.coding.code Roolin koodiarvo DefinitionKoodiarvo, joka kertoo luovutustapahtumaan osallistuneen toimijan roolin luovutustapahtumassa. Need to refer to a particular code in the system.
5
|
display | Σ | 1..1 | string | Element idAuditEvent.agent:DisclosingPractitioner.role.coding.display Asiakastiedot luovuttanut ammattihenkilö DefinitionSosiaalihuollon ammattihenkilö on osallistunut luovutustapahtumaan luovuttamalla asiakkaan asiakastiedot. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.role.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.role.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
who | Σ | 1..1 | Reference(SocialWelfarePractitionerRole) | Element idAuditEvent.agent:DisclosingPractitioner.who Asiakastiedot luovuttanut ammattihenkilö Alternate namesuserId DefinitionAsiakastiedot luovuttaneen ammattihenkilön tiedot. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Reference(SocialWelfarePractitionerRole) Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent:DisclosingPractitioner.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | booleanFixed Value | Element idAuditEvent.agent:DisclosingPractitioner.requestor False DefinitionIlmoitetaan arvo False. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
false
|
location | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.location Where DefinitionWhere the event occurred.
| |
policy | 0..0 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
purposeOfUse | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:DisclosingPractitioner.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
PractitionerReceivingDisclosure | 0..1 | BackboneElement | Element idAuditEvent.agent:PractitionerReceivingDisclosure Asiakastiedot vastaanottanut ammattihenkilö Alternate namesActiveParticipant DefinitionSen ammattihenkilön tiedot, jolle asiakastietojen rekisterinpitäjä on luovuttanut asiakkaan asiakastiedot luovutustapahtumassa. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.type How agent participated DefinitionSpecification of the participation type the user plays when performing the event. The Participation type of the agent to the event.
| |
role | 1..1 | CodeableConceptBinding | Element idAuditEvent.agent:PractitionerReceivingDisclosure.role Asiakastiedot vastaanottanut ammattihenkilö DefinitionAmmattihenkilö on osallistunut luovutustapahtumaan ottamalla vastaan luovutetut asiakastiedot. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.coding Social Welfare AuditEvent Role Category DefinitionKoodiston arvoilla ilmoitetaan mikä on toimijan (organisaatio, henkilö tai tietojärjestelmä) rooli luovutustapahtumassa, josta luovutusilmoitus tehdään. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.coding.code Roolin koodiarvo DefinitionKoodiarvo, joka kertoo luovutustapahtumaan osallistuneen toimijan roolin luovutustapahtumassa. Need to refer to a particular code in the system.
6
|
display | Σ | 1..1 | string | Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.coding.display Asiakastiedot vastaanottanut ammattihenkilö DefinitionAmmattihenkilö, joka on ottanut vastaan luovutustapahtumassa luovutetut asiakastiedot. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.role.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
who | Σ | 1..1 | Reference(SocialWelfarePractitioner) | Element idAuditEvent.agent:PractitionerReceivingDisclosure.who Identifier of who Alternate namesuserId DefinitionReference to who this agent is that was involved in the event. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Reference(SocialWelfarePractitioner) Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent:PractitionerReceivingDisclosure.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | booleanFixed Value | Element idAuditEvent.agent:PractitionerReceivingDisclosure.requestor False DefinitionIlmoitetaan arvo False. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
false
|
location | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.location Where DefinitionWhere the event occurred.
| |
policy | 0..0 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
purposeOfUse | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:PractitionerReceivingDisclosure.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
CustodianOfDisclosure | 1..1 | BackboneElement | Element idAuditEvent.agent:CustodianOfDisclosure Asiakastiedot luovuttanut rekisterinpitäjä Alternate namesActiveParticipant DefinitionRekisterinpitäjä, joka on luovuttanut sosiaalihuollon asiakkaan asiakastiedot luovutustapahtumassa. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.type How agent participated DefinitionSpecification of the participation type the user plays when performing the event. The Participation type of the agent to the event.
| |
role | 1..1 | CodeableConceptBinding | Element idAuditEvent.agent:CustodianOfDisclosure.role Asiakastiedot luovuttanut rekisterinpitäjä DefinitionRekisterinpitäjä on osallistunut luovutustapahtumaan luovuttamalla asiakastiedot. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | Element idAuditEvent.agent:CustodianOfDisclosure.role.coding Social Welfare AuditEvent Role Category DefinitionKoodiston arvoilla ilmoitetaan mikä on toimijan (organisaatio, henkilö tai tietojärjestelmä) rooli luovutustapahtumassa, josta luovutusilmoitus tehdään. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.role.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.role.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.role.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.role.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.agent:CustodianOfDisclosure.role.coding.code Roolin koodiarvo DefinitionKoodiarvo, joka kertoo luovutustapahtumaan osallistuneen toimijan roolin luovutustapahtumassa. Need to refer to a particular code in the system.
1
|
display | Σ | 1..1 | string | Element idAuditEvent.agent:CustodianOfDisclosure.role.coding.display Asiakastiedot luovuttanut rekisterinpitäjä DefinitionRekisterinpitäjä, joka on luovuttanut luovutustapahtumassa sosiaalihuollon asiakkaan asiakastiedot. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.role.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.role.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
who | Σ | 1..1 | Reference(SocialWelfareAuditEventOrganization) | Element idAuditEvent.agent:CustodianOfDisclosure.who Identifier of who Alternate namesuserId DefinitionReference to who this agent is that was involved in the event. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Reference(SocialWelfareAuditEventOrganization) Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent:CustodianOfDisclosure.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | booleanFixed Value | Element idAuditEvent.agent:CustodianOfDisclosure.requestor True DefinitionIlmoitetaan arvo True. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
true
|
location | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.location Where DefinitionWhere the event occurred.
| |
policy | 0..0 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
purposeOfUse | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:CustodianOfDisclosure.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
PatientReceivingDisclosure | 0..1 | BackboneElement | Element idAuditEvent.agent:PatientReceivingDisclosure Asiakastiedot vastaanottanut asiakas Alternate namesActiveParticipant DefinitionSen asiakkaan tiedot, jolle asiakastietojen rekisterinpitäjä on luovuttanut asiakastiedot luovutustapahtumassa. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.type How agent participated DefinitionSpecification of the participation type the user plays when performing the event. The Participation type of the agent to the event.
| |
role | 1..1 | CodeableConceptBinding | Element idAuditEvent.agent:PatientReceivingDisclosure.role Asiakastiedot vastaanottanut asiakas DefinitionAsiakas on osallistunut luovutustapahtumaan ottamalla vastaan luovutetut asiakastietonsa. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | Element idAuditEvent.agent:PatientReceivingDisclosure.role.coding Social Welfare AuditEvent Role Category DefinitionKoodiston arvoilla ilmoitetaan mikä on toimijan (organisaatio, henkilö tai tietojärjestelmä) rooli luovutustapahtumassa, josta luovutusilmoitus tehdään. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.role.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.role.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.role.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.role.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.agent:PatientReceivingDisclosure.role.coding.code Roolin koodiarvo DefinitionKoodiarvo, joka kertoo luovutustapahtumaan osallistuneen toimijan roolin luovutustapahtumassa. Need to refer to a particular code in the system.
7
|
display | Σ | 1..1 | string | Element idAuditEvent.agent:PatientReceivingDisclosure.role.coding.display Asiakastiedot vastaanottanut asiakas DefinitionAsiakas, joka on ottanut vastaan luovutustapahtumassa luovutetut asiakastietonsa. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.role.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.role.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
who | Σ | 1..1 | Reference(SocialWelfarePatient) | Element idAuditEvent.agent:PatientReceivingDisclosure.who Identifier of who Alternate namesuserId DefinitionReference to who this agent is that was involved in the event. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Reference(SocialWelfarePatient) Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent:PatientReceivingDisclosure.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | booleanFixed Value | Element idAuditEvent.agent:PatientReceivingDisclosure.requestor False DefinitionIlmoitetaan arvo False. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
false
|
location | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.location Where DefinitionWhere the event occurred.
| |
policy | 0..0 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
purposeOfUse | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:PatientReceivingDisclosure.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
LegalRepresentativeReceivingDisclosure | 0..1 | BackboneElement | Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure Asiakastiedot vastaanottanut laillinen edustaja Alternate namesActiveParticipant DefinitionSen asiakkaan laillisen edustajan tiedot, jolle asiakastietojen rekisterinpitäjä on luovuttanut asiakkaan asiakastiedot luovutustapahtumassa. An agent can be a person, an organization, software, device, or other actors that may be ascribed responsibility. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
type | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.type How agent participated DefinitionSpecification of the participation type the user plays when performing the event. The Participation type of the agent to the event.
| |
role | 1..1 | CodeableConceptBinding | Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role Asiakastiedot vastaanottanut laillinen edustaja DefinitionAsiakkaan laillinen edustaja on osallistunut luovutustapahtumaan ottamalla vastaan luovutetut asiakastiedot. 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. Should be roles relevant to the event. Should not be an exhaustive list of roles. What security role enabled the agent to participate in the event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
coding | Σ | 1..1 | Coding | Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.coding Social Welfare AuditEvent Role Category DefinitionKoodiston arvoilla ilmoitetaan mikä on toimijan (organisaatio, henkilö tai tietojärjestelmä) rooli luovutustapahtumassa, josta luovutusilmoitus tehdään. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.coding.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.coding.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.coding.code Roolin koodiarvo DefinitionKoodiarvo, joka kertoo luovutustapahtumaan osallistuneen toimijan roolin luovutustapahtumassa. Need to refer to a particular code in the system.
8
|
display | Σ | 1..1 | string | Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.coding.display Asiakastiedot vastaanottanut laillinen edustaja DefinitionAsiakkaan laillinen edustaja, joka on ottanut vastaan luovutustapahtumassa luovutetut asiakastiedot. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
text | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.role.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
who | Σ | 1..1 | Reference(SocialWelfareRelatedPerson) | Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.who Identifier of who Alternate namesuserId DefinitionReference to who this agent is that was involved in the event. This field ties an audit event to a specific resource or identifier. Where a User ID is available it will go into who.identifier. Reference(SocialWelfareRelatedPerson) Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.who.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.who.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.who.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.who.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.who.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.who.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
altId | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.altId Alternative User identity DefinitionAlternative 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. 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.
| |
name | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.name Human friendly name for the agent DefinitionHuman-meaningful name for the agent. The User ID and Authorization User ID may be internal or otherwise obscure values. This field assists the auditor in identifying the actual user.
| |
requestor | Σ | 1..1 | booleanFixed Value | Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.requestor False DefinitionIlmoitetaan arvo False. 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. There can only be one initiator. If the initiator is not clear, then do not choose any one agent as the initiator.
false
|
location | 0..0 | Reference(Location) | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.location Where DefinitionWhere the event occurred.
| |
policy | 0..0 | uri | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.policy Policy that authorized event DefinitionThe 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. This value is used retrospectively to determine the authorization policies. 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.
| |
media | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.media Type of media DefinitionType of media involved. Used when the event is about exporting/importing onto media. 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). Used when the event is about exporting/importing onto media.
| |
network | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.network Logical network location for application activity DefinitionLogical network location for application activity, if the activity has a network location.
| |
purposeOfUse | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.agent:LegalRepresentativeReceivingDisclosure.purposeOfUse Reason given for this user DefinitionThe reason (purpose of use), specific to this agent, that was used during the event being recorded. 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. The reason the activity took place.
| |
source | 1..1 | BackboneElement | Element idAuditEvent.source Luovutusilmoituksen tuottanut tietojärjestelmä DefinitionSen tietojärjestelmän tiedot, joka on tuottanut luovutusilmoituksen. The event is reported by one source. 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.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.source.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.source.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.source.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
site | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.source.site Logical source location within the enterprise DefinitionLogical source location within the healthcare enterprise network. For example, a hospital or other provider location within a multi-entity provider group. This value differentiates among the sites in a multi-site enterprise health information system.
| |
observer | Σ | 1..1 | Reference(KantaDevice) | Element idAuditEvent.source.observer Luovutusilmoituksen tuottaneen tietojärjestelmän yksilöivä tunnus Alternate namesSourceId DefinitionSen tietojärjestelmän yksilöivä tunnus, joka on tuottanut luovutusilmoituksen luovutustapahtumasta. 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. Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.source.observer.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.source.observer.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.source.observer.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.source.observer.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.source.observer.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.source.observer.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
type | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.source.type The type of source where event originated DefinitionCode specifying the type of source where event originated. 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. Code specifying the type of system that detected and recorded the event.
| |
entity | I | 1..* | BackboneElement | Element idAuditEvent.entity Luovutetun tietokokonaisuuden tiedot Alternate namesParticipantObject DefinitionLuovutetun tietokokonaisuuden yksilöivät tiedot ja/tai sen kontekstin yksilöivät tiedot. Jokaisesta luovutetusta erillisestä tietokonaisuudesta tehdään oma merkintänsä. The event may have other entities involved. 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. Unordered, Closed, by type.code(Value) Constraints
|
(All Slices) | There are no (further) constraints on this element | |||
id | 0..1 | string | There are no (further) constraints on this element Element idAuditEvent.entity.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
what | Σ | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idAuditEvent.entity.what Specific instance of resource DefinitionIdentifies a specific instance of the entity. The reference should be version specific.
|
type | 1..1 | CodingBinding | Element idAuditEvent.entity.type Type of entity involved DefinitionThe type of the object that was involved in this audit event. 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. This value is distinct from the user's role or any user relationship to the entity. Code for the entity type involved in the audit event.
| |
role | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity.role What role the entity played DefinitionCode representing the role the entity played in the event being audited. For some detailed audit analysis it may be necessary to indicate a more granular type of entity, based on the application role it serves. Code representing the role the entity played in the audit event.
| |
lifecycle | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity.lifecycle Life-cycle stage for the entity DefinitionIdentifier for the data life-cycle stage for the entity. 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. This can be used to provide an audit trail for data, over time, as it passes through the system. Identifier for the data life-cycle stage for the entity.
| |
securityLabel | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity.securityLabel Security labels on the entity DefinitionSecurity labels for the identified entity. This field identifies the security labels for a specific instance of an object, such as a patient, to detect/track privacy and security issues. Copied from entity meta security tags. Security Labels from the Healthcare Privacy and Security Classification System.
| |
name | Σ I | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity.name Descriptor for entity DefinitionA name of the entity in the audit event. Use only where entity can't be identified with an identifier. 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.
|
description | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity.description Descriptive text DefinitionText that describes the entity in more detail. Use only where entity can't be identified with an identifier.
| |
query | Σ I | 0..0 | base64Binary | There are no (further) constraints on this element Element idAuditEvent.entity.query Query parameters DefinitionThe query parameters for a query-type entities. 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. 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.
|
detail | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.entity.detail Additional Information about the entity DefinitionTagged value pairs for conveying additional information about the entity. Implementation-defined data about specific details of the object accessed or used.
| |
Patient | I | 1..1 | BackboneElement | Element idAuditEvent.entity:Patient Asiakas, jonka tietoja on luovutettu Alternate namesParticipantObject DefinitionSen sosiaalihuollon asiakkaan tiedot, jonka asiakastietoja rekisterinpitäjä on luovutustapahtumassa luovuttanut. The event may have other entities involved. 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.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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.
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
what | Σ | 1..1 | Reference(SocialWelfarePatient) | Element idAuditEvent.entity:Patient.what Specific instance of resource DefinitionIdentifies a specific instance of the entity. The reference should be version specific. Reference(SocialWelfarePatient) Allowed aggregation: contained Constraints
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.what.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.what.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 1..1 | string | Element idAuditEvent.entity:Patient.what.reference Viittaus käytettävään resurssiin DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.what.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 0..0 | Identifier | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.what.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.what.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
type | 1..1 | CodingBinding | Element idAuditEvent.entity:Patient.type Type of entity involved DefinitionThe type of the object that was involved in this audit event. 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. This value is distinct from the user's role or any user relationship to the entity. Code for the entity type involved in the audit event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.type.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.type.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.entity:Patient.type.code Person Definitionhttp://terminology.hl7.org/CodeSystem/audit-entity-type Need to refer to a particular code in the system.
1
|
display | Σ | 1..1 | stringFixed Value | Element idAuditEvent.entity:Patient.type.display Person DefinitionPerson Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
Person
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.type.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
role | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.role What role the entity played DefinitionCode representing the role the entity played in the event being audited. For some detailed audit analysis it may be necessary to indicate a more granular type of entity, based on the application role it serves. Code representing the role the entity played in the audit event.
| |
lifecycle | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.lifecycle Life-cycle stage for the entity DefinitionIdentifier for the data life-cycle stage for the entity. 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. This can be used to provide an audit trail for data, over time, as it passes through the system. Identifier for the data life-cycle stage for the entity.
| |
securityLabel | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.securityLabel Security labels on the entity DefinitionSecurity labels for the identified entity. This field identifies the security labels for a specific instance of an object, such as a patient, to detect/track privacy and security issues. Copied from entity meta security tags. Security Labels from the Healthcare Privacy and Security Classification System.
| |
name | Σ I | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.name Descriptor for entity DefinitionA name of the entity in the audit event. Use only where entity can't be identified with an identifier. 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.
|
description | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.description Descriptive text DefinitionText that describes the entity in more detail. Use only where entity can't be identified with an identifier.
| |
query | Σ I | 0..0 | base64Binary | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.query Query parameters DefinitionThe query parameters for a query-type entities. 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. 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.
|
detail | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.entity:Patient.detail Additional Information about the entity DefinitionTagged value pairs for conveying additional information about the entity. Implementation-defined data about specific details of the object accessed or used.
| |
DisclosedPersonalData | I | 1..* | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData Data or objects used Alternate namesParticipantObject DefinitionSpecific instances of data or objects that have been accessed. The event may have other entities involved. 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.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 4..* | Extension | Element idAuditEvent.entity:DisclosedPersonalData.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Constraints
|
FunctionCode | I | 1..1 | Extension(CodeableConcept) | Element idAuditEvent.entity:DisclosedPersonalData.extension:FunctionCode Sosiaalihuollon palvelutehtävä Alternate namesextensions, user content DefinitionLaajennoksella ilmoitetaan sosiaalihuollon palvelutehtävä tai palvelutehtävät, joihin asiakastieto kuuluu. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/FunctionCode Constraints
|
DocumentType | I | 0..1 | Extension(Coding) | Element idAuditEvent.entity:DisclosedPersonalData.extension:DocumentType Yleinen asiakirjatyyppi Alternate namesextensions, user content DefinitionLuovutetun asiakastiedon yleinen asiakirjatyyppi. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/DocumentType Constraints
|
SpecificDocumentType | I | 0..1 | Extension(Coding) | Element idAuditEvent.entity:DisclosedPersonalData.extension:SpecificDocumentType Asiakastiedon tarkennettu asiakirjatyyppi Alternate namesextensions, user content DefinitionAsiakastiedon tarkennettu asiakirjatyyppi ilmoitetaan koodistolla Sosiaalihuolto - Asiakasasiakirjatyyppi (1.2.246.537.6.1506.201701). Tarkennettuna asiakirjatyyppinä käytetään koodiston alatason arvoja. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/SpecificDocumentType Constraints
|
SpecificationOfDisclosure | I | 0..1 | Extension(string) | Element idAuditEvent.entity:DisclosedPersonalData.extension:SpecificationOfDisclosure Luovutetun asiakastiedon selite Alternate namesextensions, user content DefinitionLaajennoksella ilmoitetaan luovutetun asiakastiedon selite, kun luovutustapahtumassa luovutettu tieto ei ole kuvattavissa sosiaalihuollon asiakirjatyypeillä tai asiakirjasta on luovutettu vain osa. Laajennos on pakollinen, jos luovutettua asiakastietoa ei voida kuvata sosiaalihuollon yleisellä tai tarkennetulla asiakirjatyypillä tai asiakirjasta on luovutettu vain osa. Laajennos liitetään DisclosedPersonalData -rakenteella SocialWelfareAuditEvent -profiiliin. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/SpecificationOfDisclosure Constraints
|
CreationTime | I | 1..1 | Extension(dateTime) | Element idAuditEvent.entity:DisclosedPersonalData.extension:CreationTime Luovutetun asiakastiedon laatimisaika Alternate namesextensions, user content DefinitionPäivämäärä tai ajanhetki, jolloin luovutustapahtumassa luovutettu asiakastieto on laadittu. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/CreationTime Constraints
|
ReleaseForPatientViewing | I | 0..1 | Extension(Complex) | Element idAuditEvent.entity:DisclosedPersonalData.extension:ReleaseForPatientViewing Asiakastiedon viivästämisen tiedot Alternate namesextensions, user content DefinitionLaajennoksella ilmoitetaan onko luovutustapahtumassa luovutettu asiakirja viivästetty. Laajennos on pakollinen, jos luovutettu asiakirja on asia-asiakirja, 2. tai myöhemmän vaiheen asiakasasiakirja tai asiakaskertomusmerkintä. Jos luovutettu asiakirja on viivästetty, lokitietoa luovuttamisesta ei näytetä asiakkaalle tai hänen lailliselle edustajalleen. Jos luovutettu asiakirja ei ole viivästetty, lokitieto luovuttamisesta näytetään asiakkaalle tai hänen lailliselle edustajalleen. 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. Extension(Complex) Extension URLhttps://shark.kanta.fi/fhir/StructureDefinition/extension/ReleaseForPatientViewing Constraints
|
SpecialContent | I | 1..1 | Extension(boolean) | Element idAuditEvent.entity:DisclosedPersonalData.extension:SpecialContent Asiakastiedon erityissisältö Alternate namesextensions, user content DefinitionKuvaa sisältääkö luovutustapahtumassa luovutettu asiakastieto tai asiakirja erityissisältöä. Laajennos on pakollinen luovutusilmoituksessa. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/SpecialContent Constraints
|
AuthorizationConsent | I | 0..1 | Extension(boolean) | Element idAuditEvent.entity:DisclosedPersonalData.extension:AuthorizationConsent Asiakirjan näyttäminen kielletty huoltajalle Alternate namesextensions, user content DefinitionTieto kuvaa näytetäänkö lokitietoa alaikäisen asiakkaan asiakirjan tai asiakastiedon luovututamisesta alaikäisen asiakkaan huoltajalle. Laajennos on pakollinen, jos luovutustapahtumassa luovutettu asiakirja on alaikäisen asiakkaan asiakirja. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/AuthorizationConsent Constraints
|
RiskOfGivingLogData | I | 1..1 | Extension(boolean) | Element idAuditEvent.entity:DisclosedPersonalData.extension:RiskOfGivingLogData Lokitietojen antamisesta aiheutuu vaaraa Alternate namesextensions, user content DefinitionLaajennoksella ilmoitetaan voiko lokitietojen antamisesta aiheutua vakavaa vaaraa. Jos lokitietojen antamisesta saattaa aiheutua vakavaa vaaraa, lokitietoa ei näytetä asiakkaalle tai hänen lailliselle edustajalleen. Sosiaalihuollon luovutusilmoituksessa laajennoksella ilmoitetaan voidaanko lokitietoa asiakastietojen luovuttamisesta näyttää asiakkaalle tai hänen lailliselle edustajalleen. Luovutusilmoituksessa laajennos liitetään DisclosedPersonalData -rakenteella SocialWelfareAuditEvent -profiiliin. 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. https://shark.kanta.fi/fhir/StructureDefinition/extension/RiskOfGivingLogData Constraints
|
modifierExtension | Σ ?! I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.modifierExtension Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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 and/or the understanding of the containing element's descendants. 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). Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions. 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.
|
what | Σ | 0..1 | Reference(Resource) | Element idAuditEvent.entity:DisclosedPersonalData.what Ei viitata resurssiin DefinitionTässä ei viitata resurssiin vaan viittaus on identifier-rakenteeseen.
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
reference | Σ I | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
|
type | Σ | 0..0 | uriBinding | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model).
|
identifier | Σ | 1..1 | Identifier | Element idAuditEvent.entity:DisclosedPersonalData.what.identifier Luovutetun tiedon yksilöivä tunnus DefinitionLuovutetun asiakastiedon yksilöivä tunnus, esimerkiksi asiakirjan OID-muotoinen yksilöintitunnus tai sosiaalihuollon asian asiatunnus. Tieto on pakollinen, jos yksilöivä tunnus on käytettävissä. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
|
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.identifier.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.identifier.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
use | Σ ?! | 0..0 | codeBinding | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known .
|
type | Σ | 0..0 | CodeableConceptBinding | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
|
system | Σ | 1..1 | uri | Element idAuditEvent.entity:DisclosedPersonalData.what.identifier.system Organisaation määrittelemä nimiavaruus DefinitionNimiavaruus, jota organisaatio käyttää sosiaalihuollon asiakastietojensa yksilöivien tunnusten muodostamisessa. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
|
value | Σ | 1..1 | string | Element idAuditEvent.entity:DisclosedPersonalData.what.identifier.value Yksilöivä tunnus DefinitionLuovutustapahtumassa luovutetun asiakastiedon yksilöivä tunnus ilman nimiavaruutta. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
|
period | Σ | 0..0 | Period | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
|
assigner | Σ | 0..0 | Reference(Organization) | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
|
display | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.what.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
|
type | 1..1 | CodingBinding | Element idAuditEvent.entity:DisclosedPersonalData.type Type of entity involved DefinitionThe type of the object that was involved in this audit event. 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. This value is distinct from the user's role or any user relationship to the entity. Code for the entity type involved in the audit event.
| |
id | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.type.id Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
extension | I | 0..* | Extension | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.type.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay 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. 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. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints
|
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.type.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
|
version | Σ | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.type.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
code | Σ | 1..1 | codeFixed Value | Element idAuditEvent.entity:DisclosedPersonalData.type.code Other Definitionhttp://terminology.hl7.org/CodeSystem/audit-entity-type Need to refer to a particular code in the system.
4
|
display | Σ | 1..1 | stringFixed Value | Element idAuditEvent.entity:DisclosedPersonalData.type.display Other DefinitionOther Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
Other
|
userSelected | Σ | 0..0 | boolean | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.type.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
role | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.role What role the entity played DefinitionCode representing the role the entity played in the event being audited. For some detailed audit analysis it may be necessary to indicate a more granular type of entity, based on the application role it serves. Code representing the role the entity played in the audit event.
| |
lifecycle | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.lifecycle Life-cycle stage for the entity DefinitionIdentifier for the data life-cycle stage for the entity. 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. This can be used to provide an audit trail for data, over time, as it passes through the system. Identifier for the data life-cycle stage for the entity.
| |
securityLabel | 0..0 | CodingBinding | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.securityLabel Security labels on the entity DefinitionSecurity labels for the identified entity. This field identifies the security labels for a specific instance of an object, such as a patient, to detect/track privacy and security issues. Copied from entity meta security tags. Security Labels from the Healthcare Privacy and Security Classification System.
| |
name | Σ I | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.name Descriptor for entity DefinitionA name of the entity in the audit event. Use only where entity can't be identified with an identifier. 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.
|
description | 0..0 | string | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.description Descriptive text DefinitionText that describes the entity in more detail. Use only where entity can't be identified with an identifier.
| |
query | Σ I | 0..0 | base64Binary | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.query Query parameters DefinitionThe query parameters for a query-type entities. 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. 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.
|
detail | 0..0 | BackboneElement | There are no (further) constraints on this element Element idAuditEvent.entity:DisclosedPersonalData.detail Additional Information about the entity DefinitionTagged value pairs for conveying additional information about the entity. Implementation-defined data about specific details of the object accessed or used.
|