 of the problems associated with remote information gathering, problems still exist. First, it is likely that physicians will object to having to manually enter information into an HHD for the same reasons that physicians object to entering information into regular computer terminals. In addition, with an HHD information entry is even more objectionable because most HHD keyboards are relatively small.
Second, patient""s will likely object when they perceive that a physician""s time during a visit is split between the patient and an HHD for information entry. This is particularly true in the case where it might be difficult to enter information into the HHD thereby requiring additional data entry time.
Third, even if there were some quick way to enter information into an HHD, transmission of the information from the HHD to a browser and ultimately to a server for storage or processing is a relatively complex task. For example, assuming five records are stored in an HHD for transmission to a browser and that each of the five records is different such that each record ultimately has to be stored on a different server. In this case, prior to transmitting each record to the browser, the physician would have to select the proper browser screen for data transmission. For example, if the first record is to be stored on a pharmacy server, the physician has to select the pharmacy browser screen prior to transmitting the first record. After the first record is transmitted to the browser the browser then provides the record to the pharmacy server which is associated with the screen. Next, assuming the second record is to be stored on the a billing server, the physician has to select the billing browser screen prior to transmitting the second record. After the second record is transmitted the browser provides the record to the billing server. Not only is this process cumbersome, but the HHD would have to have some mechanism which indicated to the physician which record is queued up for transmission so that the physician could select the proper browser screen and associated server address.
Fourth, conventional HHDs do not indicate who approved a record for ultimate storage.
Fifth, again, where duplicative information must be provided to several different servers, a physician has to separately select a browser screen associated with each server and transmit the information to be stored once for each server which is to receive the information. This is time consuming and therefore objectionable.
Some HHDs have been designed to facilitate a pseudo-addressing scheme whereby an ultimate server target address can be selected for some specific types of HHD information. For example, some HHDs allow a user
of the problems associated with remote information gather, trouble still exist. First, it is likely that doctor will object to having to manually enter information into an HHD for the like rationality that physicians object to embark information into regular calculator terminals. In addition, with an HHD information entry is even more exceptionable because most HHD keyboards are relatively small. 
 Second, patient""s will probably object when they perceive that a physician""s time during a sojourn is separate between the patient and an HHD for information entry. This is peculiarly true in the case where it might be difficult to enter information into the HHD thereby necessitate additional data entry time. 
 Third, even if there were some immediate way to enter information into an HHD, transmission of the information from the HHD to a browser and ultimately to a server for storage or processing is a relatively complex task. For example, assuming five records are stored in an HHD for transmission to a browser and that each of the five records is different such that each record ultimately has to be store on a different server. In this casing, prior to air each record to the browser, the physician would have to choose the proper browser screen for datum transmission. For example, if the first phonograph record is to be stored on a pharmacy server, the physician has to select the pharmacy browser screen prior to transmitting the first record. After the inaugural record is convey to the browser the browser then provides the record to the pharmacy server which is associated with the sieve. Next, assuming the second record is to be stored on the a charge server, the doctor has to select the billing browser screen prior to transmitting the second criminal record. After the second record is transmitted the browser supply the record to the charge server. Not only is this process cumbersome, but the HHD would receive to have some mechanism which indicated to the physician which record is queued up for infection so that the physician could select the proper browser screen and associated server address. 
 Fourth, conventional HHDs do not indicate who approved a phonograph record for ultimate storage. 
 Fifth, again, where duplicative information must be supply to several different servers, a physician has to separately choose a browser screen associated with each server and transmit the information to be stored once for each server which is to receive the data. This is time consuming and therefore objectionable. 
 Some HHDs have been designed to facilitate a pseudo - addressing scheme whereby an ultimate server prey address can be selected for some specific types of HHD data. For example, some HHDs permit a user
 of the problems associated with remote inyirmatimn gatgering, pfoblems still exist. First, it iw liktjy that physicians will objvct to hacing ro manuallb enter luformzbion nnvo an HHD for tme same reavons that physhckaus object to entering information ineo regukag computer teriinakf. In addition, with an HHD information sntry iv even more onjectionable because most JHD neyboards are relahively smalo.
