Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test card supports Chlamydia test results #7435

Closed
3 tasks
jayna-SkylightDigital opened this issue Mar 18, 2024 · 3 comments · Fixed by #8389
Closed
3 tasks

Test card supports Chlamydia test results #7435

jayna-SkylightDigital opened this issue Mar 18, 2024 · 3 comments · Fixed by #8389

Comments

@jayna-SkylightDigital
Copy link
Collaborator

jayna-SkylightDigital commented Mar 18, 2024

Why should we do this?

  • (current experience) The test card screen currently does not support Chlamydia-specific options.
  • (why we want to make this change) When a user selects a Chlamydia device on the test card screen in SimpleReport, they should see options for Chlamydia test results and see the appropriate AOE questions.

User story

As a SimpleReport user, I want to be able to select the appropriate Chlamydia test result option on the test card screen when using a Chlamydia device so that I can accurately record and manage Chlamydia test results for my patients, ensuring the correct interpretation and documentation of their Chlamydia status.

Action Requested

  • Chlamydia test result options (e.g., negative, positive, inconclusive) are displayed when a Hepatitis-C device is selected on the test card screen.
  • The Chlamydia test result values are mapped correctly to the corresponding LOINC codes.
  • Chlamydia is added as a supported disease in our database.
  • Chlamydia specific AOE questions are displayed on the test card

Acceptance Criteria

Review

  • Reviewed with design and/or design lead
  • Reviewed with content strategist for final approval
  • Reviewed with product and engineering

Additional Context

Chlamydia result AOE Questions: (also in #7451)
The following information is to be presented on the screen for single-entry when the patient/participant has a positive/reactive Chlamydia result test result.
Symptom list was obtained on the CDC website: https://stacks.cdc.gov/view/cdc/32624

Chlamydia result
[Radio button] Positive
[Radio button] Negative
[Radio button] Inconclusive

Is the patient currently experiencing any symptoms?
[Radio button] Yes
[Radio button] No

Which symptoms are they experiencing? (Select all that apply)
[checkbox] Pain in rectum (SNOMED 77880009)
[checkbox] Rectal bleeding (SNOMED 405729008)
[checkbox] Vaginal bleeding (SNOMED 301822002)
[checkbox] Bleeding from urethra (SNOMED 249301002)
[checkbox] Burning sensation when urinating (SNOMED 49650001)
[checkbox] Penile discharge (SNOMED 9957009)
[checkbox] Vaginal discharge (SNOMED 162156001)
[checkbox] Testicular pain (SNOMED 63901009)
[checkbox] Swelling of testis (SNOMED 438457000)

Date of symptom onset
MM/DD/YYYY

What is the gender of their sexual partners? (Select all that apply)
[checkbox] Female
[checkbox] Male
[checkbox] Transwoman
[checkbox] Transman
[checkbox] Nonbinary or gender non-conforming
[checkbox] Gender identity not listed here
[checkbox] Prefer not to answer

Is the patient pregnant?
[Radio button] Yes
[Radio button] No
[Radio button] Prefer not to say

[Button] Submit results
@DanielSass
Copy link
Collaborator

Requesting some design input on the display for gender specific symptoms @khayeni-SL

@khayeni-SL
Copy link
Collaborator

Suggestion is to remove reference to "women" and "men". See below:

Which symptoms are they experiencing? (Select all that apply)

[checkbox] An abnormal discharge from vagina/penis
[checkbox] A burning sensation when urinating
[checkbox] Pain and swelling in one or both testicles (although this is less common)

[checkbox] Rectal pain
[checkbox] Discharge
[checkbox] Bleeding

@jayna-SkylightDigital
Copy link
Collaborator Author

@DanielSass SNOMED codes for symptoms have been added. Discharge and bleeding codes are specific to the area where it occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants