MHD as an API to XCA

I hope that this configuration is correctly explained in the MHD profile with a paragraph and summary in the news section 33.6.2-1.

I think I need to explain a bit more than I expected, and I need to follow the article that needs this foundation.

I often enter into the fact that XCA is an existing protocol that targets many communities. The Union is an important architectural capacity that allows many communities to act freely and cooperate in the middle.

The concept of using only MHD as the XCA application interface starts to simplify the tasks to be done. Therefore, the following diagram is still an excerpt that not only PDQm and MHD, but also ATNA for core security. IUA (or SMART-on-FHIR) is integrated into XUA for user applications and security. OAuth coupling for FHIR with SAML for Soap SOAP does not matter, but this is not an unusual configuration for security protocols. I am sure that these products / chimneys are supported for this purpose. Approval must be managed in a location that may be based on BPPC or APPC.

I will explain the relationship between PDQm / MHD and XCPD / XCA. The following diagram is shown to the left of FHIR transactions and to the right of SOAP transactions. This paragraph shows three steps: patient identification (PDQm -> XCPD), document document (MHD -> XCA) and document acquisition (MHD -> XCA). These three steps link to some transactions that occur on the client side.

It is possible that client-side processing is simply to do a document query to all the found patients, and each DocumentReference will restore the restoration of the document. However, I hope that treatment will be made to select only interest communities and only interest documents.

The requested design does not display the conversion of PDQm (FHIR request) to XCPD queries. Make sure this query is used for specific queries in general. Note that commonly used queries are smaller than compatibility with PDQm or XCPD. Then think about what’s needed as long as possible, and do it first.

Do not enter the design needed to convert MHD (required to FHIR) to XCA questions. Make sure a subset that is difficult to convert from FHIR to XCA for a particular set of frequently used queries. See the XDS timebound query to do this properly.

Note that I have not made an extension other than the one described in PDQm / MHD or XCPD / XCA files. You can make some shortcuts. Some improvements can be made. But here I just want to put the facts on the table.

The graphic above was created using the following script from https://websequencediagrams.com. I’ve shown it here for your use and enhancements, but also for your own file:

+ + ——————————
MHD-XCA address

Consumer Co
answer
Participation in the initiative
participant answer

Remember the answer of the respondent
Consumers are used as consumers of PDQm and MHD DocumentConsumer
The responder is used as Supplier of PDQm and MHD DocumentResponder
Notice the end
Remember the buyer
Based on the need for a patient of interest.
More grade in last grade
Consumer -> + Responder: PDQm patient? bla
Replying -> Reply: Check if the request is valid
An episode for all forum partners.
Responder -> Getting Started: Discovery Discovery

Activating the initiative

Get Getaway -> Response + Getaway: XCPD Patient Discovery
Responseing Gateway -> – Getting Getting Getting: The alpha beta community was found as a patient
InitationGateway -> Reply: Cache results are stored
Disable gateways
circuit rings
Responder -> Consumer: Here you will find all resources of the cache patient resource
Deactivate the responder

Remember the buyer
Based on the consumer’s treatment
Resources returned to patients
Some or all of the patients are interesting
Notice the end

5 Comments on “MHD as an API to XCA”

  1. Its like you read my thoughts! You appear to
    understand so much approximately this, like you wrote the ebook in it or something.
    I believe that you just could do with some p.c. to pressure
    the message house a bit, but instead of that,
    this is magnificent blog. A great read. I’ll certainly be back.

Leave a Reply

Your email address will not be published. Required fields are marked *