Professional Documents
Culture Documents
In the beginning
There was paper
There was PIT
Idea of a PIT distribution network
Envisaged in 1997
Full PIT support developed at that time
Data format considered inadequate for storing
endoscopy data
We discovered HL7 during research of more rich data
formats available
Joined HL7 USA as an individual member early 1998
Started understanding the HL7 v2 specifications
Been on a loop to provide full support for HL7 since
In the beginning
Researched available toolkits for HL7 v2 &
DICOM during May 1998
Largely the cost (particularly royalties) made it
impossible to write systems for specialists & GPs
Decision made to write a HL7 processing
framework
The development effort has had full time staff
members since 1998
Development has been ramped up since wide
availability of fast internet connectivity & open
source SQL servers
Initial barriers
Communications infrastructure
Solved by wide spread internet availability
(broadband speeds a BIG plus)
Encryption
Initially technology was not generally available
however this is not the case now
Initial barriers
Messaging platform
Standardisation of HTTP has solved this
Development style
Development style
Test driven
Agile
Continuous integration
Highly object orientated
Design patterns
Object Pascal & Java
Parsing HL7
HL7 messages are parsed into a tree
Read by message objects which are
flyweights
HL7 parsing rules are respected
This allows significant HL7 version
mismatch resolution
Currently the framework is at HL7 v2.3.1
HL7 is easily downgraded if needed
HL7 Abstraction
All HL7 data types appear as native data
types
All access is via interfaces
Automatic memory management
Code generation used above data type
level
All higher level methods operate on the
interfaces
Development is totally isolated from
encoding of HL7
SMTP
S/MIME
GnuPG
LLP
PGP
LDAP
Asynchronous
Proxy
Message Processing
Lab Specific
PMS Specific
MFQ
PIT
QRY^R02
ORM^O01
Firebird SQL
Etc..
Oracle*
Picture Archival
Persistence
HL7
PIT
RTF
DICOM
JPEG
HTML
Archetypes
SNOMED-CT
HL7/XML
PIT
ORU^R01
QRY^R02
PGP
HTTP
ORM^O01
PIT
Offline Index
LOINC
Lab Specific
LLP
HL7
HL7 Model
PMS Specific
MFQ
Etc..
GnuPG
Encryption Layer
S/MIME
Transport Layer
LOINC support
ICD-10AM support
SNOMED-CT support
SNOMED-CT Query
We achieved compliance
Medical Objects was the first messaging
service and organization in Australia to
receive Australian Standards AS4700.2
HL7 v2.3.1 certification, awarded by the
National Association of Testing Authorities
(NATA) approved Australian Healthcare
Messaging Laboratory (AHML).
Both our Orders & Results are compliant
To date Medical Objects are the only
organisation to have completed
certification.
Sending GP referrals
GP referrals
Captured from clinical
practice software
Digitally signed HESA PKI
USB key
Encrypted with PKI
certificates
Encrypted provider lookup
Zero configuration install
Digital
Signature
Block
Open Specification: http://download.medical-objects.com.au/docs/api/MO-Signature-v2.zip
Capsule Endoscopy
HL7 Orders
Provider directory
HL7 2.3 Master files
Defines messages for maintenance & query for
providers using the STF segment
CH 8.3.3 MFQ/MFR (Master Files Query/Response)
MFQ/MFR
HL7 Filter
Using the framework to bring existing non-compliant messages up to HL7 2.3.1.
Improving the quality of the terminology coding
Magellan
Eclipse
Word Plugin
HL7 Visualiser
Designed for trusted
message set
Part of Standards
Australia work for
IT-14-6-5
www.medical-objects.com.au