For the purposes of this chapter, the term:
(1) "Agreement" means the bargain of the parties in fact, as found in their language or inferred from other circumstances and from rules, regulations, and procedures given the effect of agreements under laws otherwise applicable to a particular transaction.
(2) "Automated transaction" means a transaction conducted or performed, in whole or in part, by electronic means or electronic records, in which the acts or records of one or both parties are not reviewed by an individual in the ordinary course in forming a contract, performing under an existing contract, or fulfilling an obligation required by the transaction.
(3) "Computer program" means a set of statements or instructions to be used directly or indirectly in an information processing system in order to bring about a certain result.
(4) "Contract" means the total legal obligation resulting from the parties' agreement as affected by this chapter and other applicable law.
(5) "Electronic" means relating to technology having electrical, digital, magnetic, wireless, optical, electromagnetic, or similar capabilities.
(6) "Electronic agent" means a computer program or an electronic or other automated means used independently to initiate an action or respond to electronic records or performances in whole or in part, without review or action by an individual.
(7) "Electronic record" means a record created, generated, sent, communicated, received, or stored by electronic means.
(8) "Electronic signature" means an electronic sound, symbol, or process attached to or logically associated with a record and executed or adopted by a person with the intent to sign the record.
(9) "Governmental agency" means an executive, legislative, or judicial agency, department, board, commission, authority, institution, or instrumentality of the federal government or of a State or of a county, municipality, or other political subdivision of a State.
(10) "Information" means data, text, images, sounds, codes, computer programs, software, databases, or the like.
(11) "Information processing system" means an electronic system for creating, generating, sending, receiving, storing, displaying, or processing information.
(12) "Person" means an individual, corporation, business trust, estate, trust, partnership, limited liability company, association, joint venture, governmental agency, public corporation, or any other legal or commercial entity.
(13) "Record" means information that is inscribed on a tangible medium or that is stored in an electronic or other medium and is retrievable in perceivable form.
(14) "Security procedure" means a procedure employed for the purpose of verifying that an electronic signature, record, or performance is that of a specific person or for detecting changes or errors in the information in an electronic record. The term includes a procedure that requires the use of algorithms or other codes, identifying words or numbers, encryption, or callback or other acknowledgment procedures.
(15) "State" means a State of the United States, the District of Columbia, Puerto Rico, the United States Virgin Islands, or any territory or insular possession subject to the jurisdiction of the United States. The term includes an Indian tribe or band, or Alaskan native village, which is recognized by federal law or formally acknowledged by a State.
(16) "Transaction" means an action or set of actions occurring between two or more persons relating to the conduct of business, commercial, or governmental affairs.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
Law 14-28, the "Fiscal Year 2002 Budget Support Act of 2001", was introduced in Council and assigned Bill No. 14-144, which was referred to the Committee Of the Whole. The Bill was adopted on first and second readings on May 1, 2001, and June 5, 2001, respectively. Signed by the Mayor on June 29, 2001, it was assigned Act No. 14-85 and transmitted to both Houses of Congress for its review. D.C. Law 14-28 became effective on October 3, 2001.
For Law 15-105, see notes following § 28-3904.
Miscellaneous Notes
Citywide Email Retention Policy, see Mayor's Order 2007-157, July 5, 2007 (54 DCR 9613).
Citywide Email Retention Policy, see Mayor's Order 2007-207, September 21, 2007 (55 DCR 127).
Rescission of Mayor's Order 2007-157, dated July 5, 2007, on Citywide Email Retention Policy, see Mayor's Order 2007-228, October 15, 2007 (55 DCR 149).
Uniform Law
This section is based upon § 2 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
(a) Except as otherwise provided in subsection (b) of this section, this chapter applies to electronic records and electronic signatures relating to a transaction.
(b) This chapter does not apply to a transaction to the extent it is governed by:
(1) A law governing the creation and execution of wills, codicils, or testamentary trusts; or
(2) Subtitle I of this title, except for §§ 28:1-107 and 28:1-206 and Articles 2 and 2A.
(c) This chapter applies to an electronic record or electronic signature otherwise excluded from the application of this chapter under subsection (b) of this section to the extent it is governed by a law other than those specified in subsection (b) of this section.
(d) A transaction subject to this chapter is also subject to other applicable substantive law.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 3 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
This chapter applies to any electronic record or electronic signature created, generated, sent, communicated, received, or stored on or after [October 3, 2001].
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 4 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
(a) This chapter does not require a record or signature to be created, generated, sent, communicated, received, stored, or otherwise processed or used by electronic means or in electronic form.
(b) This chapter applies only to transactions between parties each of which has agreed to conduct transactions by electronic means. Whether the parties agree to conduct a transaction by electronic means is determined from the context and surrounding circumstances, including the parties' conduct.
(c) A party that agrees to conduct a transaction by electronic means may refuse to conduct other transactions by electronic means. The right granted by this subsection may not be waived by agreement.
(d) Except as otherwise provided in this chapter, the effect of any of its provisions may be varied by agreement. The presence in certain provisions of this chapter of the words "unless otherwise agreed", or words of similar import, does not imply that the effect of other provisions may not be varied by agreement.
(e) Whether an electronic record or electronic signature has legal consequences is determined by this chapter and other applicable law.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 5 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
This chapter must be construed and applied:
(1) To facilitate electronic transactions consistent with other applicable law;
(2) To be consistent with reasonable practices concerning electronic transactions and with the continued expansion of those practices; and
(3) To effectuate its general purpose to make uniform the law with respect to the subject of this chapter among states enacting it.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 6 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
§ 28-4906. Legal recognition of electronic records, electronic signatures, and electronic contracts.
(a) A record or signature may not be denied legal effect or enforceability solely because it is in electronic form.
(b) A contract may not be denied legal effect or enforceability solely because an electronic record was used in its formation.
(c) If a law requires a record to be in writing, an electronic record satisfies the law.
(d) If a law requires a signature, an electronic signature satisfies the law.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 7 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
(a) If parties have agreed to conduct a transaction by electronic means and a law requires a person to provide, send, or deliver information in writing to another person, the requirement is satisfied if the information is provided, sent, or delivered, as the case may be, in an electronic record capable of retention by the recipient at the time of receipt. An electronic record is not capable of retention by the recipient if the sender or its information processing system inhibits the ability of the recipient to print or store the electronic record.
(b) If a law other than this chapter requires a record (1) to be posted or displayed in a certain manner, (2) to be sent, communicated, or transmitted by a specified method, or (3) to contain information that is formatted in a certain manner, the following rules apply:
(A) The record must be posted or displayed in the manner specified in the other law.
(B) Except as otherwise provided in subsection (d)(2) of this section, the record must be sent, communicated, or transmitted by the method specified in the other law.
(C) The record must contain the information formatted in the manner specified in the other law.
(c) If a sender inhibits the ability of a recipient to store or print an electronic record, the electronic record is not enforceable against the recipient.
(d) The requirements of this section may not be varied by agreement, but:
(1) To the extent a law other than this chapter requires information to be provided, sent, or delivered in writing but permits that requirement to be varied by agreement, the requirement under subsection (a) of this section that the information be in the form of an electronic record capable of retention may also be varied by agreement; and
(2) A requirement under a law other than this chapter to send, communicate, or transmit a record by first-class mail, postage prepaid, may be varied by agreement to the extent permitted by the other law.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 8 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
(a) An electronic record or electronic signature is attributable to a person if it was the act of the person. The act of the person may be shown in any manner, including a showing of the efficacy of any security procedure applied to determine the person to which the electronic record or electronic signature was attributable.
(b) The effect of an electronic record or electronic signature attributed to a person under subsection (a) of this section is determined from the context and surrounding circumstances at the time of its creation, execution, or adoption, including the parties' agreement, if any, and otherwise as provided by law.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 9 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
If a change or error in an electronic record occurs in a transmission between parties to a transaction, the following rules apply:
(1) If the parties have agreed to use a security procedure to detect changes or errors and one party has conformed to the procedure, but the other party has not, and the nonconforming party would have detected the change or error had that party also conformed, the conforming party may avoid the effect of the changed or erroneous electronic record.
(2) In an automated transaction involving an individual, the individual may avoid the effect of an electronic record that resulted from an error made by the individual in dealing with the electronic agent of another person if the electronic agent did not provide an opportunity for the prevention or correction of the error and, at the time the individual learns of the error, the individual:
(A) Promptly notifies the other person of the error and that the individual did not intend to be bound by the electronic record received by the other person;
(B) Takes reasonable steps, including steps that conform to the other person's reasonable instructions, to return to the other person or, if instructed by the other person, to destroy the consideration received, if any, as a result of the erroneous electronic record; and
(C) Has not used or received any benefit or value from the consideration, if any, received from the other person.
(3) If neither paragraph (1) of this subsection nor paragraph (2) of this subsection applies, the change or error has the effect provided by other law, including the law of mistake, and the parties' contract, if any.
(4) Paragraphs (2) and (3) of this subsection may not be varied by agreement.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 10 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
If a law requires a signature or record to be notarized, acknowledged, verified, or made under oath, the requirement is satisfied if the electronic signature of the person authorized to perform those acts, together with all other information required to be included by other applicable law, is attached to or logically associated with the signature or record.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 11 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
(a) If a law requires that a record be retained, the requirement is satisfied by retaining an electronic record of the information in the record which:
(1) Accurately reflects the information set forth in the record after it was first generated in its final form as an electronic record or otherwise; and
(2) Remains accessible for later reference.
(b) A requirement to retain a record in accordance with subsection (a) of this section does not apply to any information the sole purpose of which is to enable the record to be sent, communicated, or received.
(c) A person may satisfy subsection (a) of this section by using the services of another person if the requirements of that subsection are satisfied.
(d) If a law requires a record to be presented or retained in its original form, or provides consequences if the record is not presented or retained in its original form, that law is satisfied by an electronic record retained in accordance with subsection (a) of this section.
(e) If a law requires retention of a check, that requirement is satisfied by retention of an electronic record of the information on the front and back of the check in accordance with subsection (a) of this section.
(f) A record retained as an electronic record in accordance with subsection (a) of this section satisfies a law requiring a person to retain a record for evidentiary, audit, or like purposes, unless a law enacted after [October 3, 2001] specifically prohibits the use of an electronic record for the specified purpose.
(g) This section does not preclude a governmental agency of the District of Columbia from specifying additional requirements for the retention of a record subject to the agency's jurisdiction.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 12 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
In a proceeding, evidence of a record or signature may not be excluded solely because it is in electronic form.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 13 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
In an automated transaction, the following rules apply:
(1) A contract may be formed by the interaction of electronic agents of the parties, even if no individual was aware of or reviewed the electronic agents' actions or the resulting terms and agreements.
(2) A contract may be formed by the interaction of an electronic agent and an individual, acting on the individual's own behalf or for another person, including by an interaction in which the individual performs actions that the individual is free to refuse to perform and which the individual knows or has reason to know will cause the electronic agent to complete the transaction or performance.
(3) The terms of the contract are determined by the substantive law applicable to it.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 14 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
(a) Unless otherwise agreed between the sender and the recipient, an electronic record is sent when it:
(1) Is addressed properly or otherwise directed properly to an information processing system that the recipient has designated or uses for the purpose of receiving electronic records or information of the type sent and from which the recipient is able to retrieve the electronic record;
(2) Is in a form capable of being processed by that system; and
(3) Enters an information processing system outside the control of the sender or of a person that sent the electronic record on behalf of the sender or enters a region of the information processing system designated or used by the recipient which is under the control of the recipient.
(b) Unless otherwise agreed between a sender and the recipient, an electronic record is received when:
(1) It enters an information processing system that the recipient has designated or uses for the purpose of receiving electronic records or information of the type sent and from which the recipient is able to retrieve the electronic record; and
(2) It is in a form capable of being processed by that system.
(c) Subsection (b) of this section applies even if the place the information processing system is located is different from the place the electronic record is deemed to be received under subsection (d) of this section.
(d) Unless otherwise expressly provided in the electronic record or agreed between the sender and the recipient, an electronic record is deemed to be sent from the sender's place of business and to be received at the recipient's place of business. For purposes of this subsection, the following rules apply:
(1) If the sender or recipient has more than one place of business, the place of business of that person is the place having the closest relationship to the underlying transaction.
(2) If the sender or the recipient does not have a place of business, the place of business is the sender's or recipient's residence, as the case may be.
(e) An electronic record is received under subsection (b) of this section even if no individual is aware of its receipt.
(f) Receipt of an electronic acknowledgment from an information processing system described in subsection (b) of this section establishes that a record was received but, by itself, does not establish that the content sent corresponds to the content received.
(g) If a person is aware that an electronic record purportedly sent under subsection (a) of this section, or purportedly received under subsection (b) of this section, was not actually sent or received, the legal effect of the sending or receipt is determined by other applicable law. Except to the extent permitted by the other law, the requirements of this subsection may not be varied by agreement.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 15 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
(a) In this section, "transferable record" means an electronic record that:
(1) Would be a note under Article 3 of Subtitle I of this title or a document under Article 7 of Subtitle I of this title if the electronic record were in writing; and
(2) The issuer of the electronic record expressly has agreed is a transferable record.
(b) A person has control of a transferable record if a system employed for evidencing the transfer of interests in the transferable record reliably establishes that person as the person to which the transferable record was issued or transferred.
(c) A system satisfies subsection (b) of this section, and a person is deemed to have control of a transferable record, if the transferable record is created, stored, and assigned in such a manner that:
(1) A single authoritative copy of the transferable record exists which is unique, identifiable, and, except as otherwise provided in paragraphs (4), (5), and (6) of this section, unalterable;
(2) The authoritative copy identifies the person asserting control as:
(A) The person to which the transferable record was issued; or
(B) If the authoritative copy indicates that the transferable record has been transferred, the person to which the transferable record was most recently transferred;
(3) The authoritative copy is communicated to and maintained by the person asserting control or its designated custodian;
(4) Copies or revisions that add or change an identified assignee of the authoritative copy can be made only with the consent of the person asserting control;
(5) Each copy of the authoritative copy and any copy of a copy is readily identifiable as a copy that is not the authoritative copy; and
(6) Any revision of the authoritative copy is readily identifiable as authorized or unauthorized.
(d) Except as otherwise agreed, a person having control of a transferable record is the holder, as defined in § 28:1-201(20), of the transferable record and has the same rights and defenses as a holder of an equivalent record or writing under Subtitle I of this title, including, if the applicable statutory requirements under § 28:3-302(a), § 28:7-501, or § 28:9-308 are satisfied, the rights and defenses of a holder in due course, a holder to which a negotiable document of title has been duly negotiated, or a purchaser, respectively. Delivery, possession, and indorsement are not required to obtain or exercise any of the rights under this subsection.
(e) Except as otherwise agreed, an obligor under a transferable record has the same rights and defenses as an equivalent obligor under equivalent records or writings under Subtitle I of this title.
(f) If requested by a person against which enforcement is sought, the person seeking to enforce the transferable record shall provide reasonable proof that the person is in control of the transferable record. Proof may include access to the authoritative copy of the transferable record and related business records sufficient to review the terms of the transferable record and to establish the identity of the person having control of the transferable record.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 16 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
The Mayor shall determine whether, and the extent to which, a governmental agency will create electronic records and convert written records to electronic records. The retention of electronic records shall conform to the requirements and practices established under Chapter 17 of Title 2 of the District of Columbia Official Code.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881; June 13, 2008, D.C. Law 17-175, § 3, 55 DCR 5387.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
D.C. Law 17-175 rewrote the section which had read as follows:
"The Mayor shall determine whether, and the extent to which, a governmental agency will create and retain electronic records and convert written records to electronic records."
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Law 17-175, the "Electronic Mail Public Record Clarification Amendment Act of 2008", was introduced in Council and assigned Bill No.17-490 which was referred to the Committee on Workforce Development and Government Operations. The Bill was adopted on first and second readings on March 4, 2008, and April 1, 2008, respectively. Signed by the Mayor on April 22, 2008, it was assigned Act No. 17-359 and transmitted to both Houses of Congress for its review. D.C. Law 17- 175 became effective on June 13, 2008.
Uniform Law
This section is based upon § 17 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
(a) Except as otherwise provided in § 28-4911(f), the Mayor shall determine whether, and the extent to which, a governmental agency will send and accept electronic records and electronic signatures to and from other persons and otherwise create, generate, communicate, store, process, use, and rely upon electronic records and electronic signatures.
(b) To the extent that a governmental agency uses electronic records and electronic signatures under subsection (a) of this section, the Mayor, giving due consideration to security, may specify:
(1) The manner and format in which the electronic records must be created, generated, sent, communicated, received, and stored and the systems established for those purposes;
(2) If electronic records must be signed by electronic means, the type of electronic signature required, the manner and format in which the electronic signature must be affixed to the electronic record, and the identity of, or criteria that must be met by, any third party used by a person filing a document to facilitate the process;
(3) Control processes and procedures as appropriate to ensure adequate preservation, disposition, integrity, security, confidentiality, and auditability of electronic records; and
(4) Any other required attributes for electronic records which are specified for corresponding nonelectronic records or reasonably necessary under the circumstances.
(c) Except as otherwise provided in § 28-4911(f), this chapter does not require a governmental agency of the District of Columbia to use or permit the use of electronic records or electronic signatures.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Delegation of Authority
Delegation of Digital Signature Authority to Chief Technology Officer, see Mayor's Order 2005-45, March 3, 2005 (52 DCR 2870).
Delegation of Authority for Acceptance and Distribution of Electronic Records by District Government Agencies, see Mayor's Order 2009-118, June 25, 2009 (56 DCR 6867).
Uniform Law
This section is based upon § 18 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
The Mayor, in adopting standards pursuant to § 28-4917, may encourage and promote consistency and interoperability with similar requirements adopted by other governmental agencies of this and other states and the federal government and nongovernmental persons interacting with governmental agencies of the District of Columbia. If appropriate, those standards may specify differing levels of standards from which governmental agencies of the District of Columbia may choose in implementing the most appropriate standard for a particular application.
(Oct. 3, 2001, D.C. Law 14-28, § 3502(b), 48 DCR 6981; Mar. 13, 2004, D.C. Law 15-105, § 64, 51 DCR 881.)
HISTORICAL AND STATUTORY NOTES
Effect of Amendments
D.C. Law 15-105 validated previously made technical corrections.
Emergency Act Amendments
For temporary (90 day) addition of section, see § 3202(b) of Fiscal Year 2002 Budget Support Emergency Act of 2001 (D.C. Act 14-124, August 3, 2001, 48 DCR 7861).
Legislative History of Laws
For Law 14-28, see notes following § 28-4901.
For Law 15-105, see notes following § 28-3904.
Uniform Law
This section is based upon § 19 of the Uniform Electronic Transactions Act (1999 Act). See 7A, Pt. I, Uniform Laws Annotated, Master Edition, or ULA Database on Westlaw.
Refs & Annos
|
Jurisdiction
|
Laws
|
Effective Date
|
Statutory Citation
|
|
Alabama
|
2001, c. 458
|
1-1-2002
|
Code 1975, §§ 8-1A-1 to 8-1A-20.
|
|
Alaska
|
2004, c. 110
|
7-1-2004
|
AS 09.80.010 to 09.80.195.
|
|
Arizona
|
2000, c. 268
|
7-18-2000
|
A.R.S. §§ 44-7001 to 44-7051.
|
|
Arkansas
|
2001, c. 905
|
A.C.A. §§ 25-32-101 to 25-32-121.
|
|
|
California
|
1999, c. 428
|
1-1-2000
|
West"s Ann.Cal.Civil Code §§ 1633.1 to 1633.17.
|
|
Colorado
|
2002, c. 229
|
5-30-2002
|
West"s C.R.S.A. §§ 24-71.3-101 to 24-71.3-121.
|
|
Connecticut
|
2002, c. 68
|
10-1-2002
|
C.G.S.A. §§ 1-266 to 1-286.
|
|
Delaware
|
2000, c. 457
|
7-14-2000
|
6 Del. C. §§ 12A-101 to 12A-117.
|
|
District of Columbia
|
2001, D.C. Law 14-28
|
10-3-2001
|
D.C. Official Code, 2001 Ed. §§ 28-4901 to 28-4918.
|
|
Florida
|
2000, c. 164
|
7-1-2000
|
West"s F.S.A. § 668.50.
|
|
Georgia
|
2009, c. 141
|
7-1-2009
|
O.C.G.A. §§ 10-12-1 to 10-12-20.
|
|
Hawaii
|
2000, Act 282
|
6-28-2000
|
HRS §§ 489E-1 to 489E-19.
|
|
Idaho
|
2000, c. 286
|
7-1-2000
|
I.C. §§ 28-50-101 to 28-50-120.
|
|
Indiana
|
2000, P.L. 62-2000
|
7-1-2000
|
West"s A.I.C. §§ 26-2-8-101 to 26-2-8-302.
|
|
Iowa
|
2000, c. 1189
|
7-1-2000
|
I.C.A. 554D.101 to 554D.125.
|
|
Kansas
|
2000, c. 120
|
7-1-2000
|
K.S.A. §§ 16-1601 to 16-1620.
|
|
Kentucky
|
2000, c. 301
|
8-1-2000
|
KRS 369.101 to 369.120.
|
|
Louisiana
|
2001, c. 244
|
7-1-2001
|
LSA-R.S. 9:2601 to 9:2620.
|
|
Maine
|
2000, c. 762
|
8-11-2000
|
10 M.R.S.A. §§ 9401 to 9507.
|
|
Maryland
|
2000, c. 8
|
4-25-2000
|
Code, Commercial Law, §§ 21-101 to 21-120.
|
|
Massachusetts
|
2003, c. 133
|
2-24-2004
|
M.G.L.A. c. 110G, §§ 1 to 18.
|
|
Michigan
|
2000, c. 305
|
10-16-2000
|
M.C.L.A. §§ 450.831 to 450.849.
|
|
Minnesota
|
2000, c. 371
|
8-1-2000
|
M.S.A. §§ 325L.01 to 325L.19.
|
|
Mississippi
|
2001, c. 400
|
7-1-2001
|
Code 1972, §§ 75-12-1 to 75-12-39.
|
|
Missouri
|
2003, H.B. No. 254
|
V.A.M.S. §§ 432.200 to 432.295.
|
|
|
Montana
|
2001, c. 52
|
7-1-2001
|
MCA 30-18-101 to 30-18-118.
|
|
Nebraska
|
2000, c. 86
|
7-13-2000
|
R.R.S. 1943, §§ 86-2101 to 86-2116.
|
|
Nevada
|
2001, c. 548
|
NRS 719.010 to 719.350.
|
|
|
New Hampshire
|
2001, c. 265
|
9-11-2001
|
RSA 294-E:1 to 294-E:20.
|
|
New Jersey
|
2001, c. 116
|
6-26-2001
|
N.J.S.A. 12A:12-1 to 12A:12-26.
|
|
New Mexico
|
2001, c. 131
|
7-1-2001
|
NMSA 1978, §§ 14-16-1 to 14-16-19.
|
|
North Carolina
|
2000, c. 152
|
10-1-2000
|
G.S. §§ 66-311 to 66-339.
|
|
North Dakota
|
2001, c. 108
|
8-1-2001
|
NDCC 9-16-01 to 9-16-18.
|
|
Ohio
|
2000, H.B. 488
|
9-14-2000
|
R.C. §§ 1306.01 to 1306.23.
|
|
Oklahoma
|
2000, c. 372
|
11-1-2000
|
12A Okl.St.Ann. §§ 15-101 to 15-121.
|
|
Oregon
|
2001, c. 535
|
ORS 84.001 to 84.061.
|
|
|
Pennsylvania
|
1999, P.L. 971, No. 69
|
1-15-2000
|
73 P.S. §§ 2260.101 to 2260.903.
|
|
Rhode Island
|
2000, c. 00-175
|
7-13-2000
|
§§ 42-127.1-1 to 42-127.1-20.
|
|
South Carolina
|
2004, c. 279
|
7-16-2004
|
Code 1976, §§ 26-6-10 to 26-6-210.
|
|
South Dakota
|
2000, c. 225
|
2-28-2000
|
SDCL 53-12-1 to 53-12-50.
|
|
Tennessee
|
2001, c. 72
|
7-1-2001
|
T.C.A. §§ 47-10-101 to 47-10-123.
|
|
Texas
|
2001, c. 702
|
1-1-2002
|
V.T.C.A., Bus. & C. §§ 322.001 to 322.021.
|
|
Utah
|
2000, c. 74
|
5-1-2000
|
U.C.A 1953, 46-4-101 to 46-4-503.
|
|
Vermont
|
2003, c. 44
|
1-1-2004
|
9 V.S.A. §§ 270 to 290.
|
|
Virgin Islands
|
2003, No. 6634
|
12-23-2003
|
11 V.I.C. 101 to 120.
|
|
Virginia
|
2000, c. 995
|
7-1-2001
|
Code 1950, §§ 59.1-479 to 59.1-497.
|
|
West Virginia
|
2001, c. 120
|
7-13-2001
|
Code, 39A-1-1 to 39A-1-17.
|
|
Wisconsin
|
2003, c. 294
|
5-5-2004
|
W.S.A. 137.01 to 137.26.
|
|
Wyoming
|
2001, c. 58
|
7-1-2001
|
Wyo.Stat.Ann. §§ 40-21-101 to 40-21-119.
|
[FN*] Date of approval.
