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/admission (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 "admission"

StructureDefinition Work Group: fhir

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

identifier: 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

-PreviousResultForCreateCurrentResultForDeleteRequireBoth
*status:not=in-progresstest-passesstatus=in-progresstest-failstrue

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

EventTriggers

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

CanFilterBies

-DescriptionResourceFilterParameterModifier
*Matching based on the Patient (subject) of an Encounter or based on the Patient's group membership (in/not-in).Encounterpatientin, not-in

NotificationShapes

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