Copyright 2012 3M Health Information Systems, Inc. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
MmiInfo is the message used for communication with the Demographic and Encounter servers.
HemsInfo is the message used for communication with the clinical data servers. HemsInfo messages contain header information about who is making the request and what program they are using. Then they also contain a node of type TransactionObject, which is the payload for that specific service. The most common server messages or TransactionsObjects are indexed below. PatDataTrans contains what we normally think of as Clinical Data.
Clinical data is stored below a PatDataTrans node in a node called PatDatumObject. This is where the data type specific part of a clinical event begins.
|
||
|
|
|
ClinicalEvent is the base type that is used to store nearly all of the clinical data. Think of it as a template of what can be stored. Following are sub-types. Think of them as constraints or what should be stored when creating an event of this type. Notice the sub-typing hierarchy that is possible, bold subtypes have subtypes.
ClinicalEvent |
|
|
|
|
|
|
|
|
Dental Model |
|
|
PatObsEvent |
|
|
|
|
|
MedAdminEventType |
|
|
|
ReminderEvent |
|
|
|