State of Minnesota Operator License Number (OLN) Service Outputs o MN person hot files based on NAM & DOB o FBI person hot files based on NAM & DOB o DVS drivers record information

GetPersonInfo Service Business and Technical Service Definitions Page 1 of 13

State of Minnesota Department of Public Safety Bureau of Criminal Apprehension

Query Person Information Service

Published On: July 17, 2008 for Pilot Service Release Version#: Pilot 0.1

Prepared By:

Bureau of Criminal Apprehension Criminal Justice Information Systems

1430 Maryland Avenue East St. Paul, Minnesota 55106

SERVICE SUMMARY

Service Name Query Person Information

Service Visibility

Public Restricted Private (see glossary for definition of public, restricted, and internal)

Service Description

Provides users with the capability of retrieving MN and FBI person hot file information based on name and DOB, as well as MN drivers license images.

Consumer Restricted to Law Enforcement , Probation and Parole Agencies Only

Accessibility This service is intended to be accessible by a law enforcement’s local application, such as a mobile application, RMS, JMS, dispatch, etc.

Service Inputs o Name (NAM) and Date of Birth (DOB) OR

o Operator License Number (OLN)

Service Outputs

o MN person hot files based on NAM & DOB

o FBI person hot files based on NAM & DOB o DVS drivers record information o DVS drivers license image

Status Concept Planned Available


Table of Contents

BUSINESS SERVICE DEFINITION .............................................................................. 3

SERVICE OVERVIEW .................................................................................................................... 3 SERVICE CONSUMERS AND ACCESS RIGHTS .............................................................................. 3 SERVICE-RELATED STATUTES ..................................................................................................... 3 AUDITING AND INFORMATION SECURITY REQUIREMENTS ....................................................... 3 SERVICE LOGGING REQUIREMENTS............................................................................................ 4 CONTACT INFORMATION ........................................................................................................... 4

TECHNICAL SERVICE DEFINITION .......................................................................... 4

ACCESSING THE SERVICE ............................................................................................................ 4 PRE-CONDITIONS (TECHNICAL) ................................................................................................ 4 POST-CONDITIONS (TECHNICAL) .............................................................................................. 4 INFORMATION DATA MODEL .................................................................................................... 4 SERVICE INTERFACE .................................................................................................................... 5 MESSAGE FORMAT ...................................................................................................................... 6 Request Message ..................................................................................................................... 6 Response Message ................................................................................................................... 6 Soap Fault ............................................................................................................................... 7

EXCEPTION CONDITIONS AND ERROR HANDLING .................................................................... 7 Format ..................................................................................................................................... 7 Specifics ................................................................................................................................... 7

SECURITY PROFILE ...................................................................................................................... 7

APPENDIX A: GLOSSARY ........................................................................................... 8

APPENDIX B: PERSONREQUEST – SAMPLE OLN REQUEST .................................. 9

APPENDIX C: PERSONREQUEST – SAMPLE NAM AND DOB REQUEST .............. 9

APPENDIX D: SAMPLE QDRRESPONSE ................................................................. 10

APPENDIX E: SAMPLE QPRESPONSE ...................................................................... 11

APPENDIX F: SAMPLE QDLIRESPONSE ................................................................. 11

APPENDIX G: SAMPLE LEMSCOMPLETERESPONSE ............................................ 12

APPENDIX H: SAMPLE SOAP FAULT ...................................................................... 12

APPENDIX I: SERVICE LEVEL EXPECTATION ....................................................... 13

Service Availability ............................................................................................................... 13 Support ................................................................................................................................. 13 External Service Dependencies ............................................................................................. 13 Known Maintenance Windows ............................................................................................ 13 Service Downtime Notification ............................................................................................ 13 Expected Response Times ..................................................................................................... 13


Business Service Definition

Service Overview

The Query Person Information retrieves MN and FBI person hot file information based on name and DOB, as well as drivers records and driver’s license images.

REQUESTOR:

Request Person

Information

BCA:

Retrieve and Return

Results

INPUTS:

Name (NAM) and Date of Birth (DOB)

OR

Operator License Number (OLN)

OUTPUTS:

(This is not a packaged output. There will be multiple output responses for each request)

MN person hot files based on NAM & DOB

FBI person hot files based on NAM & DOB

DVS drivers record information

DVS drivers license image

Service Consumers and Access Rights

The only authorized users of the Query Vehicle and Owners’ Information service are law enforcement officials, probation and parole officers. The Query Vehicle and Owners’

Information service is a query-only service. No updates occur with this service.

Service-Related Statutes

• MSS 299C.46 – Criminal Justice Data Communications Network

