Stream: implementers
Topic: Proper way to specify TTY-Accessible phone numbers
Tristan Wilson (Aug 09 2018 at 15:55):
We're trying to find a way to specify a TTY service for telecom. There is no ContactPoint .system for TTY, so I think we need to create an extension.
We can think of two ways to approach it... what would be the correct/preferred way?
1. Add an isTTY boolean extension, which means the phone number is to be considered a TTY service.
2. Create an extension called TTYValue of type valueString, which would contain the phone number for the TTY service. This would take priority over the telecom.value field.
We're leaning towards option 1 at the moment...
Lloyd McKenzie (Aug 09 2018 at 16:20):
Agree that option 1 is appropriate and sounds like a good candidate for a standard extension
Benjamin Flessner (Nov 14 2018 at 22:45):
@Tristan Wilson - did you ever create this? We are also needing to convey this information and would love to share the same approach.
An alternative would be to expand the http://build.fhir.org/valueset-contact-point-system.html value set to include "text" or "tty" as a system.
Grahame Grieve (Nov 15 2018 at 02:24):
I'm sure we discussed this in the past. So I find GF#6089 - which said that we would create a new task for dealing with hearing impaired requirements, which I failed to do. So it fell in a hole. what requirements are there beyond TTY? Someone I know personally who is connected to the hearing impaired community told me that TTY is falling out of use now that there's so many options... but I don't know if that's reflective of the wider situation...?
Brian Postlethwaite (Dec 03 2018 at 10:11):
I would also suggest that these fit into the extension space under other.
Tristan Wilson (Dec 10 2018 at 17:15):
@Tristan Wilson - did you ever create this? We are also needing to convey this information and would love to share the same approach.
An alternative would be to expand the http://build.fhir.org/valueset-contact-point-system.html value set to include "text" or "tty" as a system.
We ended up creating a BooleanType, with value set to true, which we apply to the ContactPoint resource. We only add the extension when our telecom resource isTTY = true.
We set our ContactPoint.system = "OTHER", and our ContactPoint.use = "WORK".
We also looked at that option @Benjamin Flessner , but the extension seems the best fit for an easy solution. Definitely would prefer TTY as a valueset option, OR the "other" be redefined, as "A contact that is not a phone" is restrictive in this instance.
Last updated: Apr 12 2022 at 19:14 UTC
