TEFCA Security Incident Notice to Affected Individuals. Each Signatory that is an IAS Provider must notify each Individual whose TI has been or is reasonably believed to have been affected by a TEFCA Security Incident involving the IAS Provider. Such notification must be made without unreasonable delay and in no case later than sixty (60) days following Discovery of the TEFCA Security Incident. The notification required under this section must be written in plain language and shall include, to the extent possible:
Appears in 3 contracts
Samples: Common Agreement, Common Agreement, Common Agreement
TEFCA Security Incident Notice to Affected Individuals. Each Signatory that is an IAS Provider must notify each Individual whose TI has been or is reasonably believed to have been affected by a TEFCA Security Incident involving the IAS Provider. Such notification must be made without unreasonable delay and in no case later than sixty (60) days following Discovery of the TEFCA Security Incident. The notification required under this section must be written in plain language and shall include, to the extent possible:
Appears in 1 contract
Samples: ehealthexchange.org
TEFCA Security Incident Notice to Affected Individuals. Each Signatory Participant that is an IAS Provider must notify each Individual whose TI has been or is reasonably believed to have been affected by a TEFCA Security Incident involving the IAS Provider. Such notification must be made without unreasonable delay and in no case later than sixty (60) days following Discovery of the TEFCA Security Incident. The notification required under this section must be written in plain language and shall include, to the extent possible:
Appears in 1 contract
Samples: License Agreement
