Mismatch in specification list on the page REST API Keys and the Conformance Statements

[olw-medcom]

Hey there,

I've noticed something weird.
On this page you can see a specification called 'FHIR - EKG Recording - Document Source' and a total of 5 specifications to choose from.

And when I click "Manage Tests" and select the same system called 'Epic'

Then there is only 4 specs to choose from and the EKG one is not present?

I've added the conformance statement again which fixes the problem, but I just wanted to mention this issue to you as it has made some vendors unable to start testcases with the rest API on that spec.

[costas80]

Then there is only 4 specs to choose from and the EKG one is not present?

I agree that these two listings should be the same, and specifically, the specification list displayed in both cases should match the specifications for the system's active conformance statements. It's not clear to me however which display is initially wrong.

Taking your example, I assume that the 'EKG Recording - Document Source' displayed in the REST API keys, is not an assigned conformance statement for the system right? If this is indeed the case then the issue is that the 'REST API keys' tab shows more specifications than it should.

Can you confirm this is the case?

[olw-medcom]

Hey @costas80,

Yes that is indeed the case. I've found another example of it here:

I'm guessing the list in the specs in the REST API keys list doesn't get react to a delete conformance statement event, because after haven taken above pictures, I deleted both conformance statements:

But the list in the REST Api keys is still the same

[costas80]

I'm guessing the list in the specs in the REST API keys list doesn't get react to a delete conformance statement event, because after haven taken above pictures, I deleted both conformance statements:

Ok thanks for confirming. Most likely the REST API key display disregards which specifications the system actually has conformance statements for (it shouldn't though). I'll check and get back to you when I figure this out.

[costas80]

Hey @olw-medcom. In the end this issue was due to a bug in the filtering of presented specifications (and associated data) in the API key tab - not stale data.

More specifically, for an organisation with multiple systems, all related statements were queried and used to display a single list of specifications. For example if ORG1 defined SYS1 and SYS2, where SYS1 had statements to SPEC1 and SPEC2, whereas SYS2 had a statement to SPEC3, the specification list showed SPEC1, SPEC2 and SPEC3 regardless of whether SYS1 or SYS was selected. This meant that you could end up viewing together SYS1 and SPEC3 which was indeed not backed by a conformance statement.

The issue is now resolved on the latest nightly build. Can you confirm on your end when you've had the chance? Thanks!