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

Include FAX as CommonPhoneNumber purpose #376

Closed
nils-work opened this issue Apr 9, 2021 · 3 comments
Closed

Include FAX as CommonPhoneNumber purpose #376

nils-work opened this issue Apr 9, 2021 · 3 comments
Labels
Common Issues related to Common APIs.

Comments

@nils-work
Copy link
Member

Description

To allow for FAX numbers to be shared and used correctly, an additional enumerated value of FAX should be added as an option for the purpose property of CommonPhoneNumber.

Area Affected

The Enumerated Values associated with the CommonPhoneNumber schema.

Change Proposed

Include a value for FAX numbers.

@nils-work nils-work added the Common Issues related to Common APIs. label Feb 3, 2023
@nils-work nils-work moved this from Full Backlog to Iteration Candidates in Data Standards Maintenance Jul 12, 2023
@nils-work
Copy link
Member Author

This issue was mentioned in the first call of Maintenance Iteration 16, on 12th July 2023.

It was suggested that a number of industries, including healthcare, still make use of fax communication, so this issue may remain relevant in an expanding variety of CDR use-cases.

As adding a new enum to support a FAX purpose in the CommonPhoneNumber schema would likely cause a version increment of the Get Customer Detail endpoint, the DSB seeks feedback on the priority and timing of a potential change and whether there are related issues that could be considered in conjunction with this, for example #90 DSB Item - Business Customer and Agent Review.

@nils-work
Copy link
Member Author

This issue was discussed in today's Maintenance Iteration call and there was feedback that it could be removed as a candidate for the iteration as there appears to be no urgency for the change, and no related issues to combine it with.

@nils-work nils-work moved this from Iteration Candidates to Full Backlog in Data Standards Maintenance Aug 16, 2023
@nils-work
Copy link
Member Author

As part of a backlog review in Maintenance Iteration 21, it was suggested that this issue could be closed.
If there are no further comments, this issue will be closed on 25 October 2024.

@github-project-automation github-project-automation bot moved this from Full Backlog to Done in Data Standards Maintenance Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Common Issues related to Common APIs.
Projects
Status: Done
Development

No branches or pull requests

2 participants