ORDER
THIS CAUSE is before the Court upon Defendant’s Motion to Dismiss, (“Motion”), ECF No. [13], Plaintiffs Complaint, ECF
I. Introduction
Plaintiff Yehonatan Weinberg (“Plaintiff’) commenced this class action lawsuit on August 4, 2015, against Defendants Advanced Data Processing, Inc. (“ADP”) and Intermedix Corp. (“Intermedix,” together with ADP, “Defendants”),
At some point in 2012, Plaintiff was taken by ambulance to a hospital for emergency medical treatment. Compl. ¶36. In order to use the ambulance, Plaintiff was required to provide the ambulance service with his Sensitive Information. Id. ¶ 37. “Unbeknownst to Plaintiff,” the ambulance services he used, Philadelphia Fire Department Emergency Medical Services (“EMS”), engaged Defendants to handle its billing and payment-related processing services. Id. ¶38. As a result, Defendants received Plaintiffs Sensitive Information. Id. Between June 1 and October 2, 2012, “an Intermedix employee systematically accessed and viewed the Sensitive Information of hundreds (if not thousands) of emergency medical service patients [the Class] who used ambulances ([for] which Intermedix provided, among other things, billing and payment processing [ ]). This Sensitive Information was then provided to third parties who used it to file fraudulent tax returns with the Internal Revenue Service.” Id. ¶¶ 4, 21.
The records accessed and viewed by the Intermedix employee included Plaintiffs Sensitive Information. Id. ¶39. Plaintiffs Sensitive Information was “thereafter disclosed to or sold to a group of individuals who subsequently used that information to steal his identity and file a fraudulent tax return using, his name and Social Security number.” Id. ¶ 40. Plaintiff alleges that “after learning that his identity was stolen, Plaintiff Weinberg spent (and continues to spend) a substantial amount of time and resources fixing the identity theft that he experienced.” Id. ¶ 41. Plaintiff further claims that these instances of identity theft, both for him and for the Class, were caused directly by Inter-medix’s failure to protect his Sensitive Information. Id. ¶¶ 6, 44-46.
Intermedix’s alleged security failures include, but are not limited to, the following:
Failing to ensure the confidentiality and integrity of electronic protected health information created, received, maintained, and transmitted in violation of 45 C.F.R. § 164.306(a)(1);
Failing to implement technical policies and procedures for electronic information systems that maintain electronically protected health information to allow ac--eess only to those persons or software programs that have been granted access rights in violation of 45 C.F.R. § 164.312(a)(1);
Failing to implement policies and procedures to prevent, detect, contain, and correct security violations in violation of 45 C.F.R. § 164.308(a)(1);
Failing to identify and respond to suspected or known security incidents, and*1363 failing to mitigate, to the extent practicable, harmful effects of security incidents that are known to the covered entity in violation of 45 C.F.R. § 164.308(a)(6)(ii);
Failing to protect against any reasonably anticipated threats or hazards to the security or integrity of electronic protected health information in violation of 45 C.F.R. § 164.306(a)(2);
Failing to protect against reasonably anticipated uses or disclosures of electronic protected health information that are not permitted under the privacy rules regarding individually identifiable health information in violation of 45 C.F.R. § 164.306(a)(3);
Failing to ensure compliance with the HIPAA security standard rules by their workforce in violation of 45 C.F.R. § 164.306(a)(4);
Impermissibly and improperly using and disclosing protected health information that is and remains accessible to unauthorized persons in violation of 45 C.F.R. §§ 164.502, et seq.; and
Failing to effectively train all members of their workforce on the policies and procedures with respect to protected health information as necessary and appropriate for the members of their workforce to carry out their functions and to maintain security of protected health information in violation of 45 C.F.R. [§ ] 164.308(a)(5). . ■ .
Id. ¶¶ 30-31. The Complaint also alleges that Defendants failed to comply with industry standards relating to data security.
The Complaint states three counts — one for negligence, a second for breach of fiduciary duty, and a third for unjust enrichment. As to the negligence claim, Plaintiff asserts that Defendants “had a duty to exercise reasonable care in safeguarding and protecting” Sensitive- Information, id. ¶ 55, as well as “a duty to employ procedures to detect and prevent the improper access and misuse of the Plaintiffs and the Class’s Sensitive Information,” id. ¶ 56. Plaintiff alleges that Defendants unlawfully breached these duties. Id. ¶¶ 56-57. “But for [Defendants’] breach of its duties, Plaintiffs and the Class’s Sensitive Information would not have been compromised. Plaintiffs and the Class’s Sensitive Information was stolen and accessed as the proximate result of Intermedix failing to exercise reasonable care in safeguarding such information by adopting, implementing, and maintaining appropriate security measures.” Id. ¶59. Pursuant to the claim for breach of fiduciary duty, Defendants “owed a fiduciary duty to Plaintiff and the Class to: (1) protect their Sensitive Information; (2) timely notify them of a data breach; and (3) maintain complete and accurate records of what and where their Sensitive Information was stored and who had access to that information.” Id. ¶ 63. Defendants breached this duty to Plaintiff and the Class by failing to safeguard their Sensitive Information, which failures are articulated in more detail above and in the- Complaint. See id. ¶ 64. For counts one and two, Plaintiff alleges actual damages that proximately flow from Defendants’ breach 'of fiduciary duty, as well as “other forms of injury and/or harm including, but not limited to, anxiety, emotional distress, loss of privacy, and other economic and non-economic lósses.” Id. ¶¶ 60-61, 65-66.
II. Legal Standard
A pleading in a civil action must contain “a short and plain statement of the claim showing that the pleader is entitled to relief.” Fed.R.Civ.P. 8(a)(2). Although a complaint “does not need detailed factual allegations,” it must provide' '“more - than labels and conclusions, and a formulaic recitation of the elements of a cause of action will not do.” Bell Atl. Corp. v. Twombly,
A court considering a Rule 12(b) motion is generally limited to the facts contained in the complaint and attached exhibits, including documents referred to in the complaint that are central to the claim. See Wilchombe v. TeeVee Toons, Inc.,
III. Discussion
Defendants argue that Plaintiffs allegations are conclusory and, thus, insufficient. See Motion at 2. For this reason, they argue that none of Plaintiffs three counts state a claim upon which relief can be granted. See id. Plaintiff counters that Defendants’ arguments are unsupported and improperly rely on facts outside of the four corners of the complaint. See ECF No. [18] (“Plaintiffs Response”) at 2.
A. Negligence
Defendants argue that dismissal of Plaintiffs negligence claim is warranted because Plaintiff has failed to establish any direct relationship between the parties— and even explicitly conceded as much. See Motion at 5-6 (quoting Compl. ¶24) (“Plaintiff pleads that he ’did not have a direct relationship (business or otherwise) with [Defendants].”’). Plaintiff responds that Defendants owed him a duty that
A negligence claim requires a plaintiff to show that (1) defendant owes plaintiff a duty, (2) defendant breached the duty, (3) defendant’s breach injured plaintiff, and “(4) [plaintiffs] damage [was] caused by the injury to the plaintiff as a result of the defendant’s breach of duty.” Resnick v. AvMed, Inc.,
1. HIPAA
HIPAA provides no private right of action — a fact which Plaintiff does not contest. See Pl. Resp. at 7-8; Jenkins v. Grant Thornton LLP,
“Florida courts have refused to recognize a private right of action for negligence per se based on an alleged violation of a federal statute that does not provide for a private right of action.” Stevens v. Danek Medical, Inc.,
2. Undertaker’s Doctrine
“The undertaker’s doctrine imposes a duty of care not only on the parties to a contract but also to any third parties that perform services under the contract.” Hogan v. Provident Life & Acc. Ins. Co.,
Here,-Plaintiff alleges that Defendants voluntarily agreed to provide EMS with medical billing and payment processing services, through which Defendants knowingly received Plaintiffs (as well as the Class’s) Sensitive Information. Compl. ¶¶ 38, 55. Defendants, therefore, “assume[d] a duty to act carefully and to not put [those patients] at an undue risk of harm” by, for example, neglecting to implement data security policies and procedures. Id. ¶¶3235, These allegations are sufficient to state a claim for negligence pursuant to the undertaker’s doctrine.
In their Motion, Defendants rely on cases with no-duty findings predicated upon factual circumstances that are conspicuously absent in the instant, action. See, e.g., Willingham v. Glob. Payments, Inc.,
B. Breach of Fiduciary Duty
The elements of a claim for breach of fiduciary duty are: (1) the existence of a fiduciary relationship; (2) breach of a duty owed by the fiduciary; and (3) proximate cause. Combe v. Flocar Inv. Grp. Corp.,
“A fiduciary relationship which is implied in law is based on the specific factual circumstances surrounding 'the transaction and the relationship of the par-' ties.” First Nat’l Bank & Trust Co. of Treasurer Coast v. Pack,
By Plaintiffs own admissions, Plaintiff did not depend upon either Defendant nor did either Defendant undertake to counsel, act for, or protect Plaintiff in any capacity. Compl. ¶24 (Plaintiff “did not have a direct relationship (business or otherwise) with Intermedix.”). Because he cannot plead facts to establish any direct relationship, let alone a fiduciary one, Plaintiff appears to improperly base his claim on the conclusory allegation that “[a]s guardians .of Plaintiffs’ ... Sensitive Information, Defendant owed a fiduciary duty to Plaintiff and the Class.” Id. ¶ 63. But .the mere receipt of confidential information is insufficient by itself to transform an arm’s-length transaction into a fiduciary relationship. See Winter Park Condo. Ltd. P’ship v. Wachovia Bank, N.A.,
Defendants argue that Plaintiffs allegations demonstrate that any subject transaction was too tenuous to support a direct conferral of benefit, as required by a valid claim for unjust enrichment. Plaintiff responds that direct-contact between the parties is unnecessary to confer a direct benefit on a defendant for purposes of an unjust enrichment claim. The -Court agrees. ;
Unjust enrichment is an equitable doctrine that “has to do with wealth being in one person’s hands when it should' be in another person’s.” Jovine v. Abbott Labs., Inc.,
The Court finds Resnick instructive.
[T]hat they conferred a monetary benefit on defendant in the form of monthly premiums, that [defendant] AvMed “appreciates or has knowledge of such benefit,” that defendant uses the premiums to “pay for the administrative costs of data management and security,” and that defendant “should not be permitted to retain the money belonging to Plaintiffs ... because [AvMed] failed to implement the data management and security measures that are mandated by industry standards.” Plaintiffs also allege that AvMed either failed to implement or inadequately implemented policies to secure sensitive, inforrpation, as can be seen from the data breach.
Resnick,
Similarly, under the instant facts, Plaintiff alleges that he paid EMS for his ambulance .trip and, as a result of the direct relationship between EMS and Defendants, a portion of his payment was transferred to Defendants. Compl. ¶38; Plaintiff, further alleges that a portion of Defendants’ share of this • payment was supposed to be, but was not, “used ... to pay for the administrative costs of data management and security.” Id. ¶ 70. The only fact differentiating this case, from Resmck is the fact that Plaintiff paid Defendants through EMS, an intermediary. But, the “direct benefit” element of an unjust enrichment claim may be satisfied where a benefit is conferred through an intermediary. In other words, a direct benefit can derive from a transaction with no direct contact. See, e.g., Williams v. Wells Fargo Bank, N.A.,
Plaintiff alleges, that he made a' one-time payment to EMS for its services and, as part and parcel to those services, reasonably expected that his Sensitive Information would remain confidential and protected. Compl. ¶¶ 68-70. ÉMS, in turn, decided to hire and pay Defendants to perform the portion of those services relating to billing and payment processing, which, as alleged, also involved the transmittal of Sensitive Information belonging to Plaintiff and the Class. Id. ¶ 38. Thus, Plaintiff’s single payment directly benefited both EMS and Defendants — even if Defendants received it by way of EMS. See, e.g., Romano v. Motorola, Inc.,
IV. Conclusion
Accordingly, it is ORDERED AND ADJUDGED that Defendant’s Motion to Dismiss, ECF No. [13], is GRANTED IN PART AND DENIED IN PART as follows:
1. Defendants’ Motion is DENIED as to Plaintiffs claim for negligence;
2. Defendants’ Motion is GRANTED as to Plaintiffs claim for breach of fiduciary duty;
3. Defendants’ Motion is DENIED as to Plaintiffs claim for unjust enrichment;
4. Defendants are directed to file an Answer to the Complaint no later than December 4, 2015.
DONE AND ORDERED in Miami, Florida, this 16th day of November, 2015.
. Plaintiff cites to a report published by the National Institute of Standards and Technology detailing standards for healthcare-related service providers to come into compliance with HIPAA’s Security Rule. Id. ¶¶ 32-33. He alleges that this report illustrates Defendants’ failure to "comply with even basic industry standards.” Id. ¶ 34.
. Specifically, Plaintiff alleges damages "including, but not limited to,- expenses and/or time spent on credit monitoring and identity
