Background Checking: Background Requests
Recommendation, 2006 Feb 28
Editors: Craig Corner, HireCheck; Chuck Allen, HR-XML Consortium, Inc.
Contributors:
Brad Whitney, American Background; Sue Morgan, HireCheck; Mark Sulimirski, ChoicePoint; Paul Kiel, HR-XML Consortium, Inc.; Dan Gagne, HireRight; Owen Wilson, Total Information Services, Inc.; Ralph Jimenez and Gary Nargiz, EdVerify, Mark Jones; Kim Bartkus, HR-XML Consortium
Copyright statement
©2006 HR-XML. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of the publisher.
Abstract
HR-XML’s Background Checking specification supports requests to providers of employment screening services and the return of search results. The specification consists of a number of components, one of which is the BackgroundCheck Requests specification. As the name implies, the BackgroundCheck Requests specification defines messages to support background-check requests to third-party service providers.
Status of this Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Table of Contents
3 Implementation Considerations
3.2 Laws Governing Background Checks
3.3 Required/Recommended Fields
4 Appendix A – Document Version History
5 Appendix B – Related Documents
6 Appendix C – Reference Examples
7 Appendix D - Required/Recommended Fields Chart
1 Overview
The BackgroundCheck Requests specification is a component of the HR-XML Consortium’s Background Checking specification.
The entire Background Checking specification is explained in
a separate overview document:
http://ns.hr-xml.org/2_5/HR-XML-2_5/Screening/US/BackgroundChecking.html
This document contains only the definitions for the schema used for background check requests.
The BackgroundCheck Requests specification also makes extensive use of the Consortium’s approved “Cross Process Objects” (CPOs). A list of documentation for the Consortium’s complete set of CPOs can be found in Appendix B.
The following changes were made to the Background Requests 2.1 specification. The schema, documentation and instances have been updated accordingly.
Background Check schema and Background Requests documentation
· Added optional element BackgroundSearchPackage\ProcessingInformation
· Added optional element BackgroundSearchPackage\SupportingDocumentation
· Added SearchDrug to Screenings schema, which affected this specification.
· Added AdmittedChargeSummary to Screenings schema, which affected this specification.
1.1 Objective
The Background Requests specification defines a schema that can be used to structure background check requests to providers of employment screening services.
1.2 Design Requirements
The HR-XML Consortium’s Background Requests 2.0 specification was built upon the Consortium’s original background check specification. Wherever possible, the HR-XML Consortium’s Screening Workgroup attempted to make the schema for background check requests backwardly compatible with the original version of the specification.
2 Schema Design
2.1 BackgroundCheck Schema
2.1.1 BackgroundCheck
|
Component Name [Global types listed at the end of the table.] |
ContentModel* |
Definition |
|
/ |
- BackgroundCheckType - (1/1) |
Root element for Background Check schema, which is designed to hold data necessary to execute requests for one or more types of screenings. |
|
/
BackgroundCheck/ |
- EntityIdType - S (0/1) |
A trading-partner identifier. |
2.1.2 BackgroundSearchPackage
|
/ BackgroundCheck/ |
type - xsd:string
- optional |
Container to describe screening request information for a single search subject. |
|
/ BackgroundCheck/
BackgroundSearchPackage/ |
- xsd:string - |
Further defines the associated
element in the context provided. |
|
/ BackgroundCheck/
BackgroundSearchPackage/ |
- xsd:string - |
Indicates if the associated information is an update to existing information such as a missing information. |
|
/ BackgroundCheck/ BackgroundSearchPackage/ |
AccessCredential - AccessCredentialType - S
(0/*) |
Contains additional details related to an applicant. Contextual: The typical use of AccessCredential within this element would be in the situation where we are working with an ATS or other 3rd party that will be sending searches on behalf of a number of mutual clients. This Access Credential will contain the account information for the mutual client. |
|
/ BackgroundCheck/ BackgroundSearchPackage/
ProcessingInformation/ |
- AccessCredentialType - S (0/*) |
Information required to login to an account or document. |
|
/ BackgroundCheck/
BackgroundSearchPackage/ ProcessingInformation/ |
- FlexibleDetailType - S (0/*) |
Provides a means for overriding a clients standard scope of work. [Example: scenario where the TPA is to run criminal searches only on the primary name, however, for this specific search subject they may want to run criminal searches on a prior name. ] |
|
/ BackgroundCheck/
BackgroundSearchPackage/ |
- EntityIdType - S (0/1) |
A trading-partner specific identifier. |
|
/ BackgroundCheck/
BackgroundSearchPackage/ |
- ReferralType - S (0/1) |
This element contains the point of contact for the screening company in the event that there is missing information that the client must provide before the screening can be completed. In larger companies, there can be a number of individuals within an organization responsible for the hiring process. |
|
/ BackgroundCheck/
BackgroundSearchPackage/ |
- ReferralType - S (0/*) |
Contains information about the organization. Annotation: Identifies the organization that the search(s) will be performed upon or on behalf of depending on the value of type. |
|
/ BackgroundCheck/
BackgroundSearchPackage/ |
- ScreeningPersonalDataType - S (0/*) |
A collection of information containing descriptive elements, demographic and contact information about the person. Annotation: Personal data related to the Search Subject that the search(s) will be performed upon. |
|
/ BackgroundCheck/
BackgroundSearchPackage/ |
- DocumentationType - S (0/1) |
Container for additional information related to the specified search. [Example(s): Internet Web Address, Routing ID, Image ] |
|
/ BackgroundCheck/
BackgroundSearchPackage/ |
- ScreeningRequestType - S (0/*) |
Contains information on the specific types of screenings to be performed and the information necessary to carry out those screenings. |
2.1.3 Screenings
|
/
BackgroundCheck/ BackgroundSearchPackage/ |
- ScreeningRequestType - S (0/*) |
Contains information on the specific types of screenings to be performed and the information necessary to carry out those screenings. |
ScreeningRequestType
|
/ |
ReferenceId
- EntityIdType - S
(0/1) |
Globally scoped data type. See element or attribute declaration for definition. |
|
/
[ScreeningRequestType]/ |
- EntityIdType - S (0/1) |
A trading-partner identifier. |
|
/
[ScreeningRequestType]/ |
- EntityIdType - S (0/1) |
An identifier for a BackgroundSearchPackage. |
|
/
[ScreeningRequestType]/ |
- ScreeningPersonalDataType - S (0/*) |
A collection of demographic data supplied as input to screenings. This component has been deprecated. BackgroundSearchPackage/PersonalData is the preferred place to capture this information. |
|
/
[ScreeningRequestType]/ |
- EntityIdType - S (0/*) |
Client references, such as billing codes, department codes, etc. |
|
/
[ScreeningRequestType]/ |
- DocumentationType - S (0/1) |
Additional information supporting the search. |
|
/
[ScreeningRequestType]/ |
- xsd:boolean - S (0/1) |
Indicates if screening subject has requested a copy of the screening results. CopyToApplicant has a boolean value. |
2.1.4 AdditionalItems
The HR-XML Consortium’s Background Checking specification makes extensive use of the AdditionalItems component both within the BackgroundCheck Request and BackgroundReports schemas. This component is intended as a flexible, but structured container that allows a client to pass through additional search criteria in BackgroundCheck Requests. AdditionalItems also allows a screening provider to respond to such criteria in BackgroundReports. AdditionalItems is one means that the Background Checking specification provides trading partners to implement custom screening types and custom screening criteria.
The AdditionalItems structure is available within each screening type within both the BackgroundCheck Request and BackgroundReports schemas. Both the BackgroundCheck Request and BackgroundReports schemas also contain a UserArea in several places within the schemas. The UserArea uses the “any” datatype, which allows it to accommodate any arbitratary XML structure (see the separate specification titled HR XML Schema Extension 1.0). As a general rule, implementers should first evaluate using the AdditionalItems component as a means to exchange additional search criteria or results before resorting to the use of the UserArea.
|
/
[ScreeningRequestType]/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
Sequence
- xsd:positiveInteger - S (0/1) |
Globally scoped data type. See element or attribute declaration for definition. |
|
|
/
[FlexibleDetailType]/ |
- xsd:positiveInteger - S (0/1) |
An integer indicating the sequence in which multiple items should be considered. |
|
/
[FlexibleDetailType]/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
[FlexibleDetailType]/ EffectiveDate/ |
- FlexibleDatesType - S (0/1) |
The beginning effective date for the specified supporting information. |
|
/
[FlexibleDetailType]/ EffectiveDate/ |
- FlexibleDatesType - S (0/1) |
The ending effective date for the specified supporting information. |
|
/
[FlexibleDetailType]/ |
- xsd:string - S (1/*) |
Explanatory text. |
|
/
[FlexibleDetailType] / |
- FlexibleLineType - |
The type or classification for the related component. |
|
/
[FlexibleDetailType] / |
- xsd:string - |
Additional qualification or classification data. |
|
/
[FlexibleDetailType] / |
- VendorType - |
Identifies the vendor or supplier. |
|
/ |
- [Union]: FlexibleLineTypes,xStringPatternExtensionType |
An extensible list of types. Used to identify the type of AdditionalItem. Enumerations include “Header”, “Informational”, “Detail”, “Trace”, “RawData”, and “Unknown”. Additional values are permitted if prefixed with “x:”. |
|
/ |
xsd:restriction base: xsd:string [Enumerations]: Header, Informational, Detail, Trace, RawData, Unknown |
A list of types used to identify the type of AdditionalItem. |
2.1.5 Screening
|
/ |
type - SearchTypes
- |
Contains information for screening or testing data about the candidate. |
|
/ Screening/ |
- SearchTypes - |
Further defines the associated
element in the context provided. |
|
/ Screening/ |
- SearchQualifierType - |
Enumerated list of search type
qualifiers. Refer to SearchQualifiers for more details. |
|
/ Screening/ |
|
Globally scoped data type. See element or attribute declaration for definition. |
|
/ Screening/ |
- EntityIdType - S (0/1) |
A trading-partner specific identifier. Annotation: Reference Number associated with this screening. |
|
/ Screening/ |
- EntityIdType - S (0/1) |
Specifies the question set id to be used in a variety of candidate screening processes. |
|
/ Screening/ |
- CountryCodeType - S (0/1) |
Contains the ISO 3166-1 two-character country code. [BusinessRule(s): For
authorities not bound by a country, the attribute would be blank. ] |
|
/ Screening/ |
- xsd:string - S (0/1) |
Represents the State, Province, and/or
County. |
|
/ Screening/ |
- ServiceLevelTypes - S (0/1) |
Service level of the agreement entered into by trading partners. |
|
/ Screening/ |
- PermissiblePurposeQualifiers - S (0/1) |
Specifies the purpose of the screening. [Example(s): Consumer Initiated Transaction, Written Authorization, Collection ] |
|
/ Screening/ |
- xsd:string - S (0/1) |
It specifies the name of the company that has requested the screening. |
|
/ Screening/ |
- VendorType - S (0/1) |
An entity that provides products
or services to another entity. Annotation: Specifies the source of the
screening information. |
|
/ Screening/ |
- xsd:duration - S (0/1) |
Specifies the duration of the reported work. [BusinessRule(s): If not specified, typically the duration is derived by the receiving system on the basis of work schedule information and/or Start/EndDateTime, ] |
|
/ Screening/ |
- EntityIdType - S (0/*) |
Container to provide additional screening related information specific to all searches for the specified applicant. |
|
/ Screening/ |
- xsd:string - S (0/*) |
Describes the contextual
information relating to a group of elements. |
|
/ Screening/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing
other relevant details and search criteria. |
|
/ Screening/ |
- DocumentationType - S (0/1) |
Container for additional information related to the specified search. [Example(s): Internet Web Address, Routing ID, Image ] |
2.1.6 SearchCriminal
|
/ Screening/ |
Municipality - xsd:string - S (0/1) |
Contains information to execute a criminal background search. |
|
/ Screening/ SearchCriminal/ |
- xsd:string - S (0/1) |
Represents the city, town, village, or hamlet. Annotation: City within region to be searched. |
|
/ Screening/ SearchCriminal/ |
- xsd:string - S (0/1) |
County within region to be searched where the charge was processed. [BusinessRule(s): If county and/or court is not available, then PostalCode and Municipality must be supplied. In all cases, Region and CountryCode in the parent element must be supplied. ] |
|
/ Screening/ SearchCriminal/ |
- xsd:string - S (0/1) |
Codes established by postal authorities for purposes of sorting and delivering mail. See PostalAddress Recommendation. Annotation: Postal code within region to be searched. |
|
/ Screening/ SearchCriminal/ |
- xsd:string - S (0/1) |
Name of court. This may include the location, such as region, county or postal code. [BusinessRule(s): If court and/or country is not available, Postal Code and Municipality must be supplied in all cases. Region and country Code in the parent element must be supplied. ] |
|
/ Screening/ SearchCriminal/ |
xsd:extension base: xsd:string |
Jurisdiction of court to be searched. [Example(s): Felony, Misdemeanor, Both ] |
|
/ Screening/ SearchCriminal/
CourtType/ |
xsd:restriction base: xsd:string [Enumerations]: felony, misdemeanor, felonyMisdemeanor |
Further defines the associated
element in the context provided. |
|
/ Screening/ SearchCriminal/ |
- xsd:string - S (0/1) |
Identifies private database to be searched. [BusinessRule(s): Primarily used for statewide searches. ] |
|
/ Screening/ SearchCriminal/ |
- ScreeningPersonalDataType - S (0/*) |
Contains information on aliases admitted or supplied by the search subject. Annotation: Client provided information to enable scoring of results based upon Search Subject provided information. |
|
/ Screening/ SearchCriminal/ |
- xsd:string - C (0/1) |
Summary of Admitted Charges. |
|
/ Screening/ SearchCriminal/ |
CriminalCase - xsd:string - S (0/*) |
Contains information on charges admitted by the search subject. Annotation: Client provided information to enable scoring of results based upon Search Subject provided information. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ |
CaseNumber - xsd:string - S (0/1) |
Contains information identifying and describing a criminal case or charges to which the search subject admits. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
- xsd:string - S (0/1) |
Case number assigned by the court. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
xsd:extension base: xsd:string |
Identifies the criminal activity such as a Department of Corrections Id. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ OtherCaseId/ |
- xsd:string - |
Further defines the associated
element in the context provided. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
- xsd:string - S (0/1) |
Identification of the originating arrest agency. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
- xsd:string - S (0/1) |
The limits or territory within which authority may be exercised. Annotation: Name, division and district of the Court. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
- CountryCodeType - S (0/1) |
Contains the ISO 3166-1
two-character country code. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
- xsd:string - S (0/1) |
Represents the State, Province,
and/or County. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
- xsd:string - S (0/1) |
County within region to be searched where the charge was processed. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
- xsd:string - S (0/1) |
Represents the city, town, village, or hamlet. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
- FlexibleDatesType - S (0/1) |
Filing date related to the case. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ |
ChargeOrComplaint - xsd:string - S (1/1) |
Contains information about criminal charges related to the case. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- xsd:string - S (1/1) |
Identifies a crime, offense, infraction or violation for which the defendant was arrested. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- ChargeQualifiers - S (0/1) |
Identifies the seriousness of an
offense. [BusinessRule(s): Additional qualifiers agreed to by trading
partners may be specified by preceding the qualifier with an x: ] |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- FlexibleDatesType - S (0/1) |
Date of the arrest or date the summons was served to the person. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- FlexibleDatesType - S (0/1) |
Date offense was committed. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- xsd:string - S (0/1) |
Information regarding the penalty
for a given offense. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- FlexibleDatesType - S (0/1) |
Date of sentencing. |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- xsd:string - S (0/1) |
Describes the end result of a case. [Example(s): Guilty, Not Guilty, Pled Guilty, Mistrial ] |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- FlexibleDatesType - S (0/1) |
The date the case was disposed. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601. ] |
|
/ Screening/ SearchCriminal/
AdmittedCharges/ CriminalCase/ Charges/ |
- xsd:string - S (0/1) |
Information regarding the search subject's probation status. |
|
/ Screening/ SearchCriminal/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details and search criteria. |
2.1.7 SearchDrug
|
/ Screening/ |
ReasonForTest - ReasonForTestType - S
(0/1) |
Contains information to execute a drug background check. |
|
/ Screening/ SearchDrugs/ |
- ReasonForTestType - S (0/1) |
The reason test was performed. [Example(s): Periodic; PostAccident; Pre-employment; Random; Sports Testing; ReturnToDuty; Followup; and Other ] |
|
/ Screening/ SearchDrugs/ |
type - xsd:string
- |
Identifies the type of test to be performed, taken, or administered. |
|
/ Screening/ SearchDrugs/
TestType/ |
- xsd:string - |
Further defines the associated
element in the context provided. |
|
/ Screening/ SearchDrugs/
TestType/ |
SubstanceType - SubstanceTypeType - S (1/1) |
Contains information about the substance for which the screening is being conducted. |
|
/ Screening/ SearchDrugs/
TestType/ Substance/ |
- SubstanceTypeType - S (1/1) |
The name or type of substance for which a screening is being conducted. [Example(s): THC, PCP, AMP, Amphetamines, Barbiturates, alcohol, etc. ] |
|
/ Screening/ SearchDrugs/ |
- FlexibleDatesType - S (0/1) |
The date the specimen will be collected. |
|
/ Screening/ SearchDrugs/ |
type - xsd:string
- |
The place designated where individuals present themselves for the purpose of providing a specimen to be analyzed for the presence of drugs. |
|
/ Screening/ SearchDrugs/
CollectionSite/ |
- xsd:string - |
Further defines the associated
element in the context provided. |
|
/ Screening/ SearchDrugs/
CollectionSite/ |
- xsd:string - S (0/1) |
The name by which an organization or enterprise is known as established under the laws of a country, state, province or ruling governmental body for the purpose of conducting business transactions. |
|
/ Screening/ SearchDrugs/
CollectionSite/ |
- PostalAddressType - S (0/1) |
A mailing address. Describes a
postal address used for delivery of mail. The address may include the country
code, postal code, a region, municipality, delivery address, and the
recipient. Annotation: The address where the search subject will
provide the specimen. |
|
/ Screening/ SearchDrugs/ |
- EntityIdType - S (0/1) |
Unique identifier used to track a specimen. [BusinessRule(s): Accounts for the integrity of each specimen by tracking its handling and storage from point of specimen collection to final disposition of the specimen. ] |
|
/ Screening/ SearchDrugs/ |
- ReferralType - S (0/*) |
Contains information about the organization. Annotation: Contains contact information relating to the organizations involved with this request for Drug testing. i.e. Requesting Organization or Organization reviewing the results. |
|
/ Screening/ SearchDrugs/ |
- EntityIdType - S (0/1) |
Contains additional information regarding an applicant. Annotation: For capturing additional search related information associated with a specific question. |
|
/ Screening/ SearchDrugs/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details and search criteria. |
2.1.8 SearchEducation
SearchEducation incorporates EducationHistory.xsd. For
further information, see:
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/EducationHistory.html
|
/
Screening/ |
EducationHistory
- [see include/import] - S (1/1) |
Contains information necessary to research an individual's education history. |
|
/
Screening/ SearchEducation/ |
- EntityIdType - S (0/1) |
References an identifier associated with a customer question set. |
|
/
Screening/ SearchEducation/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
2.1.9 SearchEmployment
SearchEmployment incorporates EmploymentHistory.xsd. For
further information, see:
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/EmploymentHistory.html
|
/
Screening/ |
EmploymentHistory
- EmploymentHistoryType - S (1/1) |
Contains information necessary to research or verify a search subject's employment history. |
|
/
Screening/ SearchEmployment/ |
- EmploymentHistoryType - S (1/1) |
A list of previous positions held by the search subject. |
|
/
Screening/ SearchEmployment/ |
- EntityIdType - S (0/1) |
References an identifier associated with a customer question set. |
|
/
Screening/ SearchEmployment/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
/
Screening/ SearchEmployment/ |
- EmploymentType - |
The type or classification for the related component. |
2.1.10 SearchLicense
|
/
Screening/ |
License
- LicenseType - S
(1/1) |
A collection of information necessary to perform a license search/verification. |
|
/
Screening/ SearchLicense/ |
- LicenseType - S (1/1) |
Contains client-supplied information to identify the license. |
|
/ Screening/
SearchLicense/ License/ |
- xsd:string - S (1/1) |
License Number. |
|
/
Screening/ SearchLicense/ License/ |
- xsd:string - S (1/1) |
Client-provided information on the identity of the licensing agency. |
|
/
Screening/ SearchLicense/ License/ |
- LicenseNameType - S (0/1) |
Name of the license. An enumerated set of license names are provided by LicenseNameQualifiers. LicenseNameQualifiers include: ARRT; CNA; CPA; Dietician; Dentist; Dietician; Dentist; EMT; Engineer; FAA; FCC; GSA; LPN; Lawyer; LVN; Lawyer; MVCommercial; MVPersonal; MVPersonalCommercial; Nurse; OccupationalTherapist; Optometrist; Paramedic; Physician; PhysicalTherapist; Pharmacy; Paramedic; RNLVN; Radiology; RadTech; Radiology; RN; SpeechTherapist; SocialWorker; SpeechTherapist; and Teacher. Additional types may be supplied by prefixing the LicenseName with an x: |
|
/
Screening/ SearchLicense/ License/ |
- xsd:string - S (0/1) |
A description of the license provided by the client. |
|
/ Screening/
SearchLicense/ License/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
Screening/ SearchLicense/ |
- EntityIdType - S (0/1) |
References an identifier associated with a customer question set. |
|
/
Screening/ SearchLicense/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
2.1.11 SearchMilitary
SearchMilitary incorporates MilitaryHistory.xsd. For further
information, see:
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/MilitaryHistory.html
|
/
Screening/ |
MilitaryHistory
- ScreeningsMilitaryHistoryType - S (1/1) |
Contains information necessary or relevant for a search to verify military service. |
|
/
Screening/ SearchMilitary/ |
- ScreeningsMilitaryHistoryType - S (1/1) |
Contains a collection of information related to the search subject's military service. Includes countries served, branch of service, rank achieved, dates of service, areas of special training or experience, recognition or honors received, and discharge status. |
|
/
Screening/ SearchMilitary/ |
- EntityIdType - S (0/1) |
References an identifier associated with a customer question set. |
|
/
Screening/ SearchMilitary/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
|
/
Screening/ SearchMilitary/ |
- EmploymentType - |
The type or classification for the related component. |
2.1.12 SearchOther
|
/
Screening/ |
GovernmentId
- xsd:string - S
(0/1) |
Other type of search agreed to by trading partners. |
|
/
Screening/ SearchOther/ |
xsd:extension base: xsd:string |
An identification number issued by a government to identify a person. For example the CPF in Brazil, or the Social Security Number in the United States. |
|
/
Screening/ SearchOther/ GovernmentId/ |
- xsd:string - |
An ISO 3166 two-character country code. |
|
/
Screening/ SearchOther/ GovernmentId/ |
- xsd:string - |
The name of the jurisdiction. |
|
/
Screening/ SearchOther/ GovernmentId/ |
- xsd:string - |
Specifies the issuing authority of the identifier, e.g. United Nations, Department of Motor Vehicles. Note that “issuingAuthority” generally would contain finer-grained information than “jurisdiction”. For example, a jurisdiction might be “New York,” whereas issuingAuthority might be Department of Motor Vehicles. |
|
/
Screening/ SearchOther/ GovernmentId/ |
- xsd:string - |
Specifies the type of document associated with the GovernmentId, e.g. drivers license, passport. |
|
/
Screening/ SearchOther/ |
- EffectiveDateType - S (0/1) |
Date or time interval on or during which information is effective or known to be correct. |
|
/
Screening/ SearchOther/ |
- ReferralType - S (0/1) |
Identifies the organization that the search(s) will be performed upon, or on behalf of, depending on the value of the type attribute. Built-in enumerations include: SearchSubject; Client; Proxy; and Vendor. Additional values are permitted if prefixed with "x:". |
|
/
Screening/ SearchOther/ |
xsd:extension base: xsd:string |
Additional supporting information agreed to by the trading partners. |
|
/
Screening/ SearchOther/ AdditionalText/ |
- xsd:string - |
The type or classification for the related component. |
|
/
Screening/ SearchOther/ |
- EntityIdType - S (0/1) |
References an identifier associated with a customer question set. |
|
/
Screening/ SearchOther/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
2.1.13 SearchReference
|
/
Screening/ |
Contact
- ContactType - S
(1/1) |
Contains information necessary to research the search subject's professional references. |
|
/
Screening/ SearchReference/ |
- ContactType - S (1/1) |
Contact information for a professional or other reference. |
|
/
Screening/ SearchReference/ |
- EntityIdType - S (0/1) |
References an identifier associated with a customer question set. |
|
/
Screening/ SearchReference/ |
- FlexibleDetailType - S (0/*) |
A flexible container for passing other relevant details. |
2.1.14 Global Simple Types
|
/ |
xsd:restriction base: xsd:string [Enumerations]: To acquire/service/insure account, Consumer initiated transaction, Written authorization, Collection, Child support, Credit Transaction, Employment, Government license of benefit, Insurance Underwriting, Account Review, Court Order/subpoena, Tenant Screening |
Globally scoped data type. See element or attribute declaration for definition. |
|
/ |
- [Union]: NAPermissiblePurposeQualifiers, xStringPatternExtensionType |
Globally scoped data type. See element or attribute declaration for definition. |
3 Implementation Considerations
3.1 Data Privacy
Human resources data, by its very nature, is personal data. The laws of many jurisdictions as well as codes of fair information practice require organizations to handle personal data in a way that protects individuals from loss of privacy.
The data exchange specifications developed by the HR-XML Consortium are designed to be useful across many jurisdictions and within a variety of business contexts. It is not feasible for the HR-XML Consortium to develop specific privacy guidance for every jurisdiction or business context in which the Consortium's specifications might be implemented. When implementing data exchanges using the HR-XML Consortium's data definitions (or, for that matter, any data exchange mechanism), organizations are advised to examine the privacy protections that may be required under applicable law or codes of fair information practice.
For information on protecting personal data, general references include: European Union Data Protection Directive (95/46/EC); the Association Computing Machinery Code of Ethics (1992); Canadian Standards Association Model Code for the Protection of Personal Information (1995 -- PIPEDA); U.S.-EU Safe Harbor Principles and FAQs (2000).
3.2 Laws Governing Background Checks
Implementors of the Background Checking are advised to review applicable law in the jurisdictions in which they operate. For example, in United States, the Fair Credit Reporting Act may require third-party providers of background check services to obtain the consent of search subjects and to advise them of results before adverse action is taken.
3.3 Required/Recommended Fields
The HR-XML BackgroundSearchPackage schema incorporates a significant amount of optionality. This optionality allows the schema to be flexibly used within a variety of contexts.
The data required to execute a background check will vary significantly depending on the type of searches conducted and the requirements of the jurisdictions in which the searches are performed. For instance, one jurisdiction might require the identification of a search subject’s race and gender for a criminal record search, whereas another jurisdiction may not impose such requirement.
The data provided in a background search request also can vary based on trading partner requirements and capabilities. For instance, as a matter of policy or practice, some background search customers may not collect, or be willing to provide, data required to execute a particular search (for example, a search subject’s date of birth). Likewise, one provider of background checking services may be willing to accept less information in a background check request than what another provider might minimally require.
While requirements vary by jurisdiction, HR-XML’s Screening Workgroup has developed some broad guidance for what data generally is required to execute background searches within the United States. That guidance is contained in the matrix that appears in Appendix D, Required and Recommended Fields.
It is not practical to design constraints within a single schema to accommodate each business context. Nor does it make sense to design a separate schema for each context. Implementors may want to handle data validation at the application level or examine the best practices outlined in HR-XML’s schema design guidelines for subsetting and constraining standard schema. At the time that this standard was published, guidelines for subsetting and constraining standard schema had been drafted, but not finalized.
4 Appendix A – Document Version History
|
Date |
Description |
|
2002 Dec 16 |
Initial Draft |
|
2003 Jan 23 |
Incorporated changes required as a result of CPO and TSC review. |
|
2003 Feb 10 |
Incorporate edits from review |
|
2003 Feb 17 |
Edits to reflect schema changes to resolve ambiguous content models. |
|
2003-Feb-26 |
Approved recommendation by HR-XML Consortium. The default and targetNamespaces of all HR-XML schemas have been standardized to "http://ns.hr-xml.org". This recommendation is available as part of the HR-XML 2_0 architecture. |
|
2003-Sept-01 |
EmploymentHistory 2_2 passed a vote and incorporated here. No other changes. |
|
2004-July-01 |
See overview section for details. |
|
2006-Feb-28 |
Approved by Consortium |
5 Appendix B – Related Documents
|
Link |
|
|
Entity Identifiers |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/EntityIdentifiers.html |
|
Date/Time data types |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/DateTimeDataTypes.html |
|
Contact Method |
|
|
Person Name |
|
|
PostalAddress |
|
|
Competencies |
|
|
WorkSite |
|
|
Background Reports |
http://ns.hr-xml.org/2_5/HR-XML-2_5/Screening/US/BackgroundReports.html |
|
Background Requests |
http://ns.hr-xml.org/2_5/HR-XML-2_5/Screening/US/BackgroundRequests.html |
|
Credit Report |
http://ns.hr-xml.org/2_5/HR-XML-2_5/Screening/US/CreditReport.html |
|
Education History |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/EducationHistory.html |
|
Employment History |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/EmploymentHistory.html |
|
Military History |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/MilitaryHistory.html |
|
Job and Position Headers |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/JobAndPositionHeader.html |
|
ISO Utilities |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/GuidelinesForISOUtilities.html |
|
Identifier Types |
http://ns.hr-xml.org/2_5/HR-XML-2_5/CPO/IdentifierTypes.html |
6 Appendix C – Reference Examples
6.1 BackgroundCheck Example
See:
http://ns.hr-xml.org/2_5/HR-XML-2_5/Screening/US/BackgroundCheck.xml