This page is part of the FHIR Specification (v5.0.0-draft-final: Final QA Preview for R5 - see ballot notes). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
FHIR Infrastructure Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Not linked to any defined compartments |
This is the narrative for the resource. See also the XML, JSON or Turtle format. This example conforms to the profile SubscriptionTopic.
Generated Narrative: SubscriptionTopic
Resource SubscriptionTopic "example"
url: http://example.org/FHIR/R5/SubscriptionTopic/example
identifier: id: urn:uuid:1caa02ba-051b-4602-8856-65921748ae76
version: 1.0.0-beta.1
title: example
status: draft
date: 2019-01-01
description: Example topic for completed encounters
resourceTrigger
description: An Encounter has been completed
resource: Encounter
supportedInteraction: update
QueryCriteria
- Previous ResultForCreate Current ResultForDelete RequireBoth * status:not=completed test-passes status=completed test-fails true fhirPathCriteria: (%previous.empty() | (%previous.status != 'completed')) and (%current.status = 'completed')
canFilterBy
description: Filter based on the subject of an encounter.
resource: Encounter
filterParameter: subject
canFilterBy
description: Filter based on the group membership of the subject of an encounter.
resource: Encounter
filterParameter: _in
canFilterBy
description: Filter based on the length of an encounter.
resource: Encounter
filterParameter: length
comparator: gt, lt, ge, le
canFilterBy
description: Filter based on the account for billing an encounter.
resource: Encounter
filterParameter: account
modifier: missing, not, identifier
- | Resource | Include |
* | Encounter | Encounter:patient&iterate=Patient.link, Encounter:practitioner, Encounter:service-provider, Encounter:account, Encounter:diagnosis, Encounter:observation, Encounter:location |
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.