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.

Sign up for GitHub

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

Jump to bottom

Logical Model: prescriptionNumber #130

Closed
bdc-ehealth opened this issue Jul 28, 2022 · 5 comments · Fixed by #139
Closed

Logical Model: prescriptionNumber #130

bdc-ehealth opened this issue Jul 28, 2022 · 5 comments · Fixed by #139
Projects
Development issues

Comments

@bdc-ehealth
Copy link
Collaborator

#128
PrescriptionId prescriptionNumber 1 .. 1 0 .. 1 Must be "1.. 1" in FIHR Model. To be changed (id of prescription, always existing)
@bdc-ehealth bdc-ehealth linked a pull request Jul 28, 2022 that will close this issue
Update BeModelReferralPrescription.fsh #139
Merged
@bdc-ehealth
Copy link
Collaborator Author

WG: check with the backend team.

@bdc-ehealth bdc-ehealth added this to Inbox in Development issues via automation Nov 17, 2022
@bdc-ehealth bdc-ehealth moved this from Inbox to Agenda of WG in Development issues Nov 24, 2022
@bdc-ehealth
Copy link
Collaborator Author

WG: we check with the architects if we use a mandatory UUID to enable idempotent creation.

@bdc-ehealth
Copy link
Collaborator Author

bdc-ehealth commented Feb 10, 2023 •
edited

WG: we investigate the following options:

  • can we enforce a conformant UUID generation
  • check if we have to add a flag that the create can be a duplicate

Development issues automation moved this from Agenda of WG to Done Feb 10, 2023
@bdc-ehealth bdc-ehealth reopened this Feb 10, 2023
Development issues automation moved this from Done to In progress Feb 10, 2023
@bdc-ehealth
Copy link
Collaborator Author

WG: the proposal of the backend team is to make the FE responsible for checking whether the request is a duplicate or not in case of a network error (@MatonAnthony). The workgroup does not agree with this approach, and insists on a technical solution that does not burden the physician.

@bdc-ehealth
Copy link
Collaborator Author

Solved in #214

Development issues automation moved this from In progress to Done Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Development issues
Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update BeModelReferralPrescription.fsh hl7-be/referral
1 participant
@bdc-ehealth