- This topic has 8 replies, 6 voices, and was last updated 14 years, 4 months ago by
.
-
Topic
-
-
Replies
-
-
I’m attaching a diagram we did when broke up from one single site to multiple sites. The diagram is our PAFM (Patient Access Finanacial Managment) site. It contains processes for ADT, Registration, Abstracting, Schedules and Charges. We have a second CIS (Clinical Info Systems) site for clinical systems (Rx, Reference Labs, Rad/PACS, Transcription, etc) in which the threads and processes are similarly organized.
Hope this helps.
-
We have one site per application.
snd/rvc are extenal
in/out are internal (inter-Cloverleaf)
Here is a PAS site
Process Connection State Proto Status Count Started
top_prod_rp cap_prod_rp_adt_out up up 0 03/05/10 10:27:39
top_prod_rp ccm_prod_rp_adt_out up up 0 21/05/10 09:18:18
top_prod_rp cdc_prod_rp_adt_out up up 0 03/05/10 10:27:51
top_prod_rp cdr_prod_rp_adt_out up up 0 03/05/10 10:27:54
top_prod_rp cwb_prod_rp_adt_out up up 0 03/05/10 10:28:03
top_prod_rp eds_prod_rp_adt_out up up 0 03/05/10 10:28:06
top_prod_rp fdw_prod_rp_adt_out up up 0 20/05/10 10:27:41
top_prod_rp har_prod_rp_adt_out up up 0 03/05/10 10:28:16
top_prod_rp pma_prod_rp_adt_out up up 0 03/05/10 10:28:19
top_prod_rp ris_prod_rp_adt_out up up 0 03/05/10 10:28:25
top_prod_rp sol_prod_rp_adt_out up up 0 03/05/10 10:28:29
top_prod_rp top_prod_rp_adt_rcv up up 0 02/11/09 09:43:24
top_prod_rp top_prod_rp_adt_snd up up 0 02/11/09 09:43:44
top_prod_rp ult_prod_rp_adt_out up up 0 21/05/10 09:03:09
Here is a RIS site
Process Connection State Proto Status Count Started
ris_prod_ih ccm_prod_ih_lab_out up up 0 21/05/10 09:16:38
ris_prod_ih ris_prod_ih_adt_snd up up 0 10/05/10 21:25:54
ris_prod_ih ris_prod_ih_lab_rcv up up 0 22/03/10 07:25:52
ris_prod_ih ris_prod_ih_lab_smt up up 0 02/11/09 12:36:35
ris_prod_ih top_prod_ak_adt_in up up 0 02/11/09 12:36:38
ris_prod_ih top_prod_fh_adt_in up up 0 02/11/09 12:36:35
ris_prod_ih top_prod_ke_adt_in up up 0 02/11/09 12:36:34
ris_prod_ih top_prod_km_adt_in up up 0 02/11/09 12:36:38
ris_prod_ih top_prod_os_adt_in up up 0 02/11/09 12:36:37
ris_prod_ih top_prod_pm_adt_in up up 0 02/11/09 12:36:39
ris_prod_ih top_prod_qe_adt_in up up 0 02/11/09 12:36:37
ris_prod_ih top_prod_rk_adt_in up up 0 02/11/09 12:36:33
ris_prod_ih top_prod_rp_adt_in up up 0 02/11/09 12:36:35
ris_prod_ih top_prod_sw_adt_in up up 0 02/11/09 12:36:34
-
I tried to attached an Excel 2007 spreadsheet that I created to help with doing a cloverleaf upgrade on that production server but was unsuccessful this morning.
It lists all our sites by categories as follows:
admin sites
batch sites
receiving/inbound sites
distribution sites
grouped sites
sending/outbound sites
mock sites
golive sites
It also shows the interface names in each of those sites except for the mock sites so I would know what customers to contact when upgrading that site.
I’m not sure if the spread sheet will add much benifit to you beyond the groupings I mentioned above.
If you do get into the thread naming standards here are some of the naming conventions I can recall we use:
ib_ (inbound thread from a foreign system)
ob_ (outbound thread to a foreign system)
ls_ (leap send to another cloverleaf server)
lr_ (leap receive from another cloverleaf server)
js_ (jump send to another site on the same cloverleaf server)
jr_ (jump receive from another site on the same cloverleaf server)
hs_ (hop send to another cloverleaf process in the same site)
hr_ (hop receive from another cloverleaf process in the same site)
mock_ (interface that pretends to be foreign system during extended downtimes
dump_ (interface that appends messages to a dump file)
que_ (interface that writes one message per file to a directory)
load_ (loads file(s) at a throttled rate from a directory)
rs_ (resend messages to a foreign system that has been down or NAKed something)
grab_ (intercept a message between a hs_ -> hr_)
return_ (return a message between a hs_ -> hr_)
Russ Ross
RussRoss318@gmail.com -
-
-
Alerts do most of the work of monitoring for us.
We also have a home grown web stats page that will give us an overview at a glance on demand.
These days there is a global monitoring product that might save you the trouble of writing your own stuff to generate web pages like we did long long long ago.
Our alerts have been refined to something that works good enough that we have gotten lazy and rarely take a look at the home grown web stats pages all that often anymore.
Fortunately, the cloverleaf part of the integrations are mostly rock solid and 99% of issues are with the foriegn systems, network, or security.
We got so comfortable and busy during one period that we discovered it had been 900 days since our last reboot, which we really like to do at least annually, so we are covered on backups if the machine doesn’t come back up.
With hunderds of sites and over a thousand interfaces this is a good thing.
If we had even a fraction of the trouble the foreign systems seem to have, we would be in hell.
We run on AIX in case you are wondering and have since the beginning.
Russ Ross
RussRoss318@gmail.com -
-
Garrett,
We run multiple sites and simply have multiple NetMonitor windows (1 for each site) running on the workstation in our Operations area. We utilize alerts, and as long as the NetMonitor is active (can be minimized in the task bar), then Operations will get the Alert Window popping up on the workstation. We also will trigger alerts to our on-call phone (using e-mail).
Jim Cobane
Henry Ford Health
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