• MSS 171.07, subdivision 1A regarding access to driver photo information from Driver and

Vehicle Services.

• MSS 171.12, subdivision 7(d) regarding access to driver license address data

Auditing and Information Security Requirements

No service-specific auditing requirements currently exist for this service. Information obtained

through this service is confidential criminal justice data. Service consuming agencies must


ensure the continuing security and appropriate usage of information obtained through this service.

Service Logging Requirements

The service consuming entity must save all messages to a local log file. Both query and response information must be fully logged. Date, time of day, inquiring agency, and individual user ID

information must all be logged in addition to the content of the queries and responses. Log files require the same level of security as the original messages. Log files should be maintained for six years to meet State legislative auditor requirements. If a six

year retention program is not feasible for the consuming entity, the consuming entity may submit to the BCA a written request for an exemption to the six-year retention policy. The written request must include a detailed explanation describing the reason why the six year retention policy is not feasible and specify an alternative retention period. BCA management will consider each such request on a case by case basis.

Contact Information

For issues or questions regarding this service, please send an e-mail to the BCA Service Desk at:

[email protected].

Technical Service Definition

Accessing the Service

Access to the Query Person Information service is restricted to systems on the CJDN network. Refer to http://www.dps.state.mn.us/cjdn/ for the policies and requirements for gaining and maintaining access to the CJDN network. Follow the instructions in the Contact US section to request access to this password protected site.

Pre-Conditions (Technical)

The Query Person Information provides access to data from sources that require identification

information about the system making the request as well as user credentials for authentication and authorization. The LEMSSourceID, RequestID and UserID must be included in the body of the SOAP request. Refer to the SOAP Body under Request Message of the Message Format section for more details.

Post-Conditions (Technical)

Three data responses are returned as well as a response complete message. One or more SOAP fault messages are returned in the event of an error.

Information Data Model

The criteria for the information being requested must be placed in the body of PersonRequest. Refer to appendixes for sample SOAP request and response messages. The latest standard request schema will be available by end of year. The latest response schemas are located at:

• https://cjir.crimnet.state.mn.us/cjir/WebForms/ViewElementDetail.aspx?XPage=51fb79a3-0ec2-4469-a653-


dc7172aee77f:SetFilter:FilterField1%3d%252540Title%26FilterValue1%3dQPResponse%252520RunTime%252520Schema.

Service Interface

The Query Person Information implements a single operation.


Message Format

Request Message

The request to the Query Person Information services must be submitted as a SOAP message as follows:

SOAP Headers Not currently used

SOAP Body Refer to Appendix B and C for sample requests. The following is provided as a

high level structure only:

• OriginatingAgencyID

• LEMSSourceID

• RequestID

• UserID

• Criteria choice of o OLN or o Name and Date Of Birth

Response Message

The Query Person Information service returns multiple responses from the various source systems that it queries for data.

SOAP Headers Not currently used

SOAP Body Query Person Information returns three SOAP messages from source systems along with a lemsCompleteResponse message to signal that request processing has been completed. Refer to appendix D and F for samples of these messages:

• qdrResponse. Returns the driver license and driver history information for the person associated with the OLN.

• qpResponse. Returns information from the MN hot files such as wanted person, Orders for protection, gang members and predatory offenders. This response also includes information from NCIS such as wanted persons, missing persons, gang and terrorist organization members, convicted persons on supervised release, protection orders, sex offenders, deported and illegal alien as well as secret service protection.

• qdliResponse. Returns an image of the person associated with the requested OLN. “No Hit” Responses Within the qdrResponse and qpResponse structures, an element has been added to give a positive indication that no data was found matching the search criteria. This “No Hit” indicator applies only for the source system in which it is located, e.g. DVS or HotFiles. Consumers of the service should be aware that NoHit may be true for the HotFiles


section of a response while data is returned in the NCIC or DVS section, and vice versa.

Soap Fault

A SOAP fault is returned if errors are encountered during processing. Refer to the Exception Conditions and Error handling section of this document for more details on how errors are handled. One or more SOAP faults could be returned along with one or more responses depending on where the error occurred during processing. Refer to

Appendix H for a sample SOAP fault returned.

Fault code Fault string Request ID Level

Required Field Missing < id for this request > Fatal

Exception Conditions and Error Handling

Format

Errors are returned to the requester as SOAP faults. Within the <detail> element of the SOAP fault the following information is provided about the error:

• The unique identifier of the request which precipitated the error

• The section or unit of work where the error occurred.

• A more technical description of the error to complement the text in the <faultstring> element.

• A Boolean value which indicates whether this is a fatal error, i.e. precluding any further response, or whether the user may still expect further response(s) to their request.

