HL7 Finland 1999

1
HL7 Finland 1999

• Timo TarhonenTietotarha
• HL7 Finland, coordinator

2
Finland
www.hl7.fi
Presidency of EU 1.7.1999-31.12.1999
Home of Nokia, Linux and Santa Claus
Population 5 100 000 Area 338 145 sq km
Formula I and rally drivers world championship
1998 (and 1999)
Number one in proportional ratio of mobile phones
and internet connections
3
(No Transcript)
4
Affiliate structure
Sinikka Ripatti - Huch Seppo Ahokas - Medici
Data Martti Ikonen - Kuh Tuire Mikola - Macro
Pilot Terho Eskelinen - Mylab
Board is also technical committee
5
Additional local responsibilities
International HL7
CCOW
ARDEN- SYNTAX
PRA
HL7 V3.0
HL7 V2.X
FINLAND
DICOM
???
6
HL7 Finland

• Founded in September 1995
• Registered association in January 1997
• Affiliate agreement 1997
• 58 members (1.9.1999, 44 1.9.1998)
• all major IT and clinical system vendors in
  Finland
• most major hospital districts
• some consulting companies and some authorities
  associations
• We have some members only because of DICOM
• Cant get very many new members

7
What are we doing

• Localisation efforts (projects)
• Promotion of HL7
• Help Desk and implementation project support
• Training courses and seminars
• Follow up of international activities
• WWW-server
• monthly web magazine (or zine)
• document archive and link collection
• SIG-activities
• find out current problems and solve them

8
1999 happenings (1)

• HL7 Finland Spring meeting and seminar 8-10.2
• version 3.0 MDF, XML, Corba, Active X
• International guest Bert Kabbes, Chair of HL7 The
  Netherlands
• SIG-meetings
• IIR Patient seminar-99
• several presentations concerning HL7
• For some doctors and administrative people HL7
  was a new thing
• XXV Health care Information technology days
• HL7 technologies, project reports, affiliate and
  SIG status reports

9
1999 happenings (2)

• DICOM training 7-8.9.1999
• 50 attendees, sold out
• Teacher Marco A Demarmels, Lake Griffin Ltd,
  Switzerland
• National authorities XML-seminar 22.9.1999
• Joachim Dudeck, Chair of HL7 Germany
• Mumps meeting 23-24.9.1999 (MUSTI-trip)
• several presentations of HL7
• HL7 Finland fall meeting 1.11.1999
• Klaus Veil, chair of HL7 Australia
• HL7 training course 10-11.11.1999
• 24.12Santa Claus comes, 1.1.2000HL7 systems
  still running

10
Future

• We are trying to start a project for referrals
  and doctors reports and a project to check
  available tools (parsers etc. for 2.3, version
  3.0 tools)
• Main emphasis on deployment of HL7, actually no
  resources for RIM development
• Year 2000 may the year to localise version 3.0
• Im not sure if we know how to do it
• Technologies
• for the time being Corba and active X/DCOM have
  no role when considering Finnish HL7, In Future
  Active X may have (because of things like CCOW)
• XML has already been sold

11
Possibilities

• National authorities have followed CEN TC 251
• threat of compulsory standards
• Everybody is waiting for ISO TC215
• voluntary standards
• Companies and users admit that HL7 Finland has
  done real work for standardisation
• There is a possibility that HL7 Finland will be
  given a more official status and more
  responsibilities (but no money?)

12
Health Care Communication Profile
CORBA
HL7 eating Edifact
HL7
HL7
HL7
EDI- FACT
XML
area of usage
EDIFACT
ACTIVEX/DCOM
standardized area
Health care communication profile
new technologies
superset of standards and their usage
13
Thoughts

• In Future we might have only one way to do
  specifications
• RIM is needed for planning, in actual systems you
  have only small parts of it
• XML can technically combine old HL7 and old
  EDIFACT
• Its not difficult to transform DICOM messages
  into XML
• Could you live with the mixture of three type of
  DTDs (origins HL7, EDIFACT, DICOM)
• remember what PRA promises you
• Some light can be seen from the other end of the
  tunnel

14
Some connections
HL7
Organisation C
Organisation As SIP
proprietary
EDIFACT
in future direct HL7 connections
PACS DICOM Broker
Organisation Bs SIP
proprietary
HL7
SIPsystem integration platform
15
Diff. between EDIFACT and HL7

• HL7
• message
• segment
• field
• component
• subcomponent

• EDIFACT
• message
• segment group
• segment
• field
• subfield

16
Eating Edifact?

• Question why do we need batch driven EDIFACT
  software and also rapid HL7 software
• Answer you can use HL7 infrastructure to deliver
  EDIFACT data in many cases
• use OBX
• OBX-2 EDIFACT segment tag
• OBX-3 EDIFACT field name
• OBX-5 EDIFACT field data or subfield subfield
• Proper message specifications ORM or ORU (MSH,
  OBR, OBX)

17
More Information
Niilo Saranummi VTT Information Technology PL
1206, 33101 Tampere, Finland Phone [phone]
3300, fax [phone] E-mail
niilo.saranummi_at_vtt.fi Timo Tarhonen Tietotarha
Oy Tukholmankatu 2, 00260 Helsinki,
Finland Phone [phone], fax
358-9-2410662 E-mail timo.tarhonen_at_tto.fi Vesa
Pakarinen VTT Information Technology PL 1206,
33103 Tampere, Finland Phone [phone],
fax [phone] E-mail vesa.pakarinen_at_vtt.fi
18
See

• www.hl7.fi