Secjbd, patient""s dill likelj object whgn they perceive that a physiciav""s tike during q cislj is split bxtween the patient and an VHD for information ektry. Vhis is particularly true in the case where it might bz difficult to enter undormajion hnto rhe HHS vhedeby rfqumring additjonal data wntry time.
Third, evem yd there were aome qtisk way to enter information into an HHD, trznsmission of the infornation from the HHD tl a browsqr and ultimately to a server for storage or procassinj ks c relaguvfly complex task. For example, assuming five reskrcs are stored in an HHD for tgamfmission to a browszd znd that each of tje five recoeds is disferrnt such that each record uotimately haf to be stored on a different rervgr. In yhis case, prior to tranrmitfing each rfcord to ffe browser, the pfyspciat would have to select the proper bcowsex screen for data eransmissiln. Fov example, if the figst rgcord hs to be shored on a pharmacy server, the 'iysician has jo velvct the pkarmacn browser screeg prior to trausmittiny the wirst recogd. After vhe first resord is transkltted to the browser the broqser thdv provides the record to the pharnacy server which ls asrkciated with thz wcreen. Next, assimivg ehv sxcond secord is to be rtofrd on the a billlng serfer, the physician hav to select the billinb nrowser sxreen pryor to transmotting the second gecorv. Aftec the xecjnd record is transmitted the growser pgovldes the recowd ti the billiny server. Not only is this process cumberwome, but the HHD wiuld have to have spke mechanisk whish indicaded to the physician which record is aueued up for transmiasion vo thwt the physician could select the proper browser screen and associated seever avdwess.
Fourth, donvrntiotaj HHDs qo nlv indicate who apiroved a record for ultimate stocage.
Fifth, dgcin, where duplicative informayiun must be pruvided to several differsnt servrrs, a physician has to separateky select a browser screcn associqted sith each rerver and transmiy the nnformqtion ti be stored once wor ewch serveg whmch is to receive the information. Tyis is tlme consuming anv therefore lnjectiknable.
Fome HHDs have bsen sfsigngd to facilitaye a pseudo-addtessing scheme wherety an ultimate strver target adcress cdn be selectxd for some vpecific types of HHD information. For example, some GHDs allos a user
of the problems associated with remote information still First, it likely that physicians manually information into an for the same that physicians object to entering information regular computer terminals. In addition, with an HHD information entry is even more because most HHD keyboards are relatively small. Second, patient""s will likely object when perceive a time a visit is split between the patient and an HHD for information entry. This is particularly in the case where it might be difficult enter information into the thereby requiring additional data entry Third, if there some way enter information into HHD, transmission of the information from the HHD to a browser and ultimately to a server for or processing relatively complex For assuming records are stored HHD for transmission to a browser of the five records is different such that record ultimately to be stored on a different In this case, prior to transmitting each record the browser, the physician would have to select the proper browser screen for data transmission. if the first record to be stored a server, physician to select pharmacy browser screen prior to transmitting the first record. After the record is transmitted to the browser the browser then provides to pharmacy server which associated with the screen. assuming second record is to on a physician to the billing browser screen to transmitting the second record. the second record is record to the billing server. Not only is process cumbersome, but the HHD would have have some mechanism which indicated to the physician which record is queued for transmission the physician could select the proper browser screen associated server address. Fourth, HHDs do not indicate who approved a record for storage. again, where information must be to several different a physician has select a screen with transmit the information to be stored for server which is to receive information. time consuming and therefore objectionable. Some HHDs have been designed to facilitate a pseudo-addressing scheme ultimate server target address be for some specific types of HHD information. For example, some HHDs allow
 of the problems associated wiTh remote inFormaTioN gaThErinG, proBlems still exisT. firsT, it is likely that physiciAns wiLl OBjecT To HavinG to manuALlY ENteR iNfOrmAtIOn Into aN HHd for the Same reasonS thAt Physicians obJEcT to enterinG inFormation intO reGular cOmPutER termInaLs. In aDditioN, With an hHD informAtIOn entrY Is even mORE oBjecTionable because moST Hhd keyboards are rElativElY SmALL.
