Contact Us

25 February 2020

STAGED ASSESSMENT ORDER REQUEST




The HR Open Standards Assessments workgroup is excited to announce a new feature as part of HR Open 4.3 Assessment standard (coming mid-2020). Support for a staged assessment order request allows one system partner to request delivery of multiple, staged assessments from one assessment provider within a single message transaction. The staged assessment enhancement was designed based upon use cases submitted by a workgroup member from Development Dimensions International, Incorporated (DDI). The updated specification allows one system partner to request delivery of multiple, staged assessments from one assessment provider within a single message transaction.

Continue Reading

9 January 2020

SPOON, FORK OR BRANCH?




Well, you won’t need a spoon to develop in the HR Open Github environment. Forking and branching are two methods for deviating from the Main (approved and deployed) code. A branch is part of the original repository, whereas a fork is a copy of the original repository.  HR Open recommends our workgroups use branches.

The membership approved/deployed code is stored in the Main branch and the workgroup approved code is stored in the Development branch.

3

As workgroups follow the development process, we track all changes using the Github Issues tool. This allows us to assign a person to the issue, prioritize it, and provide comments.

3-3

When the schema editor makes changes for an open issue, the editor creates a new branch from the development branch. Once the changes are complete, the editor can create a pull request to be reviewed by the team or the TSC. Then the issue branch can be merged into development and deleted.

If you’d like to learn more about our workgroup process or want to get involved, contact Kim Bartkus.

9 January 2020

DO YOU WIKI?




Did you know that the term WikiWiki is Hawaiian for “fast; quick.” At HR Open, we use Wiki for collaborative editing of our documentation. HR Open is a global community of volunteers, dispersed throughout numerous time zones, so we can’t always communicate through conference calls.

The process for developing standards for a particular domain include:

  • Overview: this ensures everyone understands the purpose and scope of the project
  • Define the Actors: systems or roles that communicate to each other via the standard
  • Use Cases: stories of the business process and where the standards will be utilized; can include actors, diagrams, and sample data
  • Throughout the whole process we define terminology and implementation guidelines

2-1

All of this documentation helps business analysts understand the process and implementers develop their products using the standards much more quickly. Keep in mind, this is a collaborative process, so the finished product is a standard that has years of knowledge and experience behind it.

Once the workgroup has completed the project, the Wiki is converted into online documentation available to the public for free.

If you’d like to learn more about our workgroup process or want to get involved, contact Kim Bartkus.

9 January 2020

BUILDING BLOCKS FOR HR OPEN STANDARDS




Github is a great developer and collaboration tool, especially for HR Open’s distributed standards development projects. Although HR Open uses Github as intended, we wanted to share some notes on our usage guidelines within the workgroups.

Every workgroup is created based on a domain and each domain has its own repository. A complete list of domain repositories includes:

  • Assessments
  • Benefits
  • Compensation
  • Common*
  • Interviewing
  • Payroll
  • Referrals
  • Screening
  • Timecard
  • TSC Repositories*
  • Wellness

* Managed by the Technical Steering Committee (TSC), these repositories are used for technical guidelines, tools, and other TSC related work.

The Common repository contains all of the shared information between the other domains. For example, all base data types (identifier, indicator, date, etc.) and all structures (person name, communication, organization, etc.) common to the workgroups are stored here to allow reuse of the shared components. This eliminates the need for multiple, similar structures and reduces development and maintenance time. So, before you create a new data type, check out the common repository to see if we already have the content!

Within each repository, we typically have a WIP folder for documentation and minutes, a JSON folder, and an XML folder. Within the two schema folders, you will find the noun and reusable schema, a top-level schema containing a list of all domain nouns, and a sample folder of all domain instances.

1-2

All workgroup members have read/write access to their domain repository and read access to the common repository. The TSC have read/write access to all repositories. Once the standards have been approved, they are released to the public for free.

If you’d like to learn more about our repositories or want to get involved, contact Kim Bartkus.

9 January 2020

RECRUITING SEARCH SOLUTIONS MADE EASIER WITH HR OPEN STANDARDS




How will our SearchDocument criteria will help you search through resumes?

There are many choices available when searching for a candidate – job boards, staffing agencies, resume databases – just to name a few. How do you search through the various database systems and how often do you receive accurate results that are relevant to your open position?

At HR Open Standards our recruiting workgroup is working on a SearchDocument schema to help take the guess work out of your resume parsing, saving you time, and providing you with the tools to find a perfect candidate!

What is a SearchDocument schema? A SearchDocument provides a way for one system, such as an Application Tracking Systems, to request matching candidates for a query against another system, such as a Job Board or Resume Bank. Our schema allows for your products to have a more stringent and accurate integration between the two systems. For you, this means less time checking multiple sources for accuracy or more time to evaluate your top candidates.speech bubble

The HR OPEN Way

You receive a requisition for a new position opening with specific qualifications for years of experience, location, and education. You open your recruiting application and enter the search criteria; the SearchDocument calls one or more of the appropriate resume database systems and returns with a consolidated list of candidates based on your criteria, along with a summary of information on each candidate. Once you review the list of candidates you’re able to retrieve the full candidate details.

Our standards allow save you time by completing the manual search results and returns more accurate candidate results. This allows you more time to evaluate the right candidates through interviews and work samples.

The recruiting workgroup has previously released standards based on:

  • The Candidate: specifications which define a set of information about an applicant, prospective employee, or resource.
  • Position Opening: used within many recruiting processes and relied upon by multiple trading partners in the course of the recruitment lifecycle

Learn more about When A.I. Meets HR: Data, Trends & the Future of Recruiting from Somen Mondal’s 2018 Annual Meeting presentation here.

Have more questions about how HR Open Standards can help your candidate search product or service? Become a member to join the work group or post a question on our forum.

9 January 2020

HOW DO YOU – INTERVIEW?




Why is it important to have standardized interview integrations? What does it do?

Standardizing the data exchanged between systems during the interview process increases productivity, improves the interviewees experience, and reduces data errors.

The purpose of the HR Open Interviewing Standard is to define communications that occur between the interviewing tool, the ATS/CRA, interviewer, and the candidate. Our case studies provide descriptions on ordering and scheduling the interview, questions to ask (without an interviewer) and how to process the result.

Currently, our interview work group is working on Synchronous Use Cases including the following:

  • Order Synchronous Interview
  • Schedule Synchronous Interview
  • Order Synchronous Interview for Preplanned Event
  • Synchronous Interview Cancel or Reschedule Request

In our last newsletter we discussed the process of Ordering a Synchronous Interview. The next step is Scheduling the Synchronous Interview; here the recruiter has found the perfect candidate and identifies the exact time and date for the interview, the interviewers, and the candidate. This triggers the recruiter to the system user interface where the system verifies it has all the information needed to order the interview and will create the interview request. The interviewing (or requesting) system handles interview participant communication and invites the interview participant to the interview.

Learn more about HR Open Interviewing, including previously released Asynchronous information on our website.

The interview work group meets weekly to develop the standards for the case systems. If you’re interested in joining any of these groups please contact us at info@hropenstandards.org.

11 July 2012

Distributed Systems for Payroll Data Exchange




The HR Open Standards Payroll workgroup has been very active in developing standards for a variety of business needs. Our original scope was to focus on transactions between the HRIS as the System of Record and the Payroll System. We’ve recently decided to expand that focus to handle Distributed System of Record. Many organizations exchange data with internal or 3rd party systems and need to provision/sync those systems throughout the employment life cycle. The following diagram shows one scenario we are considering, where each system is its own System of Record.

The final specifications will include a narrative and associated xml instance(s) describing the ‘day in the life of the new hire’. We will also include business rules for each use case to help business analysts and developers with their implementations. We realize there are other environments in addition to the two noted here (HRIS as SOR, Distributed SORs). Most of them are not as common, but we invite you to share other scenarios.