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

Content Issue - https://nhsconnect.github.io/FHIR-NOO-API/foundations_use_case_get_the_fhir_conformance_profile.html #20

Open
InteropAdmin opened this issue Dec 21, 2017 · 2 comments
Open

Content Issue - https://nhsconnect.github.io/FHIR-NOO-API/foundations_use_case_get_the_fhir_conformance_profile.html #20

InteropAdmin opened this issue Dec 21, 2017 · 2 comments
Assignees
@dxh73
Labels
Fixed question

Comments

@InteropAdmin
Copy link
Contributor

Who is the service provider ?

image
@dxh73
Copy link

dxh73 commented Dec 22, 2017

I'll need to find out how NDOP is going to be branded. I've temp changed it to NHS Digital Spine for now, and will revisit this once the branding has been confirmed.

@dxh73 dxh73 self-assigned this Jan 2, 2018
@dxh73
Copy link

dxh73 commented Jan 2, 2018 •
edited
Loading

Changed the wording on this banner. The CS isn't out of scope, but how its implemented by Spine is due to us having limited knowledge on how their architecture is geared up to support NDOP API.

The app will be branded as an NHS service. No NHS Digital branding will be on this.

@dxh73 dxh73 added the Fixed label Jan 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dxh73 dxh73

Labels
Fixed question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@InteropAdmin @dxh73