When, if ever, can Contract Law assist victims or patients of medical malpractice? I know medical malpractice involves mostly tort law, but when and how can Contract Law enter the fray or picture? I am not a lawyer, but I work in the medical field. Ordinarily, physicians ask patients to peruse and sign forms before prescribing certain medication (e.g. Diazepam) or medical procedure. These forms raise the question of contract law in medical malpractice. I know Capacity is a vitiating factor, but I do not know if it is an element of contract formation??? BUT ASSUME CAPACITY FOR THIS QUESTION. I want to focus on capable, reasonable, shrewd ADULT patients. Undeniably, incapacitated, unconscious, diseased patients lack capacity to form contracts!!! Unquestionably, I am asking about NON emergencies! I know these 5 elements must be formed for contract. See Ewan McKendrick, Contract Law Text Cases Materials 2020 9th edition, pages 17-8. The first is that the parties have reached agreement. This is usually done by demonstrating that one party has made an offer that the other has accepted. The rules relating to offer and acceptance are discussed in Chapter 3. Secondly, the agreement must be expressed in a form that is sufficiently certain for the court to be able to enforce. The tests applied by the courts when deciding whether a term has been expressed in a form that is too vague, incomplete, or uncertain to be enforced are discussed in Chapter 4. Thirdly, the agreement must be supported by consideration (although it is possible that effect may be given to a promise that is unsupported by consideration via an estoppel). The doctrine of consideration and the role that estoppel can play in giving effect to promises that are unsupported by consideration are discussed in Chapter 5. Fourthly, the law may only recognize the validity of the agreement if it is entered into in a particular form (such as writing). The significance of requirements of form has diminished in recent years but they have not been entirely abolished. Requirements of form are discussed in Chapter 6. Finally, the parties must have had an intention to create legal relations. This intention is presumed in commercial transactions, but in the case of domestic and social agreements the law initially presumes that the parties did not intend to be legally bound by their agreement. The doctrine of intention to create legal relations is discussed in Chapter 7.
Hardly ever While all doctors in private practice has a contract with each of their patients: For most practical purposes clinical negligence lawyers can forget about these. It is not that contractual duties do not exist – all private medicine and surgery is performed pursuant to such duties – but that they rarely add anything to the parallel duty owed in tort. The courts have been very reluctant to imply a duty in contract which goes beyond the duty imposed by the common law of negligence. While tort damages aim to restore the plaintiff to the position they were in before the tort and contractural damages aim to place them in the position they would have been in had there been no breach, for medical malpractice there is no practical difference.
Should I ask for a contract, when asking for the money? The proper time to define or formalize a contract is not when asking for the money, but when agreeing what tasks are expected from you and how much you will charge therefor. That way both parties will be clear on what is expected from each other. And if a dispute is brought to court, the fact-finder will have an objective document from which to identify who breached the contract. It is always recommendable that the contract be self-contained, and that relevant interactions between the parties be in writing or memorialized in some way that leaves no room for unverifiable allegations of the type &quot;I said, he said&quot;.
Am I correct in arguing that the LHD never really had implied consent to begin with? In other words, does the failure to honour the express refusal inform us about the legitimacy of prior claims of implied consent? No. They had implied consent and had not intent at the outset to dishonor it. They have violated the patient's privacy right when consent was expressly withdrawn, and they discovered that they cannot easily comply and therefore did not comply. The fact that they have made it expensive for themselves to comply with their legal obligations going forward does not imply that they lacked implied consent at the outset, so they should have no liability for the time period from when the training materials started to be used until the time when implied consent ended. They are only responsible going forward for their failure to honor the patient's wishes. It is not at all exceptional for a legal obligation to turn out to be more difficult to comply with when it arises than was anticipated when the systems that make the legal obligation difficult to comply with were implemented. Health care companies aren't expected to be prophets who can foresee the complex confluence of factors that has painted them in a corner, particularly when a situation has never come up before the current one. It is likely that no one person was ever even simultaneously aware of all the facts necessary to know that this could happen. Someone in the IT department will often not be intimately familiar with what is going on in the training part of the operation and what the privacy rules that apply are and even if someone was, that someone may have been in no position to do anything about it at the time. Health care providers aren't supposed to be evaluated with 20-20 hindsight. Given that they almost surely did not and could not easily have known that they had made a future express withdrawal of consent very difficult to effectuate, scienter can't be attributed to it. And, honestly, they are in more than enough trouble simply trying to deal with the problem post-express withdrawal of consent when they did start to violate privacy laws.
You can write anything you want (basic First Amendment protections): the question is whether one would be liable for damage that arises from what you're written, or whether you can distribute what you've written. Distribution may be restricted, thanks to the Commerce Clause (hence FDA regulations, which figure prominently in the analysis). Most software writers are not medical practitioners, and vice versa, and what the software writer does is implement something described by a competent medical practitioner. It is logically possible that a med. practitioner might also try to write software (no problem) and distribute it (possibly a problem); or, a software writer might read up on something on Wikipedia and try to implement it (again, no problem) or distribute it (possible problem). Damages can be sorted into two categories, implementation errors and scientific errors, and having ruled out deliberate sabotage, we are left with negligence. If the software writer failed to use suitable care in writing code that sums a set of numbers, the software writer has been negligent. If the person purporting to have the qualified scientific knowledge mis-states the formula, that person has been negligent. It is possible for many parties to be negligent (the programmer failed to be diligent in understanding the software requirements; the medical professional failed to adequately explain what was required of the program). The FDA does regulate medical devices, and "device" is construed pretty broadly (condoms are non-exempt class 2 medical devices). There is FDA guidance on medical software which makes it clear that the device manufacturer shoulders the regulatory burden. Anytime you manufacture a tangible thing (which is within the scope of FDA regulation for medical devices), you have to have the thing approved. Many (most?) medical devices implement software, and are thus within the scope of FDA scrutiny. It is not illegal to write software that ends up being implemented in an unapproved medical device, but the unapproved medical device itself is illegal. It is reasonably likely that purported medical software (not a gadget with software build in) would be held to be a non-exempt device. To know if something is exempt, you would look at the exemptions list, and determine that your program (or thing) is not on or implied by anything on that list. The visual acuity eye chart is a class 1 exempt item, as is the manual toothbrush. There is no way to specifically look for things that are only software, or that contain software, so the search through the list would have to be guided by knowledge of the subject area. Canada is helpful in explaining when software is a regulated medical device. This is non-probative w.r.t. US law but gives you an idea what is likely to be considered a "device". Under Canadian law, the software would be clearly a regulated medical device. The FDA has a power-point that attempts to say something about the matter which warns you that you are on your own and "You will need to go back to study and use the source regulatory documents" to make the determination. Eventually, slide 13, they hint that if you intend the software to be used in diagnosis, prevention, or treatment, then it is a device (so, yes, the aforementioned software would be a device, and probably not exempt from regulations). General purpose software (word processors, web browsers, communications software, etc.) are not indented to be used for a regulated purpose, although they can be so used, and thus they are probably not subject to FDA regulation. There is a murky relationship between regulatory approval and liability. Being approved by the government does not convey immunity to negligence suits (see Wyeth v. Levine), but being approved can have weight in determining whether a party was negligent, since regulatory scrutiny ostensibly filters out errors that could have been caught. Federal approval does not preempt state tort law, as the court ruled. Regulations pertaining to medical devices hold for anything that qualifies as a device, and is not defined (negatively) in terms of disclaimers. If you sell a medical device but label it saying "this is not a medical device, it is not created by a competent medical practitioner", that doesn't make it not a medical device. Unfortunately, what counts as a regulated device is based on intended use, and there is an obvious connection between disclaimers and intentions. Taking MS Word as an example, MS does not as far as I know say that "Word is not intended to be used as a medical device". It can certainly be used to diagnose, teat, and prevent medical conditions, but so too can a screw driver or pretty much anything else. The number of non-medical uses vastly outweigh the medical uses, so it would be deemed not to be a regulated device. A program which prescribed a set of prayers to be uttered in case of illness would be subject to First Amendment override of any FDA regulations. Quack medical devices are prohibited (that's why there is regulation of devices in the first place), but discerning the fine line between permitted actions based on nutty beliefs and forbidden actions is not easy. The FDA also has guidance on the distinction between "Complementary and Alternative Medicine", which does not clearly state that, for example, a software reading of your cakra-energies based on a computer program's questions is not a medical device. They do say of mind-body medicine (mentioning yoga, biofeedback and tai chi as examples) that "CAM practices in this domain would not be subject to our jurisdiction under the Act or the PHS Act", but then say "any equipment or other products used as part of the practice of mind-body medicine may be subject to FDA regulation, depending on the nature of the product and its intended use" (hence a yoga-enabling program may be subject to regulation).
You cannot be compelled to sign a form indicating that you agree to something. However, your lack of agreement does not override a policy that they have authority to set. There is a contractual way that this could work out for them, depending on what exactly the document is. To be a contract, the parties must agree to the terms voluntarily, and if you do not agree to the terms, there is no contract. A 10 year old child cannot be bound to a contract, anyhow, so the child's consent is legally irrelevant, though strategically a good idea in the sense of alerting the child to their obligation. To be a contract, both sides must offer something that they are not already obligated to provide. What is the school offering? On the school's side, they might claim "We offer an education", but as a public school, they already have that obligation. Schools have broad authority to impose rules in order to operate, so in lieu of a successful lawsuit that the district overstepped their authority and violated someone's constitutional rights, the school could have a policy prohibiting use of a cell phone in school. Paired with such a policy, they can grant conditional permission, subject to the parent (and symbolically, the child) agreeing to certain terms. Since they are not obligated to allow cell phones at all, they are offering something of value to you, and you have a contract. The cell phone owner could try suing the school for keeping the phone, but the suit would fail because there was a breach of the contract. A strategy probably not worth pursuing is arguing that the confiscation clause is unconscionable (which would void the contract, which entitles the child to have a cell phone at school). Confiscating the phone is not theft, since the intent is not to permanently deprive the owner of their property (just as it is not theft when you have to leave guns or recording devices at the security desk). If a student were to take a forbidden thing without the owner's authorization (such as a gun, or a phone) and it was then confiscated, the rightful owner might be able to sue the school – as long as their hands are clear (if they had no knowledge that the thing was taken and used in an unauthorized manner). In this case, the parent clearly knows and authorizes.
Preface and Caveats The question doesn't specify where this happened. I am providing an outline of the way that most U.S. states would handle this situation, if the fats are as they are much more likely to be and not as claimed in the question probably due to a misunderstanding of the underlying transaction. I identify areas where state laws most often vary and don't describe those areas of the law in detail since that is impossible without knowing where this happens. This is a matter of state law and varies from state to state, although most U.S. states are quite similar until you get to the fine details. Atypical language in the contract between the contractor and the client could also lead to a different conclusion. I don't know how this would be resolved in a non-U.S. jurisdiction. Background: The Structure Of A Typical Construction Loan Financed Construction Project In business and contractual disputes you can only understand the answer if you understand the underlying business transaction, which the question itself doesn't spell out very fully. The fact pattern identified in the question is so unusual that I strongly suspect that there is a misunderstanding of the facts, or an inadvertent misstatement in the language used in the question due to sloppy writing that flows from not appreciating the importance of some key facts. The transaction was almost surely structures more or less as follows (for background, I'm presenting a more general very of this kind of transaction rather than the simple one with no subcontractors or material suppliers involved, because this context helps someone understand why the laws are written the way that they are written.) Usually, the client owns real property, takes out a construction loan from a bank secured by the real estate, and hires a general contractor. The client will usually make some down payment to the general contractor who will take care of paying the subcontractors and material suppliers, and will pay the balance of the amount due to the general contractor through proceeds of the construction loan disbursed by the bank which are drawn as the work is done and payment is earned. Typically, each drawn cycle, which is often monthly for a smaller project and weekly, biweekly or semimonthly in a larger project, materials suppliers and subcontractors submit invoices and lien waivers to the general contractor based upon the work done. If the work is complete, a complete lien waiver is submitted, if he work in only partially finished, a partial lien waiver is submitted. The general contractor substantively reviews the invoices based upon a physical review of the construction site and a review of the subcontract. If there are problems it is rejected and must be resubmitted by the material supplier or subcontractor. If it is approved, the general contractor attaches that invoice as a supporting document to a draw request for the draw cycle summarizing all validly submitted invoices from material suppliers, subcontractors and itself, and also attaching a partial lien waiver from the general contractor. Then, the general contractor submits that draw request to a bank officer handling the construction loan as an agent of the property owner-client, and also a client representative for approval. The bank officer and client representative make a much less probing review of the draw request, looking only for obvious irregularities or suspicious amounts, and if everything is in order, they approve the request. Then, the bank write a check in the draw amount approved to the general contractor. The general contractor then disburses the invoiced amounts to the materials materials suppliers and subcontractors and pays itself the amounts that it has earned. Sometimes, however, the general contractor gets a valid invoice from a material supplier or subcontractor, and receives funds from the client in the form of a downpayment or a loan draw, but doesn't pay the subcontractor or material supplier with those funds. Also, sometimes, the general contractor does work that it is entitled to be paid for or incurs an obligation to a material supplier or subcontractor, but the client doesn't pay or the bank doesn't disburse the funds requested even though the request is valid. When a general contractor, material supplier or subcontractor doesn't get paid for work that is actually done at a particular piece of real estate, the law gives the firm that wasn't paid for its work on that particular piece of real estate what is called a mechanic's lien encumbering that piece of real estate. The details of how a firm with a mechanic's lien gives notice to the world of its rights, the priorities of lien's vis-a-vis each other, and the way that mechanic's liens are enforced varies significantly from state to state. But typically the notice must be given very promptly and not long after notice of non-payment is given, a lawsuit to foreclose on the real estate encumbered by the lien is commenced. An unpaid material supplier or subcontractor, in addition to its lien rights, can also sue the general contractor for breach of contract, and sometimes also for misappropriation of disbursements from the client or the bank. An unpaid general contractor, in addition to its lien rights, can also sue the owner of the property for breach of contract. The Facts In The Question and Analysis The first paragraph of the question tells us what went wrong. The client paid an employee of the general contractor (probably a project manager) instead of the firm the employee worked for (basically embezzling the money by deceiving the client into thinking that the employee was authorized to receive a payment to the employee's firm on its behalf when that wasn't the case), and the firm of the employee who was paid now wants to get paid. This happens and lawsuits usually follows when it does. But exactly what happens next depends upon the facts in the next to paragraphs. The next two paragraphs of the question, however, are probably confused and incorrect. The next two paragraphs say: Two weeks later, the client received a letter from the contractor's lender asking the client for money owed to the contractor, saying that if it was not paid, the client could be double charged. Does the client owe the contractor's lender? What probably actually happened is that the finance office of the contractor submitted a draw request to the bank officer in charge of the client's construction loan with the bank, and also gave a notice of the draw request to the client. The client tells the bank officer not to approve the draw request because the client has already paid the draw request directly to the employee of the contractor (probably the project manager) without the knowledge of the firm the employee worked for. What Happens Next If The Facts Are As I Believe Them To Be? When this happens, the finance officer at the contractor firm talks to the client figures out what happens and then talks to the employee to whom the payment was made. If the employee promptly turns over the funds the the contractor firm, the finance officers at the contractor firm scolds the employee for screwing up the system and the client for making a payment to the wrong person and there is no harm, no foul, and the matter is over. But if the employee who took the client's money doesn't turn over the money which the client can prove to the contractor firm that he paid to the employee, several things are likely to happen. Non-Lawsuit Actions: The client will direct the bank not to pay the draw request. The employee who took the money from the client is fired (no big deal, he was probably long gone). The contractor firm and/or the client will often, but not always, report to the police that the employee embezzled the funds from the client, and if the police find it credible, will issue an arrest warrant. The main reason not to do so is that the facts are uncertain enough that the police and prosecutor don't want to touch it (e.g. the client paid the employee in cash and didn't get a receipt, or the employee when asked says that the payment was made but was a &quot;tip&quot; or was payment for something unrelated), or the client and/or the contractor firm don't want to harm their reputations by making public the fact that there was a theft on this job. Three lawsuits could be brought, although, in practice, these might be consolidated as claims against different parties and cross-claims between defendants, in a lawsuit brought by the contractor, or in some other configuration. The contractor firm sues the employee who took the money for converting money from a client intended for it (probably both as a tort and as a breach of fiduciary duty by an agent of the construction firm). The contractor firm sues the client for breach of contract. The question is about the liability of the client in this second lawsuit. The client might also bring a counterclaim against the contractor for negligent supervision of its employee if the employee did indeed abscond with the money and the facts support that counterclaim. If the client prevailed on that counterclaim, the judgment on the counterclaim for negligent supervision (e.g. if the contractor knew that the employee had a history of doing things like this and didn't warn the client) would be setoff against the breach of contract judgment, rather than being a defense to the breach of contract claim. The client sues the employee for fraud, conversion or theft. What Are The Rights Of The Parties In These Lawsuits? In the second lawsuit, the client has breached the contract. The contract said to pay the firm, the client paid someone else, and so the obligation under the contract was not satisfied. The disputes in the lawsuit between the contracting firm and the client will be over whether the employee had apparent authority to accept the funds as an agent of he contracting firm, over whether the payment that the client says was made to the employee was made at all, and over the purpose of the payment if a payment was made to the employee but the employee claims that it was a &quot;tip&quot; or a payment for something else (e.g. the employee also had a catering side hustle and the employee says it was for catering services). The issue of whether the client made the payment at all may be hard to prove if the payment was made in cash and the employee didn't provide a receipt and will come down to the credibility of the client and employee's testimony at trial. if the payment was made with a check or credit card, bank records will make it an open and shut case on that issue that will probably not be disputed at trial. If the facts reveal that the employee had apparent authority to accept the funds from the client for the contractor firm and that the payment was for work on the project and not something else, then the the payment made by the client to the employee satisfies the client's duty under the contract even if the employee wasn't actually authorized to receive the funds for the contractor firm. So, the client wins and the contractor firm's sole remedy is to sue its employee for misappropriating the client's funds. On the the other hand, if the employee did not have apparent authority to accept the funds from the client, or the payment was for something other than work on the project, or the client fails to prove that the payment was ever made, then the client owes the money to the contracting firm and must pay the contracting firm for the amount due (plus interest, litigation costs and possibly attorneys' fees depending on the terms of the contract). The client may pay that obligation out of separate funds of the client's own, or may authorize a the bank officer to make a draw on the construction loan to pay the amount owed. The construction loan bank of the client wouldn't sue the client or demand payment from the client for the amount that should have been paid to the contractor firm but was instead paid to the employee. It didn't pay money to someone it shouldn't have paid it to unless the client authorized the bank to do so. And, the bank won't pay the contractor without the client/borrower's say so. If the client authorized a draw payment from the construction loan to the employee rather than the contractor firm, the client still owes the bank for what it paid to the employee at the direction of the client (in addition to all other draws on the project), although the client may have a suit against the bank officer for negligence in administering the loan by failing to flag that the payee was wrong (which might lose but isn't a sure loss). The amount owed to the contractor firm proceeds under the analysis set forth above. What If The Facts Are Right? If, improbably, the facts as stating in the question are actually what happened, the client will owe or not owe the contractor money under the same analysis as above. But the client will not have liability to any company that the contractor got a loan from (which would not encumber the client's real estate), since the client has no contractual relationship with the contractor's lender. Post-Script On Double Payment Prevention Laws The question hinges on the unfairness of the client having to possibly pay twice for the same construction work. In some situations, where the general contractor firm is at fault for causing the double payment to happen, the law protects the client from double payment, even though those laws don't apply here. I explain why these laws don't apply below. Basically, the client has to eat the double payment when the double payment occurs because the client screwed up though no fault of the general contractor and the general contractor doesn't benefit from the double payment. Some states have laws designed to prevent property owners, often only residential property owners having work performed on their own residences, from having to double pay for work done in some circumstances. But these laws usually only apply when the client pays the general contractor firm as the client is supposed to, satisfying his contractual obligation, and the general contractor doesn't pay the subcontractor, causing the subcontractor to sue the general contractor for breach of contract and the owner to enforce the subcontractor's mechanic's lien. In those situations, the double payment prevention law eliminates the subcontractor's mechanic's lien rights when the client pays the general contractor in full, and the subcontractor is left only with a lawsuit against the general contractor who didn't pass on the client's or the client's bank's payment to the general contractor for the subcontractor's share of work to the subcontractor. In this case, the double payment laws usually wouldn't apply because the legal issue here is whether the client paid the contractor, or was deceived by the employee into paying someone other than the contractor in an act of conversion/embezzlement/fraud.
Is this legal? Yes Or does it mean that employee will be in breach of his/her contract? Yes You are assuming that if the evidence is allowed to be presented then that automatically means that keeping it for that purpose is not a breach of the contract. This is not necessarily so; it can be both at the same time. That said, it is unlikely that an employer would attempt to sanction an employee for this as the courts would (rightly) see it as an attempt to pervert the course of justice. As in most things in the law it is possible for all parties in a matter to be on the wrong side of it. If you want to come to the tribunal with "clean hands" then the best thing to do is make a record (not a copy) of the relevant documents and return then to the employer. Before going to the tribunal get your solicitor to subpoena the documents that you want - they will have to produce them and you have them without breaking your contract.
It sounds to me like the parties made proposals with an intent to draw them up and formalize them but didn't intend to form binding agreements. The first agreement sounds vague. The second was committed to writing, suggesting that the written deal was to be the real agreement, and not executed. In the last case, it doesn't appear that there was an agreement because there was no meeting of the minds on the essential term, which was the price. Going to court is expensive. It is expensive whether this is litigating underlying disputes or trying to enforce an alleged oral settlement that is disputed. Also, settlement discussions that don't result in a resolution are not admissible as evidence in court. Making a deal would be nice, but Dave's concept of what constitutes a deal seems to be out of touch with reality.