Subscriptiontopic-example-admission-binary

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-binary (Narrative)

Responsible Owner: FHIR Infrastructure Work Group

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 admission-binary

StructureDefinition Work Group: fhir

url: SubscriptionTopic admission-binary

identifier: Uniform Resource Identifier (URI)/urn:uuid:174f26f9-c66f-4165-9407-2c90e3fc3123

title: admission-binary

status: Active

publisher: HL7 International / FHIR Infrastructure

contact: http://www.hl7.org/Special/committees/fiwg

description:

Example admission topic using a Binary resource

trigger
description:

Admission being created or updated into an in-progress state

resource: http://hl7.org/fhir/StructureDefinition/Basic
supportedInteraction: create, update
event: ADT/ACK - Admit/visit notification
canFilterBy
description:

Matching based on the Patient. Input is expected to be a search reference and match against a reference to the patient.

resource: http://hl7.org/fhir/StructureDefinition/Binary
filterParameter: admission-patient
filterDefinition: http://example.org/SearchParameters/Binary/admission-patient
canFilterBy
description:

Matching based on the Patient Group. Input is expected to be a search reference and match against a reference to a group the patient has membership in.

resource: http://hl7.org/fhir/StructureDefinition/Basic
filterParameter: admission-patient-group
filterDefinition: http://example.org/SearchParameters/Binary/admission-patient-group
notificationShape
resource: http://hl7.org/fhir/StructureDefinition/Binary
include: Binary:admission-patient, Binary:admission-patient-group

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.