Upload
others
View
1
Download
0
Embed Size (px)
Citation preview
1FPS HEALTH, SAFETY OF THE FOOD CHAIN AND ENVIRONMENT
General Direction Healthcare – Emergency
Service
Selected certificate Managers
AMBUREG
Brussels, 24/10/2019
2
0. Program
1. Feedback from Ambulance services (1 hour)
B R E A K + P I C T U R E
2. Authority (1 hour)
2.1. Outage 20/10/19
2.2. Future
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
2.1.1. Before outage 20/10/2019, 10h
32
2.1.2. After outage 20/10/2019, 10h
33
2.1.3. Measures
- Check of emaillist eHealth
- Improovement of emails eHealth
- Review of SMALS monitoring system authority
- Suppliers emergency centers : ACC environment must be ok.
- Suppliers emergency centers : ACC test must be executed.
34
2.2.1. Emsr release R +1 : ACC 16/10/2019
1. X,Y intervention place stored in existing fields in getSds
COORD_X_TEAM_ALERT COORD_Y_TEAM_ALERT
2. Variable 44
=> Variabele 88.1.1 staffMember1BadgeNumber default value 999 999
1 mission cancelled
2 false (malicious) call
3 no patient
4 patient already left site
5 patient contact but no
transport needed
6 patient contact but
transport refused
7 patient deceased
8 patient contact but
transport by other means
9 multiple alert
10 transition to status not
available
In case of
patient.transportFlag=false,
this indicates the reason why
no patient was transported.
44 patient.reasonNoTransport
35
2.2.2. Emsr release R +2 : PROD 7/1/2020
Introduction system names (0)
36
2.2.2.Emsr release R +2 : PROD 7/1/2020
Introduction system names (1)
1st PROBLEM TO SOLVE:
- Emergency Center 112 Arlon will use FPS Home Office federal
permance names (=new names) from 7/1/2020 for service A
- Emergency Center 112 Namur will use existing perm.names
(=old names) also after 7/1/2020 for service A
- EMSR receives saveIntervention – messages with 2 ≠ names
- Service A must call getSds, … with a perm. name
37
2.2.2. Emsr release R +2 : PROD 7/1/2020
Introduction system names (2)
2nd PROBLEM TO SOLVE:
- Service B uses federal permanence name ABC for several years.
- Service C takes over from Service B inclusively name ABC.
- Service B must be capable to consult during 7 years records
with name ABC
- Service C must in the mean time be authentified as the unique
service for the registration of interventions with name ABC.
38
2.2.2. Emsr release R +2 : PROD 7/1/2020
Introduction system names (3)
SOLUTION FOR PROBLEM 1
- (..)
- getSd “Name preference” is per service stored in Ambulance
Service Reference Table (ASRT) maintained by the Authority:
e.g. AXMARC03A (new) and MXSIMA103 (old)
- requestPartA and RequestPartB may be used with old or new
names.
39
2.2.2. Emsr release R +2 : PROD 7/1/2020
Introduction system names (4)
SOLUTION FOR PROBLEM 2
- (..)
- getSheet (MVLEUV101) will succeed with certificate of service
B and service C but ASRT will determine if any and which
record is visualized.
- requestPartA(MVLEUV101) and requestPart(MVLEUV101) will
only succeed with certificate of service C.
40
2.2.2. Emsr release R +2 : PROD 7/1/2020
Introduction system names (5)
TO BE DECIDED:
❑ which name preference for which services when ?
❑ introduction scheme and modification scheme of name
preference
❑ release management of ASRT
41
2.2.3. Further Emsr releases R +x : 2020
Enlargement of intervention number from 11 to 13 characters:
❑ 10 19 145 0033 -> 10 19 145 000033
❑ eHealth bus impact !
Enlargement of Ambureg towards 20 supplementary services (PIT)
❑ Preparing study is going on.
Implementation of eraseIdentification
❑ Preparing study is done.
❑ eHealth bus impact
Modification intervention address and hospital site via requestPartB
42
2.2.4. Emergency center 112 releases
CityGIS CMS (LUX+ANT-LIM-LIE-HAI+BRW-LUX)
❑ Technically capable of associating Ambureg identifier to
permanence (=team) : 4/11/2019
❑ Technically capable of sending saveIntervention upon
transmission from status 1 to status 2, 3, 4, 5 or 6 :
4/11/2019
Migration LUX to CityGIS C&D : 7/1/2020
Migration NAM to CityGIS C&D : 2/2020
Transmission of hospital site (CityGIS C&D) : during 2020
43
2.2.5. Reporting program
Quid ?
❑ each Monday 10h, 85 ambulance services receive a report with weekly and cumulativeregistration degree
❑ Authority is capable to import reference data base and pseudonimized Ambureg data base with 1 day delay.
When new release ?
❑ 10/2019
Content ?
❑ Method of weekly report changes : “year segment”
❑ Corrections for registration grade calculation
❑ Data source for infringement statement based upon 9 first months registrations
❑ Not yet: list of not registered interventions in case of RD > 90 %
44
2.2.6. Additional observations
1. No uniformity for registration of double intervention
numbers
2. Some (very old) bugs found in emergency center 112
software and/or web service Smureg SDS: adresses!
3. Registration of strange values: e.g. > 1.000.000 km for
4. Registration of invalid Ambulance badge numbers
36 distance indicates the difference
between the endpoint and the
starpoint (in kilometers)