Ben Hutton

Sorry, I haven't been clear. We don't WANT to recieve requests originating from patients but we could if we resolve some issues... we would have to define IN the API...

I agree with @buske's summary, assuming that the requestor also includes the version of the API they are sending. I say this because currently we expect and explicitly only support...

@buske That's not actually the point I was trying to make, but actually a way more important one! Good spot on that. I agree with your statement that we shouldn't...

Correct. According to 1.0, additional fields must be prefixed with underscore. Adding a any new field to the spec must therefore trigger major version bump as we didn't make adding...

I've taken a much more legalistic approach to the implementation of the API than others. If it doesn't say you can do something, then you can't, strictly speaking.

> @Relequestual, underscores being required is actually not part of v1.0a as we tagged it. In which case, I agree, and we won't be breaking semver by making that change....

I think it could also be a huge benefit to include the JSON Schema document you've created for the reference server, even if it's just as a guide and not...

I'll write some breif documentation on how to contribute to the project.

@fschiettecatte Do you intend to or already have implemented scoring for matches based on disorders annotated? Is there a use case where such a score could be useful?

That makes sense. How would you score it? Simply 1 or 0?