03.08.2013 Views

Public Health Law Map - Beta 5 - Medical and Public Health Law Site

Public Health Law Map - Beta 5 - Medical and Public Health Law Site

Public Health Law Map - Beta 5 - Medical and Public Health Law Site

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

contact is not a physician, then the court is more likely to find that the local<br />

practitioner has become the borrowed servant of the telemedicine practitioner <strong>and</strong><br />

that the telemedicine practitioner is responsible for all aspects of the patient’s care.<br />

This would be moderated if the local contact was under the supervision of another<br />

physician, who would then have primary legal responsibility for implementing the<br />

telemedicine practitioner’s recommendations.<br />

Physicians who conduct remotely controlled surgical <strong>and</strong> medical procedures will<br />

have the same legal duties as they would if they were in the operating room with<br />

the local physician. At least for the next several years, until these procedures<br />

become commonplace, remote physicians can also assume that they will be held<br />

liable for problems with the equipment <strong>and</strong> the other aspects of the procedure that<br />

deviate from ordinary practice. This exp<strong>and</strong>ed liability mirrors the situation in<br />

experimental medicine, where the supervising physician must ensure the integrity of<br />

the entire process. They may be able to counterclaim against the manufacturers of<br />

the equipment, but these counterclaims may be limited if it was not specifically<br />

manufactured for telemedicine. For example, if a st<strong>and</strong>ard desktop computer were<br />

used as a monitoring terminal for a remote surgical procedure, the manufacturer<br />

could reasonably claim that this was not an intended use <strong>and</strong> that it should not be<br />

responsible for personal injuries flowing from the monitor’s failure.<br />

b) Being the Local Contact<br />

Traditional consultations are premised on a relationship of trust between the<br />

primary physician <strong>and</strong> the consultant. If either does not know the other, or does not<br />

trust the other, these consultation become problematic. Putting aside telemedicine,<br />

many MCOs are already raising this issue by forcing primary care physicians to<br />

consult with specialists they know nothing about, <strong>and</strong> putting consultants in the<br />

position of not knowing the capabilities of the primary physician. This will be<br />

exacerbated by telemedicine. Local practitioners could be in the same position as<br />

the consumer as regards determining the competence <strong>and</strong> license status of the<br />

remote practitioner, with the caveat that the courts are likely to find that there is a<br />

duty to ensure the competence of the remote consultant.<br />

Practitioners who work with remote consultants, especially those across state lines,<br />

should document the training <strong>and</strong> licensure of the consultant as part of their office<br />

records. This does not need to be duplicated in each patient’s record, but it must be<br />

available to show proper diligence in screening the consultant. There should also be<br />

a record of the consultation <strong>and</strong> any recommendations of the consultant. This could<br />

be in the form of ordinary chart notes <strong>and</strong> a letter from the consultant. If the<br />

consultation is conducted through a computer, then the session could be recorded by<br />

the computer <strong>and</strong> stored as an electronic file. These files can be compressed <strong>and</strong><br />

transferred to a CD-ROM that is kept with the patient’s other medical records.<br />

c) Being the Remote Consultant<br />

255

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!