Specifics

Multiple responses will be returned for a single request with a “Response Complete” notification, which lets the user know not to expect anything further. Multiple responses are returned to enable faster delivery of data, as requested by consuming agencies. Services of this nature present a challenge for error handling, since an error may affect only one of the responses while others return without any problems. A SOAP fault could be telling the user one of many things:

• There was a problem with the request, and the service is unable to return anything.

• There was a problem with one of the queries resulting from your request.

• There is an internal problem with the service which will prevent some or all of your responses from being returned.

The elements in the fault message specify at what point the error occurred, and on which query (if applicable). This helps communicates the effect the error on any remaining responses.

Security Profile

Security polices that apply to this operation including authentication/authorization, access control list and requirements for privacy, data integrity, non-repudiation, etc.


Appendix A: Glossary

Term Definition BCA Bureau of Criminal Apprehension. This division of the Minnesota Department of

Public Safety is responsible for crime lab, fingerprints, etc.

DOB Date of Birth

DVS Driver and Vehicle Services

FBI Federal Bureau of Investigation

Internal Service A classification for a service to indicate that it is available to be consumed only internally by the BCA

JMS Jail Management System. A software application specifically designed to electronically record information critical to effectively operating a prison, jail or holding facility.

LEMS Law Enforcement Message Switch.

MN Minnesota

NAM Name

NCIC National Crime Information Center. An information system and nationwide network serving local, state, and federal law enforcement agencies. A computer system maintained by the FBI, which can be queried by local agencies via state computer systems known as “control terminal agencies”.

Public Service A classification for a service to indicate that it is available for anyone to consume

QDLI Query Drivers License Image. A type of LEMS transaction that retrieves a driver’s license image from the Minnesota DVS.

QDR Query Drivers Record. A type of LEMS transaction that retrieves MN driver’s record information from the MN DVS.

QP Query Person. A type of LEMS transaction that retrieves person information from MN hot files.

Restricted Service A classification for a service to indicate that it is available for a limited group of people to consume

RMS Records Management System. A system that stores computerized records of crime

incident reports and other data. It is specifically designed to electronically record information critical to effectively operating a criminal justice facility.


Appendix B: PersonRequest – Sample OLN request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <PersonRequest xmlns="http://www.xmllegal.org/Schema/Organizations/PCG/LEMS_Simple/PersonRequest/Test02/">

<Request xmlns:r="http://www.xmllegal.org/Schema/Organizations/PCG/BuildingBlocks/LEMS/Request/Test01/"> <r:SourceID>DAK001</r:SourceID>

<r:RequestID>123456789</r:RequestID> <r:OriginatingAgencyORI>MNBCA0000</r:OriginatingAgencyORI> </Request> <CriteriaChoice>

<DriverLicenseID>R200478067967</DriverLicenseID> </CriteriaChoice> </PersonRequest> </soapenv:Body> </soapenv:Envelope>

Appendix C: PersonRequest – Sample NAM and DOB request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <PersonRequest xmlns="http://www.xmllegal.org/Schema/Organizations/PCG/LEMS_Simple/PersonRequest/Te

st02/"> <Request xmlns:r="http://www.xmllegal.org/Schema/Organizations/PCG/BuildingBlocks/LEMS/Request/Test01/">

<r:SourceID>DAK001</r:SourceID> <r:RequestID>123456789</r:RequestID> <r:OriginatingAgencyORI>MNBCA0000</r:OriginatingAgencyORI> </Request> <CriteriaChoice> <Criteria> <Name> <LastName>Duck</LastName> <FirstName>Donald</FirstName>

</Name>


<BirthDate>19730101</BirthDate> </Criteria> </CriteriaChoice> </PersonRequest> </soapenv:Body> </soapenv:Envelope>

Appendix D: Sample qdrResponse

<QDRResponse> <RequestID>111</RequestID>

<DMV> <Person> <NAM> <LAST>ROSS</LAST> <FIRST>KRISTY</FIRST> <MIDDLE>ANN</MIDDLE> </NAM> <SNM>5057 DIVISION</SNM> <CTY>WBL</CTY> <STA>MN</STA> <ZIP>55110</ZIP> <SEX>F</SEX>

<DOB>1963-12-21</DOB> <HGT>602</HGT> <WGT>100</WGT> <EYE>BLU</EYE>

<DriverLicense> <OLN>R200478067967</OLN> <OLT>1</OLT> <CLS>A</CLS> <EXP>122192 STATUS:EXPIRED DONOR:N DESIGNATED CAREGIVER:N

PHOTO:8200001001</EXP> <ISU>1988-09-13</ISU> </DriverLicense> </Person>

