3M Medical Information Models

http://www.hddaccess.com

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.

 

ASN.1 Data Model

 

In addition to the files linked below, documentation and examples of various information models are provided in files ending with "sup.html" in the html directory of this distribution. For instance, allergysup.html provides examples and documentation for the model described in allergy.html

 

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.

 

DSqlTable

DynamicSqlTransaction

ETTrans

HDDMaintTrans

MVTrans

OSHTrans

PatDataTrans

ScheduleTrans

SecurityTrans

VoserTrans

WLAdminTrans

WLQueryTrans

 

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.

 

AllergyInfo

StandardLabData

ClinicalEvent

ClinicalTextData

MmiData

EncounterData

PatientOrder

GroupPatientOrder

 

 

 

 

 

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

 

 

AdverseDrugEvent

ClinicalEncounterEvent

EncodedDataEvent

MicrobioEvent

MultiMediaImageEvent

OrderEvent

PatAlertEvent

PatObsEvent

PKCEvent

ProblemEvent

ReminderEvent

ReminderStatusEvent

SignatureEvent

 

 

 

 

 

Dental Model

 

 

DentalExamEvent

FacialAnalysisEvent

GeneralPatientEvalEvent

HairReplaceEvalEvent

OralHygieneEvent

PatientInformedEvent

PsychoSocialEvent

RadiationTxtEvent

SleepEvalEvent

 

 

PatObsEvent

 

 

EKGEvent

HeightWeightEvent

MedAdminEventType

OrthostaticVitalsEvent

PreventiveHistoryEvent

VitalSignsEvent

 

 

 

 

MedAdminEventType

 

 

ImmunizationEventType

ImmunizationHistoryEventType

 

 

ReminderEvent

 

 

ImmunizationReminderEvent

PreventiveReminderEvent