Subscriptiontopic-example-admission-lm

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-lm (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-lm

StructureDefinition Work Group: fhir

url: SubscriptionTopic admission-lm

identifier: Uniform Resource Identifier (URI)/urn:uuid:44c36873-5167-4b17-a15d-df4f8cb51343

title: admission-lm

status: Active

publisher: HL7 International / FHIR Infrastructure

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

description:

Example admission topic using a Logical Model

trigger
description:

Logical Model of Admission being created or updated into an in-progress state

resource: http://example.org/LogicalModels/Admission
supportedInteraction: create, update
event: ADT/ACK - Admit/visit notification
canFilterBy
description:

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

resource: http://example.org/LogicalModels/Admission
filterParameter: Patient
filterDefinition: http://example.org/LogicalModels/Admission/Match_Patient
canFilterBy
description:

Matching based on the Patient Group. Input is expected to be a string and match against the logical group name where a patient has membership.

resource: http://example.org/LogicalModels/Admission
filterParameter: PatientGroup
filterDefinition: http://example.org/LogicalModels/Admission/Match_Patient_Group
NotificationShapes

- Resource

* http://example.org/LogicalModels/Admission

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.