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

Issue with Timing data type #177

Closed
bdc-ehealth opened this issue Oct 20, 2022 · 5 comments
Closed

Issue with Timing data type #177

bdc-ehealth opened this issue Oct 20, 2022 · 5 comments

Comments

@bdc-ehealth
Copy link
Collaborator

The solutions proposed on fhir.chat.org are not sufficient: https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Timing.20datatype.20puzzle

WG: Marleen will reformulate her use cases in a document, and we will make it available as a Google doc to the international community and insist again.

@bdc-ehealth
Copy link
Collaborator Author

@bdc-ehealth bdc-ehealth added this to Inbox in Development issues via automation Oct 26, 2022
@bdc-ehealth
Copy link
Collaborator Author

WG: this question is still valid, we wait for the FHIR int'l input.

@bdc-ehealth bdc-ehealth moved this from Inbox to To do (Solution validated by WG) in Development issues Nov 24, 2022
@bdc-ehealth
Copy link
Collaborator Author

FHIR int'l input: accepted, will be available in a future release of the standard (i.e. will not be usable right away). See comments in:

@bdc-ehealth
Copy link
Collaborator Author

WG: Marleen will check if the solution of a start time and a duration is enough to replace the starttime - endtime need.

@bdc-ehealth bdc-ehealth moved this from To do (Solution validated by WG) to Agenda of WG in Development issues Jan 23, 2023
@bdc-ehealth
Copy link
Collaborator Author

WG: Marleen checked this with the business and they agree.

Development issues automation moved this from Agenda of WG to Done Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant