Actually the majority of my clients are in the health care industry.
Replication is huge there, especially in the SQL CE space.
For example a doctor goes into the office and picks up a his pocketPC from
its cradle which has complete information about the patients he is going to
see that day. While he sees the patient and makes entries in the chart the
entries in the Medical Record are synchronized with the central office. His
appointment schedule is updated, certain actions he does are sent to the
clinic's front desk for processing (for example he requires tests, exams,
blood work, etc). Replication is the engine here.
There are mobile medical clinics which see patients in the field (nursing
homes, community centers, etc). Patient records are transferred to these
mobile clinics, and insurance information (especially MediCal, MediCare, and
Social Security) is checked and verified. At night it is sync'd back.
Again replication is the engine.
There are many pharmaceutical industries which receive data nightly and
process it for the morning and then send it back to hospitals. Replication
again is the engine.
All this is done with strict regard to regulatory compliance, privacy
concerns, and HIPPA.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com [quoted text, click to view] "Michael Hotek" <mike@solidqualitylearning.com> wrote in message
news:O9zfYJIGGHA.3896@TK2MSFTNGP15.phx.gbl...
> Unfortunately, that can't be answered. You have very strict privacy
> requirements as well as very strict controls on the data. Before you can
> start looking at putting in an infrastructure to distribute data, you
> first have to find out whether you even can and if you can, what business
> rules does it need to be governed under. That is going to tell you
> whether you have a central repository or whether you are distributing
> data. It will also tell you if changes to the data is allowed at multiple
> locations.
>
> --
> Mike
>
http://www.solidqualitylearning.com > Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
> "Raju Joseph" <vze24srd@msn.com> wrote in message
> news:%23gYvlIAGGHA.3856@TK2MSFTNGP12.phx.gbl...
>> Hi All,
>>
>> We are in healthcare domain and we have a complete package written in VB6
>> and SQL Server 2000. We have installed in one of our clients. This client
>> is actually part of a chain of hospitals. Each hospital can have patients
>> registered with them. Also, this patient could also go to other hospitals
>> within the chain.
>>
>> My question is, What is the best way to share the patient information.
>> One option would be to have a central repository. Another option would be
>> for the hospital to request for the patient information from the hospital
>> he was registered with. Is this possible. Can I just replicate a specific
>> patient information data. We are looking for the cheapest solution. Right
>> now, we are planning to give each hospital within the chain, a location
>> code and patient ID will be generated with this code prefix.
>>
>> Also, what are the options for me to send this data across.
>>
>> Any advise, please...
>>
>> Raju
>>
>
>