Smart Hospital Management System: An Integration of Enterprise Level Solutions

Utilising Open Group Architecture Frameor! "#OGAF$

%enon &hac'!o( &hristopher chiu an) Avtar Singh
*ohli
Faculty of Engineering an) I#(
University of #echnology Sy)ney
+S, -../ Australia
'enon0chac'!o1uts0e)u0au ( christopher0chiu1uts0e)u0au
an) avtar0s0!ohli1uts0e)u0au
Ahstract2A significant portion of the Hospital Information
Systems currently consists of various in)ivi)ual legacy
applications that have to 3e integrate)( to )eliver a more
unifie) solution0 #he performance( relia3ility an) other factors
of these applications can alter the performance( relia3ility
an) other characteristics of integrate) Solution( the Smart
Hospital Management System "SHS$0 #he actual evaluation
of these parameters of these applications is outsi)e the scope
of this )ocument0 #he SHS 3eing an infrastructure
component relies heavily on the actual resources ma)e
availa3le to it for its
proper functioning( operation an) maintenance0 #his article
4en!atesh Maha)evan Faculty of
Higher E)ucation( Sin3urne
University of #echnology
4ic 567. Australia
vmaha)evan1sin3ume0e)u0au
Migration 8lanning
Implementation Governance
Architecture change Management
#he Architect iterates through these phases an) analyse
conte9tual information hich ai)s re:uirements management(
as shon in figure attache)0
Architecture
&onte9t
Iteration
Architecture
;efinition
aims to )eliver an approach in architecting solutions hich
can 3e utilise) as frameor! to a))ress common issues
in integration of enterprise level solutions0 #he
metho)ologies
)iscusse) in #OGAF version < are utilise) to )emonstrate the
feasi3ility of propose) solution0 #his paper intro)uces the
pro3lem space=scenarios( constraints( re:uirements( ena3lers(
ris!s( sample legacy application architectures an) propose)
integration solution presente) ith #OGAF components0 #he
groing num3er of aiting lists( rising pressure on me)ical
professionals an) accounta3ility for me)ical negligence are
only part of the motivation to ta!e initiative toar)s hol)s
a core mo)el integration strategy in various
legacy infrastructure systems0
*eyor)s2Smart Hospital System( the Open Group
Architecture Frameor! "#OGAF$( Integration Frameor!s(
Service Oriente) Architecture "SOA$
Architecture
Governance
Filre: Iteration
Cyclel>
Iteration
I0 I+#>O;U&#IO+
#he Smart Hospital System is a solution aime) to present
architecture Integration Frameor! using #OGAF?s
Architecture ;evelopment Metho)0 #he !ey to #OGAF is
the #OGAF Architecture ;evelopment Metho) "A;M$ 2 a
relia3le( proven approach for )eveloping enterprise
architecture )escriptions that meets the nee)s of the specific
3usiness0 #here are @ phases to the #OGAF core mo)el
hich inclu)e:
Architecture 4ision
Ausiness Architecture
Information Systems Architecture
#echnology Architecture
Opportunities an) Solutions
</@2627-772BB7.2<=6.=C-D0.. E-.6. IEEE
Figure 60 Iteration &ycles
A0 8hase 6: Architecture 4ision:
As )etaile) in the SHS 8roFect 8roposal )ocument( the
main 3usiness man)ates for the SHS are to 3uil) a ne I#
Integration 8latform=frameor! that shall 3e a3le to:
>espon) to ne 3usiness )eman)s of the
organisation "HospitalslMe)ical facilities$ for
the future "Scala3ility=ne applications=ne
)evices= more users$0
;eploye) :uic!ly at any ne location ithin
restricte) time frame( an) ith minimal
configuration an) no ne )evelopment =
customisation re:uire)0
@
Ae a3le to relia3ly service the current or!loa)
for ur3an hospital serving a population of I
million i0e0 up to 6.(... user accounts( up to
-.. concurrent users0 Along ith the ne
or!loa)s proFecte) of up to 6..(... user
accounts an) up to B(... concurrent users0
8rovi)e <<0<<<G availa3ility "hich e:uates to
B minutes of )ontime in a year$0
Fast an) efficient enough to 3e a3le to
simultaneously service several hospitals an)
mo3ile units in geographically )iverse areas of
the country0
Have no a))itional operational costs compare)
to the current infrastructure0
8rovi)e a single 4I from all the applications to
the user0
Integrate the current Sample application 8atient
Management System "8MS$ an) Accounting
an) 8ayroll 8ac!age "A88$ applications ith
minimal effort0
8rovi)e fle9i3ility in choice of application
provi)ers( to avoi) ven)or loc!2in0
A0 8hase 66: Ausiness Architecture:
#he folloing Figure - is Fust a scale) )on version of
the pro3lem s
E
ace0
Hospital Management System
External System
Figure 50 &omponents of the legacy application A88
Figure -0 #he Aoun)ary &onte9t Mo)el of the SMHS
A)ministrator: A user ho has a)ministrators privileges
to the HSIF0 Access is provi)e) to all applications an)
components ithin the SHS0 #he a)ministrator has access to
a)ministration an) maintenance functionalities ithin SHS0
Stan)ar) User: A user ith no a)ministrator privileges to
the SHS0 >estricte) access is provi)e) through the Unifie)
Interface only0 +o HSIF functionalities are surface) to this
user0 Users have access 3ase) on their user profile to specific
functionalities ithin the e9isting 8IMS an) E>8 systems
"legacy systems$H hoever this access ill 3e me)iate) via
the HSIF0
E9ternal System: An e9ternal system that can access
specifie) services through Application Integration
Frameor!0 #he folloing are the Architectural
representations of 8IMS an) AA8 for visual ai):
&lients
Server
Figure 70 &omponents of the legacy application 8MS
<
o
!
&0 8hase III: Information System Architecture:
"lIlSA#ip:ca$onaoo%a&'a
ComponentS
location of here the )ata e9ists "hich legacy )ata store$0
#he Ausiness Service component( ill :uery the Enterprise
;ata Integration Service upon receiving a client re:uest( in
or)er to fin) the location of the re:uire) information to
service the client re:uest0 #his information is then use) to
invo!e the appropriate legacy application logic to carry out
the re:ueste) tas!0
;0 8hase I 4:: #echnology Architecture:
I
"IMS Application an(
I
%ata Components
I
)*+elrserieelrllel$ace
)Sen(l'oca:y
'' et,Crt-e.uesti-esponse
Figure B0 SHS Integration Architecture "&onceptual 4ie$
#he SHS ;ata3ase is an aggregation of the ;ata3ase
&omponents of all the SHS Applications )eploye) in the
system0 #his is hoste) on the SHS ;ata3ase Server0 #he
Application &omponents of all the SHS Applications
)eploye) are hoste) on SHS Application Servers hich have
an SHS Agent each0 Each agent !nos the SHS Application
&omponents that are availa3le on the server0 #he SHS
Interface Server hosts SHS ,e3site an) the SHS ,e3
services0 #he e3site is an aggregation of the entire e3site
3ase) 4I?s of all the )eploye) SHS Applications0 #he e3
services of all the )eploye) SHS Applications are similarly
aggregate)( an) 3oth these aggregations are hoste) on the
SHS Interface Server0 #he SHS Server is a centrali'e) server
application that interacts ith all the SHS Agents in the
system( an) orchestrates the application integration process0
&urrently( the to applications are operating separately
ithout sharing any )ata0 As such it is possi3le that some
)ata is )uplicate) in the to applications? )ata stores0 #his
3rings up issues of merging of such )ata0 Although this coul)
3e a temporarily pro3lem for the life of the legacy
o
22. +e/0service Interlace
)t Sen( local
1)1 local -e.ues2-esponse
) ) )' ,et3or4 -e.uest5-esponse
Figure D0 E9ecution vie of SHS
Evaluation of technology Architecture:
A"" Application an(
%ata Components
applications in their e9isting structure( this pro3lem nee)s to
3e a))resse)0
#he Architecture #eam consi)ere) to solutions to this
pro3lem:
;ata >erite: #his re:uire) manually reconciling
conflicting )ata in the to )ata stores( an) mo)ifying the
associate) 3usiness logic to conform to this0 #his approach is
not suggeste) as it is too intrusive of the legacy applications(
an) can pose a maFor ris! to the sta3ilities of these
applications0
;ata integration using a separate )ata3ase: #his
approach envisages a separate )ata store calle) Enterprise
;ata Integration Service hich ill contain information for
)ata mapping amongst the e9isting legacy )ata( as ell as the
Evaluation &riteria: #he Evaluation as 3ase) on
>esearch on availa3le runtime environments hich are of
enterprise scale an) crossing chec!ing the
revies=pros=cons=sta3ility from various accompanying
)ocumentation an) 3logs 3y originators0
Evaluation Metho)s: #he i)ea of choosing lIS / an)
IAoss B0- are more relate) to hat suits 3est in a Enterprise
level Application runtime for applications"legacy=proprietary$
ritten in Iava=&JI&KK0 #he lIS as o3vious choice as the
Application L8IMSL( is ritten in 0+et hich re:uires a
Microsoft ,in)os runtime environment0 For the LA88L(
IAoss B0- as chosen as a )eployment server of choice
hich is a significant upgra)e from Fetty=apache=tomcat0
6.
Figure /0 ;eplyment vie of SHS
Aenefits: #he core 3enefit of a hy3ri) approach of
running - separate runtime Environments an) an ESA to
allo seamless re:uest=response style integration( inclu)e
Less ;evelopment=mo)ification on A8I on e9isting legacy
systems an) &lear separation of mi))leare( improves
performance "logical Mueues$ =security "Separate single sign
on"SSO$ mo)ule K H##8S connections$0
8itfalls: #he scala3ility of the system "a))ing more
in)epen)ent e3 applications$ oul) pose maFor
configuration surgery( if implementation )oes not a))ress
;ata synchroni'ation issues appropriately0 ;ue to e9tensive
use of e3 services the 8erformance=Muality of service may
3e hampere) if the transfer of large files is 3eteen systems
"format conversion may 3e an issue ithin -
applications 0e0g0 0o)t to 0)oc9 formats or large image file
formats$0
#echnological constraints: #he e9ecution of A88 on
IAoss i0e0 running on a U+INILinu9 server an) lIS running
on a ,in)os server an) the integration "ESA$ supporting -
E0 8hase 4:: Opportunities an) Solutions:
#he opportunities presente) 3y the integration solution
can 3e viee) in form of core :uality attri3utes( hich can
3e consi)ere):
8erformance: #he clear separation of mi))leare that
uses high2performance enterprise2class message :ueuing
solution results in this component 3eing a performance
ena3ler0 #he use of e32services for other messaging
"especially internal$ results in this factor 3ecomes a
performance constraint0 Hoever( this can 3e manage) 3y
using e32servers having sufficient capacity for the
proFecte) loa)s0 &aching of service en)points( scale2out of
e3 components 3ase) on performance re:uirements( use of
enterprise class technologies0
Usa3ility: A separate mo)ule )e)icate) to provi)ing
management services of the system is an ena3ler for the
usa3ility attri3ute0 A separate mo)ule for the Instrumentation
Logger is yet another ena3ler for usa3ility0 #his ill allo
system a)ministrators to easily trac! transactions through the
system for the folloing purposes #rou3leshooting(
;e3ugging an) Au)iting "for compliance to organisational
processes( an) for statutory compliance$0 Other ena3lers
liste) 3elo have to 3e )evelope) as part of the HL; an)
LL;0 #hese can 3e either scripts or softare mo)ules ith
user interface0
>elia3ility: >untime relia3ility shall 3e ensure) in the
system 3y having re)un)ant failover mo)ules i)entifie) an)
implemente) )uring )eployment0 Stateless services allo
loa)23alancing of critical components using specialise)
har)are )evices0 +on2runtime relia3ility shall 3e assure) 3y
having all nely )evelope) mo)ules specifically )esigne) to
cater to the 3oun)ary con)itions of Initialisation( Failure(
>ecovery an) #ermination0
Security: #he entire SHMS System shall 3e )eeme) to 3e
running ithin a corporate firealle) environment0 #he
Security aspect is covere) from B angles: single sign on
hich is on authentication gateay( encrypte) )ata access
ithin Ausiness services( >an)om :ueue num3er allocation
3y message 3ro!er( ;ou3le fireall an) Instrumentation
Logger for au)iting attac!s0 It shall employ a layere)
architecture ith critical assets in the inner area:
&6
MF
applications )eploye) on these - very )ifferent runtime
environments( may cause ;evelopers a some grief: li!e
in)os slashes"L=L$ an) Linu9 slashes"LOL$( maintaining the
consistency 3eteen ;atel;ata formats0 #he processing
times may hugely vary an) )epen) on legacy applications
internal performance=)epen)encies0
Ena3lers: #he availa3ility of source co)e for the legacy
systems an) other availa3le resources to 3uil) a suita3le ESA
E9ternal Fireall
6:
*7
&6
Cl
c:
?.
0lPP
&
e
88
&6
MF
6:
*7
&6
MF
c:
c:
&orporate Fireall
that meets all sta!ehol)er nee)s0 #he &lear separation of
application components( mi))leare an) "System=user$ ;ata
shall allo )evelopers to ma!e a hea) start on integration
process through ESA an) e3 services0
Figure @0 Security conte9t of the SHMS System
F0 8hase 4I:: Migration 8lanning:
#he SHS aims to smooth out any incompati3ilities 3y
folloing a migration plan hich aims to a))ress common
issues=challenges face) 3y enterprise level amalgamation of
applications inclu)e:
6 6
6-
A)apta3ility: #he use of generic components
infrastructural components0
Simplicity: #he propose) architecture uses the minimum
no0 of components in the simplest possi3le ay0
Fle9i3ility: #he mo)ular architecture propose) can 3e re
com3ine)( enhance)( an) scale)2out in a i)e variety of
ays( giving fle9i3ility at )eployment an) maintenance time0
Mo)ularity: #he use of layers( components( an) other
techni:ues ai) in a highly mo)ular internal structure(
enhancing overall system reusa3ility0
&onsistency: #he consistent use of the un)erlying
philosophy 3ehin) )esigning the component responsi3ilities
an) interfaces( an) special attention 3eing given toar)s
achieving a final list of nearly e:ual2si'e) components
enhances reusa3ility( an) the overall aesthetics of the
propose) architecture0
Orthogonality: #he clear2cut responsi3ilities of the
various components( ithout any overlap( ai)s in the
orthogonality of the components ithin the overall system
3oun)ary0
For ;etails on component level responsi3ilities see
appen)i90
G0 8hase 4II:: Implementation Governance
Q5R Iava EE an) 0+E# Interopera3ility( Integration strategies( patterns an)
Aest 8ractices( Marina Fisher( >ay Lai( Sonu Sharma( Laurence
Moroney( 8rentice Hall( Sun Microsystems 8ress( -..D
Q7R I# Architecture an) Mi))leare( Strategies for Auil)ing Large
Integrate) Systems( Secon) E)ition( &hris Aritton( 8eter Aye(
A))ison2,esley -..7
QBR http:==ms)n0microsoft0comlen2us=li3rary=ms<B7B<B0asp 9 Application
Architecture for 0+E#: ;esigning Applications an) Services( Last
visit 76666-..<
QDR https:ll0i3m 0 coml)eveloperor!s=li3rary=s2es3scenl
Un)erstan) Enterprise Service Aus scenarios an) solutions in
Service2Oriente) Architecture( 8art I( #he >ole of Enterprise Service
Aus( last viee) 7=666-..<Gunase!aran A0( A0 *o3u "-..-$( &itation
from Q@R( pp-B2-70
Appen)i9: ;etails of components:
An integration platform that aligns
hospital 3usiness strategies ith I#
investments through unification of
hospital?s e9isting core applications
"8atient Management System an)
Accounting an) 8ayroll System$(
Smart Hospital
8en)ing
H0 8hase 4III:: Architecture &hange Management
8en)ing
II0 &O+&LUSIO+
#he o3Fective of this paper has 3een achieve) 3y
investigation into various availa3le architecture
mo)els=frameor!s an) patterns that fit the category of
integration facilitators( ith a vision of the future )eman)s
for scala3ility an) e9tensi3ility0 ,hile SHS is aime) to
a)e:uately meet all the state) an) implie) re:uirements(
#OGAF supporte) in less reor! on the e9isting applications
to fit into the ne frameor!0 It also provi)e) a smoother
transition of the system from the imme)iate role of an
application integration frameor! for legacy applications( to
its eventual role as a pure application integration frameor!0
#hus( HSIF shall 3e )eeme) the propose) architecture of the
Architecture #eam0
#he propose) architecture 2 the HSIF 2 meets the
3usiness case re:uirements an) allos e9isting systems
"A88 an) 8MS$ to 3e open for feature rich front2en) hich
provi)es secure interfaces0 #herefore( 3oth recent
)evelopments an) our research outcomes in this fiel) proFect
are foun) to 3e very encouraging0 Hoever( more
investigation is re:uire) 3efore full confi)ence an) i)er
acceptance is to ta!e place in the I&# in)ustry0
>EFE>E+&ES
QIR >ee!ie( Iohn an) McA)am >ohan( A Softare Architecture 8rimer(
-..B( Angophora 8ress0
System "SHS$
SHS Application
;evelopment
Stan)ar)
User Interface
Management UI
provi)ing a single point of access via
implementation of a single UI "can 3e
e3 3ase) or rich2client$ an) ena3ling
future integration of other systems
"e9isting systems( or future
)eployments$ into the Hospital?s I#
A pu3lishe) set of specifications for
softare applications that have to 3e
conforme) to( III or)er for them to
integrate ith the HSIF0 Also provi)e
interface for HSIF0
&om3ination of the e9isting user
interfaces ena3le) to communicate via
e32services using e3 service pro9ies
that interface ith the Message >outer
ithin Enterprise Service Aus "ESA$0
#his is the interface for users to access
e9isting legacy functionality as ell as
any future a))itional application via the
HSIF0
Management user interface to ena3le
maintenance an) a)ministration tas!s
re:uire) to 3e carries out 3y the
a)ministrators of HSIF0 #his user
interface is )evelope) as part of this
proFect for management of all the in
house )evelope) components of the
ESA0 4en)or supplie) technologies
use) ithin the ESA ill have their on
interface0
Any 3usiness service or thir)2party
Q-R Applie) SOA( Service2Oriente) Architecture an) ;esign 8atterns(
Michael >osen( AorisLu3in!y( *evin #0 Smith( Marc I0 Aac6er( ,iley
8u3lishing Inc0 -..@
E9ternal Service application that ill 3e authorise) to
>e:uesters access specifie) hospital services using
HSIF0
Message >outer
Service ;irectory
A-A Gateay
First point of access for the 4I an)
E9ternal service re:uesters hich ill
)ynamically locate the appropriate
service re:ueste) an) route the re:uest
accor)ingly0 Message >outer( me)iates
communication an) service calls to
provi)e a separate contract ith the
service re:uesters an) the service
provi)ers0 #his separation of service
contracts ena3les changes in the service
provi)ers ith minimal effect on the
consumers0
>epository of services availa3le in the
hospital services ecosystem0 Service
)irectory ill ena3le service location
transparency in conFunction ith the
>outer0
Ma!e a selecte) su3set of hospital?s
services availa3le to e9ternal organisations
in a controlle) an) secure manner0
&om3ines the various eNlstmg services
across multiple legacy applications "8IMS
an) A88$ into a higher level 3usiness
Service service0 Service &horeographer hi)es the
&horographer granularity of the e9isting legacy
functionality into more atomic SOA li!e
services in line ith future )irection of the
&onstitutes 3usiness services )esigne) to
align to the hospital 3usiness re:uirements
3ase) on to encapsulate the legacy
Ausiness Services application A8I calls into an aggregate)(
higher level( an) atomic service call0 Each
3usiness service is the invocation point for
the
;escri3es an) coor)inate) the or!flo of
#he management engine that the
Ausiness
ho services interact "legacy an) ne$(
Management
Mo)ule
Management 4I interfaces ith in or)er to
carry out a)ministration an) maintenance
operations on the custom components of
the ESA0 #his Mo)ule may not 3e re:uire)
,or!flo
inclu)ing the logic an) the or)er of
Orchestration
interactions0
8rovi)es for )ata integration 3y mapping
Enterprise ;ata
Enterprise Service
Aus
Single Sign2On
)epen)ing on the choice of technology
use) to 3uil) the ESA0
&ollection of Message >outer( Service
;irectory( Instrumentation Logger an) the
Management Mo)ule hich carries out the
core integration responsi3ilities ithin
HSIF an) ena3les future progression of
hospitals I# ecosystem toar)s a more
stan)ar) Service Oriente) Architecture0
8rovi)es authentication ")oes user have
accessS$ an) authorisation "hat user has
access toS$ services for the hospital as a
hole( ena3ling a users to have a single
cre)entials for accessing multiple legacy
applications an) ne systems )eploye) in
future0
Integration Service
8IMS Ausiness
the relevant information from the legacy
Ausiness logic layer of e9isting 8atient
Information Management System in the
hospital0 #he 3usiness functionalities
containe) in this layer are to 3e e3 service
ena3le) for integration ith the other
in the via HSIF0
A88 Ausiness
Ausiness logic layer of eNlstmg
Accounting an) 8ayroll System in the
;etails of SUS component Interfaces
hospital0 #he 3usiness functionalities
containe) in this layer are to 3e e3
service ena3le) for integration ith the
other in the via HSIF0
Ausiness components that provi)e
the e9isting functionality ithin their
application0 #he purpose of this proFect
Ausiness is to integrate the functionality of these
&omponent components transparently an) provi)e
Interface
;escription
no0
access via a single user interface0 #he
,e32service interfaces 3eteen UI( e9ternal
internal functionality of these service re:uesters an) the Message >outer0 #his
is not at this level0 interface is responsi3le for me)iating re:uests from
A88 an) 8IMS E9isting )ata3ases of each legacy
;ata3ases application in the hospital0
;ata Access ;AL Layer of e9isting Accounting
Logic &omponents an) 8ayroll System in the hospital0
;ata Access components that
;ata Access
provi)e )ata access to the application
service consumers to the service provi)ers 3y 3eing
the first an) only point of contact 3eteen service
6(- consumers an) the Enterprise Service Aus "ESA$0
#he a)vantage of the separation of the service
provi)er interfaces to the UI is that the consumer
service contracts an) policies ill not have to
change 3y changing the service provi)ers an)=or
their service contracts0
Logic &omponent
)ata store0
E9ternal organisations that consume some services
5
provi)e) 3y the hospital
A88 ;ata Legacy Accounting an) 8ayroll
Store ;ata3ase
8IMS ;ata 8atient Information Management
Store System ;ata3ase
Any
service or application
component alrea)y liste) in this ta3le
,e32service interface 3eteen the management
User Interface an) the Management Mo)ule of the
7
ES;0 #he management mo)ule ill only control
the custom of the ESA0
,e32service interface of SSO is invo!e) 3y
Message >outer in or)er to authenticate the re:uest
B
as ell as retrieve the callers roles 3ase) access
Service or
&omponent
Message
Mueue
that is re:uire) to 3e monitore) an) or
au)ite) for performance( errors an) or
8ersistence message :ueue hich
service or component that are 3eing
monitore) ill su3mit events to0
Once a service re:uest is receive) 3y the Message
>outer an) authenticate) an) etheri'e) 3y SSO(
message router ill re:uest the most suita3le
D service provi)er for processing the re:uest 3y
engaging the Service ;irectory an) receiving the
A service that ill rea) the
service en)2point here it ill forar) the re:uest
Instrumentation su3mitte) messages su3mitte) from the to0
Logger message :ueue an) rites them to the
Instrumentation
UI
instrumentation )ata3ase0
,e3 user interface to )isplay the
instrumentation information in the
)ata3ase
A-A gateay ill relay the e9ternal client?s re:uest
/
to the message router for appropriate action0
Management Mo)ule ill sen) a comman) to the
mo)ules it can manage an) ill receive the
@
outcome of the re:uest "faile)( succee)e)$ an)
e9ecution )etails0
ESA ill invo!e the appropriate 3usiness service
<
3ase) on the re:uest message0
In case the service re:uest if for a long running
process an) re:uire) a 3usiness or!flo( ESA
ill forar) the re:uest to the Ausiness ,or!flo
6.
Orchestration hich ill ta!e the re:uest through
the appropriate 3usiness or!flo process an)
return the results once
Orchestration invo!es legacy functionality via
66
the 3usiness service0
Ausiness service invo!es the legacy
6-(67 functionality through their e32service
interfaces
Ausiness service :ueries the enterprise
)ata3ase "3efore legacy systems$ to locate
65 here the re:uire) information lives "hich
legacy system$ an) get the appropriate )ata
recor)
Service or application components that are
6B setup for monitoring ill sen) a status
message to a message :ueue
Instrumentation service that rea)s the
6D messages in the :ueue an) rites them into
the instrumentation )ata3ase
Instrumentation interface ill rea) the
6/
information from the )ata3ase for )isplay