Founda Subscription Topic Catalog

the subscription topic catalog is standardly filled with all hl7v2 x derived events, as defined in the tables below admission, discharge and transfer topic trigger description admit/visit notification adt a01 this event is sent as a result of a patient undergoing the admission process which assigns the patient to a bed it signals the beginning of a patient’s stay in a healthcare facility transfer a patient adt a02 this event is issued as a result of the patient changing his or her assigned physical location discharge/end visit adt a03 this event signals the end of a patient’s stay in a healthcare facility it signals that the patient’s status has changed to “discharged” and that a discharge date has been recorded the patient is no longer in the facility the patient’s location prior to discharge should be entered in pv1 3 assigned patient location register a patient adt a04 this event signals that the patient has arrived or checked in as a one time, or recurring outpatient, and is not assigned to a bed pre admit a patient adt a05 this event is sent when a patient undergoes the pre admission process it can also be used to pre register a non admitted patient change an outpatient to an inpatient adt a06 this event is sent when a patient who was present for a non admitted visit is being admitted after an evaluation of the seriousness of the patient’s condition change an inpatient to an outpatient adt a07 this event is sent when a patient who was admitted changes his/her status to "no longer admitted" but is still being seen for this episode of care update patient information adt a08 this event is used when any patient information has changed but when no other trigger event has occurred it is recommend that the a08 transaction be used to update fields that are not related to any of the other trigger events patient departing tracking adt a09 this event is used when there is a change in a patient’s physical location (inpatient or outpatient), and is used when this is not a change in the official census bed location, as in the case of an outpatient setting patient arriving tracking adt a10 this event is sent when a patient arrives at a new location in the healthcare facility (inpatient or outpatient), and is used when there is a change in a patient’s physical location and when this is not a change in the official census bed location, as in the case of an outpatient setting cancel admit/visit notification adt a11 this event is sent when an a01 (admit/visit notification) event is cancelled, or for "non admitted" patients, this event is sent when an a04 (register a patient) event is cancelled cancel discharge/end visit adt a13 the event is sent when an a03 (discharge/end visit) event is cancelled pending admit adt a14 this event notifies other systems of a planned admission, when there is a reservation or when patient admission is to occur imminently it is used when advanced notification of an admit is required in order to prepare for the patient’s arrival pending transfer adt a15 this event notifies other systems of a plan to transfer a patient to a new location when the patient has not yet left the old location pending discharge adt a16 this event notifies other systems of a plan to discharge a patient when the patient has not yet left the healthcare facility cancel pending discharge adt a25 this event is sent when an a16 (pending discharge) event is cancelled cancel pending transfer adt a26 this event is sent when an a15 (pending transfer) event is cancelled cancel pending admit adt a27 this event is sent when an a14 (pending admit) event is canceled add person information adt a28 this event can be used to send everything that is known about a person delete person information adt a29 this event can be used to delete all demographic information related to a given person this event "undoes" an a28 (add person information) event update person information adt a31 this event is used to update person information on an mpi merge patient patient identifier list adt a40 this event is used to signal a merge of records for a patient that was incorrectly filed under two different identifiers merge account patient account number adt a41 this event is used to signal a merge of records for an account that was incorrectly filed under two different account numbers move visit information visit number adt a45 this event is used to signal a move of records change patient identifier list adt a47 this event is used to signal a change of an incorrectly assigned pid 3 patient identifier list value update allergy information adt a60 this event is used when person/patient allergy information has changed scheduling information topic trigger description new appointment siu s12 this event is sent when a new appointment has been booked by a 'filler' application reschedule appointment siu s13 this event is sent when an existing appointment has been rescheduled modify appointment siu s14 this event is sent when an existing appointment has been modified by the 'filler' application cancel appointment siu s15 this event is sent when an appointment that has not ocurred is cancelled by the filler application discontinue appointment siu s16 this event is sent when an appointment that is in progress has been stopped delete appointment siu s17 this event is sent when an appointment that was erroneously scheduled is removed by the filler application no show appointment siu s26 this event is sent when a patient did not show up for an appointment order management topic trigger description general order orm o01 this event communicates information about an order this includes placing new orders, cancellation of existing orders, discontinuation, holding, etc general clinical order omg o19 this event communicates information about a general clinical order that uses the obr segment this includes placing new orders, cancellation of existing orders, discontinuation, holding, etc laboratory order oml o21 this event communicates information about a laboratory order pharmacy order rde o11 this event communicates a pharmacy/treatment order (orm message with rxo segment) pharmacy dispense rds o13 this event communicates the dispensing a drug or treatment to fill an existing order or orders pharmacy refill authorization rde o25 this event communicates a refill authorization request originating with the pharmacy medical records/information management topic trigger description original document mdm t01 this event communicates the creation of a document without the accompanying content original document and content mdm t02 this event communitates the the creation of a document with the accompanying content document addendum mdm t05 this event communicates an addendum to a document without the accompanying content document addendum and content mdm t06 this event communicates an addendum to a document with the accompanying content document replacement mdm t09 this event communicates the replacement to a document without the accompanying content document replacement and content mdm t10 this event communicates the replacement to a document with the accompanying content observation reporting topic trigger description unsolicited observation oru r01 the oru message is for transmitting laboratory results to other systems the oul message is designed to accommodate the laboratory processes of laboratory automation systems unsolicited point of care observation oru r30 this event instructs the receiving system to create a new order for the observation(s) contained in the message unsolicited new point of care observation oru r31 this event instructs the receiving system to search for an existing order for the observation(s) contained in the message unsolicited pre ordered point of care observation oru r32 this event instructs the receiver to place the result with the order information included in the message unsolicited alert observation oru r40 this event is used for observation reports that include an alertable condition unsolicited device event observation oru r42 this event is used for observation reports that identify a device sourced event that is relevant to clinical workflow but that does not require a response from a clinician or clinical management system unsolicited patient device association observation oru r43 this event is used for observation reports that indicate the association of one patient to one or more health care devices unsolicited specimen oriented observation oul r22 this event communicates specimen oriented testing unsolicited specimen container oriented observation oul r23 this event communicates specimen oriented testing unsolicited order oriented observation oul r24 this event communicates specimen oriented testing patient referrals topic trigger description patient referral ref i12 this event triggers a message to be sent from one healthcare provider to another regarding a specific patient cancel referral ref i14 this event triggers a message to be sent from one healthcare provider to another canceling a referral finance and billing topic trigger description post detail financial dft p03 this event is used to describe a financial transaction transmitted between systems post detail financial expanded dft p11 this event is the same as dft p03 but applies to a broader set of use cases add patient accounts bar p01 this event is used to communicate the creation of a new account that did not exist before purge patient accounts bar p02 this event is used to communicate the elimination of all billing/accounts receivable records although a series of accounts may be purged within this one event, we recommend that only one pid segment be sent per event update diagnosis/procedure bar p12 this event is used to communicate updated diagnosis and/or procedures vaccinations topic trigger description unsolicited vaccination record update vxu v04 this event is used when a provider wishes to update the patient's vaccination record being held in a registry