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

Capability Statement #22

Open
InteropAdmin opened this issue Dec 21, 2017 · 1 comment
Open

Capability Statement #22

InteropAdmin opened this issue Dec 21, 2017 · 1 comment

Comments

@InteropAdmin
Copy link
Contributor

The example on https://nhsconnect.github.io/FHIR-NOO-API/foundations_use_case_get_the_fhir_conformance_profile.html has a few issues1

  1. There should be no schema details - it is illegal to do so
  2. This is a "requirements" statement - is that what is intended?
  3. The search options do not correlate with the table here https://nhsconnect.github.io/FHIR-NOO-API/development_elements.html
@InteropAdmin InteropAdmin changed the title Caoability Statement Capability Statement Dec 21, 2017
@dxh73 dxh73 self-assigned this Jan 2, 2018
@nhsconnect nhsconnect deleted a comment from IOPS-DEV Jan 3, 2018
@dxh73
Copy link

dxh73 commented Jan 3, 2018

Schema now removed. Was added to test validity of XML structure and forgot to remove this.
The CS will remain as a requirements kind until it's content is agreed as being ready for implementation, at which time it will change to an instance kind. It's a suggest CS for NDOP. I've discussed the use of CS with TA's and this is an area which needs more discussion.
Search parameter table updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants