FHIR CI-Build

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

Example SubscriptionTopic/example (Narrative)

FHIR Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: No 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"

StructureDefinition Work Group: fhir

url: http://example.org/FHIR/R5/SubscriptionTopic/example

identifier: URI/urn:uuid:1caa02ba-051b-4602-8856-65921748ae76

version: 1.0.0-beta.1

title: example

status: draft

date: 2019-01-01

publisher: HL7 International / FHIR Infrastructure

contact:

description: Example topic for completed encounters

resourceTrigger

description: An Encounter has been completed

resource: Encounter

supportedInteraction: update

QueryCriteria

-PreviousResultForCreateCurrentResultForDeleteRequireBoth
*status:not=completedtest-passesstatus=completedtest-failstrue

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

NotificationShapes

-ResourceInclude
*EncounterEncounter: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.