MHD requirements in CapabilityStatement

[iheos]

Can these things be coded in a CapabilityStatement?

For a client:

• Is POST supported (PDB)?
• is GET supported (Query/Retrieve/Document Consumer)?
• Minimal vs Comprehensive (no clue how this might be fit in)?

For a server:

• Is POST supported (Doc Recipient/PDB)?
• is GET supported (Doc Responder/Retreive or Query)?

[skbhaskarla]

From: John Moehrke Date: Tue, Feb 11, 2020 at 4:09 AM Subject: Re: IHE MHD Recipient To: Sunil Bhaskarla Cc: Bill Majurski

Yes you should see a difference in the Recipients CapabilityStatement. It would declare support for comprehensive document reference structure definition. This is less well defined today, but will be more clear in future updates of MHD.

On Mon, Feb 10, 2020, 5:10 PM Sunil Bhaskarla wrote:

Hi John, If an IHE MHD Document Recipient actor has a choice to accept only the comprehensive metadata PDB, what is the correct way to determine this acceptance criteria by looking at the actor's Capability Statement?  I was under the impression that we can use the Recipient actor's Capability Statement to determine if they accept a comprehensive metadata PDB based on the value from CapabilityStatement.rest.resource.interaction.documentation. One main reason for this thought was that the initial IHE MHD Capability Statement "of requirements kind" example was coded with a value that seemed to match the structure definition as specified in IHE MHD Supplement Bundle Resources Section 3.65.4.1.2.1. Again, if this is a wrong approach, please let me know the correct way to determine what type of metadata is acceptable to the recipient based on their Capability Statement.