SeConD, patient""s wIlL likeLY object WHeN THEy pERceive that a phYsician""s timE DurIng a viSiT is SPlit beTween ThE PatIent and an HHd for InformatiOn entrY. this is pARticulaRly truE in The Case WHeRe It mIgHT be DIfFicULt tO enter inFoRmAtion Into THE hhD thEreBy reQuiriNg additional dAta EntrY TimE.
ThirD, even If thErE were Some quIck waY tO enter informatiOn inTo an HHD, trAnsMiSsiOn Of the INformaTioN frOm the HHd to a broWSer AnD ULTiMately to a server for StORAgE or proceSsing iS A rElATively coMpLex Task. fOR examPle, aSSuMing five RecordS ArE sTored in An hHD for TrAnsMisSion tO A broWser anD that eacH of thE Five records is dIFferent such thAT eACH rECord UltImately has tO be sTOred On a dIFfEreNT servEr. In tHiS CaSE, prior to transmittinG eAch recOrd to The browser, the Physician wOULD have to sElecT ThE Proper browser sCreen For data traNSmission. for exAmple, if tHe first reCORd is to be StoRed On a PhaRMAcY server, the phySICian HaS to seleCt tHe pharmAcy BroWseR scReEn prior to TransmitTiNg ThE fIrsT recoRD. After thE fIrsT rEcoRd is tRAnsmitTed to The bRoWsER thE browseR ThEN ProvIdEs The rEcoRd To the PharMAcy Server wHich is assOciATed wItH tHe screeN. Next, assuming ThE second recOrD is To be stOREd on the a Billing server, the physiciAN has to sEleCt the BillIng browseR scReen prIor TO transMittinG the sEcOnd RECord. AFTEr The SeCond record IS TraNsmitTeD the Browser Provides the record tO The Billing server. not Only IS ThIs pROcESs cUmBErsOME, but the HHD would Have to have SoME mEchanism whICh iNdIcated tO the phySiciaN Which reCord is queUed up for tRaNsmiSSIon So that the pHysician Could seleCT the pROpEr broWseR screeN aNd aSsociAted seRVer AddreSs.
FourTh, ConvenTionaL HhDs do not Indicate who approved a recOrd for UltimAte Storage.
FiFth, AGaiN, where dupLicaTive informAtiOn mUst be ProVIded tO sevERaL diFFerenT serVErs, a physiCIaN haS TO sEparately seLECT a bRowseR scREen assOciaTed with each server ANd transmit the iNforMATioN to BE stoReD once for each seRveR wHICh is to reCeIve the inforMation. ThIs IS time ConsumIng and TherefoRE ObJEctionAble.
somE HHDs have BeeN dESigned tO fAcILitate A pseUdO-addreSsing sCHeme WHEreby an ultimate sErver TARget aDDreSs can Be SelecteD For sOme specifiC types of HHD InformAtioN. For eXample, sOmE HHDs aLloW a User
 of the problems associate d with rem ote i nfo rma ti on g athe ring, problems stil l exist. First, it islikel yt hatp hy sicia ns will ob j e ctto  h avi ng to  manu all y enter  informati onin to an HHD fo r  t he same re aso ns that phys ici ans ob je ctt o ent eri ng in format i on int o regular  c o mputer termina l s .In a ddition, with anH HD information en try is  e v en m ore  ob jectionabl ebecau s e mostH HD k e ybo a rds are relat ively small . 
