HR-XML 3.0 Standards, 2009 September 23.
Menu: [ Home | Guidelines | BODs | Nouns | Global elements | WSDL | Packages | Code Lists | Master Index ]
Trace back: » ch25 | ch25s04 | ch26 | ch26s04 | ch27 »
Table of Contents
HR-XML's Screening specifications are designed to support three different implementation patterns: "order by package identifier"; "a la carte"; and "order by package, plus" (see separate document, Screening Scenarios for further information). This document and the accompanying runtime packages are intended to support the "order-by-package identifier" pattern. This is the most common and the simplest way of handling screening orders and reports.
As the name implies, the "order by package" pattern involves bundling all screening service options within predefined packages that are known to the customer and to the screening provider. This enables services to be ordered simply by referencing an associated "PackageID." When using this pattern, details about specific screening services do not have to be communicated within the order. This simplifies order creation significantly and provides the opportunity to use an interoperable subset of the full ScreeningOrder noun.
An order is created with a ProcessScreeningPackageOrder BOD, which is responded to with an AcknowledgeScreeningPackageOrder. A ConfirmBOD may be returned upon an error. These would be operations hosted by the screening service supplier and called by the customer or requesting system.
Under the order-by-package pattern the following constraints apply:
A PackageID MUST be specified:
/ScreeningOrder/ScreeningPackageOrder/PackageIDAn order conforming to this profile MUST NOT provide content at the level of
/ScreeningOrder/ScreeningPackageOrder/Screenings.At least one PersonName must be supplied for a screening subject, including a GivenName, MiddleName, and FamilyName.
An identifier for the screening subject MUST be provided:
/ScreeningOrder/ScreeningPackageOrder/ScreeningSubjectDetails/ID. This typically would be the "Candidate ID" used by the requester system (an applicant tracking system, for example). The schemeID attribute would be used to identify the type of identifier.At least one ResidenceAddress MUST be supplied for a screening subject.
At least one ContactMethod MUST be supplied for a screening subject. For example, email, telephone number, etc.
/ScreeningOrder/ScreeningPackageOrder/ScreeningSubjectDetails/ContactMethod
Other minimal information necessary to execute a screening order typically include a PersonLegalID (a Social Security Number in the U.S. market), a birth date, and gender. These are not enforced in the profile since some customers may not wish to store such data and delegate the collection of the information to the screening service provider.