SYSVAK Project: overview and plans

Peter HolmesTechnical Coordinator

11 Oct 2005 SYSVAK Project 2

Agenda• current system

• target system

• transition process

11 Oct 2005 SYSVAK Project 3

Background

• SYSVAK developed to help monitor vaccination

coverage in Norway

• a tool helping to ensure children receive a

satisfactory health-offer

• health-stations and other health-personnel required to

report vaccination-related information to SYSVAK

• EDB AS acts as SYSVAK databehandler for FHI

11 Oct 2005 SYSVAK Project 4

Current system: overview

InternettMail

InternettFTP

FTPFTP og RCP

ISOCOR

ISOPLEX

FTP-ServerMAIL-Server

AMTRIX

SYSVAK at EDB

U2

Modem

Modem

Modem

Mainframe

Bydel2Bydel1

Bydel27

Fire

wall

Fire

wal

l

Fire

wal

l

Fire

wal

l

NFS

KommunerSentralisert DB

i datarom

KommunerSentralisert DB

i datarom

Mindre helsestasjoner

Fire

wal

lF

irew

all

Fire

wal

lF

irew

all

Modem

Fire

wal

l

Firewall

KonsernNett

11 Oct 2005 SYSVAK Project 5

Current message formats and clients

SYSVAK SENTRAL

INFODOC(Infodoc)

HSPRO(Hiadata)

WINMED(Profdoc)

PROFDOC DOS(Profdoc)

SYSVAK LOKAL(FHI)

meldinger i EDIFACT format

meldinger i SYSVAK format

EDB

11 Oct 2005 SYSVAK Project 6

Design challenges

• five client types

• two message formats

• heterogeneous connectivity deployments

• data transport alternatives vs. local security policies

• data in many places

11 Oct 2005 SYSVAK Project 7

Optimal situation

• data in one place,… …but this is not an option (forskrift om pasientjournal)

• data submission validated against SYSVAK Sentral before (eventual) entry into local database(s)

→ design goal: to enable this possibility,……can be exploited when journaling system suppliers are ready

11 Oct 2005 SYSVAK Project 8

Target system: features

• backward compatibility– controlled transition to next generation

• new functionality to address data quality issues

• support for– alternative transport protocols and

– service interfaces

11 Oct 2005 SYSVAK Project 9

Target system: features (ii)

• will offer web application for data registration– virksomhetssertifikater

– sikkerhetsportalen

• intention to develop web service client components– for synchronous or asynchronous transactions

11 Oct 2005 SYSVAK Project 10

Target system: features (iii)

• possibly, a component for eSMTP over Helsenett– current formats (?)

– new formats

11 Oct 2005 SYSVAK Project 11

Target system: logical overview

Mottak av meldinger på nytt format

Mottak av meldinger på gammelt format

Konvertering

Behandling av meldinger

Lokalt journalsystem

Lokalt journalsystem

Lokalt journalsystem

XML

Gammelt format

DatabaseIISNettleser HTML Applikasjonslogikk

XM

L

11 Oct 2005 SYSVAK Project 12

Transition process

• compatibility with existing solution

• centralized traffic routing via EDB

• will develop new SYSVAK XML message standards

11 Oct 2005 SYSVAK Project 13

Transition overview

InternettMail

InternettFTP

FTPFTP og RCP

ISOCOR

ISOPLEX

FTP-ServerMAIL-Server

AMTRIX U2

Modem

Modem

Modem

Mainframe

Bydel2Bydel1

Bydel27

Fire

wall

Fire

wall

Fire

wall

Firew

all

NFS

KommunerSentralisert DB

i datarom

KommunerSentralisert DB

i datarom

Mindre helsestasjoner

Firew

all

Firew

all

Firew

all

Firew

all

Modem

Firew

all

Firewall

Firewall

BizTalk Server +App Server

SYSVAK at FHI

FHI

FTP, IIS, Exchange

Svrs

KonsernNett

Firewall

11 Oct 2005 SYSVAK Project 14

New message standards

• initiate XML message definition process with KITH

• define message compliance process with journaling system suppliers and KITH

11 Oct 2005 SYSVAK Project 15

Cooperation

• workshops with journaling system suppliers– to understand client systems more fully

– to present FHIs vision for improved SYSVAK reporting and data quality

– to discuss concrete plans for improved integration

– to discuss approaches for client testing and message compliance