Release 5 R6 Ballot (1st Draft)

This page is part of the FHIR Specification (v5.0.0: R5 - STU v6.0.0-ballot1: Release 6 Ballot (1st Draft) (see Ballot Notes ). This is the The current published version in it's permanent home (it will always be available at this URL). is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B

Example SubscriptionTopic/admission (Narrative)

FHIR Infrastructure Work Group Maturity Level : N/A Standards Status : Informative Compartments : 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 "admission"

StructureDefinition Work Group : fhir

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

identifier : id: urn:uuid:915c2040-b0a8-4935-adf8-94d6e1a74052 id:  # urn:uuid:915c2040-b0a8-4935-adf8-94d6e1a74052

title : admission

status : active

publisher : HL7 International / FHIR Infrastructure

contact :

description : Example admission topic

resourceTrigger

description : Encounter resource moving to state 'in-progress'

resource : Encounter

supportedInteraction : create, update

QueryCriteria

- Previous ResultForCreate Current ResultForDelete RequireBoth
* status:not=in-progress test-passes status=in-progress test-fails true

fhirPathCriteria : %previous.status!='in-progress' and %current.status='in-progress'

EventTriggers

- Description Event Resource
* Patient admission is covered by HL7v2 ADT^A01 ADT/ACK - Admit/visit notification ( eventType #A01) Encounter

CanFilterBies

- Description Resource FilterParameter Modifier
* Matching based on the Patient (subject) of an Encounter or based on the Patient's group membership (in/not-in). Encounter patient in, not-in

NotificationShapes

- Resource Include
* Encounter Encounter:patient, 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.