Language: English (mozilla)
There are a variety of applications that offer telehealth transition related services to transgender and nonbinary individuals. These exist in the US, UK, and in other locations worldwide. Depending on one’s location, the transition-related services they can access via telehealth are limited. In some cases, telehealth is more expensive than traditional in-person services. Are medical providers aware of this? Many subscription-based models charge far more for services than in-person services do. Is this taking advantage of a vulnerable population?
As developers coding telehealth applications, how can we ensure that we are doing so in a secure way? In this presentation, we will explore and brainstorm the ways in which healthcare and insurance providers, or public health initiatives better serve transgender, gender diverse, and nonbinary individuals accessing care?
Attendees will also iterate on the software development side of this issue. In particular: Are Telehealth applications being developed securely? How can we ensure that DevSecOps best practices are being followed and adhered to in regards to handling people’s personal identifiable information?
We will be brainstorming and hacking on ways to develop software in a secure fashion that considers the whole person. Often, transgender, gender diverse, and nonbinary individuals have co-morbid medical concerns such as depression, anxiety, chronic pain, are disabled, or are neurodivergent and are in need of a unique combination of mental health, physical health, and emotional health services.
Key learning takeaways include:
— Telehealth accessibility and software development considerations when developing applications for use by transgender, nonbinary, and gender diverse individuals
— DevSecOps best practices for those handling personal identifiable information
— Ways to advocate for one’s healthcare in the digital age
— Considering the whole person when developing healthcare-related software
This presentation aligns with not only discussions around gender identity, transgender healthcare, LGBTQIAP+ healthcare concerns in the digital age, and more. It also explores how we create and develop intersectional, secure applications.
How will you deal with varying numbers of participants in your session? What if 30 participants attend? What if there are 3?:This conversation will allow for flexibility in hearing from those of varying lived experiences and backgrounds with more people, but allows for also being much more in depth with a smaller audience and is very easy to scale up or scale down depending on the amount of individuals interested in partaking. It also allows for further asynchronous discussion on Slack, and on Twitter.
What happens after MozFest? We're hoping that many efforts and discussions will continue after MozFest. Share any ideas you already have for how to continue the work from your session.:Potential Outcomes:
- Public policy brainstorming
- Conversations re: Designing secure applications
- App development hackathon
- Social opportunities to raise awareness
- Conversations re: How we can improve telehealth and digital transition services for transgender, gender diverse, and nonbinary individuals
- Conversations with health practitioners and the communities they serve regarding the current state of digital healthcare for transgender, gender diverse, and nonbinary individuals and ways we can improve
- Brainstorming re: DevSecOps and healthcare-related applications
English