| Submitted By: Genevieve Luensman
/ Centers for Disease Control and Prevention, National Institute for Occupational Safety and Health (NIOSH)
|
| Data Element Information |
| Data Element Description |
NEW DATA CLASS DESCRIPTION: Patient Work is a framework for a self-reported, structured and standardized patient work history that has broad applicability to healthcare as part of the medical record; it is suitable for many use cases supporting patient care, population health, and public health.
DATA ELEMENT DESCRIPTION:
A set of self-reported, related components that remain associated with one-another to characterize a person’s job and that provide clinically-relevant information. A job is a work situation, training position, or (potentially clinically-relevant) volunteer position held for a specified time period; a person can have more than one job at the same time and multiple jobs over time. A history of reported jobs is expected to be built over time (and be retained), with start date and end date for each job (at least the year). Current job(s) information (aka Present Job) is the most important and can be identified by a flag or Y/N value set.
A Job element includes one of each component: (1) Job Occupation, (2) Job Industry, (3) Employer Name, (4) Employer Address, (5) Work Classification (6) Supervisory Level of Pay Grade, and (7) Work Schedule. Other components listed in the Patient Work (Occupational Data for Health; ODH) interoperability standards templates are optional.
(1) Job Occupation is a self-reported, coded term that identifies the type of work done by a person in a job. If an appropriate term is not available (e.g., a new type of work), then a text entry is used.
(2) Job Industry is a self-reported, coded term that identifies the kind of business that compensates the person for a job (e.g., wages, training) or assigns work to a volunteer. It is based on the primary business activity conducted by the company, organization, or individual (for those who are self-employed). For a military position, this is the self-reported branch of service. If an appropriate term is not available (e.g., a new kind of business), then a text entry is used.
(3) Employer Name refers to the company, organization, or individual that provides compensation for a job or that assigns work to a volunteer, as reported by the person. For a military position, this is the self-reported duty station (home base).
(4) The self-reported Employer Address is also captured; this is not necessarily the work location.
(5) Work Classification is a coded term that characterizes the arrangement between the employer and the person in a job, such as 'paid work, self-employed' or 'voluntary work in disaster/emergency response', as reported by the person.
(6) Supervisory Level or Pay Grade is a coded term that indicates the responsibilities of a person’s job for directing work and managing personnel, as reported by the person. Pay grade is used for a military position, since it distinguishes between officers and enlisted service members and conveys similar meaning across all branches of service.
(7) Work Schedule is a coded term for the typical arrangement of working hours for a job, as reported by the person. |
| Use Case Description(s) |
| Use Case Description |
On average, workers in the U.S. spend more than half their waking hours at work and (based on 2018 data) nearly 75% of adults have worked in the past 12 months. Work and health are inextricably related; knowledge of job-related risks informs diagnosis and management of illness and injury and health needs to be managed in the work environment, regardless of whether a condition is work-related. While knowing about a person’s current job(s) is likely to be most important, some work-related health conditions can manifest after a long latency so a history of jobs can also provide valuable information. Only 5% of adults report that they have never worked. NIOSH has developed user stories describing the value of Job information and examples will be provided on the NIOSH-EHR website (in preparation). See: Institute of Medicine. Incorporating Occupational Information in Electronic Health Records: Letter Report. Washington, DC. National Academies Press; 2011. https://doi.org/10.17226/13207
Job information is expected to be collected/reviewed/updated at or prior to registration for every adult, and some children as determined by locality (e.g., in some places an organization might want to collect information for younger people who could be working on a family farm or in a family business). The use of a patient portal or in-office kiosk or tablet is expected to facilitate this process. In addition, the Occupational Data for Health (ODH) set of templates for Patient Work, including a Job template (Past or Present Job), is an option in the IHE Exchange of Personal Health Record Profile (XPHR), allowing the patient to enter the data in their personal health record and share it with care providers to reduce the burden of data collection in the clinical setting.
The Job template (Past or Present Job) also is included in key interoperability standards as part of the ODH set of templates for Patient Work, which can reduce the burden of re-entering data for a new care provider to access. The template (aka Past or Present Job) is an option in the HL7 Consolidated CDA (C-CDA) Templates for Clinical Notes, Social History section. Within C-CDA, Social History is required in the Continuity of Care Document (CCD) and History and Physical Document; it is optional in the Consultation Note, Discharge Summary, Transfer Summary, Referral Note, and Procedure Note. The ODH set of templates, including a Job template, is also an option in the IHE profiles for medical summary (XDS-MS), emergency department referral data (EDR), international patient summary (IPS), data query using FHIR (QEDm), and healthy weight (HW) data. Leveraging these implementation guides and profiles with the structured and standardized Job template can improve the quality of care by providing a more complete picture of factors that may affect the patient’s health and supporting referrals; they can also reduce the burden of data reentry.
Without this Job element, care providers sometimes record some information about a patient’s work in their Notes, which makes it difficult to use outside of the initial consultation. Obstetricians are required to ask a pregnant woman about her current job at the first visit and patient-centered medical homes (PCMH) are required to record occupation to provide comprehensive care in the primary care setting. However, a lack of standardization and collection as text make the information less amenable to use and reuse. Shifting to structured and standardized Job element will facilitate access to clinical decision support and reuse of the data for examination of populations, both in healthcare and public health. For example, the CCD and XDS-MS with the Job template provide the opportunity to convey a more complete picture of the patient’s health factors when referring patients to specialty care (e.g., a pulmonologist for recent-onset asthma in a painter).
The Job element also could contribute to patient matching algorithms.
|
| Estimate the breadth of applicability of the use case(s) for this data element
|
In 2018, approximately 75% of adults age 18 and older had worked in the past 12 months and on average approximately 60% of adults in the U.S. currently are working. Since work and health are interrelated, most of the 209,000 primary care physicians and many of the 120,000 certified physician assistants and 290,000 licensed nurse practitioners in the U.S. would potentially benefit from the capture, access, use, and exchange of the Job information.
In addition to primary care providers, there are another 415,000 physicians who are also primarily involved in direct patient care. Many specialty providers would also benefit from Job information: e.g., those who care for injuries and are faced with return-to-work decisions, such as emergency medicine specialists, orthopedists, physiatrists; those who care for patients with chronic diseases caused by occupational exposures, such as pulmonologists, neurologists, nephrologists, and oncologists.
|
| Link to use case project page |
https://www.cdc.gov/niosh/topics/ehr/default.html |
| Supporting Attachments |
eCaseReporting Use Case NACCHO_2020.pdf
Immunization Scenario NACCHO_2020.pdf
Opioid Abuse and Prevention NACCHO_2020.pdf
|
| Use Case Description |
The structured and standardized Job element components are amenable to use in CQL and will facilitate automated access to clinical decision support. For example, Work Schedule can be used to identify patients with diabetes who are on a rotating shift with nights and provide them with appropriate educational materials about managing their diet and blood glucose levels as their shifts change (https://cds.ahrq.gov/cdsconnect/artifact/occupational-factors-impacting-diabetes). Job Occupation and Job Industry can be used to identify those who need certain vaccinations, screening for exposure to health hazards, and screening for early signs of work-related disease, e.g. chest radiographs for workers in industries with potential for silica exposure. In addition, the Occupational Data for Health (ODH) value set for Occupation is an extension of the O*NET-SOC classifications, which could facilitate access to lists of tasks, activities, and work contexts available via O*NET OnLine (https://www.onetonline.org/).
In response to a recommendation from the National Transportation Safety Board (NTSB), two EHR vendors have devised clinical decision support tools related to “the evaluation of nontraumatic loss of consciousness episodes or for a diagnosis of epilepsy that will notify providers of the patient’s occupation, such as commercial driver; and remind them to address the occupational and driving Status of the patient” (https://data.ntsb.gov/carol-main-public/sr-details/H-18-021). One EHR vendor also increased visibility of the patient’s Job Occupation to care providers. Having structured and standardized Job element data could increase the success of these tools by providing coded Job Occupation data to facilitate identifying persons in high-risk types of work.
Standardized current Job Occupation has been shown to be useful for population health. A Federally-Qualified Health Center collected Current Job Occupation as text during registration for one year (more than 27,000 patients). The data were extracted, coded by public health, and analyzed with Demographic information that was also available in the EHR. Linked demographic and occupation information is enabling this primary care network to tailor resources and information to its patient population. In this instance, it was noted that many patients primarily spoke Portuguese and of those patients most of the women were maids or hotel housekeepers and many of the men were construction or maintenance painters. The Health Center updated their intranet site with educational materials, in Portuguese, for painters about lead exposure and for housekeepers about ergonomic hazards and exposure to cleaning agents. This was so popular that they developed additional materials for more of their working patients, including those who speak Spanish. The painters can also be identified for annual blood-lead-level screening. Collecting structured and standardized Job information will facilitate analyses and activities like this without the need to standardize the data outside of the EHR (https://apha.confex.com/apha/141am/webprogram/Paper288596.html).
Job Industry is also critical for healthcare. For example, a person has a job as a customer service specialist (Job Occupation) at a newspaper publisher and printing business (Job Industry). She sees her primary care provider for respiratory issues. The care provider sees the job information, which prompts them to ask if she works near the newspaper printing operation. She reports that she moved to an office adjacent to the printing operation three months ago. The care provider provides an electronic referral to an occupational medicine specialist who can evaluate whether workplace exposures are causing the patient’s respiratory symptoms.
Work Classification and Supervisory Level or Pay Grade also support understanding of a patient’s work. For example, Supervisory Level or Pay Grade distinguishes between an officer position versus an enlisted position for certain military service occupations (as self-reported). Work Classification indicates type of employment such as self-employment, which can be an indicator of access to benefits and financial stability. Work Classification also may prompt consideration of important voluntary work, such as volunteer firefighter.
Collecting self-reported military service information using this Job element can prompt important conversations between a care provider and patient, and can be used to facilitate referrals to the VA and support data-sharing. The HL7 Military Service History and Status reporting project, sponsored by the VA, is using the Patient Work (ODH) FHIR template for Job (Past or Present Job) as the basis for a FHIR standard to share service member data (https://confluence.hl7.org/display/CGP/Military+Service+History+and+Status+FHIR+Profiles+Project+Page).
|
| Estimate the breadth of applicability of the use case(s) for this data element
|
In 2018, approximately 75% of adults age 18 and older had worked in the past 12 months and on average approximately 60% of adults in the U.S. currently are working. Since work and health are interrelated, most of the 209,000 primary care physicians and many of the 120,000 certified physician assistants and 290,000 licensed nurse practitioners in the U.S. would potentially benefit from the capture, access, use, and exchange of the Job information.
In addition to primary care providers, there are another 415,000 physicians who are also primarily involved in direct patient care. Many specialty providers would also benefit from Job information: e.g., those who care for injuries and are faced with return-to-work decisions, such as emergency medicine specialists, orthopedists, physiatrists; those who care for patients with chronic diseases caused by occupational exposures, such as pulmonologists, neurologists, nephrologists, and oncologists.
|
| Link to use case project page |
https://journals.lww.com/joem/Fulltext/2017/11000/Recognition_of_the_Relationship_Between_Patients_.25.aspx |
| Use Case Description |
The Job element can be reused for electronic case reporting and the ODH Job template (Past or Present Job) is included as an option in the CDA Release 2 and FHIR Electronic Initial Case Report (eICR). The Job element can provide information for public health to locate infectious disease outbreaks and intervene to prevent further illness. The data also will support public health analyses of work-related conditions such as silicosis and pesticide poisoning and can be used to identify Industry sectors and Employers for whom interventions are needed to mitigate risk.
Related References:
Making EHR Data More Available for Research and Public Health (MedMorph): https://www.cdc.gov/csels/phio/making-ehr-data-more-available.html
Outbreak of Silicosis among Engineered Stone Countertop Workers in Four States: https://blogs.cdc.gov/niosh-science-blog/2019/10/29/silicosis-countertop/
NIOSH Data and Statistics Gateway: https://www.cdc.gov/niosh/data/default.html
Work-Related Lung Disease Surveillance System (e(WoRLD)): https://wwwn.cdc.gov/eworld
Work-Related Asthma: https://www.cdc.gov/niosh/topics/asthma/default.html
|
| Estimate the breadth of applicability of the use case(s) for this data element
|
Job data are important for public health infectious disease case reporting in all jurisdictions. Thirty states currently require health care providers to report selected occupational illnesses to a state agency and in the future these data will be collected electronically, reducing the reporting burden on clinicians. |
| Link to use case project page |
https://www.cdc.gov/ecr/index.html |
| Healthcare Aims |
- Improving patient experience of care (quality and/or satisfaction)
- Improving the health of populations
- Improving provider experience of care
|
| Maturity of Use and Technical Specifications for Data Element |
| Applicable Standard(s) |
An information model of the Patient Work data elements, called Occupational Data for Health (ODH), has been published ( https://doi.org/10.1093/jamia/ocaa070) and the data are represented in the Federal Health Information Model (FHIM; https://fhim.org/). An HL7 informative EHR-S Functional Profile has been published (http://www.hl7.org/implement/standards/product_brief.cfm?product_id=498). A Guide to Collection of Occupational Data for Health (ODH) is in preparation.
Logical Observation Identifiers Names and Codes (LOINC; https://loinc.org/) codes are available for each Patient Work Data Element and each component of the data elements. Job: Job Occupation, Industry, Employer Name, Employer Address, Work Classification, Supervisory Level or Pay Grade, Work Schedule.
The ODH code set (https://phinvads.cdc.gov/vads/ViewCodeSystem.action?id=2.16.840.1.114222.4.5.327) provides value sets for Occupation (includes military occupations), Industry (includes military branches of service), Work Classification, Supervisory Level or Pay Grade (includes military pay grades), Work Schedule, and Employment Status (https://phinvads.cdc.gov/vads/SearchValueSets_search.action?searchOptions.searchText=ODH). The PHIN VADS ODH Hot Topics section provides downloadable files with Preferred Concept Names and Easy Read Descriptions for Work Classification, Supervisory Level or Pay Grade (includes military pay grades), Work Schedule, and Employment Status values (https://phinvads.cdc.gov/vads/SearchVocab.action). The PHIN VADS Hot Topics section also provides downloadable files of the ODH Occupation and Industry value sets that are designed to support search algorithms.
Interoperability standard formats for all of the Patient Work Data Elements are published as aligned HL7 CDA, V2, and FHIR ODH templates as well as an IHE CDA profile ODH template. Related References:
HL7 CDA® R2 Implementation Guide: Consolidated CDA Templates for Clinical Notes; Occupational Data for Health, Release 1 – US Realm; STU. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=522
IHE Patient Care Coordination (PCC) Technical Framework Supplement: CDA Content Modules, Revision 2.6 – Trial Implementation. https://www.ihe.net/resources/technical_frameworks/#pcc
HL7 FHIR Release 4.0.1 Profile: Occupational Data for Health (ODH), Release 1.0 STU. http://hl7.org/fhir/us/odh/STU1/
HL7 Version 2.9 Messaging Standard – An Application Protocol for Electronic Data Exchange in Healthcare Environments, Normative. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=516 . Chapter 2C, Tables, Tables 0954-0959 provide the Patient Work Data Element component value sets. Chapter 3, Patient Administration, section 3.4.16 describes the Patient Work Job Data Elements as an Occupational Health (OH) segment.
The value sets for Occupation and Industry expressed in current interoperability standards are the CDC_Census2010 category value sets (https://phinvads.cdc.gov/vads/SearchValueSets_search.action?searchOptions.searchText=2010). However, the new ODH Occupation and Industry value sets assist with self-selection of coded entries that provide detail to support patient care. These new value sets are extensions of federal classification systems for Occupation and Industry. Crosswalks from ODH codes to CDC_Census2010 codes are available in the PHIN VADS Hot Topics section. A non-breaking “translation” in CDA or “slice” in FHIR can be used to transmit either or both ODH or CDC_Census2010 values; HL7 interoperability implementation guides and IHE interoperability content profiles are being updated accordingly.
https://doi.org/10.1093/jamia/ocaa070
|
| Additional Specifications |
IHE Patient Care Coordination (PCC) Technical Framework Supplement to Volume 1, CDA Occupational Data Options, Revision 1.1 – Trial Implementation. https://www.ihe.net/resources/technical_frameworks/#pcc. This adds the Occupational Data for Health (ODH) template of all Patient Work Data Elements as an option to three profiles in the PCC Technical Framework: Cross-Enterprise Sharing of Medical Summaries (XDS-MS), Exchange of Personal Health Record (XPHR), Emergency Department Referral (EDR).
IHE Patient Care Coordination (PCC) Technical Framework Supplement: Query for Existing Data for Mobile (QEDm), Revision 2.2 – Trial Implementation. https://www.ihe.net/resources/technical_frameworks/#pcc. (ODH template for all Patient Work Data Elements is an option)
IHE Patient Care Coordination (PCC) Technical Framework Supplement: International Patient Summary (IPS), Revision 1.1 – Trial Implementation. https://www.ihe.net/resources/technical_frameworks/#pcc. (ODH template for all Patient Work Data Elements is an option)
IHE Quality, Research and Public Health Technical Framework Supplement: Healthy Weight (HW), Revision 2.3 – Trial Implementation. https://www.ihe.net/resources/technical_frameworks/#qrph. (ODH template for all Patient Work Data Elements is an option)
HL7 CDA R2 Implementation Guide: Public Health Case Report – the Electronic Initial Case Report (eICR), Release 1.1 – US Realm; HL7 Standard for Trial Use and Release 1, STU Release 2.0. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=436. (ODH Job and Usual Work templates are options)
HL7 FHIR® Release 4.0.1 Implementation Guide: Electronic Case Reporting (eCR) – US Realm. Version 1.0.0 (Standard for Trial Use). http://hl7.org/fhir/us/ecr/STU1/. ODH Job and Usual Work templates are options)
HL7 Version 2.9 Messaging Standard – An Application Protocol for Electronic Data Exchange in Healthcare Environments, Normative. http://www.hl7.org/implement/standards/product_brief.cfm?product_id=516 Patient Work (OH) segments and Retirement Date are included as options in: Chapter 3, Patient Administration, 13 ADT/ACK message events; Chapter 4, Orders, 1 OMG, 4 OML and 1 OMI message events; Chapter 7, Observations, 7 ORU, 2 OUL, and 1 OPU message event.
|
| Current Use |
In limited use in production environments |
| Supporting Artifacts |
Promoting Interoperability Programs Eligible Hospitals and Critical Access Hospitals are required to, and Merit-based Incentive Payment System (MIPS) participants may optionally, report on any two measures under the Public Health and Clinical Data Exchange objective of these programs. The § 170.315(f)(5) – Transmission to public health agencies – electronic case reporting certification criteria in the 2015 Edition Final Rule and the ONC Cures Act Final Rule is one measure to meet this option.
The current standard for § 170.315(f)(5), as listed in ONC’s 2020 Interoperability Standards Advisory Reference Edition, is HL7® CDA® R2 Implementation Guide: Public Health Case Report, Release 2: the Electronic Initial Case Report (eICR), Release 1, STU Release 1.1. ONC’s CHPL lists 73 product/versions certified to (f)(5) using this standard. This implementation guide permits transmission of some job information in a loosely defined structure. Limited job information has been included in some electronic case reporting recently; over 5,400 facilities are now actively doing electronic case reporting for COVID-19. Because the job information is in text-form, it places an added burden on public health to translate the data into standardized codes for analyses. However, the next CDA and FHIR versions of the eICR implementation guide include the ODH templates for Job and Usual Work. The FHIR implementation guide has been Connectathon-tested. Related References:
eCase Reporting: https://ecr.aimsplatform.org/about-us#:~:text=A%20US%20federal%20agency%20under,the%20United%20States%20and%20internationally
2020-09 Public Health Track, HL7 FHIR Connectathon: https://confluence.hl7.org/display/FHIR/2020-09+Public+Health+Track
ODH interoperability templates for Patient Work have been used to demonstrate exchange at HIMSS Interoperability Showcases annually since 2016 and the PHI Conference Interoperability Showcases in 2016 and 2018 using the IHE Healthy Weight (HW) profile. These transactions and demonstrations have involved four personal health records, one interface engine, one public health representative, one provider portal, and one EHR. One personal health record and the interface engine used production environments; the others used test environments. For three 2020 NACCHO 360X Interoperability Demonstrations, Patient Work was exchanged using the QEDm (FHIR) and CCD (CDA) formats. Related References:
“Health and Fitness,” Interoperability Showcase. Health Information Management and Systems Society (HIMSS) Annual Conference. Feb 19-24, 2017. Video at https://www.youtube.com/watch?v=ZxRx1UECUkg&list=PLFB222C2B798A2877&t=0s&index=22
“Value-Based Care,” Interoperability Showcase. Health Information Management and Systems Society (HIMSS) Annual Conference. Las Vegas, NV. Mar 5-8, 2018. Video available at https://www.youtube.com/watch?v=JH4Y4pV3mw8&t=0s&index=7&list=PLGFNwETCTdKlvMmCk0XjXksTDMW57kxUx
“Patient-Centered Interoperability,” Interoperability Showcase. Health Information Management and Systems Society (HIMSS) Annual Conference. Orlando, FL. Feb 11-15, 2019. Video available at https://www.youtube.com/watch?v=0ZCyjHG8Kpo&t=584s
https://www.cdc.gov/niosh/topics/ehr/default.html
eCaseReporting Use Case NACCHO_2020_0.pdf
Immunization Scenario NACCHO_2020_0.pdf
Opioid Abuse and Prevention NACCHO_2020_0.pdf
|
| Extent of exchange
|
5 or more. This data element has been tested at scale between multiple different production environments to support the majority of anticipated stakeholders. |
| Supporting Artifacts |
The CHPL lists 73 product/versions that have attested to electronic case reporting (https://chpl.healthit.gov/#/search). The currently used implementation guide (R1.1) permits transmission of some job information in a loosely defined structure. Limited job information has been included in some electronic case reporting recently; over 5,400 facilities are now actively doing electronic case reporting for COVID-19. Because the job information is in text-form, it places an added burden on public health to translate the data into standardized codes for analyses. However, the next CDA and FHIR versions of the eICR implementation guide include the ODH templates for Job and Usual Work. The FHIR eICR implementation guide with the ODH Job and Usual Work templates was tested at the HL7 FHIR Connectathon Sept. 2020 ( https://confluence.hl7.org/display/FHIR/2020-09+Public+Health+Track).
ODH interoperability templates for Patient Work have been tested at IHE Connectathons and demonstrated at annual HIMSS and bi-annual PHI Conference Interoperability Showcases since 2016 using the IHE Healthy Weight (HW) profile (https://product-registry.ihe.net/PR/pr/search.seam?integrationProfileOption=424&integrationProfile=372&domain=9&date=ANY|1601300810685|1601300810685). The 2020 NACCHO 360X Interoperability Demonstrations used the FHIR QEDm and CDA CCD standards. These transactions and demonstrations have involved four personal health records, one interface engine, one public health representative, one provider portal, and one EHR. One personal health record and the interface engine used production environments; the others used test environments.
https://www.cdc.gov/niosh/topics/ehr/default.html
|
| Potential Challenges |
| Restrictions on Standardization (e.g. proprietary code) |
The value sets for Occupation and Industry expressed in current interoperability standards are the CDC_Census2010 category value sets. However, the new ODH Occupation and Industry value sets assist with self-selection of coded entries that provide detail to support patient care. Crosswalks from ODH to CDC_Census2010 codes are available in the PHIN VADS Hot Topics section. A non-breaking “translation” in CDA or “slice” in FHIR can be used to transmit either or both ODH or CDC_Census2010 values; HL7 interoperability implementation guides and IHE interoperability content profiles are being updated accordingly. |
| Restrictions on Use (e.g. licensing, user fees) |
None |
| Privacy and Security Concerns |
The Data Elements in the Patient Work Data Class are intended to be a part of the medical record and protected as such. |
| Estimate of Overall Burden |
We estimate that it will take approximately 600 hours to implement all of the Patient Work Data Elements (Job, Usual Work, Employment Status and Retirement Date, and Combat Zone Period) as described in the HL7 EHR-S Work and Health Functional Profile and A Guide for Collection of Occupational Data for Health (ODH, aka Patient Work. NIOSH, in preparation). The functional profile suggests system features to manage the information (including rendering, storing, etc.) so that it will be most useful and accessible to the care provider at the right time.
Initially, data collection will likely occur primarily via patient self-entry, e.g., during preregistration in their patient portal or via a kiosk on arrival in the clinic. Based on user testing of a Patient Work collection prototype, initial entry of all Patient Work Data Elements (Job, Usual Work, Employment Status and Retirement Date, and Combat Zone Period) takes 5-30 minutes. As with other data classes, such as medications and family history, the opportunity to review previously entered information will be key to reducing the collection burden. Leveraging interoperability standards will also help to minimize the collection burden by sharing the information across systems.
|
| Other Implementation Challenges |
The ODH value sets for Occupation and Industry are large, in order to provide recognizable terms. However, keyword text searches can be used to facilitate selection and NIOSH is preparing A Guide to Collection of Occupational Data for Health (ODH; aka Patient Work). |
|
Submitted by nedragarrett_CDC on
Recommendations for Updated Submission
We recommend that this submission be broken up into separate data elements, as they were submitted to us as such. We've received a number of data elements marked as duplicates, which offer more information pertaining to each separate entity of which is described in this submission above. Here are the elements listed that can be applied but should be considered to be their own submissions based on their differing use case descriptions but were marked as duplicating this prior submission:
Current Occupation; A self-reported term that identifies the type of work done by a person in a current work situation or position (i.e., a job; also some voluntary work, such as volunteer firefighter). The self-reported term for a set of activities or tasks that a person is currently paid to perform or, if unpaid or voluntary, the person’s contribution to a household/family business/community. Characterizes a job when paired with current industry.
Current Industry; A self-reported term that identifies the kind of business, i.e., primary business activity, conducted by the company, organization, or individual that provides compensation (either direct or indirect) for a current job or that currently assigns work to a volunteer. Characterizes a job/voluntary work when paired with current occupation. For a military position, this is the self-reported branch of service.
Current Industry; The company, organization, or individual that provides compensation (either direct or indirect) for a current job or that currently assigns work to a volunteer, as reported by the person. For a military position, this is the self-reported current duty station (home base).
Current Employer Address; Address of Employer for a current job or voluntary work, as reported by the person. For a military position, this is the self-reported address for the current duty station (home base).
Current Work Classification; A characterization of the arrangement between an employer and a person for a current work situation or position, such as 'paid work, self-employed' or 'voluntary work in disaster/emergency response', as reported by the person.
Current Job Start Date; The date a current job begins, formatted as MM/DD/YYYY or MM/YYYY
These each have differing descriptions and other differing language and that should be included within the individual submissions we've provided.