PHSA Misys Lab Interfaces - Glossary
3/31/2006 10:10 AM
PHSA Misys Lab Interfaces
Glossary
Term
Definition
.btm
File suffix for a BizTalk map file.
.odx
File suffix for a BizTalk orchestration file.
ACCPAC
Financial billing software. In this solution ACCPAC is used for Non-MSP billing.
binding
Set of port properties that determines which messages the port receives or
sends.
BIX
BizTalk abbreviation. E.g., BIX 2004 = BizTalk 2004 release.
BizTalk
Microsoft message broker software.
See http://msdn2.microsoft.com/en-us/biztalk/default.aspx
PHSA Misys Lab Interfaces uses BizTalk 2004.
BizTalk Accelerator
Extension of Microsoft’
s BizTalk Server specifically for HL7 messaging between
health care organizations. See Microsoft's BizTalk Accelerator
BTX
BizTalk Server. E.g., BTStype.
canonical message
format
For the PHSA Misys Lab Interfaces installation of BizTalk, the canonical message
format is HL7 v2.3. All messages operated upon within BizTalk are assumed to
be in this format. Inbound messages, if not received in the canonical format, are
mapped to it before BizTalk processing proceeds. If the target system for an
outbound message requires a different format, the message is mapped from the
canonical to the native format before being sent. Generic is a synonym for
canonical and is widely used in this implementation.
(E.g., the map Affinity_A01_To_Generic_A01.btm converts an inbound
Affinity ADT A01 message from its native format to the canonical format, HL7
v2.3)
NOTE:
Pass-through messages need not be converted to canonical
format.
Cerner
Cerner Health Care Information Technology proprietary software product.
Clinical Broker
BizTalk functionality in PHSA Misys Lab Interfaces implementation.
CoPath
Lab Information System software used for Anatomical Pathology work. CoPath
submits lab results (ORUs) through GenLabs only.
Data Closet
Archive of all XML records processed by PHSA Misys Lab Interfaces. (See
BizTalk DataCloset_Orchestrations.*)
decrypt
Remove message encryption. Inbound pipeline function.
disassemble
BizTalk inbound pipeline: Convert inbound message to XML
distribution list
A named collection of ports to which messages are directed.
EHR viewer
Electronic Health Record Viewer (e.g., EVE)
functoid
Executable script invoked from a map and facilitating transformations more
complex than direct mappings.
Page 1 / 5
PHSA Misys Lab Interfaces - Glossary
3/31/2006 10:10 AM
Term
Definition
generic
See canonical message format.
GenLab
Misys GenLab is Lab Information System software used to control all aspects of
laboratory work.
HL7 message
header
MSH: Message Header Segment. Contains critical routing and message
processing information. The HL7 standards define these fields. Consult the
documentation for the message format, e.g., Generic messages, HL7 2.3; or
native formats HL7 2.2, 2.4, etc.
HL7 standard
See Health Level Seven, Version 2.2 ©1994; Health Level Seven, Version 2.3:
HL7 Canada Documentation
inbound pipeline
Processing sequence specified for inbound messages arriving at an associated
BizTalk receive location. BizTalk Documentation - PHSA.chm lists receive
locations for each pipeline. Standard BizTalk processes are commonly invoked in
the pipeline. In some cases custom components are used. Refer to
Custom Scripts.
iPHIS
Population Health Information System. Proprietary Health Information software.
See http://www.bccdc.org/downloads/partnernet/pdf/July_2003.pdf
LIS
Laboratory Information Systems (PHSA)
map
BizTalk file specifying message transformation from a source schema to a target
schema.
MAP COMPARE
A MAP COMPARE is an automated HTML document generated for a particular
map. It provides a line by line comparison of the source schema and the target
schemas.
Map changes can include:
?
field name change
?
data change
?
field locations remapped
All MAP COMPARE files can and should be regenerated whenever the system is
rebuilt. (See Generating Map Compare Documents.) They reside in the
DOCUMENTATION/Mappings directory and contain the following:
1. Direct node-to-node mappings are shown first, source node above target
node.
Changed nodes have a blue highlighted.
2. Scripted modifications are detailed at the end, with the target node
shown on the right.
MCI
Master Client Index (PHSA).
message header
The initial fields in HL7 message. See HL7 message header.
Page 2 / 5
PHSA Misys Lab Interfaces - Glossary
3/31/2006 10:10 AM
Term
Messagebox
Definition
BizTalk message storage. Messages coming from an inbound pipeline are
published to the messagebox database. Orchestrations retrieve and publish
messages. Send ports retrieve messages.
The MessageBox database has three essential functions. It stores subscriptions
and tracking information and it delivers the messages to the services that match
the subscriptions.Error! Bookmark not defined.
When a message arrives in the MessageBox database, that message is
dispatched to its target orchestration ... or send pipeline.
Information about persistence and aging needed.
Misys
Proprietary Health Information software used by Lab Information Systems.
See http://www.misyshealthcare.com/ .
Three PHSA Misys entities (GenLab, CoPath, and RefLab) relate to PHSA Misys
Lab Interfaces via Misys through two interfaces (GenLab and RefLab):
Other systems may also use Misys, e.g., VGH.
MLLP
Minimal Lower Layer Protocol (MLLP). TCP/IP protocol for HL7.
namespace
File name Messaging address (needs better definition)
native format
Message format used by a BizTalk communicant system.
Message format other than the canonical XML v2.3 format of BizTalk.
OBR
ORU message segment: Observation request
OBX
ORU message segment: Observation result
ORC
ORU message segment: Common Order.
Page 3 / 5
PHSA Misys Lab Interfaces - Glossary
3/31/2006 10:10 AM
Term
orchestration
Definition
BizTalk automated process implementation. (Formerly schedule in earlier
versions of BizTalk)
?
Subscribes to one or more class of messages.
?
Uses maps.
?
Invoke other procedures.
?
Writes one or more messages to the message box.
ORM
Message type: Laboratory Request.
ORU
Message type: Laboratory Results
Osler
Software used to upload MSP billing information to the Ministry for payment.
Outbound Pipeline
BizTalk processing sequence for outbound messages retrieved by an associated
send port. BizTalk Documentation - PHSA.chm lists send ports for each outbound
pipeline. Standard BizTalk processes are commonly invoked in the pipeline. In
some cases custom scripting is used. Refer to Custom Scripts.
Party Name
Identity defined in BizTalk. A party may have multiple “aliases.”Each party has a
unique identifier (PID).
See BizTalk Parties
PHSA
Provincial Health Services Administration
PID
Party Identifier. See Party Name.
port/port binding
BizTalk: “A port binding is the configuration information that determines where
and how a message will be sent or received. Depending on type, bindings might
refer to physical locations, pipelines, or other orchestrations.”
receive location
Logical destination of Inbound messages.
“The physical, design-time notion of a location (such as a URL) and an adapter
type. A receive location in the Host node in the BizTalk Server Administration
console, defines the receive functionality”
See Adding a Receive Location using BizTalk Explorer.
receive port
A logical grouping of similar receive locations.
A Receive Port must be defined for every Receive Location.
See Adding a Receive Port using BizTalk Explorer.
PHSA Misys Lab Interfaces Receive Port naming convention:
RP_protocol.format_message.type
For example:
RP_FILE_HL7_ADT is a receive port for files containing HL7-formatted ADT
records.
RP_MLLP_HL7_ADT is a receive port for an MLLP message containing an HL7formatted ADT record.
resolve party
BizTalk Inbound Pipeline: Determine message-sending party.
schema
XML schemas define the types and structure of information in a document.
BizTalk uses XSD (XML schema definition language) schemas. They are
generated by the BizTalk editor.
Page 4 / 5
PHSA Misys Lab Interfaces - Glossary
3/31/2006 10:10 AM
Term
send port
Definition
“The location to which messages are sent or from which messages are received,
and the technology that is used to implement the communication action. The
location is uniquely identified by the name of the port.”
Send port naming convention:
SP_protocol.format_receiver_message.format_message type
For example:
SP_MLLP_Misys_HL7_ALL is a send port for encoded files containing HL7formatted records for MLLP.
See Adding a Receive Port with BizTalk Explorer
SOAP
Simple Object Access Protocol. “A lightweight XML-based messaging protocol
used to encode the information in Web service request and response messages
before sending them over a network. SOAP messages are independent of any
operating system or protocol and may be transported using a variety of Internet
protocols, including SMTP, MIME, and HTTP.”
http://www.webopedia.com/TERM/S/SOAP.html
subscriber
An orchestration or port that receives messages of a certain class.
subscription
In BizTalk, a subscription is a specified set of criteria that determines which
messages an orchestration processes or which messages a port receives. An
orchestration specifies its own criteria and thus subscribes to messages that
meet them. A send pipeline is associated with one or more ports and processes
messages to which the send-ports subscribe. Send-port subscriptions are
specified as BizTalk filters.
VCH
Vancouver Coastal Health, a network of hospitals and health facilities.
VGH
Vancouver General Hospital, one member of the VCH network. (VGH is a Misys
system and submits both ORMs and ORUs for processing via PHSA GenLabs and
RefLabs)
Web service
An application-to-application based alternative to the client-server model for
exchanging data over the Web. See Web services.
XSD
XML Schema Definition Language.
Page 5 / 5