|
1
|
Patient
|
This object is the patient that is the subject of care related to this event. It is identifiable by patient ID or equivalent. The patient may be either human or animal.
|
|
2
|
Location
|
This is a location identified as related to the event. This is usually the location where the event took place. Note that for shipping, the usual events are arrival at a location or departure from a location.
|
|
3
|
Report
|
This object is any kind of persistent document created as a result of the event. This could be a paper report, film, electronic report, DICOM Study, etc. Issues related to medical records life cycle management are conveyed elsewhere.
|
|
4
|
Resource
|
(deprecated)
|
|
5
|
Master File
|
This is any configurable file used to control creation of documents or behavior. Examples include the objects maintained by the HL7 Master File transactions, Value Sets, etc.
|
|
6
|
User
|
A human participant not otherwise identified by some other category
|
|
7
|
List
|
(deprecated)
|
|
8
|
Doctor
|
A person who is providing or performing care related to the event, generally a physician. The key distinction between doctor and provider is the nature of their participation. The doctor is the human who actually performed the work. The provider is the human or organization that is responsible for the work.
|
|
9
|
Subscriber
|
A person or system that is being notified as part of the event. This is relevant in situations where automated systems provide notifications to other parties when an event took place.
|
|
10
|
Guarantor
|
Insurance company, or any other organization who accepts responsibility for paying for the healthcare event.
|
|
11
|
Security User Entity
|
A person or active system object involved in the event with a security role.
|
|
12
|
Security User Group
|
(deprecated)
|
|
13
|
Security Resource
|
A passive object, such as a role table, that is relevant to the event.
|
|
14
|
Security Granularity Definition
|
(deprecated) Relevant to certain RBAC security methodologies.
|
|
15
|
Provider
|
A person or organization responsible for providing care. This encompasses all forms of care, licensed or otherwise, and all sorts of teams and care groups. Note, the distinction between providers and the doctor that actually provided the care to the patient.
|
|
16
|
Data Destination
|
The destination for data transfer, when some other role is not appropriate.
|
|
17
|
Data Archive
|
A source or destination for data transfer that acts as an archive, database, or similar role.
|
|
18
|
Schedule
|
An object that holds schedule information. This could be an appointment book, availability information, etc.
|
|
19
|
Customer
|
An organization or person that is the recipient of services. This could be an organization that is getting services for a patient, or a person that is getting services for an animal.
|
|
20
|
Job
|
An order, task, work item, procedure step, or other description of work to be performed. E.g., a particular instance of an MPPS.
|
|
21
|
Job Stream
|
A list of jobs or a system that provides lists of jobs. E.g., an MWL SCP.
|
|
22
|
Table
|
(Deprecated)
|
|
23
|
Routing Criteria
|
An object that specifies or controls the routing or delivery of items. For example, a distribution list is the routing criteria for mail. The items delivered may be documents, jobs, or other objects.
|
|
24
|
Query
|
The contents of a query. This is used to capture the contents of any kind of query. For security surveillance purposes knowing the queries being made is very important.
|
|
25
|
Data Source
|
The source or origin of data, when there is no other matching role available.
|
|
26
|
Processing Element
|
A data processing element that creates, analyzes, modifies, or manipulates data as part of this event.
|