Search correlationId for tracking audit events

Find the participant of an ActivityDefinition

Search by publisherId for an ActivityDefinition

Search requestId for tracking audit events

Search domain resources by resource-origin.

Search Tasks based on a (set of) ActivityDefinition which in turn can conform to a specific PublisherId

Search trace id for tracking audit events

The (FHIR) ActivityDefinition (resource) describes an eHealth activity that is available for assignment to a patient. When assigning an eHealth activity to a patient, an eHealth Task is created, in which sub-activities are included as contained resources that refer to the main task via Task.partOf.

Koppeltaal AuditEvent profile as used to consolidate logging information.

The care team of a patient that aids the patient in his/her treatment

The (FHIR) Device (resource) is a representation of an application that is used in the provision of healthcare without being substantially changed through that activity. The device may be a module, portal or eHealth app.

The (FHIR) Endpoint (resource) is a representation of a technical contact point of an application that offers one or more eHealth services for a healthcare provider.

The (FHIR) Organization (resource) describes a formally or informally recognized grouping of people or organizations formed for the purpose of achieving some form of collective action. Includes also departments, community groups, healthcare practice groups, etc.

The (FHIR) Patient (resource) is a representation of a person who is being treated by the Healthcare Provider to whom eHealth activities are assigned.

The (FHIR) Practitioner (resource) is a representation of a person who is directly or indirectly involved in the provision of health care.

A related person is a person with a specific role and/or relationship to the patient to assist in the therapy

The (FHIR) Subscription (resource) is used to define a push-based subscription from a server to another system. Once a Subscription is registered with the server, the server checks every resource that is created or updated, and if the resource matches the given criteria, it sends a message on the defined "channel" so that another system can take an appropriate action.

The (FHIR) Task (resource) describes an eHealth task, that is, an eHealth activity assigned to a patient.

The correlation-id is an identifier related to the message and the workflow it's part of

Reference extension to the service application (endpoint) that provides the eHealth activity.

Extension added to a Task to refer to the ActivityDefinition which is instantiated by this Task

Identifier of the publisher (organization or individual). This extension is used as id in the ActivityDefinition.

ID of the request. Together with the trace-id it uniquely identifies a request in logging

Defines the author of the resource

The ID of the workflow. The traceId is intended to track a log entry across multiple logs.

Endpoint connection type ValueSet

High-level categorization of the definition, used for indicating special patient initialised activities

ValueSet for Task.code

ValueSet defining the allowed eventtypes for Koppeltaal

COD472-VEKT Soort relatie cliënt — uitsluitend bedoeld voor testdoeleinden!!! Dit is geen volledige lijst noch een door Vektis goedgekeurd uittreksel. Deze lijst is uitsluitend bedoeld voor testen binnen Koppeltaal.

High-level categorization of the definition, used for indicating special patient initialised activities

Type of endpoint connection as used in Koppeltaal

Type of Task.code specifically used in Koppeltaal

Identifier system of the Devices as used within Koppeltaal

Example of an ActivityDefinition that defines the use of a journal

Vragenlijst ROM

Example of an ActivityDefinition that defines a questionnaire

Auditevent with OperationOutcome

Example of an AuditEvent with an OperationOutcome indicating an error in the update

Example of an AuditEvent about creating a Patient

Example of an AuditEvent about deleting a patient

Auditevent with error about invalid subscription

Example of AuditEvent on application launch

Example of AuditEvent on user authentication

Example of AuditEvent with create Operation resulting in outcome code 4

Example of Device indicating an authorisation server

Example of a Device

Example of CareTeam with multiple participants

Example of bare minimum of CareTeam

Example of CareTeam that has a RelatedPerson as one of the participants

Example of a Device with all elements populated

Example of an Endpoint as used in Koppeltaal

Nictiz Example of RelatedPerson only to test validation

Example of an Organization department

Bare minimum definition of an Organization

Example of an Organization with a name and type

Bare minimum of Patient elements populated

Example of a Patient with a telephone number and managing organization

Example of Patient with resource origin extension populated

Example of Patient with full address

Example of Patient with full name and address

Example of Patient with full name and maiden name

Example of Patient with name and initials

Example of Practitioner

Example of Practitioner with all elements populated

The RelatedPerson is the contact person

RelatedPerson example

RelatedPerson multiple relationships

RelatedPerson with as much elements filled in as possible

Example of a RelatedPerson (neighbour) 2

RelatedPerson with multiple codes for relationship

Example of a RelatedPerson (neighbour)

Nictiz Example of RelatedPerson only to test validation

Example of a subscription

Example of a task in progress

Example of a sub task, part of another task

Task with view code set

Example of a Task

Example of an overarching task