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

Foundations and Appointments - Add ContactPoint data type population requirement (1.2.2) #118

Closed
AndrewGuiseley opened this issue Oct 25, 2018 · 2 comments
Closed

Foundations and Appointments - Add ContactPoint data type population requirement (1.2.2) #118

AndrewGuiseley opened this issue Oct 25, 2018 · 2 comments
Assignees
@rbutterf @AndrewGuiseley
Labels
Appointments Automated test Foundations High priority Manual provider test
Milestone
1.2.2

Comments

@AndrewGuiseley
Copy link
Contributor

Add explicit requirements for the population of ContactPoint data type in line with consumer expectations set by the examples

See ticket nhsconnect/gpconnect#579
@rbutterf
Copy link

added tests for system,value and use contactpoint data

@RiChallinor RiChallinor added this to the 1.2.2 milestone Oct 30, 2018
@AndrewGuiseley
Copy link
Contributor Author

Amended the following manual tests:

FAPM-40 - Contact system valueset to state that system shall be populated (Patient)
FAPM-41 - Contact use valueset to state that use shall be populated (Patient)
FAPM-60 - Contact details for the Patient contact system valueset to state that system shall be populated (Patient)
FAPM-61 - Contact details for the Patient contact use valueset use shall be populated (Patient)
RAPM-40 - Contact system valueset to state that system shall be populated (Patient)
RAPM-41 - Contact use valueset to state that use shall be populated (Patient)
RAPM-60 - Contact details for the Patient contact system valueset to state that system shall be populated (Patient)
RAPM-61 - Contact details for the Patient contact use valueset use shall be populated (Patient)
LREM-10 - Telecom system to state that the system shall be populated (Location)
LREM-11 - Telecom use to state that the use should be populated (Location)
OSEM-8 - Telecom - Must Support to state that the system Shall be populated and the Use Should be populated
FAPM-70 - Patient contact gender type valueset to state that gender will be populated if available
RAPM-69 - Patient contact gender type valueset to state that gender will be populated if available
FAPM-62 - Contact details for the Patient contact - period to state that the Patient.contact.telecom.period shall be returned if available
RAPM-61 - Contact details for the Patient contact - period to state that the Patient.contact.telecom.period shall be returned if available
FAPM-71 - Patient contact organization to state that the organisation contact period should also be returned if available
FAPM-55 - Patient contact relationship to state that only the relationship.text element should be populated
RAPM-55 - Patient contact relationship to state that only the relationship.text element should be populated

SimonFarrowNHS added a commit that referenced this issue Nov 2, 2018
@SimonFarrowNHS
Updates for 1.2.2 appointments
5ac7923 
Addresses Issues #108,#109,#111,#112,#115,#116.#117,#118,#119,#120,#121,#122,#123,#124,#125,#126,#131,#132,#133,#134,#135,#136
@SimonFarrowNHS SimonFarrowNHS mentioned this issue Nov 2, 2018
Merged
@rbutterf rbutterf closed this as completed Nov 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rbutterf rbutterf

@AndrewGuiseley AndrewGuiseley

Labels
Appointments Automated test Foundations High priority Manual provider test
Projects
None yet
Milestone
1.2.2
Development

No branches or pull requests
3 participants
@rbutterf @AndrewGuiseley @RiChallinor