<CSC>VALID</CSC> <BLOB> * * * * TXT NAM/ROSS,KRISTY ANN.*RECORD DISSEMINATION RESTRICTED* SNM/5057 DIVISION. CTY/WBL. STA/MN. ZIP/55110. SEX/F. DOB/19631221. HGT/602. WGT/100. EYE/BLU. DISABILITY CERTIFICATES:N OLN/R200478067967. OLT/1. CLS/A.

CSC/VALID. EXP/122192 STATUS:EXPIRED DONOR:N DESIGNATED CAREGIVER:N PHOTO:8200001001.ISU/091388.DNR TRAINING=FIREARM:N,SNOWMOBILE:N NO VIOLATIONS</BLOB> </DMV> </QDRResponse>


Appendix E: Sample qpResponse

<QPResponse> <RequestID>111</RequestID> <HotFiles> <ORI>DAK001</ORI> <Person> <NAM> <LAST>ROSS</LAST> <FIRST>KRISTY</FIRST> <MIDDLE>ANN</MIDDLE> </NAM> <DOB>1963-12-21</DOB> </Person>

<BLOB>NO HIT WANTED PERSON FILE QP ORI/DAK001.NAM/ROSS, KRISTY ANN.DOB/19631221. </BLOB> </HotFiles> <NCIC>1L0103BC000FC92QW MNBCA0000 NO NCIC WANT NAM/R0SS,KRISTY ANN D0B/19631221 ***MESSAGE KEY QW SEARCHES WANTED PERSON FILE FELONY RECORDS REGARDLESS OF EXTRADITION AND MISDEMEANOR RECORDS INDICATING POSSIBLE EXTRADITION FROM THE INQUIRING AGENCY'S LOCATION. ALL OTHER NCIC PERSONS FILES ARE SEARCHED WITHOUT LIMITATIONS.</NCIC> </QPResponse>

Appendix F: Sample qdliResponse ** Note – Only the first few characters of <BinaryObject.Base64> is shown below

<QDLIResponse> <RequestID>111</RequestID> <HotFiles> <ResponseTxt>Driver License Photo Response DL Photo for: </ResponseTxt> <Person> <NAM>

<LAST>ROSS</LAST> <FIRST>KRISTY</FIRST> <MIDDLE>ANN</MIDDLE> </NAM> <DriverLicense> <OLN>P136181797010</OLN> </DriverLicense> </Person> <BinaryObject.Base64>/9j/4AAQSkZJRgABAAEAYABgAAD/2wCEAA4KCw0LCQ4NDA . . . Rest of binary object … </BinaryObject.Base64> <BinaryFormatText>JPG</BinaryFormatText> </HotFiles> </QDLIResponse>


Appendix G: Sample lemsCompleteResponse <?xml version="1.0"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <lemsResponseComplete> <RequestID>123456789</RequestID> </lemsResponseComplete> </soapenv:Body> </soapenv:Envelope>

Appendix H: Sample SOAP Fault

<?xml version="1.0"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <soapenv:Fault>

<faultcode>soap:Client</faultcode> <faultstring>Required Field Missing</faultstring> <detail> <RequestID>123456789</RequestID> <Level>Fatal</Level> </detail> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope>


Appendix I: Service Level Expectation

Service Availability

The Query Vehicle and Owners’ Information service is designed to operate 24/7/365.

Support

On call support is available Monday – Friday, 8:00 a.m. to 4:30 p.m. through the BCA Service Desk at telephone number: 651-793-2500 or 1-888-234-1119

External Service Dependencies

• Motor vehicle registration and Driver License Data, including the driver license image is provided through an interface with MN Driver and Vehicle Services Division (DVS).

• NCIC Hot Files data is provided by the FBI National Crime Information System

Known Maintenance Windows

The DVS driver license image server goes down for maintenance Tuesday – Saturday from about 6:03 a.m. until about 6:08 a.m. Queries sent during this timeframe may receive the following error:

ERROR: Database Error - cause unknown.

Service Downtime Notification

Describe how consuming entity will be notified of planned downtimes and system problems

Expected Response Times

Responses from each system queried are delivered separately to ensure the speedy return of information as it becomes available. Average response times vary depending on the responding system as described

below.

• DVS Responses: within one second

• MN Hot Files Responses: within two seconds

• NCIC Hot File Responses: within 30 seconds

Revision History

Rev. Num. Rev. Date Reason Prepared by

0.1 07/17/2008 Pilot Release Patty Hunter

State of Minnesota Operator License Number (OLN) Service Outputs o MN person hot files based on NAM & DOB o FBI person hot files based on NAM & DOB o DVS drivers record information

Documents