System Requirements Specification
System Requirements Specification
CDLIS Modernization
Last Updated: June 29, 2010
Final Version: 1.2
Revision History
|Date |Version |Description |
|5/21/2010 |v.01 |First draft of the document distributed to the SEMT and|
| | |other designated reviewers |
|6/4/2010 |v1.0 |Version of the document with suggested changes |
| | |incorporated following the 6/2 document review meeting |
|6/14/2010 |v1.1 |Version of the document including suggested changes by |
| | |the SEMT and changes identified during the first to-be |
| | |process mapping session (6/8) |
|6/29/2010 |v1.2 |Version of the document including suggested changes by |
| | |the SEMT and changes identified during the review of |
| | |the requirements traceability matrix. |
| | | |
Table of Contents
1. Introduction 5
1.1 Purpose 5
1.2 Scope 6
1.2.1 In Scope 6
1.2.2 Out of Scope 6
1.3 Definitions, Acronyms, and Abbreviations 7
1.4 References 11
2. Overall Description 11
2.1 Medical Certification Requirements Overview 11
2.2 CDLIS Release 5.1 Modernization Requirements Overview 13
2.3 Transaction and Message Overview 17
2.4 Constraints 27
2.5 Assumptions 27
2.6 Detail Change Tracking 27
3. Specific Requirements 28
3.1 CDLIS Release 5.1 Medical Certification 30
3.1.1 Self-Certification 30
3.1.2 Medical Certificates 32
3.1.3 Variances 34
3.1.4 Licensing Transactions 36
3.1.5 Downgrades 39
3.1.6 Restrictions 40
3.1.7 Driver Information 41
3.1.8 Electronic Document Storage and Management 44
3.1.9 Correspondence 45
3.1.10 CDLIS Release 5.1 Medical Certification Transactions 46
3.2 CDLIS Release 5.1 Modernization 54
3.2.1 Architectural Changes 54
3.2.2 Name Expansion 62
3.2.3 Backward Compatibility – Name Expansion 84
3.2.4 Backward Compatibility – Sex Field 92
3.2.5 Backward Compatibility – Partial SSN 97
3.2.6 Change State of Record (CSOR) 99
3.2.7 Data Cleanup 106
4. Detail Change Tracking Log 108
5. Final System Requirements Specification Approval 110
6. Appendix A –Data Dictionary 112
6.1 Medical Certificate 112
6.2 CDLIS Modernization 118
7. Appendix B – New Data Elements by Message Type 135
7.1 Medical Fields 136
7.1.1 Medical Fields 137
7.2 Modernization Fields 138
7.2.1 Person Name Group(BPENGP) Fields 138
7.2.2 Person Old Name Group (BPENG1) Fields 140
7.2.3 Person Duplicate Name Group (BPENG2) Fields 141
7.2.4 Person Name Group (BPENGP) – Person Old Name Group (BPENG1) Fields 142
7.2.5 Person Name Group (BPENGP) –Person Old Name Group (BPENG1) – Person AKA Name Group (BPENG3) Fields 143
7.2.6 Person Name Group (BPENGP) – Person AKA Name Group (BPENG3) Fields 144
7.2.7 Person Old Name Group (BPENG1) – Person AKA Name Group (BPENG3) Fields 145
7.2.8 Person Name Group (BPENGP) – Person Duplicate Name Group (BPENG2) Fields 146
7.2.9 Validation Control Name Fields 147
7.2.10 Architectural Current Fields 148
7.2.11 Architectural Current-Duplicate-AKA SSN Count Fields 150
7.2.12 Architectural AKA DOB Fields 151
7.2.13 Architectural AKA SSN – AKA SSN Count Fields 151
7.2.14 Architectural AKA SSN Count Field 152
7.2.15 Architectural Sex Field 153
7.2.16 Architectural Duplicate Sex Field 154
7.2.17 On-Demand Re-Drive 155
7.2.18 Backward Compatibility – Partial SSN – Old SSN 156
7.2.19 Backward Compatibility – Partial SSN – Duplicate SSN 156
7.2.20 Backward Compatibility – Partial SSN - SSN 156
8. Appendix C – CDLIS Transaction Diagrams 158
8.1 CD01 Search Inquiry 158
8.2 CD02 Verification Inquiry 159
8.3 CD03 State-to-State Status Request 160
8.4 CD04 State-to-State History Request 161
8.5 CD05 AKA Data Inquiry 162
8.6 CD07 Add New Driver 163
8.7 CD08 Change State of Record 164
8.8 CD08 On Demand Re-Drive 165
8.9 CD08 Automated Re-Drive 166
8.10 CD09 Change Data 167
8.11 CD10 Delete Master Pointer Record 168
8.12 CD11 Report Out-of-State Convictions 169
8.13 CD12 Negate Out-of-State Convictions 170
8.14 CD14 Mark Driver Unique 171
8.15 CD15 Update AKA Data 172
8.16 CD16 Report Out-of-State Withdrawal 173
8.17 CD17 Negate Out-of-State Withdrawal 174
8.18 CDA1 Duplicate Driver 175
8.19 CD30 CDLIS Batch Inquiry 176
8.20 CD31 MPR Data Validation and Verification Process 177
9. Appendix D – Person Name Formatting 178
System Requirements Specification
Introduction
The Commercial Driver’s License Information System (CDLIS), established under the Commercial Motor Vehicle Safety Act (CMVSA) of 1986, is the nation-wide computer system that enables State Driver Licensing Agencies (SDLAs) to ensure that each commercial driver has only one driver’s license and that the State of Record (SOR) has the driver’s complete driver record. CDLIS is based on the Federal Motor Carrier Safety Regulations (FMCSRs) in 49 CFR 383 and 384. The SDLAs use CDLIS to complete various procedures, including transmitting out-of-state convictions and withdrawals, transferring the driver record when a CDL holder moves to another state, and responding to requests for driver status and history.
Changes in federal law have recently required changes to the CDLIS system, and new system specifications have been released by the operator of CDLIS, the American Association of Motor Vehicle Administrators (AAMVA). All state jurisdictions must develop and implement the required changes by January 30, 2012.
CDLIS Release 5.1 changes include the following areas:
• CDL Medical Certification
o Driver Self-Certification of Driving Type
o Collection of Medical Examiner’s Certificate Information
o Check of Medical Certification Status (impacts initial, renewal, upgrade, and transfer licensing transactions)
• CDLIS Modernization
o Name Expansion
o Modifications to CSOR Processing
o Architectural Changes
▪ Upgrade from current version of UNI to new version that supports CDLIS 5.1
▪ Removal of fields from the Master Pointer Record and Driver History Record stored at the CDLIS Central Site
▪ Backward compatibility during the transition period
o Data cleanup as required in CDLIS Release 5.1 specifications to synchronize data between PennDOT and the Central Site
In February 2010, PennDOT initiated the CDLIS Modernization Requirements Study in order to identify and document the business and system requirements necessary to comply with the Final Rule and other specification documents published by AAMVA (the operator of CDLIS). The business analysis team reviewed the applicable source documents (refer to the section entitled “References”) and drafted the system requirement statements included in this document.
1 Purpose
The purpose of this document is to record the system requirements necessary to successfully implement CDLIS Release 5.1. The system requirements include changes that PennDOT will need to make to existing system processes that are needed to support the CDLIS Release 5.1 implementation. In most cases, the system requirements will be further supported by business process changes (please refer to the CDLIS Modernization Business Requirements Specification document for further information related to business requirements). The relationships between the business requirements and the system requirements will be documented using the IBM Rational Requisite Pro tool.
2 Scope
1 In Scope
The system requirements contained in this document describe PennDOT’s responsibilities related to the following areas:
Medical Certification
• Requesting, collecting, and reporting a driver’s self-certification status
• Requesting, collecting, and reporting the information provided on a driver’s medical examiner’s certificate and medical variance documents (if applicable)
• Verifying a driver’s medical examiner’s certificate prior to issuing a CDL (new issuance, renewal, upgrade, or transfer)
• Notifications communicated to drivers related to the self-certification and medical certificate requirements
• Processing of medical variances, downgrades, and new license restrictions
CDLIS Modernization
• Ensuring that PennDOT is sending driver and medical examiner names in the new format
• Ensuring that PennDOT is able to receive messages from CDLIS that no longer include personal information about the driver (i.e. height, weight, sex, etc.).
• Ensuring that PennDOT complies with the new backward compatibility rules
• Participation in the new quality validation procedures instituted by CDLIS
• Ensuring that PennDOT is able to send and receive the new messages that are part of the Change State of Record transaction.
2 Out of Scope
This document does not include specific requirements related to business process changes. All business requirements are contained in a separate document that can be found on the CDLIS Modernization PCS. In addition, this document does not contain system requirements documenting PennDOT’s existing CDL processes (e.g. driver checks against PDPS, reporting of commercial driver convictions and withdrawals, etc.).
The following system requirement categories will be documented in the CDLIS Modernization Supplementary Requirements Specification:
• Business rules related to how the DL&C system will calculate a driver’s medical certification status (i.e. “certified” vs. “not certified”)
• Interface requirements related to the CLEAN interface with JNET
• Reporting Requirements
• Performance Requirements (i.e. the CDLIS transaction processing time thresholds)
• Data Conversion Requirements (i.e. requirements specifying the conversion of customer name for all types of customers – commercial, non-commercial, and non-drivers)
3 Definitions, Acronyms, and Abbreviations
|Term |Acronym/ |Definition |
| |Abbreviation | |
|American Association of Motor Vehicle |AAMVA |Non-governmental, private corporation which strives to develop model |
|Administrators | |programs in motor vehicle administration, police traffic services, and |
| | |highway safety |
|Commercial Driver’s License |CDL |A license issued by a State or other jurisdiction, in accordance with |
| | |the standards contained in 49 CFR parts 383 and 384, to an individual |
| | |which authorizes the individual to operate a class of a commercial motor|
| | |vehicle. |
|Commercial Driver’s License Information System |CDLIS |Information system maintained and operated by AAMVA in which nation-wide|
| | |commercial driver’s license information is captured, stored and provided|
| | |to other entities. |
|CDLIS Release 5.1 |N/A |Updated version of the CDLIS system that will support the exchange of |
| | |medical certification information between jurisdictions as well as other|
| | |enhancements (i.e. new name format, new messages, etc.) |
|Code of Federal Regulations |CFR |The Code of Federal Regulations (CFR) is the codification of the general|
| | |and permanent rules published in the Federal Register by the executive |
| | |departments and agencies of the Federal Government. |
|Commercial Motor Vehicle |CMV |Vehicle used for interstate or intrastate commerce |
|Commercial Motor Vehicle Safety Act |CMVSA |The Commercial Motor Vehicle Safety Act of 1986 established national |
| | |minimum testing and licensing standards for operators of large trucks |
| | |and buses. |
|Change State of Record |CSOR |Transaction in which the state of record is transferred from one |
| | |jurisdiction to another jurisdiction |
|Common Validation Process |CVP |This process provided by AAMVA ensures consistent edits on convictions, |
| | |withdrawals, and conviction-withdrawal linkages on driver histories. |
| | |This assists in reducing the number of CSOR transactions in suspense. |
|Driver Licensing and Control |DL&C |PennDOT system which processes driver licensing applications and |
| | |sanction notifications |
|Department of Transportation |DOT |United States Government entity responsible for ensuring that the U.S. |
| | |transportation system is fast, safe, efficient, accessible and |
| | |convenient |
|Electronic Document Management System |EDMS |PennDOT system in which electronic versions of scanned documents are |
| | |stored |
|Exemption |N/A |Temporary regulatory relief from one or more of the FMCSRs given to a |
| | |person or class of persons subject to the regulations. An exemption |
| | |provides the person with relief from the regulation for up to two years.|
|Term |Acronym/ |Definition |
| |Abbreviation | |
|Federal Motor Carrier Safety Administration |FMCSA |Federal agency responsible for ensuring safety in motor carrier |
| | |operations through strong enforcement of safety regulations, targeting |
| | |high-risk carriers and commercial motor vehicle drivers; improving |
| | |safety information systems and commercial motor vehicle technologies; |
| | |strengthening commercial motor vehicle equipment and operating |
| | |standards; and increasing safety awareness. |
|Federal Motor Carrier Safety Regulation |FMCSR |The Federal Motor Carrier Safety Regulations are established by the |
| | |FMCSA (Federal Motor Carrier Safety Administration). These regulations |
| | |are dedicated to improving the safety of commercial motor vehicles. |
|Information Systems Governance |ISG |PennDOT group within the Office of Information Systems that assists with|
| | |project procurements and strategic planning |
|Master Pointer Record |MPR |Information stored on the CDLIS Central File pertaining to all |
| | |commercial drivers. The file also stores information pertaining to all |
| | |noncommercial drivers convicted of violations while operating a |
| | |commercial motor vehicle |
|Medical Certification Information |N/A |The sum of all the information provided by a commercial driver that |
| | |supports the determination of his/her medical certification status (i.e.|
| | |medical examiner’s certificate information and medical variance |
| | |information) |
|Medical Certification Status |N/A |An indication of the status of a driver’s medical certification based on|
| | |an evaluation of the medical certification information and the medical |
| | |variance information. The driver is determined to be either “certified”|
| | |or “not certified”. |
|Medical Examiner |ME |Medical practitioner who performs commercial driver medical |
| | |examinations. Medical examiners determine a driver’s medical fitness for|
| | |duty which is a critical element of the FMCSA safety program. |
|Medical Examiner’s Certificate |MEC |The form (certificate) an ME completes when he/she finds that a driver |
| | |examined is medically qualified to operate a commercial motor vehicle |
| | |(CMV) in accordance with 49 CFR 391.41(b) |
|Medical Variance Information |N/A |Information related to a waiver, exemption letter, or skill performance |
| | |evaluation certificate that qualifies a driver to obtain a medical |
| | |examiner’s certificate. All three documents are issued by the FMCSA per|
| | |their regulation. |
|Motor Vehicle Record |MVR |The report of the driving status and history of a driver generated from |
| | |the driver record, provided to users, such as, drivers or employers, and|
| | |subject to the provisions of the Driver Privacy Protection Act, 18 |
| | |U.S.C. 2721–2725 |
|Term |Acronym/ |Definition |
| |Abbreviation | |
|Project Collaboration System |PCS |PennDOT system in which project documents are stored and shared with |
| | |project team members |
|Problem Driver Pointer System |PDPS |The PDPS is used to search the National Driver Register (NDR). This is a|
| | |repository of information on problem drivers provided by all 51 U.S. |
| | |jurisdictions. |
|Self-certification Type |N/A |A driver’s self-certification pertaining to the type of driving he/she |
| | |intends to perform. Valid values are excepted intrastate, excepted |
| | |interstate, non-excepted intrastate, and non-excepted interstate. |
|State Driver’s Licensing Agencies |SDLA |Any jurisdiction which issues driver licenses |
|Study Execution Management Team |SEMT |The business leads and IT leads assigned to the study initiative |
|Study Execution Team |SET |The team members (other than the SEMT) assigned to the study initiative |
|State of Record |SOR |The jurisdiction who currently holds the CDL pointer for a driver on the|
| | |CDLIS Central Site |
|Skill Performance Evaluation |SPE |Evaluation performed by the applicable FMCSA field service center in |
| | |order to determine if a commercial driver is capable of safe driving |
| | |despite a physical issue such as the loss of foot, leg, hand or arm. |
|Skill Performance Evaluation Certificate |SPEC |The SPE certificate allows the SPE applicant to operate commercial motor|
| | |vehicles in interstate commerce. |
|Unified Network Interface |UNI |The UNI product resides on a site's host and fills an "interface" role |
| | |between a site's application system and the telecommunications network |
| | |(AAMVA). |
|United States Code |U.S.C. |A consolidation and codification by subject matter of the general and |
| | |permanent laws of the United States that is prepared and published by a |
| | |unit of the United States House of Representatives |
|Waiver |N/A |Temporary regulatory relief from one or more of the FMCSRs given to a |
| | |person subject to the regulations. A waiver provides the person with |
| | |relief from the regulation for up to three months. |
|Waiver/Exemption Type |N/A |Indication provided on the MEC by the medical examiner as to the type of|
| | |waiver or exemption that has been granted by the FMCSA. Valid values |
| | |are diabetes or vision. |
4 References
|Document Title |Abbreviation |Author/Publisher |Location |
|(including version and release date) | | | |
|Federal Register, Part VII, DOJ, 49 CFR Parts 383, |FR |DOJ |CDLIS Modernization PCS; Federal |
|384, 390, and 391 Medical Certification Requirements| | |Regulations folder |
|as Part of the CDL, National Registry of Certified | | | |
|Medical Examiners, CDLIS Final Rule, December 1, | | | |
|2008 | | | |
|CDLIS State Procedures Manual, Release 5.1.0, |SPM |AAMVA |CDLIS Modernization PCS, Federal Docs |
|February 2010 | | |folder |
|CDLIS Master Specifications Document, Release 5.1.0,|MSD |AAMVA |CDLIS Modernization; Federal Docs folder |
|January 2010 | | | |
Overall Description
The system requirements are presented in a table layout with the following columns – ID (unique identifier for the requirement statement), Requirement Statement, Source (link to the reference document form which the requirement was elicited during the requirement identification sessions).
The system requirements cover a wide range of areas impacted by both the medical certificate requirements specified in the Federal Register dated 12/1/2008 and the new version of CDLIS (Release 5.1) that includes changes to CDLIS transactions and messages. Sections “2.1 Medical Certification Requirements Overview” and “2.2 CDLIS Release 5.1 Modernization Requirements Overview” outline what types of requirements are presented in this document.
1 Medical Certification Requirements Overview
|Section |Contents |
|Self-Certification |Requirements related to system changes necessary to support the collection of commercial |
| |driver’s self-certification types (i.e. non-excepted interstate, non-excepted intrastate, |
| |excepted interstate, and excepted intrastate). |
|Medical Certificates |Requirements related to system changes necessary to support the collection and maintenance of|
| |a commercial driver’s medical certificate information. This section also includes the system|
| |changes necessary to ensure that PennDOT collects medical certification information from |
| |existing CDL holders prior to 1/30/2014. |
|Variances |Requirements related to system changes necessary to support the collection and maintenance of|
| |a commercial driver’s medical variance information. |
|Licensing Transactions |Requirements related to system changes necessary to ensure that PennDOT verifies a commercial|
| |driver’s medical certification status prior to issuing, renewing, upgrading, or transferring |
| |a commercial license to a driver. |
|Downgrades |Requirements related to system changes necessary to support the process of downgrading a |
| |commercial driver if he/she does not comply with the self-certification, medical certificate,|
| |and/or medical variance requirements. |
|Section |Contents |
|Restrictions |Requirements related to system changes necessary to support adding and removing the “V” |
| |(variance) commercial driver licensing restriction to a driver’s license. |
|Driver Information, Electronic Data Storage and |Requirements related to system generated customer correspondence necessary to support the |
|Management, and Correspondence |other system requirements in the medical certification section. This section also includes |
| |the system requirements related to supplying self-certification, medical examiner’s |
| |certificate, and medical variance information to requestors (i.e. Pennsylvania drivers, motor|
| |carriers, perspective motor carriers, etc.). |
|CDLIS Release 5.1 Medical Certification |Requirements related to the CDLIS Release 5.1 transactions and messages that include |
|Transactions |self-certification, medical examiner’s certificate, and medical variance information. The |
| |system requirements include two scenarios – 1) PennDOT is the State of Inquiry (SOI) and 2) |
| |PennDOT is the SOR (State of Record). |
3 CDLIS Release 5.1 Modernization Requirements Overview
|Section |Contents |
|Architectural Changes |Requirements related to data fields no longer being stored at the CDLIS Central Site. The |
| |system requirements specify which transactions and messages that are impacted by the change |
| |at the CDLIS Central Site. The system requirements include two scenarios – 1) PennDOT is the|
| |State of Inquiry (SOI) and 2) PennDOT is the SOR (State of Record). |
|Name Expansion |Requirements related to the new name format required by CDLIS after PennDOT implements CDLIS |
| |Release 5.1. The system requirements specify which transactions and messages must include |
| |the new name format. The system requirements include two scenarios – 1) PennDOT is the State|
| |of Inquiry (SOI) and 2) PennDOT is the SOR (State of Record). |
|Backward Compatibility – Name Expansion |Requirements related to the format and content of messages specific to the message |
| |originator’s CDLIS release (i.e. version 4.1 or version 5.1). This section includes the |
| |backward compatibility requirements related to the new name format. |
|Backward Compatibility – Sex Field |Requirements related to the format and content of messages specific to the message |
| |originator’s CDLIS release (i.e. version 4.1 or version 5.1). This section includes the |
| |backward compatibility requirements related to the sex field. |
|Backward Compatibility – Partial SSN |Requirements related to the format and content of messages specific to the message |
| |originator’s CDLIS release (i.e. version 4.1 or version 5.1). This section includes the |
| |backward compatibility requirements related to the partial SSN field. |
|Change State of Record (CSOR) |Requirements related to the new On Demand Re-drive and Automated Re-drive functionality |
| |supported by CDLIS. The system requirements include two scenarios – 1) PennDOT is the State |
| |of Inquiry (SOI) and 2) PennDOT is the SOR (State of Record). |
|Section |Contents |
|Data Cleanup |Requirements related to the Master Pointer Record (MPR) Data Quality Validation and |
| |Verification process supported by CDLIS. The system requirements include the date elements |
| |that PennDOT will be sending to the CDLIS Central Site as part of this process. |
4 Transaction and Message Overview
The table below lists the transactions and messages impacted by both the medical certificate requirements and the CDLIS Release 5.1 changes. The table includes the transaction name, transaction description, transaction messages, and the category describing the type of change that impacts applicable messages (i.e. medical certificate, architectural changes, name change, backward compatibility, change state of record, and data cleanup).
|Transaction |
In reviewing the system requirements related to message type/transactions, it is helpful to concurrently view the applicable CDLIS Transaction Diagram found in Section 8, Appendix C, of this document.
|[pic] |
5 CDLIS Release 5.1 Medical Certification
1 Self-Certification
|ID |Requirement Statement |Source |
|3.1.1.1 |The DL&C system will provide users the capability to enter a driver’s self-certification type as NI |SPM; Pg. 114 |
| |(non-excepted interstate), EI (excepted interstate), NA (non-excepted intrastate), or EA (excepted | |
| |intrastate). | |
| |Users who access Conversation 95 (EDV) and enter the business action code of “CMP” Commercial |May 5th Mtg. Minutes, Pg. |
| |License KTA/Learner’s Permit Issuance will have the capability to enter a driver’s |2 |
| |self-certification type. | |
| |Users who access Conversation 95 (EDV) and enter the business action code of “CLE” Commercial |May 5th Mtg. Minutes, Pg. |
| |Learner’s Permit Extension/Duplicate will have the capability to enter a driver’s self-certification|2 |
| |type. | |
| |Users who access Conversation 95 (EDV) and enter the business action code of “CMI” Commercial |May 5th Mtg. Minutes, Pg. |
| |License Issuance will have the capability to enter a driver’s self-certification type. |2 |
| |Users who access Conversation 95 (EDV) and enter the business action code of “CMO” CDL Advance |May 5th Mtg. Minutes, Pg. |
| |Issuance will have the capability to enter a driver’s self-certification type. |2 |
| |Users who access Conversation 95 (EDV) and enter the business action code of “EXM” Exam Posting will|May 5th Mtg. Minutes, Pg. |
| |have the capability to enter a driver’s self-certification type. |2 |
| |Users who access Conversation 95 (EDV) and enter the business action code of “SBE” School Bus |May 5th Mtg. Minutes, Pg. |
| |Endorsement will have the capability to enter a driver’s self-certification type. |2 |
| |Users who access Conversation 95 (EDV) and enter the business action code of “CMD” Commercial |May 5th Mtg. Minutes, Pg. |
| |License Duplicate will have the capability to enter a driver’s self-certification type. |2 |
| |Users who access Conversation 95 (EDV) and enter the business action code of “RCL” Replace |May 5th Mtg. Minutes, Pg. |
| |Commercial License (Fee Waiver) will have the capability to enter a driver’s self-certification |2 |
| |type. | |
| |Users who access Conversation 95 (EDV) and enter the business action code of “CMR” Commercial |May 5th Mtg. Minutes, Pg. |
| |License Renewal will have the capability to enter a driver’s self-certification type. |2 |
| |Users who access Conversation 12 (Counter Application) will have the capability to enter a driver’s |May 5th Mtg. Minutes, Pg. |
| |self-certification type. |2 |
| |Users who access Conversation 13 (Counter Maintenance) will have the capability to enter a driver’s |May 5th Mtg. Minutes, Pg. |
| |self-certification type. |2 |
| |Users who access Conversation 16 (Mail Maintenance Application) will have the capability to enter a |May 5th Mtg. Minutes, Pg. |
| |driver’s self-certification type. |2 |
| |Users who access Conversation 18 (Mail Application) will have the capability to enter a driver’s |May 5th Mtg. Minutes, Pg. |
| |self-certification type. |2 |
|ID |Requirement Statement |Source |
| |Users who access Conversation 29 (Driver Exam Results, Counter) will have the capability to enter a |May 5th Mtg. Minutes, Pg. |
| |driver’s self-certification type. |2 |
| |Users who access Conversation 30 (Driver Exam Results, Mail) will have the capability to enter a |May 5th Mtg. Minutes, Pg. |
| |driver’s self-certification type. |2 |
| |Users who access Conversation 95 and enter a new business action code (to be defined) will have the |June 8th, To-Be Process |
| |capability to enter a driver’s self-certification type. |Mapping |
|3.1.1.2 |On or after January 30th, 2012, if a driver’s self-certification type is not entered, the DL&C |May 5th Mtg. Minutes, Pg. |
| |system will prevent a new issuance of a commercial driver’s license product (includes new issuances |2 |
| |and upgrades). | |
|3.1.1.3 |When a DL&C User enters a self-certification type of “EA” or EI”, the DL&C system will set the |May 4th Mtg. Minutes |
| |driver’s medical certification status to “certified”. | |
|3.1.1.4 |On January 30th, 2014, the DL&C system will run a one-time nightly batch process to update the |April 15th Meeting Minutes|
| |medical certification status as “not certified” for all commercial drivers whose self-certification | |
| |driving type is set to “blank”. | |
|3.1.1.5 |On a nightly basis, the DL&C system will evaluate the self-certification type of driving fields to |May 4th Mtg. Minutes |
| |determine a driver’s medical certification status. | |
| |If the driver’s self-certification status is “EA” or “EI”, the DL&C system will retain the driver’s |May 4th Mtg. Minutes |
| |medical certification status as “certified”. | |
| |If the driver’s self-certification status is “NA” or “NI”, the DL&C system will evaluate the date |May 4th Mtg. Minutes |
| |fields associated to the driver’s medical certificate and medical variance information (refer to | |
| |requirement 3.1.5.1). | |
|3.1.1.6 |On or after January 30th, 2014, if a driver’s self-certification type is not entered, the DL&C |SEMT Review of |
| |system will prevent a re-issuance of a commercial driver’s license product (includes renewals, |Traceability Matrix |
| |duplicates, and replacements). | |
2 Medical Certificates
Assumption: Medical examiner’s certificates will be required for the following self-certification types: 1) non-excepted interstate and 2) non-excepted intrastate.
|ID |Requirement Statement |Source |
|3.1.2.1 |The DL&C system, via Conversation 95, will provide users the capability to enter the required |FR 383.73;SPM; Pg. 108-115|
| |data elements from a driver’s medical examiner’s certificate. | |
| |The user will enter the Medical Examiner’s Name (as per CDLIS name expansion requirements). |FR 383.73; SPM; Pg. |
| | |108-115 |
| |The user will enter the Medical Examiner’s Telephone Number. |FR 383.73; SPM; Pg. |
| | |108-115 |
|ID |Requirement Statement |Source |
| |The user will enter the Medical Examiner’s Specialty including – Advanced Practice Nurse, |SPM; Pg. 108-115 |
| |Chiropractor, Osteopathic Doctor, Medical Doctor, or Physician Assistant. | |
| |The user will enter the Issue Date of the Medical Certificate. |FR 383.73; SPM; Pg. |
| | |108-115 |
| |The user will enter the Expiration Date of the Medical Certificate. |FR 383.73; SPM; Pg. |
| | |108-115 |
| |The user will enter the Medical Examiner’s License Number. |FR 383.73; SPM; Pg. |
| | |108-115 |
| |The user will enter the Medical Licensing Jurisdiction Code. |FR 383.73; SPM; Pg. |
| | |108-115 |
| |The user will enter the Medical Examiner’s Certificate Restriction(s) including – 1) wearing |FR 383.73; MSD 5.1; pg 86 |
| |corrective lenses, 2) wearing hearing aid, 3) accompanied by a waiver/exemption, 4) driving | |
| |within an exempt intra city zone, 5) accompanied by a Skill Performance Evaluation Certificate | |
| |(SPEC), and 6) qualified by operation of 49 CFR 391.64. | |
| |If a user enters a restriction of 3 (accompanied by a waiver/exemption), the user will be |May 5th Mtg. Minutes, Pg. |
| |prompted to indicate the Waiver/Exemption Type as Vision or Diabetes. |6 |
|3.1.2.2 |The DL&C system will calculate and store the Medical Certification Status as “certified” or “not |FR 383.73; SPM; Pg. |
| |certified” (refer to the CDLIS Modernization Supplementary Requirements Specification for the |108-115 |
| |business rules related to calculating a driver’s medical certification status). | |
|3.1.2.3 |The Medical Examiner’s National Registry Number field will be created on the DL&C database for |FR 383.73 |
| |future use. | |
| |Note: Although this field will not be populated by the user initially, the Medical Examiner’s | |
| |National Registry Number will be sent to CDLIS on the CD01, CD02, CD03, CD04, CD05, and CD08 | |
| |transactions. | |
|3.1.2.4 |The DL&C system will calculate and store the date the medical examiner’s certificate information |FR 383.73; MSD 5.1; pg 86 |
| |was posted to the DL&C system. | |
|3.1.2.5 |The DL&C system will store the two most recent entries of a driver’s medical examiner’s |May 5th Mtg. Minutes, Page|
| |certificate information (refer to requirement 3.1.2.1 for a list of date elements). |3 |
3 Variances
|ID |Requirement Statement |Source |
|3.1.3.1 |The DL&C system, via Conversation 95, will provide users the capability to enter the required data |FR 383.73; SPM; Pg. 108-115|
| |elements from a driver’s medical variance issued by FMCSA. | |
| |Users will have the ability to enter the Driver SPEC Effective Date. |SPM; Pg. 108-115 |
| |Users will have the ability to enter the Driver SPEC Expiration Date. |SPM; Pg. 108-115 |
|ID |Requirement Statement |Source |
| |Users will have the ability to enter the Driver Waiver/Exempt Effective Date. |SPM; Pg. 108-115 |
| |Users will have the ability to enter the Driver Waiver/Exempt Expiration Date. |SPM; Pg. 108-115 |
| |Users will have the ability to enter the Waiver/Exempt type as Vision or Diabetes. |SPM; Pg. 108-115 |
|3.1.3.2 |If the Driver SPEC Effective Date and the Driver SPEC Expiration Date fields are populated, the DL&C|May 5th Mtg. Minutes, Pg. |
| |system will allow entry in the Driver SPEC Rescind Date field. |3 |
|3.1.3.3 |If the Driver Waiver/Exempt Effective Date and the Driver Waiver/Exempt Expiration Date fields are |May 5th Mtg. Minutes, Pg. |
| |populated, the DL&C system will allow entry in the Driver Waiver/Exempt Rescind Date field. |2 |
4 Licensing Transactions
Assumption: The Counter/DLE staff will examine the medical examiner’s certificate and any variance documentation supplied by the customer prior to processing the application. If the proper documentation is not submitted, they will not proceed with processing the application. The DL&C system will verify a driver’s medical certification status if MEC, SPEC, and/or Waiver/Exemption information has been entered by APDEX on a prior occasion.
|ID |Requirement Statement |Source |
|3.1.4.1 |Before issuing a new CDL to a driver who self-certifies as non-excepted interstate/intrastate, if |SPM; Pg. 92 |
| |MEC/variance information exists for the driver, the DL&C System will verify that the driver’s | |
| |medical certification status is set to “Certified” (refer to the Business Rules in the Supplementary| |
| |Requirements Specification for the requirements surrounding verifying and setting the medical | |
| |certification status field). | |
| |If the driver’s medical certification status is verified as “certified”, the DL&C Counter Mode |SPM; Pg. 92 |
| |transaction will process successfully (pending the outcome of other system verifications). | |
| |If the driver’s medical certification status is verified as “not certified”, the DL&C Counter Mode |SPM; Pg. 92 |
| |transaction will be stopped and an error message will be displayed for the user. | |
|3.1.4.2 |Before renewing a CDL to a driver who self-certifies as non-excepted interstate/intrastate, if |SPM; Pg. 92 |
| |MEC/variance information exists for the driver, the DL&C System will verify that the driver’s | |
| |medical certification status is set to “Certified”. | |
| |If the driver’s medical certification status is verified as “certified”, the DL&C Mail Mode |SPM; Pg. 92 |
| |transaction will process successfully (pending the outcome of other system verifications). | |
| |If the driver’s medical certification status is verified as “not certified”, the DL&C Mail Mode |SPM; Pg. 92 |
| |transaction will be suspended and a rejection letter will be generated for the driver. | |
|ID |Requirement Statement |Source |
| |If the driver’s medical certification status is verified as “certified”, the DL&C Counter Mode |SPM; Pg. 92 |
| |transaction will process successfully (pending the outcome of other system verifications). | |
| |If the driver’s medical certification status is verified as “not certified”, the DL&C Counter Mode |SPM; Pg. 92 |
| |transaction will be stopped and an error message will be displayed for the user. | |
|3.1.4.3 |Before upgrading a CDL to a driver who self-certifies as non-excepted interstate/intrastate, if |SPM; Pg. 92 |
| |MEC/variance information exists for the driver, the DL&C System will verify that the driver’s | |
| |medical certification status is set to “Certified”. | |
| |If the driver’s medical certification status is verified as “certified”, the DL&C Counter Mode |SPM; Pg. 92 |
| |transaction will process successfully (pending the outcome of other system verifications). | |
| |If the driver’s medical certification status is verified as “not certified”, the DL&C Counter Mode |SPM; Pg. 92 |
| |transaction will be stopped and an error message will be displayed for the user. | |
|3.1.4.4 |Before transferring a CDL issued by another state to a driver who self-certifies as non-excepted |SPM; Pg. 92 |
| |interstate/intrastate, the DL&C System will perform the following actions (refer to | |
| |sub-requirements). | |
| |The DL&C system will initiate an OOS Transfer CDLIS transaction to retrieve the driver’s |SPM; Pg. 92 |
| |MEC/variance information from the current state of record. | |
| |The DL&C system will post the MEC/variance information to the driver’s record. |SPM; Pg. 92 |
| |If MEC/variance information exists, the DL&C System will verify that the medical certification |SPM; Pg. 92 |
| |status is set to “Certified”. | |
| |If the MEC/variance information exists and the medical certification status for the driver is “Not |SPM; Pg. 92 |
| |Certified”, the DL&C system will prevent processing of the license transaction and will display an | |
| |error message to the user. | |
|3.1.4.5 |Before issuing a duplicate or replacement license to a driver who self-certifies as non-excepted |SPM; Pg. 92 |
| |interstate/intrastate, if MEC/variance information exists for the driver, the DL&C System will | |
| |verify that the driver’s medical certification status is set to “Certified”. | |
| |If the driver’s medical certification status is verified as “certified”, the DL&C Mail Mode |SPM; Pg. 92 |
| |transaction will process successfully (pending the outcome of other system verifications). | |
| |If the driver’s medical certification status is verified as “not certified”, the DL&C Mail Mode |SPM; Pg. 92 |
| |transaction will be suspended and a rejection letter will be generated for the driver. | |
|ID |Requirement Statement |Source |
| |If the driver’s medical certification status is verified as “certified”, the DL&C Counter Mode |SPM; Pg. 92 |
| |transaction will process successfully (pending the outcome of other system verifications). | |
| |If the driver’s medical certification status is verified as “not certified”, the DL&C Counter Mode |SPM; Pg. 92 |
| |transaction will be stopped and an error message will be displayed for the user. | |
5 Downgrades
|ID |Requirement Statement |Source |
|3.1.5.1 |On a nightly basis, the DL&C system will evaluate the following date fields to determine a driver’s |SPM; Pg. 125-126; FR |
| |medical certification status – MEC Expiration Date, Waiver/Exemption Expiration Date, SPEC |383.73 |
| |Expiration Date, Waiver/Exemption Rescind Date, and SPEC Rescind Date (refer to the CDLIS | |
| |Modernization Supplementary Requirements Specification for the business rules related to calculating| |
| |a driver’s medical certification status). | |
|3.1.5.2 |After 7 calendar days if the driver’s medical certification status expired or a medical variance |SPM; Pg. 125-126; FR |
| |expired or was rescinded, the DL&C system will update the medical certification status of that |383.73 |
| |driver as ‘‘not certified” (refer to the CDLIS Modernization Supplementary Requirements | |
| |Specification for the business rules related to calculating a driver’s medical certification | |
| |status). | |
|3.1.5.3 |On January 30th, 2014, the DL&C system will run a one-time nightly batch process to update the |April 15th, Meeting |
| |medical certification status as “not certified” for all commercial drivers whose medical |Minutes, Pg. 3 |
| |certification status is set to “blank”. | |
|3.1.5.4 |On the 30th day following a driver’s medical certification status changing from “certified” to “not |SPM; Pg. 92; FR 383.73; |
| |certified”, the DL&C system will downgrade the driver’s license to non-commercial. |SPM; Pg. 125-126 |
|3.1.5.5 |Prior to downgrading a CDL driver (refer to requirement 3.1.5.4); the DL&C System will retain the |April 12th BR |
| |current CDL class, endorsements, and restrictions of the CDL driver. |Review Mtg. |
|3.1.5.6 |The DL&C system, via Conversation 95, will provide users the capability to re-certify a downgraded |April 12th BR |
| |driver if the driver applies for the re-certification within 6 months of being downgraded. |Review Mtg. |
| |The DL&C system will process the re-certification fee required by PennDOT. |April 12th BR |
| | |Review Mtg. |
| |The DL&C system will restore the driver’s CDL class, endorsements, and restrictions that were in |April 12th BR |
| |place prior to the driver being downgraded. |Review Mtg. |
6 Restrictions
|ID |Requirement Statement |Source |
|3.1.6.1 |When a user enters a Driver SPEC Effective Date and a Driver SPEC Expiration date, the DL&C system |SPM; Pg. 115; FR 383.95 |
| |will place a “V” restriction on the driver’s record. | |
|3.1.6.2 |When a user enters a Driver SPEC Effective Date and a Driver SPEC Expiration date, the DL&C System |FR 383.95 |
| |will generate a camera card including the “V” restriction on the CDL license. | |
|3.1.6.3 |When a user enters a Driver Waiver/Exemption Effective Date and a Driver Waiver/Exemption Expiration|SPM; Pg. 115; FR 383.95 |
| |date, the DL&C system will place a “V” restriction on the driver’s record. | |
|3.1.6.4 |When a user enters a Driver Waiver/Exemption Effective Date and a Driver Waiver/Exemption Expiration|FR 383.95 |
| |date, the DL&C System will generate a camera card including the “V” restriction on the CDL license. | |
|3.1.6.5 |When a user enters a Waiver/Exemption Rescind Date or SPEC Rescind Date that is less than or equal |SPM; Pg. 125-126; FR |
| |to the current system date, the DL&C system will remove the “V” restriction from the driver’s |383.73 |
| |record. | |
|3.1.6.6 |When a user enters a Waiver/Exemption Rescind Date or SPEC Rescind Date that is less than or equal |SPM; Pg. 125-126; FR |
| |to the current system date, the DL&C System will generate a camera card without the “V” restriction |383.73 |
| |on the commercial driver’s license. | |
|3.1.6.7 |On a nightly basis, the DL&C system will evaluate the Waiver/Exemption Expiration Date and SPEC |SPM; Pg. 125-126; FR |
| |Expiration date fields to determine the validity of a driver’s medical variance license restriction.|383.73 |
|3.1.6.8 |If either the Waiver/Exemption Expiration Date or the SPEC Expiration Date is equal to or less than |SPM; Pg. 125-126; FR |
| |the current system date, the DL&C system will remove the “V” restriction from the driver’s record. |383.73 |
|3.1.6.9 |If either the Waiver/Exemption Expiration Date or the SPEC Expiration Date is equal to or less than |SPM; Pg. 125-126; FR |
| |the current system date, the DL&C system will generate a camera card without the “V” restriction on |383.73 |
| |the commercial driver’s license. | |
7 Driver Information
|ID |Requirement Statement |Source |
|3.1.7.1 |The existing DL&C Mail Mode Customer Inquiry Conversation will include the driver’s |May 17th, Meeting Minutes,|
| |self-certification driving type, the MEC information, and the medical variance information (refer to|Pg. 2 |
| |sub-requirements). | |
| |The DL&C Mail Mode Customer Inquiry Conversation will display the driver’s self-certification type |May 17th, Meeting Minutes,|
| |as NI (non-excepted interstate), EI (excepted interstate), NA (non-excepted intrastate), or EA |Pg. 2 |
| |(excepted intrastate). | |
| |The DL&C Mail Mode Customer Inquiry Conversation will display the MEC information including the |May 17th, Meeting Minutes,|
| |Medical Licensing Jurisdiction Code, Medical Examiner’s Name, Medical Examiner Specialty, Medical |Pg. 2 |
| |Examiner Telephone, MEC Restrictions, Waiver/Exemption Type, Medical Certification Status, MEC | |
| |Expiration Date, MEC Issue Date, and MEC Posting Date. | |
| |The DL&C Mail Mode Customer Inquiry Conversation will display the medical variance information |May 17th, Meeting Minutes,|
| |including the SPEC Expiration Date, SPEC Effective Date, SPEC Rescind Date, Waiver/Exemption |Pg. 2 |
| |Expiration Date, Waiver/Exemption Effective Date, and Waiver/Exemption Rescind Date. | |
| |Mail Mode Users will have the ability to view the current MEC information and medical variance |May 17th, Meeting Minutes,|
| |information. |Pg. 2 |
| |Mail Mode Users will have the ability to view the prior MEC and medical variance information. |May 17th, Meeting Minutes,|
| | |Pg. 2 |
|3.1.7.2 |The existing DL&C Counter Mode Customer Inquiry Conversation will include the driver’s |May 17th, Meeting Minutes,|
| |self-certification driving type, the MEC information, and the medical variance information (refer to|Pg. 2 |
| |sub-requirements). | |
| |The DL&C Counter Mode Customer Inquiry Conversation will display the driver’s self-certification |May 17th, Meeting Minutes,|
| |type as NI (non-excepted interstate), EI (excepted interstate), NA (non-excepted intrastate), or EA |Pg. 2 |
| |(excepted intrastate). | |
| |The DL&C Counter Mode Customer Inquiry Conversation will display the MEC information including the |May 17th, Meeting Minutes,|
| |Medical Licensing Jurisdiction Code, Medical Examiner’s Name, Medical Examiner Specialty, Medical |Pg. 2 |
| |Examiner Telephone, MEC Restrictions, Waiver/Exemption Type, Medical Certification Status, MEC | |
| |Expiration Date, MEC Issue Date, and MEC Posting Date. | |
| |The DL&C Counter Customer Inquiry Conversation will display the medical variance information |May 17th, Meeting Minutes,|
| |including the SPEC Expiration Date, SPEC Effective Date, SPEC Rescind Date, Waiver/Exemption |Pg. 2 |
| |Expiration Date, Waiver/Exemption Effective Date, and Waiver/Exemption Rescind Date. | |
|ID |Requirement Statement |Source |
| |Counter Mode Users will have the ability to view the current MEC information and medical variance |May 17th, Meeting Minutes,|
| |information. |Pg. 2 |
| |Counter Mode Users will have the ability to view the prior MEC information and medical variance |May 17th, Meeting Minutes,|
| |information. |Pg. 2 |
|3.1.7.3 |The following driver abstract products produced by the DL&C system will include the driver’s |May 17th, Meeting Minutes,|
| |self-certification driving type, the MEC information, and the medical variance information – Three |Pg. 2 |
| |Year History, Ten Year History, Certified History, and Full History. | |
|3.1.7.4 |The existing “SB Driver History Request Report” produced by the DL&C system will include the |May 17th, Meeting Minutes,|
| |driver’s self-certification driving type, the MEC information, and the medical variance information.|Pg. 2 |
|3.1.7.5 |Driver Record Services Users will have the ability to generate abstracts including the driver’s |May 17th, Meeting Minutes,|
| |self-certification driving type, the medical certificate information, and the medical variance |Pg. 2 |
| |information for the following types of requestors – Employers, Employment Agencies, Drivers, Law | |
| |Enforcement Agencies, Legislative Services, and Lawyers. | |
|3.1.7.6 |Driver abstract products including the driver’s self-certification driving type, the medical |May 17th, Meeting Minutes,|
| |certificate information, and the medical variance information will be available via the following |Pg. 2 |
| |formats (refer to sub-requirements). | |
| |The existing FTP file transmitted to business partners who request driver information from PennDOT |May 17th, Meeting Minutes,|
| |will include the driver’s self-certification driving type, the MEC information, and the medical |Pg. 2 |
| |variance information. | |
| |The existing data tape provided to business partners who request driver information from PennDOT |May 17th, Meeting Minutes,|
| |will include the driver’s self-certification driving type, the MEC information, and the medical |Pg. 2 |
| |variance information. | |
| |The existing IMS Interactive Transaction that is sent to business partners who request driver |May 17th, Meeting Minutes,|
| |information from PennDOT will include the driver’s self-certification driving type, the MEC |Pg. 2 |
| |information, and the medical variance information | |
| |The existing internet function used to provide business partners with driver information from |May 17th, Meeting Minutes,|
| |PennDOT will provide the driver’s self-certification driving type, the MEC information, and the |Pg. 2 |
| |medical variance information. | |
8 Electronic Document Storage and Management
|ID |Requirement Statement |Source |
|3.1.8.1 |DL&C Users will have the ability to scan the documents related to a driver’s medical certification |April 12th BR Review Mtg. |
| |status (refer to sub-requirements) into the Electronic Data Management System (EDMS). | |
| |Users will have the ability to scan a commercial driver’s medical examiner’s certificate. |April 12th BR Review Mtg. |
| |Users will have the ability to scan a commercial driver’s Skill Performance Evaluation Certificate |April 12th BR Review Mtg. |
| |(SPEC). | |
| |Users will have the ability to scan a commercial driver’s diabetes or vision waiver. |April 12th BR Review Mtg. |
| |Users will have the ability to scan a commercial driver’s diabetes or vision exemption letter. |April 12th BR Review Mtg. |
|3.1.8.2 |The EDMS system will store the documents related to a driver’s medical certification status by the |April 12th BR Review Mtg.|
| |Work Identification Number (WID) associated with the DL&C licensing transaction. | |
|3.1.8.3 |EDMS Users will have the ability to retrieve the documents related to a driver’s medical |April 12th BR Review Mtg. |
| |certification status by providing the system with the Work Identification Number (WID) associated | |
| |with the DL&C licensing transaction. | |
|3.1.8.4 |The EDMS system will retain an electronic copy of the documents related to a driver’s medical |April 12th BR Review Mtg. |
| |certification status for 3 years beyond the MEC Issue Date. | |
9 Correspondence
|ID |Requirement Statement |Source |
|3.1.9.1 |The DL&C system will generate a notification letter that will be sent to existing Pennsylvania CDL |FR 383.71 |
| |holders indicating that they must self-certify no later than January 30, 2014. | |
| |Notification letters will be sent each month beginning January 30th, 2012 and ending October 30th, |April 15th BR Review Mtg. |
| |2013. | |
| |Each monthly group of notification letters will be sent to a different group of commercial drivers |April 15th BR Review Mtg.|
| |using designated criteria. | |
|3.1.9.2 |When the DL&C system changes a driver’s medical certification status to “not certified”, the DL&C |April 12th BR Review Mtg. |
| |System will generate a Medical Certification Status Change Notification letter. | |
|3.1.9.3 |During commercial driver mail-in licensing transactions (refer to sub-requirements below), if the |April 12th BR Review Mtg. |
| |DL&C system determines that a driver’s medical certification status is “not certified”, the DL&C | |
| |system will include the reason for rejection on the existing Combination Rejection Letter generated | |
| |by the DL&C system. | |
| |During a mail mode CDL renewal transaction, if the DL&C system determines that a driver’s medical |April 12th BR Review Mtg. |
| |certification status is “not certified”, the DL&C system will include the reason for the rejection | |
| |on the existing Combination Rejection Letter. | |
| |During a mail mode CDL replacement or duplicate transaction, if the DL&C system determines that a |April 12th BR Review Mtg. |
| |driver’s medical certification status is “not certified”, the DL&C system will include the reason | |
| |for the rejection on the existing Combination Rejection Letter. | |
|3.1.9.4 |Prior to a CDL holder’s medical certificate expiration date, the DL&C system will generate a Medical|April 12th BR Review Mtg. |
| |Certification Reminder letter. | |
|3.1.9.5 |Thirty days after a CDL holder’s medical certification status is changed from “certified” to “not |April 12th BR Review Mtg. |
| |certified”, the DL&C system will generate a Downgrade Notification Letter. | |
|3.1.9.6 |When a DL&C User enters a SPE Expiration Date and a SPE Effective Date in the DL&C system, the DL&C |April 12th BR Review Mtg. |
| |system will generate a Medical Variance Notification letter. | |
|3.1.9.7 |When a DL&C User enters a Waiver/Exemption Expiration Date and a Waiver/Exemption Effective Date in |April 12th BR Review Mtg. |
| |the DL&C system, the DL&C system will generate a Medical Variance Notification letter. | |
10 CDLIS Release 5.1 Medical Certification Transactions
The transactions listed in this section are the CDLIS transactions that will transmit medical certification information between the current state of record (SOR) and a state of inquiry (SOI).
For more information related to the CDLIS transactions, messages, and date elements, please refer to the following appendices:
• “Appendix B – Data Elements by Message Type”
• “Appendix C – CDLIS Transaction Diagrams
• “Appendix E – Person Name Formatting”
|ID |Requirement Statement |Source |
|3.1.10.1 |HC: SOR ( SOI |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOR, the DL&C System will send a CD01/HC message to the SOI that, if available, |MSD Appendix A |
| |will include the following medical certificate fields: |MSD Appendix D |
| | | |
| |HC Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.2 |HC: SOR ( SOI |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD01/HC Status Response message |MSD Appendix A |
| |that, if available, will include the following medical certificate fields: |MSD Appendix D |
| | | |
| |HC Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.3 |HC: SOR ( SOI |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOR, the DL&C System will send a CD02/HC Status Response message to the SOI |MSD Appendix A |
| |that, if available, will include the following medical certificate fields: |MSD Appendix D |
| | | |
| |HC Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.4 |HC: SOR ( SOI |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD02/HC Status Response message |MSD Appendix A |
| |that, if available, will include the following medical certificate fields: |MSD Appendix D |
| | | |
| |HC Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.5 |HG: SOR ( SOI |SPM; Pg. 28-30 |
| |CD03 |MSD 76-91(CD03) |
| |When PennDOT is the SOR, the DL&C System will send a CD03/HG Status Response message to the SOI that|MSD Appendix A |
| |will, if available, include the following medical certificate fields: |MSD Appendix D |
| | | |
| |HG Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.6 |HG: SOR ( SOI |SPM; Pg. 28-30 |
| |CD03 |MSD Pg. 76-91 (CD03) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD03/HG Status Response message from|MSD Pg. 85-86 |
| |the SOR that will include, if available, the following medical certificate fields: |MSD Appendix A Pg. 505-507|
| | |MSD Appendix D |
| |HG Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.7 |HB: SOR ( Common Validation Processor (SOI |SPM; Pg. 31-33 |
| |CD04 |MSD 92-96(CD04) |
| |When PennDOT is the SOR, the DL&C System will send a CD04/HB Driver History Response message to the |MSD Appendix A |
| |SOI (via the CDLIS Common Validation Processor) that will include, if available, the following |MSD Appendix D |
| |medical certificate fields: | |
| | | |
| |HB Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.8 |HB: SOR ( CDLIS Common Validation Processor ( SOI |SPM; Pg. 31-33 |
| |CD04 |MSD 92-96(CD04) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD04/HB Driver History Response |MSD Appendix A |
| |message from the SOR (via the CDLIS Common Validation Processor) that will include, if available, |MSD Appendix D |
| |the following medical certificate fields: | |
| | | |
| |HB Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.9 |HC: SOR ( SOI |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOR, the DL&C System will send a CD05/HC Status Response message to the SOI that|97-108(CD05) |
| |will include, if available, the following medical certificate fields: |MSD Appendix A |
| | |MSD Appendix D |
| |HC Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.10 |HC: SOR ( SOI |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD05/HC Status Response message from|97-108(CD05) |
| |the SOR that will include, if available, the following medical certificate fields: |MSD Appendix A |
| | |MSD Appendix D |
| |HC Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.11 |HD: Old SOR ( CDLIS Common Validation Processor ( New SOR |SPM; Pg. 41-47 |
| |CD08 |MSD |
| |When PennDOT is the Old SOR, the DL&C System will send a CD08/HD Driver History Response message to |134-167(CD08) |
| |the New SOR via the CDLIS Common Validation Processor that will include, if available, the |MSD Appendix A |
| |following medical certificate fields: |MSD Appendix D |
| | | |
| |HD Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
|3.1.10.12 |HD: Old SOR ( CDLIS Common Validation Processor ( New SOR |SPM; Pg. 41-47 |
| |CD08 |MSD |
| |When PennDOT is the New SOR, the DL&C System will receive/process a CD08/HD Driver History Response |134-167(CD08) |
| |message from the Old SOR via the CDLIS Common Validation Processor that will include, if available, |MSD Appendix A |
| |the following medical certificate fields: |MSD Appendix D |
| | | |
| |HD Status Response Message – Medical Fields | |
| |CDL MEDICAL SELF CERTIFICATION CODE | |
| |MEDICAL CERTIFICATE ISSUE DATE | |
| |MEDICAL CERTIFICATE EXPIRATION DATE | |
| |MEDICAL CERTIFICATION STATUS CODE | |
| |MEDICAL CERTIFICATE RESTRICTION CODE | |
| |MEDICAL LICENSING JURISDICTION CODE | |
| |MEDICAL EXAMINER LICENSE NUMBER | |
| |MEDICAL EXAMINER TELEPHONE NUMBER | |
| |MEDICAL EXAMINER REGISTRY NUMBER | |
| |MEDICAL EXAMINER SPECIALTY CODE | |
| |DRIVER WAIVER/EXEMPT EFFECTIVE DATE | |
| |DRIVER WAIVER/EXEMPT EXPIRATION DATE | |
| |DRIVER SPE EFFECTIVE DATE | |
| |DRIVER SPE EXPIRATION DATE | |
| |MEDICAL EXAMINER LAST NAME | |
| |MEDICAL EXAMINER FIRST NAME | |
| |MEDICAL EXAMINER MIDDLE NAME | |
| |MEDICAL EXAMINER NAME SUFFIX | |
| |ME LAST NAME TRUNCATION IND | |
| |ME FIRST NAME TRUNCATION IND | |
| |ME MIDDLE NAME TRUNCATION IND | |
| |ME LAST NAME TRANSLITERATION IND | |
| |ME FIRST NAME TRANSLITERATION IND | |
| |ME MIDDLE NAME TRANSLITERATION IND | |
6 CDLIS Release 5.1 Modernization
For a complete description of the CDLIS transaction flow, please refer to “Appendix C – CDLIS Transaction Diagrams” when reviewing the requirements in this section.
1 Architectural Changes
Assumptions
• CDLIS R5.1 Overview-Pg 33: Removal of height, weight and eye color
“Fields not included on any message to or from the Central Site. Fields included as usual on messages between Jurisdictions”
• CDLIS R5.1 Imp. Planning-Pg 10:
“Height, weight, eye color, AKA DOB and AKA SSN are being eliminated as of Central Site Day 1. Any jurisdiction processes that used this information from the Central Site need to be modified. NOTE: These fields will continue to be exchanged from state-to-state in the same manner as with CDLIS Release 4.1.”
• CDLIS R5.1 Overview-Pg 35: Removal of AKA DOBs and AKA SSN
“Messages from State to CDLIS Central Site: AKA DOBs will still be sent on inquiry messages. Messages from State to State: Retains all AKA data. Messages from CDLIS Central Site: AKA count no longer sent.”
|ID |Requirement Statement |Source |
|3.2.1.1 |RD: CDLIS ( SOI |SPM; Pg. 22-24 |
| |CD01 Search Inquiry |MSD 51-62(CD01) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD01/RD message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |RD Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
| |DRIVER AKA SOCIAL SECURITY NUMBER | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.2 |SC: CDLIS ( SOR |SPM; Pg. 22-24 |
| |CD01 Search Inquiry |MSD 51-62(CD01) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD01/SC message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |SC Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.3 |IM (or IO) : SOI ( CDLIS |SPM; Pg. 22-24 |
| |CD01 Search Inquiry |MSD 51-62(CD01) |
| |When PennDOT is the SOI, the DL&C System will send a CD01/IM (or IO) message to CDLIS that will |MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |IM (or IO) Message Type | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
|3.2.1.4 |RD: CDLIS ( SOI |SPM; Pg. 25-27 |
| |CD02 Verification Inquiry |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD02/RD message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |RD Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
| |DRIVER AKA SOCIAL SECURITY NUMBER | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.5 |SC: CDLIS ( SOR |SPM; Pg. 25-27 |
| |CD02 Verification Inquiry |MSD 63-75(CD02) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD02/SC message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |SC Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.6 |RD: CDLIS ( SOI |SPM; Pg. 34-36 |
| |CD05 AKA Data Inquiry |MSD |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD05/RD message from CDLIS that will|Pg.97-108(CD05) |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix A |
| | |MSD Appendix D |
| |RD Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
| |DRIVER AKA SOCIAL SECURITY NUMBER | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.7 |SC: CDLIS ( SOR |SPM; Pg. 34-36 |
| |CD05 AKA Data Inquiry |MSD |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD05/SC message from CDLIS that will|Pg.97-108(CD05) |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix A |
| | |MSD Appendix D |
| |SC Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.8 |IK: SOI ( CDLIS |SPM; Pg. 34-36 |
| |CD05 AKA Data Inquiry |MSD |
| |When PennDOT is the SOI, the DL&C System will send a CD05/IK message to CDLIS that will exclude the |Pg.97-108(CD05) |
| |following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix A |
| | |MSD Appendix D |
| |IK Message Type | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
|3.2.1.9 |UA: SOR ( CDLIS |MSD |
| |CD07 Add New Driver |Pg.119-133(CD07) |
| |When PennDOT is the SOR, the DL&C System will send a CD07/UA message to CDLIS that will exclude the |MSD Appendix A |
| |following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |UA Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
| |DRIVER AKA SOCIAL SECURITY NUMBER | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.10 |CB: CDLIS ( SOR |MSD |
| |CD07 Add New Driver |Pg.119-133(CD07) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD07/CB message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |CB Message Type | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.11 |SD: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |When PennDOT is the Old SOR, the DL&C System will receive/process a CD08/SD message from CDLIS that |Pg.134-167(CD08) |
| |will exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix A |
| | |MSD Appendix D |
| |SD Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.12 |UD: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| | |Pg.134-167(CD08) |
| |When PennDOT is the New SOR, the DL&C System will send a CD08/UD message to CDLIS that will exclude |MSD Appendix A |
| |the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |UD Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.13 |CC: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| | |Pg.134-167(CD08) |
| |When PennDOT is the New SOR, the DL&C System will send a CD08/CC message to CDLIS that will exclude |MSD Appendix A |
| |the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |CC Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.14 |UC: SOR ( CDLIS |MSD |
| |CD09 Change Data |Pg.168-185(CD09) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will send a CD09/UC message to CDLIS that will exclude the |MSD Appendix D |
| |following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): | |
| | | |
| |UC Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
| |DRIVER AKA SOCIAL SECURITY NUMBER | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.15 |CD: CDLIS ( SOR |MSD |
| |CD09 Change Data |Pg.168-185(CD09) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD09/CD message from CDLIS that will|MSD Appendix D |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): | |
| | | |
| |CD Message Type | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.16 |UE: SOR ( CDLIS |MSD |
| |CD10 Delete Master Pointer Record |Pg.186-194(CD10) |
| |When PennDOT is the SOR, the DL&C System will send a CD10/UE message to CDLIS that will exclude the |MSD Appendix A |
| |following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |UE Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.17 |HF: CDLIS ( SOR |MSD |
| |CD11 Report Out-of-State Convictions |Pg.195-215(CD11) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD11/HF message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |HF Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.18 |HX: CDLIS ( SOR |MSD |
| |CD12 Negate Out-of-State Convictions |Pg.216-232(CD12) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD12/HX message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |HX Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.19 |UK: SOR ( CDLIS |MSD |
| |CD15 Update AKA Data |Pg.243-256(CD15) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will send a CD15/UK message to CDLIS that will exclude the |MSD Appendix D |
| |following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): | |
| | | |
| |UK Message Type | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
| |DRIVER AKA SOCIAL SECURITY NUMBER | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.20 |HT: CDLIS ( SOR |MSD |
| |CD16 Report Out-of-State Withdrawal |Pg.257-281(CD16) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD16/HT message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |HT Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.21 |HV: CDLIS ( SOR |MSD |
| |CD17 Negate Out-of-State Withdrawal |Pg.282-309(CD17) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD17/HV message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |HV Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
|3.2.1.22 |NA: CDLIS ( SOR |MSD |
| |CDA1 Duplicate Driver |Pg.310-332(CDA1) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CDA1/NA message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |NA Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
| |DRIVER DUPLICATE HEIGHT | |
| |DRIVER DUPLICATE WEIGHT | |
| |DRIVER DUPLICATE EYE COLOR | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.23 |NE: CDLIS ( SOR |MSD |
| |CDA1 Duplicate Driver |Pg.310-332(CDA1) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CDA1/NE message from CDLIS that will|MSD Appendix A |
| |exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010): |MSD Appendix D |
| | | |
| |NE Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
| |DRIVER DUPLICATE HEIGHT | |
| |DRIVER DUPLICATE WEIGHT | |
| |DRIVER DUPLICATE EYE COLOR | |
| |MESSAGE AKA SSN COUNT | |
|3.2.1.24 |EM: SOI ( CDLIS | |
| |CD30 CDLIS Batch Inquiry | |
| |When PennDOT is the SOI, PennDOT will send a CD30/EM Batch Inquiry File to CDLIS that will exclude | |
| |the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010) | |
| | | |
| |EM Message Type | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
|3.2.1.25 |QD: CDLIS ( SOI | |
| |CD30 CDLIS Batch Inquiry | |
| |When PennDOT is the SOI, PennDOT will receive/process a CD30/QD Batch Inquiry File from CDLIS that | |
| |will exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010) | |
| | | |
| |QD Message Type | |
| |DRIVER CURRENT HEIGHT | |
| |DRIVER CURRENT WEIGHT | |
| |DRIVER CURRENT EYE COLOR | |
| |DRIVER AKA SOCIAL SECURITY NUMBER | |
| |MESSAGE AKA SSN COUNT | |
| |DRIVER AKA DATE OF BIRTH | |
| |DRIVER AKA 2ND DATE OF BIRTH | |
| |DRIVER AKA 3RD DATE OF BIRTH | |
|3.2.1.26 |When PennDOT receives the results of a search, the DL&C System will receive/process the results of |Overview Webinar handout; |
| |the CDLIS improved search algorithm. |page 31 |
2 Name Expansion
For a complete description of the CDLIS transaction flow, please refer to “Appendix C – CDLIS Transaction Diagrams” when reviewing the requirements in this section. Please refer to “Appendix E – Person Name Formatting” in the CDLIS Master Specifications Release 5.1 for the new rules in formatting the name fields, including the new Truncation and Transliteration rules.
Assumptions
* If applicable references:
✓ PennDOT will send messages to CDLIS in the new name format.
✓ CDLIS will send PennDOT messages in the new name format.
✓ CDLIS will send PennDOT messages that require a response directly to a state in either the 4.1 or new name format; depending on the release of the state receiving the response. If the state receiving the response is using release 4.1, then CDLIS will send PennDOT the message in the 4.1 name format. If the state receiving the response is using Release 5.1, then CDLIS will send PennDOT the message in the new name format.
✓ PennDOT will send/receive state-to-state inquiries in both the 4.1 and new name formats during the transition period. Post-transition, PennDOT will send/receive state-to-state inquiries in only the new name format.
✓ If the new name field is populated, PennDOT will send responses in the new name format.
✓ If the new name field is not populated, PennDOT will send responses in the 4.1 name format during the transition period. Post-transition, PennDOT will send all responses in the new name format.
✓ PennDOT will receive responses in the new name format.
|ID |Requirement Statement |Source |
|3.2.2.1 |HC: SOR ( SOI |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD01/HC Status Response message |MSD Appendix A |
| |from the SOR that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |HC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.2 |IM (or IO): SOI ( CDLIS |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOI, the DL&C System will send a CD01/IM (or IO) message to the CDLIS Central |MSD Appendix A |
| |Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |IM (or IO) Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.3 |RD: CDLIS ( SOI |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD01/RD message from the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |RD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.4 |HC: SOR ( SOI |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOR, the DL&C System will send a CD01/HC Status Response message to the SOI |MSD Appendix A |
| |that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |HC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.5 |SC: CDLIS ( SOR |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD01/SC Status Request message |MSD Appendix A |
| |from the CDLIS Central Site that, if applicable*, will include the following CDLIS modernization |MSD Appendix D |
| |fields: | |
| | | |
| |SC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.6 |HC: SOR ( SOI |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD02/HC Status Response message |MSD Appendix A |
| |from the SOR that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |HC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.7 |RD: CDLIS ( SOI |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD02/RD message from the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |RD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.8 |IN: SOI ( CDLIS |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will send a CD02/IN Verify Inquiry message to the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |IN Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.9 |IA: SOI ( CDLIS |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will send a CD02/IA Inquiry Request message to the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |IA Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.10 |IB: SOI ( CDLIS |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will send a CD02/IB Inquiry Request message to the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |IB Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.11 |IC: SOI ( CDLIS |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will send a CD02/IC Inquiry Request message to the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |IC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.12 |ID: SOI ( CDLIS |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will send a CD02/ID Inquiry Request message to the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |ID Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.13 |IE: SOI ( CDLIS |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will send a CD02/IE Inquiry Request message to the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |IE Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.14 |HC: SOR ( SOI |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOR, the DL&C System will send a HC Status Response message to the SOI that, |MSD Appendix A |
| |if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |HC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.15 |SC: CDLIS ( SOR |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD02/SC Status Request message |MSD Appendix A |
| |from the CDLIS Central Site that, if applicable*, will include the following CDLIS modernization |MSD Appendix D |
| |fields: | |
| | | |
| |SC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.16 |SG: SOI ( SOR |SPM; Pg. 28-30 |
| |CD03 |MSD 76-91(CD03) |
| |When PennDOT is the SOI, the DL&C System will send a CD03/SG message type to the SOR that, if |MSD Appendix A |
| |applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |SG Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.17 |HG: SOR ( SOI |SPM; Pg. 28-30 |
| |CD03 |MSD 76-91(CD03) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD03/HG message from the SOR |MSD Appendix A |
| |that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |HG Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.18 |SG: SOI ( SOR |SPM; Pg. 28-30 |
| |CD03 |MSD 76-91(CD03) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD03/SG message from the SOI |MSD Appendix A |
| |that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |SG Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.19 |HG: SOR ( SOI |SPM; Pg. 28-30 |
| |CD03 |MSD 76-91(CD03) |
| |When PennDOT is the SOR, the DL&C System will send a CD03/HG message to the SOI that, if |MSD Appendix A |
| |applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |HG Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.20 |SB: SOI ( SOR |SPM; Pg. 31-33 |
| |CD04 |MSD 92-96(CD04) |
| |When PennDOT is the SOI, the DL&C System will send a CD04/SB message to the SOR that, if |MSD Appendix A |
| |applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |SB Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.21 |HB: SOR ( CDLIS Common Validation Processor ( SOI |SPM; Pg. 31-33 |
| |CD04 |MSD 92-96(CD04) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD04/HB message from the SOR via |MSD Appendix A |
| |the CDLIS Common Validation Processor that, if applicable*, will include the following CDLIS |MSD Appendix D |
| |modernization fields: | |
| | | |
| |HB Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.22 |SB: SOI ( SOR |SPM; Pg. 31-33 |
| |CD04 |MSD 92-96(CD04) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD04/SB message from the SOI |MSD Appendix A |
| |that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |SB Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.23 |HB: SOR ( CDLIS Common Validation Processor ( SOI |SPM; Pg. 31-33 |
| |CD04 |MSD 92-96(CD04) |
| |When PennDOT is the SOR, the DL&C System will send a CD04/HB message to the SOI via the CDLIS |MSD Appendix A |
| |Common Validation Processor that, if applicable*, will include the following CDLIS modernization |MSD Appendix D |
| |fields: | |
| | | |
| |HB Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.24 |IK: SOI ( CDLIS |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOI, the DL&C System will send a CD05/IK message to the CDLIS Central Site |Pg.97-108(CD05) |
| |that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |IK Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.25 |HC: SOR ( SOI |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD05/HC message from the CDLIS |Pg.97-108(CD05) |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |HC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.26 |RD: CDLIS ( SOI |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD05/RD message from the CDLIS |Pg.97-108(CD05) |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |RD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.27 |SC: CDLIS ( SOR |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD05/SC message from the CDLIS |Pg.97-108(CD05) |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |SC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.28 |HC: SOR ( SOI |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOR, the DL&C System will send a CD05/HC message to the SOI that, if |Pg.97-108(CD05) |
| |applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |HC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.29 |UA: SOR ( CDLIS |MSD |
| |CD07 |Pg.119-133(CD07) |
| |When PennDOT is the SOR, the DL&C System will send a CD07/UA message to CDLIS that, if |MSD Appendix A |
| |applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |UA Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.30 |UC: SOR ( CDLIS |MSD |
| |CD09 Change Data |Pg.168-185(CD09) |
| |When PennDOT is the SOR, the DL&C System will send a CD09/UC Change Data message to the CDLIS |MSD Appendix A |
| |Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |UC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAME TRANSLIT CODE | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.31 |UE: SOR ( CDLIS |MSD |
| |CD10 Delete Master Pointer Record |Pg.186-194(CD10) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will send a CD10/UE Delete Master Pointer Record message |MSD Appendix D |
| |to the CDLIS Central Site that, if applicable*, will include the following CDLIS modernization | |
| |fields: | |
| | | |
| |UE Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.32 |HA: SOC ( CDLIS |MSD |
| |CD11 Report OOS (Out of State) Conviction |Pg.195-215(CD11) |
| | |MSD Appendix A |
| |When PennDOT is the SOC, the DL&C System will send a CD11/HA Report OOS Conviction message to the |MSD Appendix D |
| |CDLIS Central Site that, if applicable*, will include the following CDLIS modernization fields: | |
| | | |
| |HA Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |HF: CDLIS ( SOR |MSD |
|3.2.2.33 |CD11 Process OOS (Out of State) Conviction |Pg.195-215(CD11) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD11/HF Report OOS Conviction |MSD Appendix D |
| |message from the CDLIS Central Site that, if applicable*, will include the following CDLIS | |
| |modernization fields: | |
| | | |
| |HF Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.34 |HH: SOC ( CDLIS |MSD |
| |CD12 Negate OOS (Out of State) Conviction |Pg.216-232(CD12) |
| | |MSD Appendix A |
| |When PennDOT is the SOC, the DL&C System will send a CD12/HH Negate OOS Conviction message to the |MSD Appendix D |
| |CDLIS Central Site that, if applicable*, will include the following CDLIS modernization fields: | |
| | | |
| |HH Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.35 |HX: CDLIS ( SOR |MSD |
| |CD12 Negate OOS (Out of State) Conviction |Pg.216-232(CD12) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD12/HX Negate OOS Conviction |MSD Appendix D |
| |message from the CDLIS Central Site that, if applicable*, will include the following CDLIS | |
| |modernization fields: | |
| | | |
| |HX Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.36 |UG: SOR ( CDLIS |MSD |
| |CD14 Mark Driver Unique |Pg.233-242(CD14) |
| | |MSD Appendix A |
| |(When CDLIS identifies duplicates, the MPR of each possible duplicate driver is marked as such and|MSD Appendix D |
| |notifications are sent to the SOR(s). The SORs receiving notifications determine whether or not | |
| |the drivers are duplicates. If the SORs determine the matching information on the possible | |
| |duplicates is accurate and positive determination has been made that he drivers are, indeed | |
| |unique, both SORs initiate the Mark Unique transaction to specify that the two drivers with | |
| |matching identification are not the same.) When PennDOT is the SOR, the DL&C System will | |
| |receive/process a CD14/UG Mark Driver Unique message from the CDLIS Central Site that, if | |
| |applicable*, will include the following CDLIS modernization fields: | |
| | | |
| |UG Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON DUPLICATE LAST NAME | |
| |PERSON DUPLICATE FIRST NAME | |
| |PERSON DUPLICATE MIDDLE NAME | |
| |DRIVER DUPLICATE NAME SUFFIX | |
| |PERSON DUP LAST NAME TRUNCATION CODE | |
| |PERSON DUP FIRST NAME TRUNCATION | |
| |PERSON DUP MIDDLE NAME TRUNCATION | |
| |PERSON DUP LAST NAME TRANSLIT | |
| |PERSON DUP FIRST NAME TRANSLIT CODE | |
| |PERSON DUP MIDDLE NAME TRANSLIT CODE | |
|3.2.2.37 |UK: SOR ( CDLIS |MSD |
| |CD15 Update AKA Data |Pg.243-256(CD15) |
| | |MSD Appendix A |
| |(The update AKA Data transaction enables a State of Record (SOR) to correct the AKA information on|MSD Appendix D |
| |a MPR at the CDLIS Central Site. The Update AKA Data transaction removes all existing AKA | |
| |information and replaces it with the new AKA information submitted on the Update AKA Data | |
| |message.) When PennDOT is the SOR, the DL&C System will send a CD15/UK Update AKA Data message to| |
| |the CDLIS Central Site that, if applicable*, will include the following CDLIS modernization | |
| |fields: | |
| | | |
| |UK Message Type | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAME TRANSLIT CODE | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.2.38 |HW: SOW ( CDLIS |MSD |
| |CD16 Report OOS Withdraw |Pg.257-281(CD16) |
| | |MSD Appendix A |
| |When PennDOT is the SOW, the DL&C System will send a CD16/HW Report OOS Withdraw message to the |MSD Appendix D |
| |CDLIS Central Site that, if applicable*, will include the following CDLIS modernization fields: | |
| | | |
| |HW Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.39 |HT: CDLIS ( SOR |MSD |
| |CD16 Report OOS Withdraw |Pg.257-281(CD16) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD16/HT Report OOS Withdraw |MSD Appendix D |
| |message from the CDLIS Central Site that, if applicable*, will include the following CDLIS | |
| |modernization fields: | |
| | | |
| |HT Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.40 |HY: SOW ( CDLIS |MSD |
| |CD17 Negate OOS Withdraw |Pg.282-309(CD17) |
| | |MSD Appendix A |
| |When PennDOT is the SOW, the DL&C System will send a CD17/HY Negate OOS Withdraw message to the |MSD Appendix D |
| |CDLIS Central Site that, if applicable*, will include the following CDLIS modernization fields: | |
| | | |
| |HY Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.41 |HV: CDLIS ( SOR |MSD |
| |CD17 Negate OOS Withdraw |Pg.282-309(CD17) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD17/HV Negate OOS Withdraw |MSD Appendix D |
| |message from the CDLIS Central Site that, if applicable*, will include the following CDLIS | |
| |modernization fields: | |
| | | |
| |HV Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
|3.2.2.42 |NA: CDLIS ( SOR |MSD |
| |CDA1 Duplicate Driver |Pg.310-332(CDA1) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CDA1/NA message from CDLIS that |MSD Appendix A |
| |will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |NA Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON DUPLICATE LAST NAME | |
| |PERSON DUPLICATE FIRST NAME | |
| |PERSON DUPLICATE MIDDLE NAME | |
| |DRIVER DUPLICATE NAME SUFFIX | |
| |PERSON DUP LAST NAME TRUNCATION CODE | |
| |PERSON DUP FIRST NAME TRUNCATION | |
| |PERSON DUP MIDDLE NAME TRUNCATION | |
| |PERSON DUP LAST NAME TRANSLIT | |
| |PERSON DUP FIRST NAME TRANSLIT CODE | |
| |PERSON DUP MIDDLE NAME TRANSLIT CODE | |
|3.2.2.43 |NE: CDLIS ( SOR |MSD |
| |CDA1 Duplicate Driver |Pg.310-332(CDA1) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CDA1/NE message from CDLIS that |MSD Appendix A |
| |will include the following CDLIS modernization fields: |MSD Appendix D |
| | | |
| |NE Message Type | |
| |PERSON DUPLICATE LAST NAME | |
| |PERSON DUPLICATE FIRST NAME | |
| |PERSON DUPLICATE MIDDLE NAME | |
| |DRIVER DUPLICATE NAME SUFFIX | |
| |PERSON DUP LAST NAME TRUNCATION CODE | |
| |PERSON DUP FIRST NAME TRUNCATION | |
| |PERSON DUP MIDDLE NAME TRUNCATION | |
| |PERSON DUP LAST NAME TRANSLIT | |
| |PERSON DUP FIRST NAME TRANSLIT CODE | |
| |PERSON DUP MIDDLE NAME TRANSLIT CODE | |
3 Backward Compatibility – Name Expansion
For a complete description of the CDLIS transaction flow, please refer to “Appendix C – CDLIS Transaction Diagrams” when reviewing the requirements in this section.
Assumptions
✓ PennDOT will send messages to CDLIS in the new name format.
✓ CDLIS will send PennDOT non-response messages in the new name format.
✓ CDLIS will send PennDOT messages that require a response directly to a state in either the 4.1 or new name format; depending on the release of the state receiving the response. If the state receiving the response is using release 4.1, then CDLIS will send PennDOT the message in the 4.1 name format. If the state receiving the response is using Release 5.1, then CDLIS will send PennDOT the message in the new name format.
✓ PennDOT will send/receive state-to-state inquiries in both the 4.1 and new name formats during the transition period. Post-transition, PennDOT will send/receive state-to-state inquiries in only the new name format.
✓ If the new name field is populated, PennDOT will send responses in the new name format.
✓ If the new name field is not populated, PennDOT will send responses in the 4.1 name format during the transition period. Post-transition, PennDOT will send all responses in the new name format.
✓ PennDOT will receive responses in the new name format.
|ID |Requirement Statement |Source |
|3.2.3.1 |HC: SOR ( SOI |MSD (CD01), pg. 53 |
| |CD01 | |
| |During the transition period, when PennDOT is the SOI and the SOR is release 4.1, then the PennDOT | |
| |system will receive a HC/CDO1 release 4.1 message format from the SOR for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOI and the SOR is Release 5.1, then the PennDOT | |
| |system will receive a HC/CD01 Release 5.1 message format from the SOR for the Name. | |
|3.2.3.2 |IM (or IO): SOI ( CDLIS |MSD (CD01), pg. 53 |
| |CD01 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send a IM (or | |
| |IO)/CD01 Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.3 |RD: CDLIS ( SOI |MSD (CD01), pg. 53 |
| |CD01 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will receive a | |
| |RD/CD01 Release 5.1 message format from CDLIS for the Name. | |
|3.2.3.4 |HC: SOR ( SOI |MSD (CD01), pg. 53 |
| |CD01 | |
| |During the transition period, when PennDOT is the SOR and a SOI is using release 4.1, then the | |
| |PennDOT system will send a HC/CD01 release 4.1 message format to the SOI for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and a SOI is using Release 5.1, then the | |
| |PennDOT system will send a HC/CD01 Release 5.1 message format to the SOI for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the name is not present on the SC message,| |
| |then the PennDOT system will send both a HC/CD01 release 4.1 and Release 5.1 message format to the | |
| |SOI for the Name. | |
|3.2.3.5 |SC: CDLIS ( SOR |MSD (CD01), pg. 53 |
| |CD01 | |
| |During the transition period, when PennDOT is the SOR and the SOI is using release 4.1, then the | |
| |PennDOT system will receive a SC/CD01 release 4.1 message format from CDLIS for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI is using Release 5.1, then the | |
| |PennDOT system will receive a SC/CD01 Release 5.1 message format from CDLIS for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the name is not present, then the PennDOT | |
| |system will receive both a SC/CD01 release 4.1 and Release 5.1 message format from CDLIS for the | |
| |Name. | |
|3.2.3.6 |HC: SOR ( SOI |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOI and the SOR is using release 4.1, then the | |
| |PennDOT system will receive a HC/CD02 release 4.1 message format from the SOR for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOI and the SOR is using Release 5.1, then the | |
| |PennDOT system will receive a HC/CD02 Release 5.1 message format from the SOR for the Name. | |
|3.2.3.7 |RD: CDLIS ( SOI |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will receive a | |
| |RD/CD02 Release 5.1 message format from CDLIS for the Name. | |
|3.2.3.8 |IN: SOI ( CDLIS |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send an IN/CD02 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.9 |IA: SOI ( CDLIS |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send an IA/CD02 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.10 |IB: SOI ( CDLIS |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send an IB/CD02 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.11 |IC: SOI ( CDLIS |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send an IC/CD02 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.12 |ID: SOI ( CDLIS |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send an ID/CD02 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.13 |IE: SOI ( CDLIS |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send an IE/CD02 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.14 |HC: SOR ( SOI |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOR and a SOI is using release 4.1, then the | |
| |PennDOT system will send a HC/CD02 4.1 message format to the SOI for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and a SOI is using Release 5.1, then the | |
| |PennDOT system will send a HC/CD02 Release 5.1 message format to the SOI for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the name is not present on the SC message,| |
| |then the PennDOT system will send both a HC/CD02 release 4.1 and Release 5.1 message format to the | |
| |SOI for the Name. | |
|3.2.3.15 |SC: CDLIS ( SOR |MSD (CD02), pg. 65 |
| |CD02 | |
| |During the transition period, when PennDOT is the SOR and the SOI is using release 4.1, then the | |
| |PennDOT system will receive a SC/CD02 release 4.1message format from CDLIS for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI is using Release 5.1, then the | |
| |PennDOT system will receive a SC/CD02 Release 5.1 message format from CDLIS for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the name is not present, then the PennDOT | |
| |System will receive both a SC/CD02 release 4.1 and Release 5.1 message format from CDLIS for the | |
| |Name. | |
|3.2.3.16 |SG: SOI ( SOR |MSD (CD03), pg. 78 |
| |CD03 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send both a | |
| |SG/CD03 release 4.1 and Release 5.1 message format to the SOR for the Name. | |
|3.2.3.17 |HG: SOR ( SOI |MSD (CD03), pg. 78 |
| |CD03 | |
| |During the transition period, when PennDOT is the SOI and the SOR is using release 4.1, then PennDOT| |
| |will receive a HG/CD03 release 4.1 message format from the SOR for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOI and the SOR is using Release 5.1, then PennDOT| |
| |will receive a HG/CD03 Release 5.1 message format from the SOR for the Name. | |
|3.2.3.18 |SG: SOI ( SOR |MSD (CD03), pg. 78 |
| |CD03 | |
| |During the transition period, when PennDOT is the SOR and the SOI is using release 4.1, then the | |
| |PennDOT system will receive a SG/CD03 release 4.1 message format from the SOI for the name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI is using Release 5.1, then the | |
| |PennDOT system will receive both a SG/CD03 release 4.1 and Release 5.1 message format from the SOI | |
| |for the name. | |
|3.2.3.19 |HG: SOR ( SOI |MSD (CD03), pg. 78 |
| |CD03 | |
| |During the transition period, when PennDOT is the SOR and the SOI is using release 4.1, then PennDOT| |
| |will send a HG/CD03 release 4.1 message format to the SOI for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI is using Release 5.1, then PennDOT| |
| |will send a HG/CD03 Release 5.1 message format to the SOI for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI did not provide any name on the SG| |
| |message, then PennDOT will send both a HG/CD03 release 4.1 and Release 5.1 message format to the SOI| |
| |for the Name. | |
|3.2.3.20 |SB: SOI ( SOR |MSD (CD04), pg. 94 |
| |CD04 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send both a | |
| |SB/CD04 release 4.1 and a Release 5.1 message format to the SOR for the Name. | |
|3.2.3.21 |HB: SOR ( CDLIS Common Validation Processor ( SOI |MSD (CD04), pg. 94 |
| |CD04 | |
| |During the transition period, when PennDOT is the SOI and the SOR is release 4.1, then the PennDOT | |
| |system will receive a HB/CD04 release 4.1 message format from the SOR via the CDLIS Common | |
| |Validation Processor for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOI and the SOR is Release 5.1, then the PennDOT | |
| |system will receive a HB/CD04 Release 5.1 message format from the SOR via the CDLIS Common | |
| |Validation Processor for the Name. | |
|3.2.3.22 |SB: SOI ( SOR |MSD (CD04), pg. 94 |
| |CD04 | |
| |During the transition period, when PennDOT is the SOR and the SOI is using Release 5.1, then the | |
| |PennDOT system will receive both a SB/CD04 release 4.1 and a Release 5.1 message format from the SOI| |
| |for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI is using release 4.1, then the | |
| |PennDOT system will receive a SB/CD04 release 4.1 message format from the SOI for the name. | |
|3.2.3.23 |HB: SOR ( CDLIS Common Validation Processor ( SOI |MSD (CD04), pg. 94 |
| |CD04 | |
| |During the transition period, when PennDOT is the SOR and the SOI is using release 4.1, then PennDOT| |
| |will send a HB/CD04 release 4.1 message format to the SOI (via the CDLIS Common Validation | |
| |Processor) for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI is using Release 5.1, then PennDOT| |
| |will send a HB/CD04 Release 5.1 message format to the SOI (via the CDLIS Common Validation | |
| |Processor) for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI did not provide any name in the SB| |
| |message, then PennDOT will send both a HB/CD04 release 4.1 and Release 5.1 message format to the SOI| |
| |(via the CDLIS Common Validation Processor) for the Name. | |
|3.2.3.24 |IK: SOI ( CDLIS |MSD (CD05), pg. 99 |
| |CD05 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send an IK/CD05 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.25 |HC: SOR ( SOI |MSD (CD05), pg. 99 |
| |CD05 | |
| |During the transition period, when PennDOT is the SOI and the SOR is release 4.1, then the PennDOT | |
| |system will receive a HC/CD05 release 4.1 message format from the SOR for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOI and the SOR is Release 5.1, then the PennDOT | |
| |system will receive a HC/CD05 Release 5.1 message format from the SOR for the Name. | |
|3.2.3.26 |RD: CDLIS ( SOI |MSD (CD05), pg. 99 |
| |CD05 | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will receive a | |
| |RD/CD05 Release 5.1 message format from CDLIS for the Name. | |
|3.2.3.27 |SC: CDLIS ( SOR |MSD (CD05), pg. 99 |
| |CD05 | |
| |During the transition period, when PennDOT is the SOR and the SOI is using release 4.1, then the | |
| |PennDOT system will receive a SC/CD05 release 4.1 message format from CDLIS for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the SOI is using Release 5.1, then the | |
| |PennDOT system will receive a SC/CD05 Release 5.1 message format from CDLIS for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the name is not present, then the PennDOT | |
| |system will receive both a SC/CD05 release 4.1 and Release 5.1 message format from CDLIS for the | |
| |Name. | |
|3.2.3.28 |HC: SOR ( SOI |MSD (CD05), pg. 99 |
| |CD05 | |
| |During the transition period, when PennDOT is the SOR and a SOI is using release 4.1, then the | |
| |PennDOT system will send a HC/CD05 release 4.1 message format to the SOI for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and a SOI is using Release 5.1, then the | |
| |PennDOT system will send a HC/CD05 Release 5.1 message format to the SOI for the Name. | |
| | | |
| |During the transition period, when PennDOT is the SOR and the name is not present on the SC message,| |
| |then the PennDOT system will send both a HC/CD05 release 4.1 and Release 5.1 message format to the | |
| |SOI for the Name. | |
|3.2.3.29 |UA: SOR ( CDLIS |MSD (CD07), pg. 121 |
| |CD07 | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will send a UA/CD07 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.30 |UD: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |During the transition period, when PennDOT is the New SOR, then the PennDOT system will send a |Pg.134-167(CD08) |
| |UD/CD08 Release 5.1 message format to CDLIS for the Name. |MSD Appendix A |
| | |MSD Appendix D |
|3.2.3.31 |CC: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |During the transition period, when PennDOT is the New SOR, then the PennDOT system will send a |Pg.134-167(CD08) |
| |CC/CD08 Release 5.1 message format to CDLIS for the Name. |MSD Appendix A |
| | |MSD Appendix D |
|3.2.3.32 |HD: Old SOR (CDLIS Common Validation Processor ( New SOR |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |During the transition period, when PennDOT is the New SOR and the Old State of Record is using |Pg.134-167(CD08) |
| |release 4.1, then the PennDOT system will receive a HD/CD08 release 4.1 message format from the Old |MSD Appendix A |
| |SOR (via the CDLIS Common Validation Processor) for the Name. |MSD Appendix D |
| | | |
| |During the transition period, when PennDOT is the New SOR and the Old State of Record is using | |
| |Release 5.1, then the PennDOT system will receive a HD/CD08 Release 5.1 message format from the Old| |
| |SOR (via the CDLIS Common Validation Processor) for the Name. | |
|3.2.3.33 |HD: Old SOR (CDLIS Common Validation Processor ( New SOR |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |During the transition period, when PennDOT is the Old SOR and a New SOR is using release 4.1, then |Pg.134-167(CD08) |
| |the PennDOT system will send a HD/CD08 release 4.1 message format to the New SOR (via the CDLIS |MSD Appendix A |
| |Common Validation Processor) for the Name. |MSD Appendix D |
| | | |
| |During the transition period, when PennDOT is the Old SOR and a New SOR is using Release 5.1, then | |
| |the PennDOT system will send a HD/CD08 Release 5.1 message format to the New SOR (via the CDLIS | |
| |Common Validation Processor) for the Name. | |
|3.2.3.34 |NF: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 – Change State of Record |MSD |
| |During the transition period, when PennDOT is the Old SOR, then the PennDOT system will receive a |Pg.134-167(CD08) |
| |NF/CD08 Release 5.1 message format from CDLIS for the Name. |MSD Appendix A |
| | |MSD Appendix D |
|3.2.3.35 |SD: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 – Change State of Record |MSD |
| |During the transition period, when PennDOT is the Old SOR and the New SOR is using release 4.1, then|Pg.134-167(CD08) |
| |the PennDOT system will receive a SD/CD08 release 4.1 message format from CDLIS for the Name. |MSD Appendix A |
| | |MSD Appendix D |
| |During the transition period, when PennDOT is the Old SOR and the New SOR is using Release 5.1, then|CDLIS R5 CSOR 201002 |
| |the PennDOT system will receive a SD/CD08 Release 5.1 message format from CDLIS for the Name. |webinar notes, pg. 13-14 |
|3.2.3.36 |SD: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 – Automated Re-drive |MSD |
| |During the transition period, when PennDOT is the Old SOR, then the PennDOT system will receive a |Pg.134-167(CD08) |
| |SD/CD08 Release 5.1 message format from CDLIS for the Name. |MSD Appendix A |
| | |MSD Appendix D |
|3.2.3.37 |UC: SOR ( CDLIS |MSD (CD09), pg. 170 |
| |CD09 Change Data | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will send a UC/CD09 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.38 |UE: SOR ( CDLIS |MSD (CD10), pg. 188 |
| |CD10 Delete Master Pointer Record | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will send a UE/CD10 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.39 |HA: SOC ( CDLIS |MSD (CD11), pg. 199 |
| |CD11 Report OOS (Out of State) Conviction | |
| |During the transition period, when PennDOT is the State of Conviction, then the PennDOT system will | |
| |send a HA/CD11 Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.40 |HF: CDLIS ( SOR |MSD (CD11), pg. 199 |
| |CD11 Process OOS (Out of State) Conviction | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will receive a | |
| |HF/CD11 Release 5.1message format from CDLIS for the Name. | |
|3.2.3.41 |HH: SOC ( CDLIS |MSD (CD12), pg. 219 |
| |CD12 Negate OOS (Out of State) Conviction | |
| |During the transition period, when PennDOT is the State of Conviction, then the PennDOT system will | |
| |send a HH/CD12 Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.42 |HX: CDLIS ( SOR |MSD (CD12), pg. 219 |
| |CD12 Negate OOS (Out of State) Conviction | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will receive a | |
| |HX/CD12 Release 5.1message format from CDLIS for the Name. | |
|3.2.3.43 |UG: SOR ( CDLIS |MSD (CD14), pg. 235 |
| |CD14 Mark Driver Unique | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will send a UG/CD14 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.44 |UK: SOR ( CDLIS |MSD (CD15), pg. 245 |
| |CD15 Update AKA Data | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will send a UK/CD15 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.45 |HW: SOW ( CDLIS |MSD (CD16), pg. 261 |
| |CD16 Report OOS Withdraw | |
| |During the transition period, when PennDOT is the State of Withdraw, then the PennDOT system will | |
| |send a HW/CD16 Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.46 |HT: CDLIS ( SOR |MSD (CD16), pg. 261 |
| |CD16 Report OOS Withdraw | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will receive a | |
| |HT/CD16 Release 5.1 message format from CDLIS for the Name. | |
|3.2.3.47 |HY: SOW ( CDLIS |MSD (CD17), pg. 285 |
| |CD17 Negate OOS Withdraw | |
| |During the transition period, when PennDOT is the State of Withdraw, then the PennDOT system will | |
| |send a HY/CD17 Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.48 |HV: CDLIS ( SOR |MSD (CD17), pg. 285 |
| |CD17 Negate OOS Withdraw | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will receive a | |
| |HV/CD17 Release 5.1 message format from CDLIS for the Name. | |
|3.2.3.49 |EM: SOI ( CDLIS |MSD (CD30), pg. 420 |
| |CD30 CDLIS Batch Inquiry | |
| |During the transition period, when PennDOT is the SOI, then the PennDOT system will send a EM/CD30 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.50 |DQ: SOR ( CDLIS |MSD (CD31), pg. 442 |
| |CD31 MPR Data Quality Validation and Verification (V&V) | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will send a DQ/CD31 | |
| |Release 5.1 message format to CDLIS for the Name. | |
|3.2.3.51 |NA: CDLIS ( SOR |MSD (CDA1), pg. 313 |
| |CDA1 Duplicate Driver Process | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will receive a | |
| |NA/CDA1 Release 5.1 message format from CDLIS for the Name. | |
|3.2.3.52 |NE: CDLIS ( SOR |MSD (CDA1), pg. 313 |
| |CDA1 Duplicate Driver Process | |
| |During the transition period, when PennDOT is the SOR, then the PennDOT system will receive a | |
| |NE/CDA1 Release 5.1 message format from CDLIS for the Name. | |
4 Backward Compatibility – Sex Field
For a complete description of the CDLIS transaction flow, please refer to “Appendix C – CDLIS Transaction Diagrams” when reviewing the requirements in this section.
Assumptions
• CDLIS R5 Imp Planning-Pg. 10:
“Sex will be eliminated after ALL jurisdictions are operating CDLIS Release 5.1”
• CDLIS R5 Overview-Pg 34: Removal of sex
“Sex field maintained at the CDLIS Central Site during transition; thus included on messages to the Central Site. Sex field will not be sent by the Central Site on any message. Sex field included as usual on messages between jurisdictions.”
• CDLIS R5 Overview-Pg44: Removal of sex
“When the SOR has implemented CDLIS Release 5.1, sex will not be sent on the SC”
|ID |Requirement Statement |Source |
|3.2.4.1 |RD: CDLIS ( SOI |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD01/RD message from the CDLIS |MSD Appendix A |
| |Central Site that will exclude the following fields as of CDLIS Central Site Day 1 (projected |MSD Appendix D |
| |date-Dec 2010). | |
| | | |
| |RD Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.2 |SC: CDLIS ( SOR |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD01/SC Status Request message from |MSD Appendix A |
| |the CDLIS Central Site that will exclude the following fields as of CDLIS Central Site Day 1 |MSD Appendix D |
| |(projected date-Dec 2010). | |
| | | |
| |SC Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.3 |RD: CDLIS ( SOI |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD02/RD message from the CDLIS |MSD Appendix A |
| |Central Site that will exclude the following fields as of CDLIS Central Site Day 1 (projected |MSD Appendix D |
| |date-Dec 2010). | |
| | | |
| |RD Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.4 |SC: CDLIS ( SOR |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD02/SC Status Request message from |MSD Appendix A |
| |the CDLIS Central Site that will exclude the following fields as of CDLIS Central Site Day 1 |MSD Appendix D |
| |(projected date-Dec 2010). | |
| | | |
| |SC Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.5 |RD: CDLIS ( SOI |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD05/RD message from the CDLIS |Pg.97-108(CD05) |
| |Central Site that will exclude the following fields as of CDLIS Central Site Day 1 (projected |MSD Appendix A |
| |date-Dec 2010). |MSD Appendix D |
| | | |
| |RD Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.6 |SC: CDLIS ( SOR |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD05/SC message from the CDLIS |Pg.97-108(CD05) |
| |Central Site that will exclude the following fields as of CDLIS Central Site Day 1 (projected |MSD Appendix A |
| |date-Dec 2010). |MSD Appendix D |
| | | |
| |SC Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.7 |UA: SOR ( CDLIS |MSD |
| |CD07 |Pg.119-133(CD07) |
| |When PennDOT is the SOR, the DL&C System will send a CD07/UA message to CDLIS that will exclude the|MSD Appendix A |
| |following fields once all jurisdictions have converted to CDLIS Release 5.1 (projected date – Jan 30|MSD Appendix D |
| |2012). | |
| | | |
| |UA Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.8 |CC: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |When PennDOT is the New SOR, the DL&C System will send a CC/CD08 message to CDLIS that will exclude |Pg.134-167(CD08) |
| |the following fields once all jurisdictions have converted to CDLIS Release 5.1 (projected date – |MSD Appendix A |
| |Jan 30 2012). |MSD Appendix D |
| | | |
| |CC Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.9 |SD: CDLIS Central Site ( Old SOR |SPM; Pg. 41-47 |
| |CD08 – Change State of Record |MSD |
| |When PennDOT is the Old SOR, the DL&C System will receive/process a CD08/SD message sent from the |Pg.134-167(CD08) |
| |CDLIS Central Site that will exclude the following fields as of CDLIS Central Site Day 1 (projected |MSD Appendix A |
| |date-Dec 2010). |MSD Appendix D |
| | | |
| |SD Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.10 |UD: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |When PennDOT is the New SOR, the DL&C System will send a CD08/UD message to CDLIS that will exclude|Pg.134-167(CD08) |
| |the following fields once all jurisdictions have converted to CDLIS Release 5.1 (projected date – |MSD Appendix A |
| |Jan 30 2012). |MSD Appendix D |
| | | |
| |UD Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.11 |UC: SOR ( CDLIS |MSD |
| |CD09 Change Data |Pg.168-185(CD09) |
| |When PennDOT is the SOR, the DL&C System will send a CD09/UC Change Data message to the CDLIS |MSD Appendix A |
| |Central Site that will exclude the following fields once all jurisdictions have converted to CDLIS |MSD Appendix D |
| |Release 5.1 (projected date – Jan 30 2012). | |
| | | |
| |UC Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.12 |UE: SOR ( CDLIS |MSD |
| |CD10 Delete Master Pointer Record |Pg.186-194(CD10) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will send a CD010/UE Delete Master Pointer Record message |MSD Appendix D |
| |to the CDLIS Central Site that will exclude the following fields once all jurisdictions have | |
| |converted to CDLIS Release 5.1 (projected date – Jan 30 2012). | |
| | | |
| |UE Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.13 |HF: CDLIS ( SOR |MSD |
| |CD11 Process OOS (Out of State) Conviction |Pg.195-215(CD11) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD011/HF Report OOS Conviction |MSD Appendix D |
| |message from the CDLIS Central Site that will exclude the following fields as of CDLIS Central Site | |
| |Day 1 (projected date-Dec 2010). | |
| | | |
| |HF Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.14 |HX: CDLIS ( SOR |MSD |
| |CD12 Negate OOS (Out of State) Conviction |Pg.216-232(CD12) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD12/HX Negate OOS Conviction |MSD Appendix D |
| |message from the CDLIS Central Site | |
| |that will exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010). | |
| | | |
| |HX Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.15 |HT: CDLIS ( SOR |MSD |
| |CD16 Report OOS Withdraw |Pg.257-281(CD16) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD16/HT Report OOS Withdraw message |MSD Appendix D |
| |from the CDLIS Central Site | |
| |that will exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010). | |
| | | |
| |HT Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.16 |HV: CDLIS ( SOR |MSD |
| |CD17 Negate OOS Withdraw |Pg.282-309(CD17) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD17/HV Negate OOS Withdraw message |MSD Appendix D |
| |from the CDLIS Central Site | |
| |that will exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010). | |
| | | |
| |HV Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.17 |QD: CDLIS ( SOI | |
| |CD30 CDLIS Batch Inquiry | |
| | | |
| |When PennDOT is the SOI, PennDOT will receive/process a CD30/QD message from the CDLIS Central Site | |
| |that will exclude the following fields as of CDLIS Central Site Day 1 (projected date-Dec 2010). | |
| | | |
| |QD Message Type | |
| |DRIVER CURRENT SEX | |
|3.2.4.18 |NA: CDLIS ( SOR |MSD |
| |CDA1 Duplicate Driver Process |Pg.310-332(CDA1) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CDA1/NA CDLIS Possible Duplicate |MSD Appendix D |
| |message from the CDLIS Central Site that will exclude the following fields as of CDLIS Central Site | |
| |Day 1 (projected date-Dec 2010). | |
| | | |
| |NA Message Type | |
| |DRIVER CURRENT SEX | |
| |DRIVER DUPLICATE SEX | |
|3.2.4.19 |NE: CDLIS ( SOR |MSD |
| |CDA1 Duplicate Driver Process |Pg.310-332(CDA1) |
| | |MSD Appendix A |
| |When PennDOT is the SOR, the DL&C System will receive/process a CDA1/NE CDLIS Duplicate Resolved |MSD Appendix D |
| |message from the CDLIS Central Site that will exclude the following fields as of CDLIS Central Site | |
| |Day 1 (projected date-Dec 2010). | |
| | | |
| |NE Message Type | |
| |DRIVER CURRENT SEX | |
| |DRIVER DUPLICATE SEX | |
5 Backward Compatibility – Partial SSN
For a complete description of the CDLIS transaction flow, please refer to “Appendix C – CDLIS Transaction Diagrams” when reviewing the requirements in this section.
Assumptions
• CDLIS R5 Overview-Pg 36: SSN Last 5 Digits
“SSN sent to the CDLIS Central Site and between jurisdictions without change. Messages with SSN between jurisdictions will not change.
• CDLIS R5 Imp Planning-Pg 11: SSN Last 5 Digits
“The full 9 digit SSN will continue to be sent to the CDLIS Central Site.”
|ID |Requirement Statement |Source |
|3.2.5.1 |RD: CDLIS ( SOI |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD01/RD message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |RD Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.2 |SC: CDLIS ( SOR |SPM; Pg. 22-24 |
| |CD01 |MSD 51-62(CD01) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD01/SC message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |SC Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.3 |RD: CDLIS ( SOI |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD02/RD message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |RD Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.4 |SC: CDLIS ( SOR |SPM; Pg. 25-27 |
| |CD02 |MSD 63-75(CD02) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD02/SC message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |SC Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.5 |RD: CDLIS ( SOI |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOI, the DL&C System will receive/process a CD05/RD message from CDLIS that will|Pg.97-108(CD05) |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix A |
| | |MSD Appendix D |
| |RD Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.6 |SC: CDLIS ( SOR |SPM; Pg. 34-36 |
| |CD05 |MSD |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD05/SC message from CDLIS that will|Pg.97-108(CD05) |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix A |
| | |MSD Appendix D |
| |SC Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.7 |NF: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 |MSD |
| |When PennDOT is the Old SOR, the DL&C System will receive/process a CD08/NF message from CDLIS that |Pg.134-167(CD08) |
| |will include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix A |
| | |MSD Appendix D |
| |NF Message Type | |
| |DRIVER OLD SOCIAL SECURITY NUMBER | |
|3.2.5.8 |SD: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 |MSD |
| |When PennDOT is the Old SOR, the DL&C System will receive/process a CD08/SD message from CDLIS that |Pg.134-167(CD08) |
| |will include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix A |
| | |MSD Appendix D |
| |SD Message Type | |
| |DRIVER OLD SOCIAL SECURITY NUMBER | |
| |DRIVER SSN-CDLIS | |
|3.2.5.9 |HF: CDLIS ( SOR |MSD |
| |CD11 |Pg.195-215(CD11) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD11/HF message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |HF Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.10 |HX: CDLIS ( SOR |MSD |
| |CD12 |Pg.216-232(CD12) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD12/HX message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |HX Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.11 |HT: CDLIS ( SOR |MSD |
| |CD16 |Pg.257-281(CD16) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD16/HT message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |HT Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.12 |HV: CDLIS ( SOR |MSD |
| |CD17 |Pg.282-309(CD17) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CD17/HV message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |HV Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.13 |QD: CDLIS ( SOI | |
| |CD30 CDLIS Batch Inquiry | |
| | | |
| |When PennDOT is the SOI, PennDOT will receive/process a CD30/QD message from CDLIS that will include| |
| |the last 5 digits of the SSN, rather than the full 9 digit SSN. | |
| | | |
| |QD Message Type | |
| |DRIVER SSN-CDLIS | |
|3.2.5.14 |NA: CDLIS ( SOR |MSD |
| |CDA1 |Pg.310-332(CDA1) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CDA1/NA message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |NA Message Type | |
| |DRIVERS DUPLICATE SSN | |
| |DRIVER SSN-CDLIS | |
|3.2.5.15 |NE: CDLIS ( SOR |MSD |
| |CDA1 |Pg.310-332(CDA1) |
| |When PennDOT is the SOR, the DL&C System will receive/process a CDA1/NE message from CDLIS that will|MSD Appendix A |
| |include the last 5 digits of the SSN, rather than the full 9 digit SSN. |MSD Appendix D |
| | | |
| |NE Message Type | |
| |DRIVERS DUPLICATE SSN | |
| |DRIVER SSN-CDLIS | |
6 Change State of Record (CSOR)
This section includes all changes to the messages related to a change state of record transaction including the new on-demand re-drive and scheduled re-drive. For a complete description of the CDLIS transaction flow, please refer to “Appendix C – CDLIS Transaction Diagrams” when reviewing the requirements in this section.
The on-demand re-drive is an OPTIONAL piece of CDLIS Release 5.1 – from the perspective of the initiator of the message. The SR message is a mechanism for either the NSOR or the OSOR to re-drive the SD message.
|ID |Requirement Statement |Source |
|3.2.6.1 |UD: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |When PennDOT is the New SOR, the DL&C System will send a CD08/UD message to CDLIS that, if |Pg.134-167(CD08) |
| |applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |UD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAME TRANSLIT CODE | |
|3.2.6.2 |CC: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |When PennDOT is the New SOR, the DL&C System will send a CD08/CC message to CDLIS that, if |Pg.134-167(CD08) |
| |applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |CC Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAME TRANSLIT CODE | |
|3.2.6.3 |HD: Old SOR (CDLIS Common Validation Processor ( New SOR |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |When PennDOT is the New SOR, the DL&C System will receive/process a CD08/HD message sent from the |Pg.134-167(CD08) |
| |Old SOR via the CDLIS Common Validation Processor that, if applicable*, will include the following |MSD Appendix A |
| |CDLIS modernization fields: |MSD Appendix D |
| | | |
| |HD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.6.4 |HD: Old SOR (CDLIS Common Validation Processor ( New SOR |SPM; Pg. 41-47 |
| |CD08 Change State of Record |MSD |
| |When PennDOT is the Old SOR, the DL&C System will send a CD08/HD message to the New SOR via the |Pg.134-167(CD08) |
| |CDLIS Common Validation Processor that, if applicable*, will include the following CDLIS |MSD Appendix A |
| |modernization fields: |MSD Appendix D |
| | | |
| |HD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.6.5 |NF: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 – Change State of Record |MSD |
| |When PennDOT is the Old SOR, the DL&C System will receive/process a CD08/NF message sent from the |Pg.134-167(CD08) |
| |CDLIS Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |NF Message Type | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAME TRANSLIT CODE | |
|3.2.6.6 |SD: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 – Change State of Record |MSD |
| |When PennDOT is the Old SOR, the DL&C System will receive/process a CD08/SD message sent from the |Pg.134-167(CD08) |
| |CDLIS Central Site that, if applicable*, will include the following CDLIS modernization fields: |MSD Appendix A |
| | |MSD Appendix D |
| |SD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAME TRANSLIT CODE | |
|3.2.6.7 |SD: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 – On Demand Re-drive |MSD |
| |When PennDOT is the Old SOR, the DL&C System will receive/process a CD08 On Demand Re-drive/SD |Pg.134-167(CD08) |
| |message sent from the CDLIS Central Site that, if applicable*, will include the following CDLIS |MSD Appendix A |
| |modernization fields: |MSD Appendix D |
| |SD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAME TRANSLIT CODE | |
|3.2.6.8 |SR: New SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 – On Demand Re-drive |MSD |
| |When PennDOT is the New SOR, the DL&C System will send the new CD08 On Demand Re-drive/SR message to|Pg.134-167(CD08) |
| |the CDLIS Central Site consisting of the following CDLIS fields. |MSD Appendix A |
| | |MSD Appendix D |
| |NOTE: The highlighted fields are the new fields. | |
| | | |
| |SR Message Type | |
| |MESSAGE LENGTH | |
| |MESSAGE DESTINATION | |
| |MESSAGE ORIGIN | |
| |MESSAGE DATE | |
| |MESSAGE TIME | |
| |MESSAGE SEQUENCE ID | |
| |APPLICATION ID | |
| |MESSAGE TYPE | |
| |SEGMENT SEQUENCE NUMBER | |
| |LAST SEGMENT INDICATOR | |
| |NUMBER OF TEXT BLOCKS COUNT | |
| |NETWORK SESSION INDICATOR | |
| |TEST/PRODUCTION INDICATOR | |
| |TRANSMIT MODE CODE | |
| |NCB ERROR CODE | |
| |TRANSACTION ORIGINATOR | |
| |NETWORK STATUS | |
| |APPLICATION STATUS | |
| |MESSAGE LOCATOR/HEADER | |
| |PROCESSING STATUS | |
| |MESSAGE SENDER PASSWORD | |
| |SYSTEM RELEASE CODE | |
| |DL OLD JURISDICTION NUMBER | |
| |DRIVER LICENSE JURIS NUMBER | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAMETRANSLIT CODE | |
| |ERROR BLOCK OUT | |
|3.2.6.9 |SR: Old SOR ( CDLIS |SPM; Pg. 41-47 |
| |CD08 – On Demand Re-drive |MSD |
| |When PennDOT is the Old SOR, the DL&C System will send the new CD08 On Demand Re-drive/SR message to|Pg.134-167(CD08) |
| |the CDLIS Central Site consisting of the following CDLIS fields. |MSD Appendix A |
| | |MSD Appendix D |
| |NOTE: The highlighted fields are the new fields. | |
| | | |
| |SR Message Type | |
| |MESSAGE LENGTH | |
| |MESSAGE DESTINATION | |
| |MESSAGE ORIGIN | |
| |MESSAGE DATE | |
| |MESSAGE TIME | |
| |MESSAGE SEQUENCE ID | |
| |APPLICATION ID | |
| |MESSAGE TYPE | |
| |SEGMENT SEQUENCE NUMBER | |
| |LAST SEGMENT INDICATOR | |
| |NUMBER OF TEXT BLOCKS COUNT | |
| |NETWORK SESSION INDICATOR | |
| |TEST/PRODUCTION INDICATOR | |
| |TRANSMIT MODE CODE | |
| |NCB ERROR CODE | |
| |TRANSACTION ORIGINATOR | |
| |NETWORK STATUS | |
| |APPLICATION STATUS | |
| |MESSAGE LOCATOR/HEADER | |
| |PROCESSING STATUS | |
| |MESSAGE SENDER PASSWORD | |
| |SYSTEM RELEASE CODE | |
| |DL OLD JURISDICTION NUMBER | |
| |DRIVER LICENSE JURIS NUMBER | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAMETRANSLIT CODE | |
| |ERROR BLOCK OUT | |
|3.2.6.10 |SD: CDLIS ( Old SOR |SPM; Pg. 41-47 |
| |CD08 – Automated Re-drive |MSD |
| |When PennDOT is the Old SOR, the DL&C System will receive/process a CD08 Automated Re-drive/SD |Pg.134-167(CD08) |
| |message sent from the CDLIS Central Site that, if applicable*, will include the following CDLIS |MSD Appendix A |
| |modernization fields: |MSD Appendix D |
| |SD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON OLD LAST NAME | |
| |PERSON OLD FIRST NAME | |
| |PERSON OLD MIDDLE NAME | |
| |DRIVER OLD NAME SUFFIX | |
| |PERSON OLD LAST NAME TRUNCATION CODE | |
| |PERSON OLD FIRST NAME TRUNCATION | |
| |PERSON OLD MIDDLE NAME TRUNCATION | |
| |PERSON OLD LAST NAME TRANSLIT | |
| |PERSON OLD FIRST NAME TRANSLIT CODE | |
| |PERSON OLD MIDDLE NAME TRANSLIT CODE | |
7 Data Cleanup
For a complete description of the CDLIS transaction flow, please refer to “Appendix C – CDLIS Transaction Diagrams” when reviewing the requirements in this section.
|ID |Requirement Statement |Source |
|3.2.7.1 |EM: SOI ( CDLIS | |
| |CD30 CDLIS Batch Inquiry | |
| | | |
| |When PennDOT is the SOI, PennDOT will send a CD30/EM Batch Inquiry file to the CDLIS Central Site | |
| |that will include the following CDLIS modernization fields: | |
| | | |
| |EM Message Type | |
| | | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.7.2 |QD: CDLIS ( SOI | |
| |CD30 CDLIS Batch Inquiry | |
| | | |
| |When PennDOT is the SOI, PennDOT will receive/process a CD30/QD Batch Inquiry File from CDLIS that | |
| |will include the following CDLIS modernization fields: | |
| | | |
| |QD Message Type | |
| |PERSON LAST NAME | |
| |PERSON FIRST NAME | |
| |PERSON MIDDLE NAME | |
| |PERSON NAME SUFFIX | |
| |PERSON FIRST NAME TRUNCATION CODE | |
| |PERSON MIDDLE NAME TRUNCATION CODE | |
| |PERSON LAST NAME TRUNCATION CODE | |
| |PERSON FIRST NAME TRANSLITERATION | |
| |PERSON MIDDLE NAME TRANSLITERATION | |
| |PERSON LAST NAME TRANSLITERATION | |
| |PERSON AKA LAST NAME | |
| |PERSON AKA FIRST NAME | |
| |PERSON AKA MIDDLE NAME | |
| |DRIVER AKA NAME SUFFIX | |
| |PERSON AKA LAST NAME TRUNCATION CODE | |
| |PERSON AKA FIRST NAME TRUNCATION | |
| |PERSON AKA MIDDLE NAME TRUNCATION | |
| |PERSON AKA LAST NAME TRANSLIT | |
| |PERSON AKA FIRST NAME TRANSLIT CODE | |
| |PERSON AKA MIDDLE NAME TRANSLIT CODE | |
|3.2.7.3 |DQ: SOR ( CDLIS | |
| |CD31 MPR Data Quality Validation and Verification (V&V) | |
| | | |
| |When PennDOT is the SOR, PennDOT will send a CD31/DQ message to the CDLIS Central Site that, if | |
| |applicable*, will include the following CDLIS modernization fields: | |
| | | |
| |DQ Message Type | |
| | | |
| |MESSAGE LENGTH | |
| |MESSAGE DESTINATION | |
| |MESSAGE ORIGIN | |
| |MESSAGE DATE | |
| |MESSAGE TIME | |
| |MESSAGE SEQUENCE ID | |
| |APPLICATION ID | |
| |MESSAGE TYPE | |
| |SEGMENT SEQUENCE NUMBER | |
| |LAST SEGMENT INDICATOR | |
| |NUMBER OF TEXT BLOCKS COUNT | |
| |NETWORK SESSION INDICATOR | |
| |TEST/PRODUCTION INDICATOR | |
| |TRANSMIT MODE CODE | |
| |NCB ERROR CODE | |
| |TRANSACTION ORIGINATOR | |
| |NETWORK STATUS | |
| |APPLICATION STATUS | |
| |DRIVER DATA RECORD TYPE | |
| |JURISDICTION CODE – LICENSING | |
| |RECORD AS OF DATE | |
| |RECORD AS OF TIME | |
| |DRIVER COUNT | |
| |RECORD COUNT | |
| |DRIVER SSN START RANGE | |
| |DRIVER SSN END RANGE | |
| |DRIVER LICENSE NUMBER START RANGE | |
| |DRIVER LICENSE NUMBER END RANGE | |
| |MESSAGE LOCATOR/HEADER | |
Detail Change Tracking Log
|# |Section |Page |Change |Change Description |Version |
| | | |Date | | |
|2 |3.1.2 Medical Certificates |Pg. 23 |6/4/2010 |Removed “SPE” from requirement 3.1.2.1.9 due to the fact that the |v1.0 |
| | | | |FMCSA confirmed that it is not a valid choice for Waiver/Exemption | |
| | | | |Type. | |
|3 |3.1.3 Variances |Pg. 24 |6/4/2010 |Removed requirements 3.1.3.1.1 and 3.1.3.1.2 due to the fact that |v1.0 |
| | | | |they are no longer valid (i.e. SPE is not a valid Waiver/Exemption | |
| | | | |Type). | |
|4 |3.1.4 Licensing Transactions |Pg. 25 |6/4/2010 |Added verbiage to requirement 3.1.4.1 to specify that the DL&C |v1.0 |
| | | | |system will perform that same certification check that occurs | |
| | | | |during the nightly batch process (i.e. referred to in the | |
| | | | |Supplementary Requirements Specification). | |
|5 |3.1.4 Licensing Transactions |Multiple |6/4/2010 |Added sub-requirements to each requirement in this section to |v1.0 |
| | | | |specify what the DL&C actions are when a driver is determined to be| |
| | | | |“certified” or “not certified”. Requirements include counter mode | |
| | | | |and mail mode. | |
|6 |3.1.5 Downgrades |Pg. 28 |6/4/2010 |Changed verbiage in requirement 3.1.5.4 to read “downgrade license |v1.0 |
| | | | |to non-commercial”. This replaces the verbiage that specified a | |
| | | | |drop to a class “C” license. | |
|7 |3.1.9 Correspondence |Pg. 32 |6/4/2010 |Changed verbiage in requirement 3.1.9.3 (and sub-requirements) to |v1.0 |
| | | | |specify that the rejection letter generated for drivers who are | |
| | | | |“not certified” will be an update to the existing Combination | |
| | | | |Rejection letter already generated by the DL&C system. | |
|8 |3.1.10 CDLIS 5.1 Medical |Multiple |6/4/2010 |Renumbered the requirements in this section to make them consistent|v1.0 |
| |Certification Transactions | | |with the section heading. | |
|9 |3.1.10 CDLIS 5.1 Medical |Pg. 36 |6/4/2010 |Added references to the sources section to indicate which sections |v1.0 |
| |Certification Transactions | | |of the MSD list what medical certification information must be sent| |
| | | | |to CDLIS and/or SOIs. | |
|10 |1.2 Scope |Pg. 6 |6/14/2010 |Added bullets to document the in scope items related to the CDLIS |v1.1 |
| | | | |Modernization areas of the study. | |
|11 |1.3 Definitions, Acronyms, and |Pg. 7 |6/14/2010 |Added Common Validation Process to the list of terms, definitions, |v1.1 |
| |Abbreviations | | |and acronyms. | |
|12 |3.1.1 Self-Certification |Pg. 23 |6/14/2010 |Added requirement 3.1.1.1.16 to specify that users will have the |v1.1 |
| | | | |ability to enter a driver’s self-certification type independently | |
| | | | |of a licensing transaction. | |
|13 |3.1.3 Variances |Pg. 24 |6/14/2010 |Updated requirement 3.1.3.1 and sub-requirements to specify that |v1.1 |
| | | | |the entry of variance information will not be tied to the entry of | |
| | | | |the medical examiner certificate restrictions. | |
|14 |3.1.3 Variances |Pg. 24 |6/14/2010 |Added requirement 3.1.3.1.5 to specify that the Waiver/Exemption |v1.1 |
| | | | |Type (valid values are Vision or Diabetes) will be added by users | |
| | | | |along with the other waiver/exemption information. | |
|15 |3.1.1 Self-Certification |Pg. 13 |6/29/2010 |Added requirement 3.1.1.6 to specify that the DL&C system will |v1.2 |
| | | | |require self-certification for re-issuances of a commercial driver | |
| | | | |license product (i.e. renewals, duplicates, and replacements). | |
Final System Requirements Specification Approval
Approval of the System Requirements Specification indicates acknowledgement that all system requirements identified during the requirement identification sessions conducted for the CDLIS Modernization Requirements Study have been documented correctly. It should be noted that additions and modifications to the system requirements may be identified during subsequent study or project activities.
Appendix A –Data Dictionary
1 Medical Certificate
All of the Medical Certificate fields that were added to Appendix D – Data Dictionary of the CDLIS Master Specs 5.1.0 have been included in 6.1 Medical Certificate.
|Element Code |Business Name |Technical Name, Type and Length |Description and Values |
|BMPJO1 |MEDICAL LICENSING JURISDICTION CODE |CLMF-MEDIC-JUR-CODE-1 |A medical licensing jurisdiction is an |
| | |AN |organization with the authority to license |
| | |2 |medical practitioners, who act as medical |
| | | |examiners. |
| | | | |
| | | |VALUE MEANING/DESCRIPTION |
| | | |See BJUCDE for a list of the U.S. Jurisdiction |
| | | |codes. |
|BMPLF1 |ME FIRST NAME TRANSLITERATION IND |CLMF-MEDIC-TRANS-1ST-1 |An indication if a medical examiner's first |
| | |AN |name has been transliterated. Transliteration |
| | |1 |refers to the practice of replacing non-English |
| | | |letters with comparable letters from the English |
| | | |alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N First name not transliterated |
| | | |T First name transliterated |
| | | |U Unknown if first name is transliterated |
|BMPLI1 |MEDICAL EXAMINER LICENSE |CLMF-MEDIC-NUM-1 |A jurisdiction assigned number used to identify |
| |NUMBER |AN |the license of medical practitioner who acts as a |
| | |14 |medical examiner. |
|BMPLL1 |ME LAST NAME TRANSLITERATION |CLMF-MEDIC-TRANS-LAST-1 |An indication if a medical examiner's last |
| |IND |AN |name has been transliterated. Transliteration |
| | |1 |refers to the practice of replacing non-English |
| | | |letters with comparable letters from the English |
| | | |alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Last name not transliterated |
| | | |T Last name transliterated |
| | | |U Unknown if last name is transliterated |
|BMPLM1 |ME MIDDLE NAME |CLMF-MEDIC-TRANS-MID-1 |An indication if a medical examiner's middle |
| |TRANSLITERATION IND |AN |name has been transliterated. Transliteration |
| | |1 |refers to the practice of replacing non-English |
| | | |letters with comparable letters from the English |
| | | |alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Middle name not transliterated |
| | | |T Middle name transliterated |
| | | |U Unknown if middle name is transliterated |
|BMPNF1 |MEDICAL EXAMINER FIRST NAME |CLMF-MEDIC-NAME-1ST-1 |A first name of a medical examiner. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BMPNGP |MEDICAL EXAMINER NAME GROUP |NONE |A group of components that make up a name of |
| | |AN |a medical examiner. |
| | |146 |The group contains: |
| | | |- Medical Examiner First Name (BMPNF1) |
| | | |- Medical Examiner Middle Name (BMPNM1) |
| | | |- Medical Examiner Last Name (BMPNL1) |
| | | |- Medical Examiner Name Suffix (BMPNS1) |
| | | |- ME First Name Truncation Code (BMPTF1) |
| | | |- ME Middle Name Truncation Code |
| | | |(BMPTM1) |
| | | |- ME Last Name Truncation Code (BMPTL1) |
| | | |- ME First Name Transliteration Code |
| | | |(BMPLF1) |
| | | |- ME Middle Name Transliteration Code |
| | | |(BMPLM1) |
| | | |- ME Last Name Transliteration Code |
| | | |(BMPLL1) |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
|BMPNL1 |MEDICAL EXAMINER LAST NAME |CLMF-MEDIC-NAME-LAST-1 |A last name of a medical examiner. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BMPNM1 |MEDICAL EXAMINER MIDDLE |CLMF-MEDIC-NAME-MIDDLE-1 |A middle name of a medical examiner. |
| |NAME |AN |See the AAMVA Person Name Standard-2008 |
| | |35 |for the |
| | | |complete set of rules governing the format of a |
| | | |person's name. |
|BMPNRN |MEDICAL EXAMINER REGISTRY NUMBER |CLMF-MEDIC-REG-NUM |A number used as the identifier in a National |
| | |AN |Registry of Medical Examiners who issue |
| | |15 |Medical |
| | | |Certificates |
|BMPNS1 |MEDICAL EXAMINER NAME SUFFIX |CLMF-MEDIC-NAME-SFX-1 |A name suffix of a medical examiner. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |5 |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |JR Junior |
| | | |SR Senior |
| | | |I 1st |
| | | |II 2nd |
| | | |III 3rd |
| | | |IV 4th |
| | | |V 5th |
| | | |VI 6th |
| | | |VII 7th |
| | | |VIII 8th |
| | | |IX 9th |
| | | |1ST 1st |
| | | |2ND 2nd |
| | | |3RD 3rd |
| | | |4TH 4th |
| | | |5TH 5th |
| | | |6TH 6th |
| | | |7TH 7th |
| | | |8TH 8th |
| | | |9TH 9th |
|BMPSP1 |MEDICAL EXAMINER SPECIALTY |CLMF-MEDIC-SPECIALTY-1 |A code indicating the specialty of the medical |
| |CODE |AN |practitioner. |
| | |2 |VALUE MEANING/DESCRIPTION |
| | | |AN Advanced Practice Nurse |
| | | |CH Chiropractor |
| | | |DO Osteopathic Doctor |
| | | |MD Medical Doctor |
| | | |PA Physician Assistant |
|BMPTF1 |ME FIRST NAME TRUNCATION IND |CLMF-MEDIC-TRUNC-1ST-1 |An indication if a medical examiner's first |
| | |AN |name has been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N First name not truncated |
| | | |T First name truncated |
| | | |U Unknown if the first name is truncated |
|BMPTL1 |ME LAST NAME TRUNCATION IND |CLMF-MEDIC-TRUNC-LAST-1 |An indication if a medical examiner's last |
| | |AN |name has been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Last name not truncated |
| | | |T Last name truncated |
| | | |U Unknown if the last name is truncated |
|BMPTM1 |ME MIDDLE NAME TRUNCATION |CLMF-MEDIC-TRUNC-MID-1 |An indication if a medical examiner's middle |
| |IND |AN |name has been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Middle name not truncated |
| | | |T Middle name truncated |
| | | |U Unknown if the middle name is |
| | | |Truncated |
|BMPTP1 |MEDICAL EXAMINER TELEPHONE |CLMF-MEDIC-PHONE-NUM-1 |A telephone number at which a medical |
| |NUMBER |AN |examiner can be reached. |
| | |10 | |
|DDLSCT |CDL MEDICAL SELF CERTIFICATION |CLMF-MED-SELF-CERTIFICATION |A driver's self certification of the driver's |
| |CODE |AN |status regarding 49 CFR 390.3 and the type of |
| | |2 |driving. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |EA Excepted Intrastate |
| | | |EI Excepted Interstate |
| | | |NA Non-excepted Intrastate |
| | | |NI Non-excepted Interstate |
|DDLSED |DRIVER SPE EXPIRATION DATE |CLMF-SPE-EXP-DATE |The expiration date of the most recent variance |
| | |AN |of a medical certificate, due to a Skills |
| | |8 |Performance Evaluation. |
| | | |The data format is CCYYMMDD. |
|DDLSSD |DRIVER SPE EFFECTIVE DATE |CLMF-SPE-START-DATE |The start date of the most recent variance of |
| | |AN |a medical certificate, due to a Skills Performance Evaluation. |
| | |8 |The data format is CCYYMMDD. |
|DDLWED |DRIVER WAIVER/EXEMPT |CLMF-WE-EXP-DATE |The expiration date of the most recent variance |
| |EXPIRATION DATE |AN |of a medical certificate, due to a waiver or |
| | |8 |exemption. |
| | | |The data format is CCYYMMDD. |
|DDLWSD |DRIVER WAIVER/EXEMPT |CLMF-WE-START-DATE |The start date of the most recent variance of |
| |EFFECTIVE DATE |AN |a medical certificate, due to a waiver or |
| | |8 |exemption. |
| | | |The data format is CCYYMMDD |
|DMCCTC |MEDICAL CERTIFICATION STATUS |CLMF-MED-CERT-STATUS-CODE |An indication of the status of a driver's medical |
| |CODE |AN |certification. |
| | |1 |VALUE MEANING/DESCRIPTION |
| | | |C The driver is certified. |
| | | |N The driver is not certified. |
|DMCEDT |MEDICAL CERTIFICATE |CLMF-MED-CERT-EXP-DATE |A date on which a medical certificate expires. |
| |EXPIRATION DATE |AN |The data format is CCYYMMDD. |
| | |8 | |
|DMCPED |MEDICAL CERTIFICATE ISSUE DATE |CLMF-MED-CERT-ISS-DATE |A date on which a medical practitioner |
| | |AN |performed an examination and on which a |
| | |8 |medical certificate was subsequently issued. |
| | | |The data format is CCYYMMDD. |
|DMCRES |MEDICAL CERTIFICATE |CLMF-MED-CERT-RESTRICTION |A restriction imposed on a driver by a medical |
| |RESTRICTION CODE |AN |examiner. |
| | |1 |VALUE MEANING/DESCRIPTION |
| | | |1 Wearing corrective lenses |
| | | |2 Wearing hearing aid |
| | | |3 Accompanied by a waiver/exemption |
| | | |4 Driving within an exempt intra city zone |
| | | |5 Accompanied by a Skill Performance |
| | | |Evaluation certificate (SPE) |
| | | |6 Qualified by operation of 49 CFR |
| | | |391.64 |
2 CDLIS Modernization
All of the CDLIS Modernization fields that were added to Appendix D – Data Dictionary of the CDLIS Master Specs 5.1.0 have been included in 6.2 CDLIS Modernization.
|Element Code |Business Name |Technical Name, Type and Length |Description and Values |
|BPEDOB | PERSON DATE OF BIRTH |CLMF-PERSON-DOB |Date of birth of an individual. The format |
| | |AN |is CCYYMMDD |
| | |8 | |
|BPENF1 |PERSON OLD FIRST NAME |CLMF-PERSON-OLD-FIRST-NAME |An old first name of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENF2 |PERSON DUPLICATE FIRST NAME |CLMF-PERSON-DUP-FIRST-NAME |A duplicate first name of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENF3 |PERSON AKA FIRST NAME |CLMF-PERSON-AKA-FIRST-NAME |An AKA first name of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENFT |PERSON FIRST NAME |CLMF-PERSON-FIRST-NAME |A first name of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENG1 |PERSON OLD NAME GROUP |NONE |A group of components that make up an old |
| | |AN |name of a person. The group contains: |
| | |146 |- Person Old First Name (BPENF1) |
| | | |- Person Old Middle Name (BPENM1) |
| | | |- Person Old Last Name (BPENL1) |
| | | |- Person Old Name Suffix (BPENS1) |
| | | |- Person Old First Name Truncation Code |
| | | |(BPETF1) |
| | | |- Person Old Middle Name Truncation Code |
| | | |(BPETM1) |
| | | |- Person Old Last Name Truncation Code |
| | | |(BPETL1) |
| | | |- Person Old First Name Transliteration Code |
| | | |(BPERF1) |
| | | |- Person Old Middle Name Transliteration Code |
| | | |(BPERM1) |
| | | |- Person Old Last Name Transliteration Code |
| | | |(BPERL1) |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENG2 |PERSON DUPLICATE NAME GROUP |NONE |A group of components that make up a |
| | |AN |duplicate name of a person. The group contains: |
| | |146 |- Person Duplicate First Name (BPENF2) |
| | | |- Person Duplicate Middle Name (BPENM2) |
| | | |- Person Duplicate Last Name (BPENL2) |
| | | |- Person Duplicate Name Suffix (BPENS2) |
| | | |- Person Duplicate First Name Truncation Code |
| | | |(BPETF2) |
| | | |- Person Duplicate Middle Name Truncation |
| | | |(BPETM2) |
| | | |- Person Duplicate Last Name Truncation Code |
| | | |(BPETL2) |
| | | |- Person Dup First Name Transliteration Code |
| | | |(BPERF2) |
| | | |- Person Dup Middle Name Transliteration |
| | | |Code (BPERM2) |
| | | |- Person Dup Last Name Transliteration Code |
| | | |(BPERL2) |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENG3 |PERSON AKA NAME GROUP |NONE |A group of components that make up an AKA |
| | |AN |name of a person. The group contains: |
| | |146 |- Person AKA First Name (BPENF3) |
| | | |- Person AKA Middle Name (BPENM3) |
| | | |- Person AKA Last Name (BPENL3) |
| | | |- Person AKA Name Suffix (BPENS3) |
| | | |- Person AKA First Name Truncation Code |
| | | |(BPETF3) |
| | | |- Person AKA Middle Name Truncation Code |
| | | |(BPETM3) |
| | | |- Person AKA Last Name Truncation Code |
| | | |(BPETL3) |
| | | |- Person AKA First Name Transliteration Code |
| | | |(BPERF3) |
| | | |- Person AKA Middle Name Transliteration |
| | | |Code (BPERM3) |
| | | |- Person AKA Last Name Transliteration Code |
| | | |(BPERL3) |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENGP |PERSON NAME GROUP |NONE |A group of components that make up a name of |
| | |AN |a person. |
| | |146 |The group contains: |
| | | |- Person First Name (BPENFT) |
| | | |- Person Middle Name (BPENMD) |
| | | |- Person Last Name (BPENLT) |
| | | |- Person Name Suffix (BPENSX) |
| | | |- Person First Name Truncation Code |
| | | |(BPENTF) |
| | | |- Person Middle Name Truncation Code |
| | | |(BPENTM) |
| | | |- Person Last Name Truncation Code |
| | | |(BPENTL) |
| | | |- Person First Name Transliteration Code |
| | | |(BPENRF) |
| | | |- Person Middle Name Transliteration Code |
| | | |(BPENRM) |
| | | |- Person Last Name Transliteration Code |
| | | |(BPENRL) |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENL1 |PERSON OLD LAST NAME |CLMF-PERSON-OLD-LAST-NAME |An old last name of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENL2 |PERSON DUPLICATE LAST NAME |CLMF-PERSON-DUP-LAST-NAME |A duplicate last name of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENL3 |PERSON AKA LAST NAME |CLMF-PERSON-AKA-LAST-NAME |An AKA last name of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |40 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENLT |PERSON LAST NAME |CLMF-PERSON-LAST-NAME |The last name of a person. Also referred to as |
| | |AN |surname of a person. |
| | |40 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENM1 |PERSON OLD MIDDLE NAME |CLMF-PERSON-OLD-MID-NAME |The old middle name(s) of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |35 |for the complete set of rules governing the |
| | | |format of a person's name |
|BPENM2 |PERSON DUPLICATE MIDDLE NAME |CLMF-PERSON-DUP-MID-NAME |A duplicate middle name of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |35 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENM3 |PERSON AKA MIDDLE NAME |CLMF-PERSON-AKA-MID-NAME |The AKA middle name(s) of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |35 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENMD |PERSON MIDDLE NAME |CLMF-PERSON-MIDDLE-NAME |The middle name(s) of a person. |
| | |AN |See the AAMVA Person Name Standard-2008 |
| | |35 |for the complete set of rules governing the |
| | | |format of a person's name. |
|BPENRF |PERSON FIRST NAME |CLMF-PERSON-TRLIT-1ST |An indication if a person's first name has been |
| |TRANSLITERATION |AN |transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPENRL |PERSON LAST NAME |CLMF-PERSON-TRLIT-LAST |An indication if a person's last name has been |
| |TRANSLITERATION |AN |transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPENRM |PERSON MIDDLE NAME |CLMF-PERSON-TRLIT-MID |An indication if a person's middle name has |
| |TRANSLITERATION |AN |been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPENS1 |DRIVER OLD NAME SUFFIX |CLMF-PERSON-OLD-NAME-SUFFIX |The suffix for a person's old name. |
| | |AN |VALUE MEANING/DESCRIPTION |
| | |5 |JR Junior |
| | | |SR Senior |
| | | |I 1st |
| | | |II 2nd |
| | | |III 3rd |
| | | |IV 4th |
| | | |V 5th |
| | | |VI 6th |
| | | |VII 7th |
| | | |VIII 8th |
| | | |IX 9th |
| | | |1ST 1st |
| | | |2ND 2nd |
| | | |3RD 3rd |
| | | |4TH 4th |
| | | |5TH 5th |
| | | |6TH 6th |
| | | |7TH 7th |
| | | |8TH 8th |
| | | |9TH 9th |
|BPENS2 |DRIVER DUPLICATE NAME SUFFIX |CLMF-PERSON-DUP-NAME-SUFFIX |A duplicate suffix for a person's name. |
| | |AN |VALUE MEANING/DESCRIPTION |
| | |5 |JR Junior |
| | | |SR Senior |
| | | |I 1st |
| | | |II 2nd |
| | | |III 3rd |
| | | |IV 4th |
| | | |V 5th |
| | | |VI 6th |
| | | |VII 7th |
| | | |VIII 8th |
| | | |IX 9th |
| | | |1ST 1st |
| | | |2ND 2nd |
| | | |3RD 3rd |
| | | |4TH 4th |
| | | |5TH 5th |
| | | |6TH 6th |
| | | |7TH 7th |
| | | |8TH 8th |
| | | |9TH 9th |
|BPENS3 |DRIVER AKA NAME SUFFIX |CLMF-PERSON-AKA-NAME-SUFFIX |The suffix for a person's AKA name. |
| | |AN |VALUE MEANING/DESCRIPTION |
| | |5 |JR Junior |
| | | |SR Senior |
| | | |I 1st |
| | | |II 2nd |
| | | |III 3rd |
| | | |IV 4th |
| | | |V 5th |
| | | |VI 6th |
| | | |VII 7th |
| | | |VIII 8th |
| | | |IX 9th |
| | | |1ST 1st |
| | | |2ND 2nd |
| | | |3RD 3rd |
| | | |4TH 4th |
| | | |5TH 5th |
| | | |6TH 6th |
| | | |7TH 7th |
| | | |8TH 8th |
| | | |9TH 9th |
|BPENSX |PERSON NAME SUFFIX |CLMF-PERSON-NAME-SUFFIX |The suffix for a person's name. |
| | |AN |VALUE MEANING/DESCRIPTION |
| | |5 |JR Junior |
| | | |SR Senior |
| | | |I 1st |
| | | |II 2nd |
| | | |III 3rd |
| | | |IV 4th |
| | | |V 5th |
| | | |VI 6th |
| | | |VII 7th |
| | | |VIII 8th |
| | | |IX 9th |
| | | |1ST 1st |
| | | |2ND 2nd |
| | | |3RD 3rd |
| | | |4TH 4th |
| | | |5TH 5th |
| | | |6TH 6th |
| | | |7TH 7th |
| | | |8TH 8th |
| | | |9TH 9th |
|BPENTF |PERSON FIRST NAME TRUNCATION |CLMF-PERSON-TRUNC-1ST |An indication if a person's first name has been |
| |CODE |AN |truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPENTL |PERSON LAST NAME TRUNCATION |CLMF-PERSON-TRUNC-LAST |An indication if a person's last name has been |
| |CODE |AN |truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPENTM |PERSON MIDDLE NAME |CLMF-PERSON-TRUNC-MID |An indication if a person's middle name has |
| |TRUNCATION CODE |AN |been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPERF1 |PERSON OLD FIRST NAME |CLMF-PERSON-OLD-TRLIT-1ST |An indication if a person's old first name has |
| |TRANSLIT CODE |AN |been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacingnon-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPERF2 |PERSON DUP FIRST NAME |CLMF-PERSON-DUP-TRLIT-1ST |An indication if a person's duplicate first name |
| |TRANSLIT CODE |AN |has been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPERF3 |PERSON AKA FIRST NAME |CLMF-PERSON-AKA-TRLIT-1ST |An indication if a person's AKA first name has |
| |TRANSLIT CODE |AN |been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPERL1 |PERSON OLD LAST NAME TRANSLIT |CLMF-PERSON-OLD-TRLIT-LAST |An indication if a person's old last name has |
| | |AN |been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPERL2 |PERSON DUP LAST NAME TRANSLIT |CLMF-PERSON-DUP-TRLIT-LAST |An indication if a person's duplicate last name |
| | |AN |has been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPERL3 |PERSON AKA LAST NAME TRANSLIT |CLMF-PERSON-AKA-TRLIT-LAST |An indication if a person's AKA last name has |
| | |AN |been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPERM1 |PERSON OLD MIDDLE NAME |CLMF-PERSON-OLD-TRLIT-MID |An indication if a person's old middle name has |
| |TRANSLIT CODE |AN |been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPERM2 |PERSON DUP MIDDLE NAME |CLMF-PERSON-DUP-TRLIT-MID |An indication if a person's duplicate middle |
| |TRANSLIT CODE |AN |name has been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPERM3 |PERSON AKA MIDDLE NAME |CLMF-PERSON-AKA-TRLIT-MID |An indication if a person's AKA middle name |
| |TRANSLIT CODE |AN |has been transliterated. |
| | |1 |Transliteration refers to the practice of |
| | | |replacing non-English letters with comparable |
| | | |letters from the English alphabet. |
| | | |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not transliterated |
| | | |T Transliterated |
| | | |U Unknown if it is transliterated |
|BPESSD |PERSON SSN LAST 5 DIGITS |NONE |The last 5 digits of a person's social security |
| | |AN |number. |
| | |5 | |
| | | | |
|BPETF1 |PERSON OLD FIRST NAME |CLMF-PERSON-OLD-TRUNC-1ST |An indication if a person's old first name has |
| |TRUNCATION |AN |been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPETF2 |PERSON DUP FIRST NAME |CLMF-PERSON-DUP-TRUNC-1ST |An indication if a person's duplicate first name |
| |TRUNCATION |AN |has been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPETF3 |PERSON AKA FIRST NAME |CLMF-PERSON-AKA-TRUNC-1ST |An indication if a person's AKA first name has |
| |TRUNCATION |AN |been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPETL1 |PERSON OLD LAST NAME |CLMF-PERSON-OLD-TRUNC-LAST |An indication if a person's old last name has |
| |TRUNCATION CODE |AN |been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPETL2 |PERSON DUP LAST NAME |CLMF-PERSON-DUP-TRUNC-LAST |An indication if a person's duplicate last name |
| |TRUNCATION CODE |AN |has been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
| | | | |
|BPETL3 |PERSON AKA LAST NAME |CLMF-PERSON-AKA-TRUNC-LAST |An indication if a person's AKA last name has |
| |TRUNCATION CODE |AN |been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPETM1 |PERSON OLD MIDDLE NAME |CLMF-PERSON-OLD-TRUNC-MID |An indication if a person's old middle name has |
| |TRUNCATION |AN |been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPETM2 |PERSON DUP MIDDLE NAME |CLMF-PERSON-DUP-TRUNC-MID |An indication if a person's duplicate middle |
| |TRUNCATION |AN |name has been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|BPETM3 |PERSON AKA MIDDLE NAME |CLMF-PERSON-AKA-TRUNC-MID |An indication if a person's AKA middle name |
| |TRUNCATION |AN |has been truncated. |
| | |1 |See the AAMVA Person Name Standard-2008 |
| | | |for the complete set of rules governing the |
| | | |format of a person's name. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |N Not truncated |
| | | |T Truncated |
| | | |U Unknown if it is truncated |
|DCDPUI |MASTER POINTER UNIQUE |NONE |The Master Pointer Unique Indicator is used to |
| |INDICATOR |AN |convey whether or not a given MPR is currently |
| | |1 |identified as a likely duplicate of another MPR, |
| | | |is in the process of being marked as unique, or |
| | | |has been successfully marked as unique. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |D Possible Duplicate |
| | | |P Mark Unique Pending |
| | | |U Mark Unique Complete |
|DDVAGE |DRIVER AGE |CLMF-DRIVER-AGE |The age in years of an individual driver. |
| | |AN | |
| | |3 | |
|DDVSS0 |DRIVER SSN START RANGE |CLMF-SSN-START |A unique number assigned by the Social |
| | |AN |Security Administration to an individual, who is |
| | |9 |a driver. The Start Range indicates the SSN |
| | | |with the lowest value, when describing a |
| | | |number of drivers. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |NUMERIC VALUES WHEN |
| | | |PRESENT |
|DDVSS9 |DRIVER SSN END RANGE |CLMF-SSN-END |A unique number assigned by the Social |
| | |AN |Security Administration to an individual, who is |
| | |9 |a driver. The End Range indicates the SSN |
| | | |with the highest value, when describing a |
| | | |number of drivers. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |NUMERIC VALUES WHEN |
| | | |PRESENT |
|DDVSSI |DRIVER SSN TYPE |CLMF-SSN-TYPE |The type of SSN associated with the driver. |
| | |AN |VALUE MEANING/DESCRIPTION |
| | |1 |A SSA-Assigned SSN - Assigned by the |
| | | |Social Security Administration |
| | | |S Substitute SSN - Has a value of "999-99- |
| | | |9999" and is used only when a non-CDL driver |
| | | |has been convicted of a CMV violation, but no |
| | | |SSN was provided or available for that driver. |
| | | |P Pseudo SSN - Has a value of "000-nnnnnn" |
| | | |and is used only when the driver isn't |
| | | |required by SSA to have an SSN. (ie SSA has |
| | | |issued a waiver for religious reasons or a nonresident |
| | | |is issued a CDL) AAMVA assigns a |
| | | |unique range of pseudo SSN values to each |
| | | |state for their use. |
|GMSFMS |MESSAGE FIRST MATCH SEQUENCE |CLMF-1ST-MATCH-SEQ-ID |A match sequence ID is the sequence in which |
| |ID |AN |matches are found at a central site or site of |
| | |2 |record. The first match sequence ID is the ID |
| | | |of the first of the matches to be returned in a |
| | | |response. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |NUMERIC VALUES WHEN |
| | | |PRESENT |
|GMSIRL |IMPLEMENTATION RELEASE CODE |NONE |The identifier indicating at what release a |
| | |AN |given participant is authorized to perform a |
| | |2 |particular function. |
| | | |VALUE MEANING/DESCRIPTION |
| | | |41 CDLIS Release 4.1.0 |
| | | |51 CDLIS Release 5.1.0 |
|GMSSCH |MESSAGE SOR CHANGE IN |CLMF-INDC-MEC-CHANGE-SOR |This field is used to indicate whether or not a |
| |PROGRESS IND |AN |"Change State of Record" is in progress for a |
| | |1 |Master Pointer Record (MPR). |
| | | |VALUE MEANING/DESCRIPTION |
| | | |Y Yes, a CSOR has been initiated but not |
| | | |completed |
| | | |E Yes, a CSOR has been initiated but an |
| | | |error occurred preventing its completion |
| | | |N No, a CSOR is not currently in progress |
|GMSSYR |MESSAGE SEARCH YEAR RANGE |CLMF-SEARCH-YEAR-RANGE |A number of years before and after a date, on |
| | |AN |which a search is performed. So if a range of 2 |
| | |2 |years is specified for the year 1966, the search |
| | | |range will be 1964 to 1968. |
|GRCCDT |RECORD CREATION DATE |NONE |The Record Creation Date is the date that the |
| | |AN |given record was first added. |
| | |8 | |
|GRCCTM |RECORD CREATION TIME |NONE |The Record Creation Time is the time that the |
| | |AN |given record was created. |
| | |6 | |
|GRCDDT |DRIVER DATA RECORD TYPE |CLMF-DRIVER-DATA-TYPE |An indicator that specifies the type of a record. |
| | |AN |VALUE MEANING/DESCRIPTION |
| | |1 |1 MPR |
| | | |2 DHR |
|GRCUDT |DATE OF LAST UPDATE |NONE |The Date of Last Update is the date that the |
| | |AN |given record was last updated. When initially |
| | |8 |created, the creation date is reflected in this |
| | | |field. |
|GRCUTM |TIME OF LAST UPDATE |NONE |The Time of Last Update is the time that the |
| | |AN |given record was last updated. When initially |
| | |6 |created, the creation time is reflected in this |
| | | |field. |
| | | | |
Appendix B – New Data Elements by Message Type
Appendix B Key
|[pic] |
7.1 Medical Fields
7.1.1 Medical Fields
|Message Type |CDLISTrans |Medical Fields | |
|HB Driver History Resp |CD04 |CDL MEDICAL SELF CERTIFICATION CODE |DDLSCT |
|(SOR-SOI) | |MEDICAL CERTIFICATE ISSUE DATE |DMCPED |
|HC Status Response (SOR-SOI) |CD01 |MEDICAL CERTIFICATE EXPIRATION DATE |DMCEDT |
|HC Status Response (SOR-SOI) |CD02 |MEDICAL CERTIFICATION STATUS CODE |DMCCTC |
|HC Status Response (SOR-SOI) |CD05 |MEDICAL CERTIFICATE RESTRICTION CODE |DMCRES |
|HG Status Response (SOR-SOI) |CD03 |MEDICAL LICENSING JURISDICTION CODE |BMPJO1 |
|HD Driver History Resp |CD08 |MEDICAL EXAMINER LICENSE NUMBER |BMPLI1 |
|(SOR-SOR) | |MEDICAL EXAMINER TELEPHONE NUMBER |BMPTP1 |
| | |MEDICAL EXAMINER REGISTRY NUMBER |BMPNRN |
| | |MEDICAL EXAMINER SPECIALTY CODE |BMPSP1 |
| | |DRIVER WAIVER/EXEMPT EFFECTIVE DATE |DDLWSD |
| | |DRIVER WAIVER/EXEMPT EXPIRATION DATE |DDLWED |
| | |DRIVER SPE EFFECTIVE DATE |DDLSSD |
| | |DRIVER SPE EXPIRATION DATE |DDLSED |
| | |MEDICAL EXAMINER LAST NAME |BMPNL1 |
| | |MEDICAL EXAMINER FIRST NAME |BMPNF1 |
| | |MEDICAL EXAMINER MIDDLE NAME |BMPNM1 |
| | |MEDICAL EXAMINER NAME SUFFIX |BMPNS1 |
| | |ME LAST NAME TRUNCATION IND |BMPTL1 |
| | |ME FIRST NAME TRUNCATION IND |BMPTF1 |
| | |ME MIDDLE NAME TRUNCATION IND |BMPTM1 |
| | |ME LAST NAME TRANSLITERATION IND |BMPLL1 |
| | |ME FIRST NAME TRANSLITERATION IND |BMPLF1 |
| | |ME MIDDLE NAME TRANSLITERATION IND |BMPLM1 |
| | | | |
7.2 Modernization Fields
7.2.1 Person Name Group(BPENGP) Fields
|Message Type |CDLISTrans |Modernization Fields | |
|HA Report Out of State Conviction |CD11 |PERSON LAST NAME |BPENLT |
|HF Fwd Rpt Out of St Conviction |CD11 |PERSON FIRST NAME |BPENFT |
|HH Negate Conviction |CD12 |PERSON MIDDLE NAME |BPENMD |
|HT Forward Out-of-State Withdrawal |CD16 |PERSON NAME SUFFIX |BPENSX |
|HV Forward Negate Withdrawal |CD17 |PERSON FIRST NAME TRUNCATION CODE |BPENTF |
|HW Report Out-of-State Withdrawal |CD16 |PERSON MIDDLE NAME TRUNCATION CODE |BPENTM |
|HX Fwd Negate Conviction |CD12 |PERSON LAST NAME TRUNCATION CODE |BPENTL |
|HY Negate Out-of-State Withdrawal |CD17 |PERSON FIRST NAME TRANSLITERATION |BPENRF |
|IA Inq Req Chg Data/Mark Unique |CD02 |PERSON MIDDLE NAME TRANSLITERATION |BPENRM |
|IB Inq Request Preceding Del MPR |CD02 |PERSON LAST NAME TRANSLITERATION |BPENRL |
|IC Inq Request Preceding CSOR |CD02 | | |
|ID Inq Req Precede Rpt OOS |CD02 | | |
|Convct | | | |
|IE Inquiry Request Preceding DHR |CD02 | | |
|IN Verification Inquiry |CD02 | | |
|SB Driver History Request |CD04 | | |
|SC Status Request |CD01 | | |
|SC Status Request |CD02 | | |
|SC Status Request |CD05 | | |
|SG State Request for Status |CD03 | | |
|UE Delete Master Pointer Record |CD10 | | |
7.2.2 Person Old Name Group (BPENG1) Fields
|Message Type |CDLISTrans |Modernization Fields | |
| NF Confirm CSOR Is Complete | CD08 |PERSON OLD LAST NAME |BPENL1 |
| | |PERSON OLD FIRST NAME |BPENF1 |
| | |PERSON OLD MIDDLE NAME |BPENM1 |
| | |DRIVER OLD NAME SUFFIX |BPENS1 |
| | |PERSON OLD LAST NAME TRUNCATION CODE |BPETL1 |
| | |PERSON OLD FIRST NAME TRUNCATION |BPETF1 |
| | |PERSON OLD MIDDLE NAME TRUNCATION |BPETM1 |
| | |PERSON OLD LAST NAME TRANSLIT |BPERL1 |
| | |PERSON OLD FIRST NAME TRANSLIT CODE |BPERF1 |
| | |PERSON OLD MIDDLE NAME TRANSLIT CODE |BPERM1 |
7.2.3 Person Duplicate Name Group (BPENG2) Fields
|Message Type |CDLISTrans |Modernization Fields | |
|NE CDLIS Duplicate Resolved | CDA1 |PERSON DUPLICATE LAST NAME |BPENL2 |
| | |PERSON DUPLICATE FIRST NAME |BPENF2 |
| | |PERSON DUPLICATE MIDDLE NAME |BPENM2 |
| | |DRIVER DUPLICATE NAME SUFFIX |BPENS2 |
| | |PERSON DUP LAST NAME TRUNCATION CODE |BPETL2 |
| | |PERSON DUP FIRST NAME TRUNCATION |BPETF2 |
| | |PERSON DUP MIDDLE NAME TRUNCATION |BPETM2 |
| | |PERSON DUP LAST NAME TRANSLIT |BPERL2 |
| | |PERSON DUP FIRST NAME TRANSLIT CODE |BPERF2 |
| | |PERSON DUP MIDDLE NAME TRANSLIT CODE |BPERM2 |
7.2.4 Person Name Group (BPENGP) – Person Old Name Group (BPENG1) Fields
|Message Type |CDLISTrans |Modernization Fields | |
|CC Confirm DHR Rec’vd/Processed |CD08 |PERSON LAST NAME |BPENLT |
|SD CSOR History Request |CD08 |PERSON FIRST NAME |BPENFT |
|UD Change State of Record |CD08 |PERSON MIDDLE NAME |BPENMD |
| | |PERSON NAME SUFFIX |BPENSX |
| | |PERSON FIRST NAME TRUNCATION CODE |BPENTF |
| | |PERSON MIDDLE NAME TRUNCATION CODE |BPENTM |
| | |PERSON LAST NAME TRUNCATION CODE |BPENTL |
| | |PERSON FIRST NAME TRANSLITERATION |BPENRF |
| | |PERSON MIDDLE NAME TRANSLITERATION |BPENRM |
| | |PERSON LAST NAME TRANSLITERATION |BPENRL |
| | |PERSON OLD LAST NAME |BPENL1 |
| | |PERSON OLD FIRST NAME |BPENF1 |
| | |PERSON OLD MIDDLE NAME |BPENM1 |
| | |DRIVER OLD NAME SUFFIX |BPENS1 |
| | |PERSON OLD LAST NAME TRUNCATION CODE |BPETL1 |
| | |PERSON OLD FIRST NAME TRUNCATION |BPETF1 |
| | |PERSON OLD MIDDLE NAME TRUNCATION |BPETM1 |
| | |PERSON OLD LAST NAME TRANSLIT |BPERL1 |
| | |PERSON OLD FIRST NAME TRANSLIT CODE |BPERF1 |
| | |PERSON OLD MIDDLE NAME TRANSLIT CODE |BPERM1 |
7.2.5 Person Name Group (BPENGP) –Person Old Name Group (BPENG1) – Person AKA Name Group (BPENG3) Fields
|Message Type |CDLISTrans |Modernization Fields | |
|UC Change Data (SOR-CDLIS) |CD09 |PERSON LAST NAME |BPENLT |
| | |PERSON FIRST NAME |BPENFT |
| | |PERSON MIDDLE NAME |BPENMD |
| | |PERSON NAME SUFFIX |BPENSX |
| | |PERSON FIRST NAME TRUNCATION CODE |BPENTF |
| | |PERSON MIDDLE NAME TRUNCATION CODE |BPENTM |
| | |PERSON LAST NAME TRUNCATION CODE |BPENTL |
| | |PERSON FIRST NAME TRANSLITERATION |BPENRF |
| | |PERSON MIDDLE NAME TRANSLITERATION |BPENRM |
| | |PERSON LAST NAME TRANSLITERATION |BPENRL |
| | |PERSON OLD LAST NAME |BPENL1 |
| | |PERSON OLD FIRST NAME |BPENF1 |
| | |PERSON OLD MIDDLE NAME |BPENM1 |
| | |DRIVER OLD NAME SUFFIX |BPENS1 |
| | |PERSON OLD LAST NAME TRUNCATION CODE |BPETL1 |
| | |PERSON OLD FIRST NAME TRUNCATION |BPETF1 |
| | |PERSON OLD MIDDLE NAME TRUNCATION |BPETM1 |
| | |PERSON OLD LAST NAME TRANSLIT |BPERL1 |
| | |PERSON OLD FIRST NAME TRANSLIT CODE |BPERF1 |
| | |PERSON OLD MIDDLE NAME TRANSLIT CODE |BPERM1 |
| | |PERSON AKA LAST NAME |BPENL3 |
| | |PERSON AKA FIRST NAME |BPENF3 |
| | |PERSON AKA MIDDLE NAME |BPENM3 |
| | |DRIVER AKA NAME SUFFIX |BPENS3 |
| | |PERSON AKA LAST NAME TRUNCATION CODE |BPETL3 |
| | |PERSON AKA FIRST NAME TRUNCATION |BPETF3 |
| | |PERSON AKA MIDDLE NAME TRUNCATION |BPETM3 |
| | |PERSON AKA LAST NAME TRANSLIT |BPERL3 |
| | |PERSON AKA FIRST NAME TRANSLIT CODE |BPERF3 |
| | |PERSON AKA MIDDLE NAME TRANSLIT CODE |BPERM3 |
| | | | |
7.2.6 Person Name Group (BPENGP) – Person AKA Name Group (BPENG3) Fields
|Message Type |CDLISTrans |Modernization Fields | |
|EM DLIS Batch Search Inquiry |CD30 |PERSON LAST NAME |BPENLT |
|HB Driver History Resp (SOR-SOI) |CD04 |PERSON FIRST NAME |BPENFT |
|HC Status Response (SOR-SOI) |CD01 |PERSON MIDDLE NAME |BPENMD |
|HC Status Response (SOR-SOI) |CD02 |PERSON NAME SUFFIX |BPENSX |
|HC Status Response (SOR-SOI) |CD05 |PERSON FIRST NAME TRUNCATION CODE |BPENTF |
|HD Driver History Resp (SOR-SOR) |CD08 |PERSON MIDDLE NAME TRUNCATION CODE |BPENTM |
|HG Status Response (SOR-SOI) |CD03 |PERSON LAST NAME TRUNCATION CODE |BPENTL |
|IK Inquiry for AKA Data |CD05 |PERSON FIRST NAME TRANSLITERATION |BPENRF |
|IM CDLIS Search Inquiry |CD01 |PERSON MIDDLE NAME TRANSLITERATION |BPENRM |
|IO CDLIS Search Inquiry |CD01 |PERSON LAST NAME TRANSLITERATION |BPENRL |
|QD Batch MPR Data Match(es) |CD30 |PERSON AKA LAST NAME |BPENL3 |
|RD MPR Data Match(s) on Inq Trans |CD01 |PERSON AKA FIRST NAME |BPENF3 |
|RD MPR Data Match(s) on Inq Trans |CD02 |PERSON AKA MIDDLE NAME |BPENM3 |
|RD MPR Data Match(s) on Inq Trans |CD05 |DRIVER AKA NAME SUFFIX |BPENS3 |
|UA Add New Driver (SOR-CDLIS) |CD07 |PERSON AKA LAST NAME TRUNCATION CODE |BPETL3 |
| | |PERSON AKA FIRST NAME TRUNCATION |BPETF3 |
| | |PERSON AKA MIDDLE NAME TRUNCATION |BPETM3 |
| | |PERSON AKA LAST NAME TRANSLIT |BPERL3 |
| | |PERSON AKA FIRST NAME TRANSLIT CODE |BPERF3 |
| | |PERSON AKA MIDDLE NAME TRANSLIT CODE |BPERM3 |
7.2.7 Person Old Name Group (BPENG1) – Person AKA Name Group (BPENG3) Fields
|Message Type |CDLISTrans |Modernization Fields | |
| UK Update AKA (SOR-CDLIS) | CD15 |PERSON OLD LAST NAME |BPENL1 |
| | |PERSON OLD FIRST NAME |BPENF1 |
| | |PERSON OLD MIDDLE NAME |BPENM1 |
| | |DRIVER OLD NAME SUFFIX |BPENS1 |
| | |PERSON OLD LAST NAME TRUNCATION CODE |BPETL1 |
| | |PERSON OLD FIRST NAME TRUNCATION |BPETF1 |
| | |PERSON OLD MIDDLE NAME TRUNCATION |BPETM1 |
| | |PERSON OLD LAST NAME TRANSLIT |BPERL1 |
| | |PERSON OLD FIRST NAME TRANSLIT CODE |BPERF1 |
| | |PERSON OLD MIDDLE NAME TRANSLIT CODE |BPERM1 |
| | |PERSON AKA LAST NAME |BPENL3 |
| | |PERSON AKA FIRST NAME |BPENF3 |
| | |PERSON AKA MIDDLE NAME |BPENM3 |
| | |DRIVER AKA NAME SUFFIX |BPENS3 |
| | |PERSON AKA LAST NAME TRUNCATION CODE |BPETL3 |
| | |PERSON AKA FIRST NAME TRUNCATION |BPETF3 |
| | |PERSON AKA MIDDLE NAME TRUNCATION |BPETM3 |
| | |PERSON AKA LAST NAME TRANSLIT |BPERL3 |
| | |PERSON AKA FIRST NAME TRANSLIT CODE |BPERF3 |
| | |PERSON AKA MIDDLE NAME TRANSLIT CODE |BPERM3 |
7.2.8 Person Name Group (BPENGP) – Person Duplicate Name Group (BPENG2) Fields
|Message Type |CDLISTrans |Modernization Fields | |
|NA CDLIS Possible Duplicate | CDA1 |PERSON LAST NAME |BPENLT |
|UG Mark Driver Unique |CD14 |PERSON FIRST NAME |BPENFT |
| | |PERSON MIDDLE NAME |BPENMD |
| | |PERSON NAME SUFFIX |BPENSX |
| | |PERSON FIRST NAME TRUNCATION CODE |BPENTF |
| | |PERSON MIDDLE NAME TRUNCATION CODE |BPENTM |
| | |PERSON LAST NAME TRUNCATION CODE |BPENTL |
| | |PERSON FIRST NAME TRANSLITERATION |BPENRF |
| | |PERSON MIDDLE NAME TRANSLITERATION |BPENRM |
| | |PERSON LAST NAME TRANSLITERATION |BPENRL |
| | |PERSON DUPLICATE LAST NAME |BPENL2 |
| | |PERSON DUPLICATE FIRST NAME |BPENF2 |
| | |PERSON DUPLICATE MIDDLE NAME |BPENM2 |
| | |DRIVER DUPLICATE NAME SUFFIX |BPENS2 |
| | |PERSON DUP LAST NAME TRUNCATION CODE |BPETL2 |
| | |PERSON DUP FIRST NAME TRUNCATION |BPETF2 |
| | |PERSON DUP MIDDLE NAME TRUNCATION |BPETM2 |
| | |PERSON DUP LAST NAME TRANSLIT |BPERL2 |
| | |PERSON DUP FIRST NAME TRANSLIT CODE |BPERF2 |
| | |PERSON DUP MIDDLE NAME TRANSLIT CODE |BPERM2 |
7.2.9 Validation Control Name Fields
|Message Type |CDLISTrans |Modernization Fields | |
|DQ MPR DHR Validation Control |CD31 |MESSAGE LENGTH |GMSLEN |
| | |MESSAGE DESTINATION |GMSDST |
| | |MESSAGE ORIGIN |GMSORG |
| | |MESSAGE DATE |GMSDAT |
| | |MESSAGE TIME |GMSTIM |
| | |MESSAGE SEQUENCE ID |GMSSEQ |
| | |APPLICATION ID |GAPPID |
| | |MESSAGE TYPE |GMSTYP |
| | |SEGMENT SEQUENCE NUMBER |GSGSEQ |
| | |LAST SEGMENT INDICATOR |GLSEGI |
| | |NUMBER OF TEXT BLOCKS COUNT |GNBTXT |
| | |NETWORK SESSION INDICATOR |GNETSI |
| | |TEST/PRODUCTION INDICATOR |GTPIND |
| | |TRANSMIT MODE CODE |GXMODC |
| | |NCB ERROR CODE |GNCBER |
| | |TRANSACTION ORIGINATOR |GTRORG |
| | |NETWORK STATUS |GNETST |
| | |APPLICATION STATUS |GAPPST |
| | |DRIVER DATA RECORD TYPE |GRCDDT |
| | |JURISDICTION CODE – LICENSING |DDLJUR |
| | |RECORD AS OF DATE |GRCAOD |
| | |RECORD AS OF TIME |GRCAOT |
| | |DRIVER COUNT |DDVCNT |
| | |RECORD COUNT |GRCCNT |
| | |DRIVER SSN START RANGE |DDVSS0 |
| | |DRIVER SSN END RANGE |DDVSS9 |
| | |DRIVER LICENSE NUMBER START |DDLNU0 |
| | |RANGE | |
| | |DRIVER LICENSE NUMBER END |DDLNU9 |
| | |RANGE | |
| | |MESSAGE LOCATOR/HEADER |GMSLOC |
7.2.10 Architectural Current Fields
|Message Type |CDLIS Trans |Modernization Fields | |
|CC Confirm DHR Rcv’d/Processed |CD08 |DRIVER CURRENT HEIGHT |DDVHT3 |
|HF Fwd Rpt Out of St Conviction |CD11 |DRIVER CURRENT WEIGHT |DDVWT3 |
|HT Forward Out-of-State Withdrawal |CD16 |DRIVER CURRENT EYE COLOR |DDVEY3 |
|HV Forward Negate Withdrawal |CD17 | | |
|HX Fwd Negate Conviction |CD12 | | |
|QD Batch MPR Data Match (ES) |CD30 | | |
|RD MPR Data Match(s)On Inq Trans |CD01 | | |
|RD MPR Data Match(s)On Inq Trans |CD02 | | |
|RD MPR Data Match(s)On Inq Trans |CD05 | | |
|SC Status Request |CD01 | | |
|SC Status Request |CD02 | | |
|SC Status Request |CD05 | | |
|SD CSOR History Request |CD08 | | |
|UA Add New Driver (SOR-CDLIS) |CD07 | | |
|UC Change Data (SOR-CDLIS) |CD09 | | |
|UD Change State-of-Record |CD08 | | |
|UE Delete Master Pointer Record |CD10 | | |
Note: The sex field will be maintained during the transition period and will be eliminated after ALL jurisdictions are operating CDLIS Release 5.1. (DRIVER CURRENT SEX (DDVSX3) and DRIVER DUPLICATE SEX (DDVSX2 )
7.2.11 Architectural Current-Duplicate-AKA SSN Count Fields
|Message Type |CDLISTrans |Modernization Fields | |
|NA CDLIS Possible Duplicate | CDA1 |DRIVER CURRENT HEIGHT |DDVHT3 |
|NE CDLIS Duplicate Resolved |CDA1 |DRIVER CURRENT WEIGHT |DDVWT3 |
| | |DRIVER CURRENT EYE COLOR |DDVEY3 |
| | |DRIVER DUPLICATE HEIGHT |DDVHT2 |
| | |DRIVER DUPLICATE WEIGHT |DDVWT4 |
| | |DRIVER DUPLICATE EYE COLOR |DDVEY2 |
| | |MESSAGE AKA SSN COUNT |GMSCSS |
Note: The sex field will be maintained during the transition period and will be eliminated after ALL jurisdictions are operating CDLIS Release 5.1. (DRIVER CURRENT +SEX (DDVSX3) and DRIVER DUPLICATE SEX (DDVSX2 )
7.2.12 Architectural AKA DOB Fields
|Message Type |CDLISTrans |Modernization Fields | |
|EM CDLIS Batch Search Inquiry |CD30 |DRIVER AKA DATE OF BIRTH |DDVKDB |
|IK Inquiry for AKA Data |CD05 |DRIVER AKA 2ND DATE OF BIRTH |DDVKD2 |
|IM CDLIS Search Inquiry |CD01 |DRIVER AKA 3RD DATE OF BIRTH |DDVKD3 |
|IO CDLIS Search Inquiry |CD01 | | |
|QD Batch MPR Data Match(es) |CD30 | | |
|RD MPR Data Match(s)On Inq Trans |CD01 | | |
|RD MPR Data Match(s)On Inq Trans |CD02 | | |
|RD MPR Data Match(s)On Inq Trans |CD05 | | |
|UA Add New Driver (SOR-CDLIS) |CD07 | | |
|UC Change Data (SOR-CDLIS) |CD09 | | |
|UK Update AKA (SOR-CDLIS) |CD15 | | |
7.2.13 Architectural AKA SSN – AKA SSN Count Fields
|Message Type |CDLISTrans |Modernization Fields | |
|QD Batch MPR Data Match(es) |CD30 |DRIVER AKA SOCIAL SECURITY NUMBER |DDVKSS |
|RD MPR Data Match(s)On Inq Trans |CD01 |MESSAGE AKA SSN COUNT |GMSCSS |
|RD MPR Data Match(s)On Inq Trans |CD02 | | |
|RD MPR Data Match(s)On Inq Trans |CD05 | | |
|UA Add New Driver (SOR-CDLIS) |CD07 | | |
|UC Change Data (SOR-CDLIS) |CD09 | | |
|UK Update AKA (SOR-CDLIS) |CD15 | | |
| | | | |
| | | | |
7.2.14 Architectural AKA SSN Count Field
|Message Type |CDLISTrans |Modernization Fields | |
|CB Confirmation of Driver Added |CD07 |MESSAGE AKA SSN COUNT |GMSCSS |
|CD Confirm Change Data Complete |CD09 | | |
|CD Confirm Change Data Complete |CD14 | | |
|CD Confirm Change Data Complete |CD15 | | |
| | | | |
| | | | |
7.2.15 Architectural Sex Field
|Message Type |CDLISTrans |Modernization Fields | |
|CC Confirm DHR Rcv’d/Processed |CD08 |DRIVER CURRENT SEX |DDVSX3 |
|HF Fwd Rpt Out of St Conviction |CD11 | | |
|HT Forward Out-of-State Withdrawal |CD16 | | |
|HV Forward Negate Withdrawal |CD17 | | |
|HX Fwd Negate Conviction |CD12 | | |
|NA CDLIS Possible Duplicate |CDA1 | | |
|NE CDLIS Duplicate Resolved |CDA1 | | |
|QD Batch MPR Data Match(es) |CD30 | | |
|RD MPR Data Match(s)On Inq Trans |CD01 | | |
|RD MPR Data Match(s)On Inq Trans |CD02 | | |
|RD MPR Data Match(s)On Inq Trans |CD05 | | |
|SC Status Request |CD01 | | |
|SC Status Request |CD02 | | |
|SC Status Request |CD05 | | |
|SD CSOR History Request |CD08 | | |
|UA Add New Driver (SOR-CDLIS) |CD07 | | |
|UC Change Data (SOR-CDLIS) |CD09 | | |
|UD Change State-of-Record |CD08 | | |
|UE Delete Master Pointer Record |CD10 | | |
7.2.16 Architectural Duplicate Sex Field
|Message Type |CDLISTrans |Modernization Fields | |
|NA CDLIS Possible Duplicate | CDA1 |DRIVER DUPLICATE SEX |DDVSX2 |
|NE CDLIS Duplicate Resolved |CDA1 | | |
| | | | |
7.2.17 On-Demand Re-Drive
Note: The SR History Re-Drive message is a new message type that is comprised of both existing fields and new fields. New fields are highlighted in yellow.
|Message Type |CDLISTrans |Modernization Fields | |
|SR History Re-drive |CD08 |MESSAGE LENGTH |GMSLEN |
| | |MESSAGE DESTINATION |GMSDST |
| | |MESSAGE ORIGIN |GMSORG |
| | |MESSAGE DATE |GMSDAT |
| | |MESSAGE TIME |GMSTIM |
| | |MESSAGE SEQUENCE ID |GMSSEQ |
| | |APPLICATION ID |GAPPID |
| | |MESSAGE TYPE |GMSTYP |
| | |SEGMENT SEQUENCE NUMBER |GSGSEQ |
| | |LAST SEGMENT INDICATOR |GLSEGI |
| | |NUMBER OF TEXT BLOCKS COUNT |GNBTXT |
| | |NETWORK SESSION INDICATOR |GNETSI |
| | |TEST/PRODUCTION INDICATOR |GTPIND |
| | |TRANSMIT MODE CODE |GXMODC |
| | |NCB ERROR CODE |GNCBER |
| | |TRANSACTION ORIGINATOR |GTRORG |
| | |NETWORK STATUS |GNETST |
| | |APPLICATION STATUS |GAPPST |
| | |MESSAGE LOCATOR/HEADER |GMSLOC |
| | |PROCESSING STATUS |GPROST |
| | |MESSAGE SENDER PASSWORD |GMSPSW |
| | |SYSTEM RELEASE CODE |GMSSRL |
| | |DL OLD JURISDICTION NUMBER |DDLJD1 |
| | |DRIVER LICENSE JURIS NUMBER |DDLJDL |
| | |PERSON OLD LAST NAME |BPENL1 |
| | |PERSON OLD FIRST NAME |BPENF1 |
| | |PERSON OLD MIDDLE NAME |BPENM1 |
| | |DRIVER OLD NAME SUFFIX |BPENS1 |
| | |PERSON OLD LAST NAME TRUNCATION CODE |BPETL1 |
| | |PERSON OLD FIRST NAME TRUNCATION |BPETF1 |
| | |PERSON OLD MIDDLE NAME TRUNCATION |BPETM1 |
| | |PERSON OLD LAST NAME TRANSLIT |BPERL1 |
| | |PERSON OLD FIRST NAME TRANSLIT CODE |BPERF1 |
| | |PERSON OLD MIDDLE NAMETRANSLIT CODE |BPERM1 |
| | |ERROR BLOCK OUT |GEROUT |
7.2.18 Backward Compatibility – Partial SSN – Old SSN
|Message Type |CDLISTrans |Modernization Fields | |
|NF Confirm CSOR Is Complete |CD08 |DRIVER OLD SOCIAL SECURITY NUMBER |DDVSS1 |
|SD CSOR History Request |CD08 | | |
7.2.19 Backward Compatibility – Partial SSN – Duplicate SSN
|Message Type |CDLISTrans |Modernization Fields | |
|NA CDLIS Possible Duplicate |CDA1 |DRIVERS DUPLICATE SSN |DDVSS2 |
|NE CDLIS Duplicate Resolved |CDA1 | | |
7.2.20 Backward Compatibility – Partial SSN - SSN
|Message Type |CDLISTrans |Modernization Fields | |
|HF Fwd Rpt Out of St Conviction |CD11 |DRIVER SSN-CDLIS |DDVSS6 |
|HT Forward Out-of-State Withdrawal |CD16 | | |
|HV Forward Negate Withdrawal |CD17 | | |
|HX Fwd Negate Conviction |CD12 | | |
|NA CDLIS Possible Duplicate |CDA1 | | |
|NE CDLIS Duplicate Resolved |CDA1 | | |
|QD Batch MPR Data Match(es) |CD30 | | |
|RD MPR Data Match(s) on Inq Trans |CD01 | | |
|RD MPR Data Match(s) on Inq Trans |CD02 | | |
|RD MPR Data Match(s) on Inq Trans |CD05 | | |
|SC Status Request |CD01 | | |
|SC Status Request |CD02 | | |
|SC Status Request |CD05 | | |
|SD CSOR History Request |CD08 | | |
Appendix C – CDLIS Transaction Diagrams
8.1 CD01 Search Inquiry
|[pic] |
8.2 CD02 Verification Inquiry
|[pic] |
8.3 CD03 State-to-State Status Request
|[pic] |
8.4 CD04 State-to-State History Request
|[pic] |
8.5 CD05 AKA Data Inquiry
|[pic] |
8.6 CD07 Add New Driver
|[pic] |
8.7 CD08 Change State of Record
|[pic] |
8.8 CD08 On Demand Re-Drive
|[pic] |
8.9 CD08 Automated Re-Drive
|[pic] |
8.10 CD09 Change Data
|[pic] |
8.11 CD10 Delete Master Pointer Record
|[pic] |
8.12 CD11 Report Out-of-State Convictions
|[pic] |
8.13 CD12 Negate Out-of-State Convictions
|[pic] |
8.14 CD14 Mark Driver Unique
|[pic] |
8.15 CD15 Update AKA Data
|[pic] |
8.16 CD16 Report Out-of-State Withdrawal
|[pic] |
8.17 CD17 Negate Out-of-State Withdrawal
|[pic] |
8.18 CDA1 Duplicate Driver
|[pic] |
8.19 CD30 CDLIS Batch Inquiry
|[pic] |
8.20 CD31 MPR Data Validation and Verification Process
|[pic] |
Appendix D – Person Name Formatting
APPENDIX E – PERSON NAME FORMATTING
APPENDIX E.1 – AAMVA PERSON NAME FORMATTING RULES
The information contained in ‘Appendix E.1 - AAMVA Person Name Formatting Rules’ reflects the AAMVA person name formatting rules as they pertain to the CDLIS Master Specifications (Release 4.1). ‘Appendix E.1 – AAMVA Person Name Formatting Rules’ is being retained only for backward compatibility purposes.
New standards become effective with the implementation of the CDLIS Master Specifications (Release 5.1) and are reflected in ‘Appendix E.2 Ŕ AAMVA Person Name Standard (2008)’.
APPENDIX E.2 - AAMVA PERSON NAME STANDARD (2008)
The information contained in ‘Appendix E.2 Ŕ AAMVA Person Name Standard (2008)’ reflects the new AAMVA person name formatting rules as they pertain to the CDLIS Master Specifications (Release 5.1) and greater. The new rules replace those that are reflected in ‘Appendix E.1 - AAMVA Person Name Formatting Rules’ and become effective with the implementation of the CDLIS Master Specifications (Release 5.1).
E.2.1 Structure
Composite field names are used to represent various business name entities. Examples of composite field names include the following:
Person Name Group (BPENGP)
Person Old Name Group (BPENG1)
Person Duplicate Name Group (BPENG2)
Person AKA Name Group (BPENG3)
Medical Examiner Name Group (BMPNGP)
Each composite field name is comprised of individual component fields as described below. Note that prefixes and titles are not supported:
Group_Name: the composite field name
o First_Name: up to 40 characters
o Middle_Name(s): up to 35 characters
o Last_Name: up to 40 characters
o Suffix: up to 5 characters
o Truncation_Code for the First_Name field
o Truncation_Code for the Middle_Name(s) field
o Truncation_Code for the Last_Name field
o Transliteration_Code for the First_Name field
o Transliteration_Code for the Middle_Name(s) field
o Transliteration_Code for the Last_Name field
As an example, the Person Name Group (BPENGP) composite field is comprised of the following individual component fields:
Person Name Group (BPENGP)
o Person First Name (BPENFT)
o Person Middle Name (BPENMD)
o Person Last Name (BPENLT)
o Person Suffix (BPENSX)
o Person First Name Truncation Code (PBENTF)
o Person Middle Name Truncation Code (BPENTM)
o Person Last Name Truncation Code (BPENTL)
o Person First Name Transliteration (BPENRF)
o Person Middle Name Transliteration (BPENRM)
o Person Last Name Transliteration (BPENRL)
E.2.2 Conventions
While composite field names are referenced in the process description sections of the specification, the associated component fields are not. If a particular composite field is either required or optional on a given message, the associated process description makes reference to the requirement in terms of the composite field only. Additional reference to "APPENDIX E.3 - AAMVA PERSON NAME STANDARD (2008) VALIDATIONS" is made to ensure that data content complies with the standards detailed in that section.
E.2.2.1 Example 1
As an example, Person Name Group (BPENGP) is required on the Search Inquiry (IM) message and is reflected in
‘CD01.1.2 Transmission of Search Inquiry (IM) Message’ as follows:
The Search Inquiry (IM) message must include:
Person Name Group (BPENGP) set to the driver's name
If Person Name Group (BPENGP) is not provided on the Search Inquiry (IM) message (determined because none of its component fields is provided), the following error is returned as reflected in ‘CD01.2.2.2 Required Data Errors’ and no additional validations specific to the Person Name Group (BPENGP) field are performed:
At least one component field of Person Name Group (BPENGP) must be present
Error Text: 'REQUIRED NAME'
If, however, the Person Name Group (BPENGP) is provided on the Search Inquiry (IM) message (determined because one or more of its component fields is provided), it will pass the ‘required field’ edit described above. Additional validations are performed, however, based on the standards described in ‘APPENDIX E.3 - AAMVA
PERSON NAME STANDARD (2008) VALIDATIONS’.
In this example, if the Person Name Group (BPENGP) component fields are populated as described below,
Person Name Group (BPENGP)
o Person First Name (BPENFT) set to ‘JANE’
o Person Middle Name (BPENMD) not provided
o Person Last Name (BPENLT) not provided
o Person Suffix (BPENSX) not provided
o Person First Name Truncation Code (PBENTF) set to ‘N’
o Person Middle Name Truncation Code (BPENTM) set to ‘N’
o Person Last Name Truncation Code (BPENTL) not provided
o Person First Name Transliteration (BPENRF) not provided
o Person Middle Name Transliteration (BPENRM) not provided
o Person Last Name Transliteration (BPENRL) not provided
the following error messages are returned:
'LAST NAME REQUIRED'
'INVALID SPACE AT LEFTMOST POSITION IN FIRST NAME'
'TRUNCATION IND NOT ALLOWED WITHOUT MIDDLE NAME'
'TRANSLITERATION IND REQUIRED FOR FIRST NAME'
E.2.2.2 Example 2
As a second example, Person AKA Name Group (BPENG3) is optional on the Search Inquiry (IM) message and is reflected in ‘CD01.1.2 Transmission of Search Inquiry (IM) Message’ as follows:
The Search Inquiry (IM) message may optionally include:
The first occurrence of Person AKA Name Group (BPENG3) set to the first name by which the driver may be known other than the current name
If Person AKA Name Group (BPENG3) is not provided on the Search Inquiry (IM) message (determined because none of its component fields is provided), there is no associated validation in ‘CD01.2.2.2 Required Data Errors’ and no additional validations as described in ‘APPENDIX E.3 - AAMVA PERSON NAME STANDARD (2008)
VALIDATIONS’ are performed.
If, however, Person AKA Name Group (BPENG3) is provided on the Search Inquiry (IM) message (determined because one or more of its component fields is provided), the additional validations described in ‘APPENDIX E.3 -
AAMVA PERSON NAME STANDARD (2008) VALIDATIONS’ are performed to ensure that Person AKA Name
Group (BPENG3) meets the prescribed standards.
E.2.3 Field formatting
For the First_Name, Last_Name, Middle_Name(s) and Suffix fields the following characters are allowed:
A to Z
a to z
0 to 9
Special characters:
[pic]
In addition, the following formatting rules apply to the First_Name, Last_Name and Middle_Name(s) fields:
Uppercase, lowercase and mixed cases are allowed. For example, the First_Name fields "John", "JOHN" or
"john" are all valid and have the same meaning.
Trailing spaces are allowed but have no meaning. A trailing character is the character that appears at the rightmost position in a field.
Leading spaces are not allowed. A leading character is the character that appears at the leftmost position in a field.
Except for trailing spaces, a space character may not appear adjacent to another space character.
Name components that are longer than the allowed field lengths are truncated as described in the Truncation section below. Names in non-Latin characters are not supported. Unsupported Latin characters are transliterated as specified in the Transliteration section below. If a character does not have a transliterated equivalent, the character is dropped.
If an individual has only a single name, the name is stated in the Last_Name field. Other fields are omitted.
Any field not used is omitted.
Values for the Suffix field are limited to the following values:
JR (Junior)
SR (Senior)
1ST or I (First)
2ND or II (Second)
3RD or III (Third)
4TH or IV (Fourth)
5TH or V (Fifth)
6TH or VI (Sixth)
7TH or VII (Seventh)
8TH or VII (Eighth)
9TH or IX (Ninth)
Leading spaces are not allowed in the Suffix field, and except for trailing spaces, a space character may not appear adjacent to another space character.
The Truncation_Code for the First_Name field is present if and only if the First_Name field is present.
The Truncation_Code for the Last_Name field is present if and only if the Last_Name field is present.
The Truncation_Code for the Middle_Name(s) field is present if and only if the Middle_Name(s) field is present.
The Transliteration_Code for the First_Name field is present if and only if the First_Name field is present.
The Transliteration_Code for the Last_Name field is present if and only if the Last_Name field is present.
The Transliteration_Code for the Middle_Name(s) field is present if and only if the Middle_Name(s) field is present.
If present, a Truncation_Code has to have one of the following values:
T: Field content truncated
N: Field content not truncated
U: It is unknown whether or not the field content is truncated. This value is used when transitioning from the name format described in "APPENDIX E.1 Ŕ AAMVA PERSON NAME FORMATTING RULES".
If present, a Transliteration_Code has to have one of the following values:
T: Field content transliterated
N: Field content not transliterated
U: It is unknown whether or not the field content is transliterated. This value is used when transitioning from the name format described in "APPENDIX E.1 Ŕ AAMVA PERSON NAME FORMATTING RULES".
E.2.4 Truncation
For all name fields, characters are eliminated from a field in the following order until the name fits into the field:
Starting from the right and moving to the left, eliminate spaces adjacent to hyphens
Starting from the right and moving to the left, eliminate apostrophes
Starting from the right and moving to the left, eliminate any remaining characters, excluding:
o Hyphens
o Remaining spaces
o Characters immediately following a hyphen or a space.
For example, in the case where a person's middle names are "V'Erylongmiddlename01 V'Erylongmiddlename02 Marie
Ŕ Louise" (58 characters), the truncation sequence will progress as follows:
Remove spaces adjacent to hyphens, resulting in "V'Erylongmiddlename01 V'Erylongmiddlename02 Marie-
Louise" (56 characters)
Remove apostrophes, resulting in "VErylongmiddlename01 VErylongmiddlename02 Marie-Louise" (54 characters)
Remove other characters as allowed, resulting in "VErylongmiddlename01 VErylongmi M-L" (35 characters)
E.2.5 Transliteration
The table below lists the transliteration values used when converting names to the characters allowed.
[pic]
[pic]
Note 1: The table is based on the transliteration tables used by ICAO for passports, with the difference that each character has only one transliterated value. The intent is to keep the table synchronized with the ICAO tables, but to do so in an orderly and planned fashion
Note 2: When matching characters on source documentation to characters in the table, it is important to note that different fonts may show the same character in different ways.
APPENDIX E.3 - AAMVA PERSON NAME STANDARD (2008) VALIDATIONS
A name is in conformance with this Appendix if all of the following are true:
It meets all the validations in the table below. If any of the validations are not met, the associated error text is returned.
It complies with the structure, formatting, truncation and transliteration requirements rules in "APPENDIX E.2 -
AAMVA PERSON NAME STANDARD (2008)" insofar as these rules are not already reflected in the table below.
It is administered in compliance with "APPENDIX E.4 Ŕ NAMES STORED ON JURISDICTIONS' SYSTEMS", if applicable.
[pic]
[pic]
APPENDIX E.4 – NAMES STORED ON JURISDICTIONS' SYSTEMS
Within technical limitations, names have to be retained in the same manner (including characters, spaces, apostrophes etc.) as the name appears on the credential from which it was obtained.
The First_Name, Middle_Name(s), Last_Name, and Suffix fields must respectively accommodate at least 40, 35, 40 and 5 characters. If name information has to be truncated to fit into the name fields stored by a Jurisdiction, the truncation rules specified in "E.2.4 Truncation" have to be used. If name information has to be transliterated to remove non-supported Latin characters, the transliteration rules specified in "E.2.5 Transliteration" have to be used.
Jurisdictions are encouraged to support extended character sets within their systems, especially those with significant Spanish or French Canadian populations. However, when communicating with other jurisdictions, the transliteration rule must be followed.
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- physical exam form
- website design search engine optimization and web
- system requirements specification
- note you can control click on the part numbers in this
- federal motor carrier safety administration
- connecticut department of transportation interview
- to connecticut cdl holders
- scanning tour of innovative towing programs
Related searches
- system requirements for office
- system requirements document example
- system requirements document template
- system requirements specification example
- dod system requirements document example
- system requirements for office 2019
- system requirements for office mac
- system requirements for office mobile
- office 2019 system requirements for windows
- office 365 system requirements pc
- office 365 system requirements windows
- office 365 system requirements mac