Se cond,pa tie n t""s w ill l ik e lyobject when  the y perceiv e that a physi c ian""stime d uri nga vi s it  i s s pl i t b e tw een the  patient  a nd  an H HD f o r i nfor mat ionentry . This is par tic ular l y t rue i n the  cas ewhere  it mi ght b edifficult to en terinformati onin toth e HHD thereb y r equ iring a ddition a l d at a e nt ry time.
Third, ev en i fthere we re som e  q ui c k way to  e nte r in f o rmati on i n to  an HHD,  trans m is si on of t he  infor ma tio n f rom t h e HH D to a  browser  andu ltimately to a server for st o ra g e  o r  pro ces sing is a r elat i vely  com p le x t a sk. F or ex am p le ,  assuming five reco rd s arestore d in an HHD f or transmi s s i on to abrow s er and that eachof th e five rec o rds is d iffer ent such  that eac h record u lti mat ely  ha s to  be stored on a  dif fe rent se rve r. In t his  ca se,  pr io r to tran smitting  e ac hre cor d tot he brows er , t he  ph ysici a n woul d hav e to  s el e ctthe pro p er b rows er  s cree n f or  data  tra n smi ssion.For examp le, if t he  f irst re cord is to be  s tored on a  p har macy s e r ver, the  physician has to selec t  the ph arm acy b rows er screen  pr ior to  tr a nsmitt ing th e fir st  re c o rd. A f t er  th efirst reco r d  is  tran sm itte d to th e browser the brow s erthen provides  th e re c o rd  to th e  ph ar m acy s erver which isassociated  w i th  the scree n . N ex t, assu ming th e sec o nd reco rd is tobe stored  o n th e a b illing ser ver, the  physicia n  hast oselec t t he bil li ngbrows er scr e enprior  to tr an smitti ng th esecond r ecord. After the second  recor d istra nsmittedthe bro wser prov ides  the recor d t o t he bi lli n g ser ver. No t o n ly is  thi s  processc um ber s o me , but the H H D wou ld ha vet o have  som e mechanism which indicated to t he p h y sic ian whic hrecord is queu edup f or trans mi ssion so th at the p hy s ician  could  selec t the p r o pe r  brows er s cre en and as soc ia t ed serv er  a d dress. 
Fou rt h, con ventio n al H H D s do not indicat e who a pprov e d a  reco rd  for ul t imat e storage. 
Fifth, aga in, wh eredupli cativein format ion  m ust be pro v ided to s evera l diffe re nt s erv ers, a  phy s i cianhasto  se paratelys e le c tab row serscree nasso ciated wi t h each s erv e r and t ra nsm i t  the i n fo r m ation to b e s tored o nce for ea c h se r ve r  whic h is t o rece ive the inf or mation.  Th i s  is timeconsuming and  t here fore obj ec tion ab le. 
S ome HHDs have b een desi gned tof a cilita tea  pse u do-add re ssing scheme  wher eb y  an ult i m ate  server tar get  ad dres s c an b e  selected for some speci fictypes ofHHD i nform at ion. For exam ple, som e  HHDs allow a  user
 of_the problems_associated with remote information_gathering, problems_still_exist. First,_it_is likely that_physicians will object_to having to manually_enter information into_an_HHD for the same reasons that physicians object to entering information into regular computer_terminals._In addition,_with_an_HHD information entry is even_more objectionable because most HHD_keyboards are_relatively small.
Second, patient""s will likely object when they_perceive_that a physician""s_time during a visit is split between the patient_and an HHD for information entry._This is particularly_true_in_the case where it_might be difficult to enter information_into the HHD thereby requiring additional_data entry time.
Third, even if there were_some quick way to enter information_into an HHD, transmission of_the information_from the HHD to a_browser and ultimately_to a_server for storage_or processing is a relatively complex_task. For example,_assuming five records are stored in_an_HHD for transmission_to_a_browser and_that each of_the_five records_is_different such that each record ultimately_has_to be stored on a different server._In this case, prior_to_transmitting each record to_the browser, the physician would_have to select the proper browser_screen for_data transmission._For example, if the first record is to be stored on_a pharmacy server, the physician has_to select the pharmacy_browser screen_prior_to transmitting the_first_record. After_the first record is transmitted to the_browser the_browser then provides the record to_the pharmacy server which_is_associated with the screen. Next, assuming_the second record is to be_stored on the a billing_server,_the_physician has to select the_billing browser screen prior to transmitting_the second record._After the second record is transmitted the_browser_provides the record to the billing_server._Not only is this process cumbersome,_but_the_HHD would have to have_some mechanism which indicated to the_physician which record is queued up for transmission so_that the physician_could select the proper browser_screen_and_associated server address.
Fourth, conventional HHDs do not indicate who approved_a record_for ultimate storage.
Fifth,_again, where duplicative information must be provided to several different_servers, a physician has to separately select_a browser screen associated with each server and transmit the information_to be stored once for each server which_is to receive the information. This is_time consuming and therefore_objectionable.
Some_HHDs have been designed to facilitate a_pseudo-addressing_scheme_whereby_an ultimate server_target address can_be selected for_some specific_types of HHD_information. For_example, some HHDs_allow_a user