[Bug]: Revise Use Case #3: Managing Work-Related Illness While Working Abroad
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- content, documentation
Research direction
Locate section 1:XX.4.2.3, “Use Case #3: Managing Work-Related Illness While Working Abroad,” and review its current scenario. Update it to use the Australia wildland-firefighter and new-onset-asthma scenario described in the issue; done means the revised use case is present and remains consistent with the IPS Occupational Data for Health Option.
Written by the indexing model from the issue text.
Description
Contact Details
ums1@cdc.gov
Section Number
1:XX.4.2.3 Use Case #3: Managing Work-Related Illness While Working Abroad
What is wrong
NIOSH proposes to revise the use case in an effort to maintain our commitment to advancing respiratory health, consistent with the focus of the existing scenario. However, since the International Patient Summary is designed to facilitate the exchange of data across borders (whether state or international border), updating the occupational context aims to ensure the use case is relevant and relatable for implementers within the United States and globally.
Describe the solution you'd like
A 22-year-old male was mobilized and deployed through the National Interagency Fire Center (NIFC) to assist with ongoing wildfires in Australia. During his assignment he experienced tightness in his chest, shortness of breath, and wheezing after simple exertion and seeks medical care. He is diagnosed with new-onset asthma.
The attending clinician reviews his International Patient Summary (IPS) that implements the Occupational Data for Health Option, which includes information about his new job as wildland firefighter. The clinician infers the causal link between the new work and the asthma and refers the patient to a specialist for further evaluation and appropriate treatment.
Relevant log output
Priority
{"Medium" => "Significant issue or clarification. Requires discussion, but should not lead to long debate."}
Code of Conduct
- I agree to follow the IHE Code of Conduct
- Dominant language
- GLSL
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from IHE/PCC.FIIO
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
bug
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
bug
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TheOdinProject/curriculum#31408 ·
-
archived coursework help wanted scope: curriculum
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
freeCodeCamp/freeCodeCamp#70260 · 1 comment ·
-
雪鸿集 Open待处理 申请收录
Difficulty 1/5 Under an hour Newbie friendliness 72/100
travellings-link/travellings#4000 · 1 comment ·