- IHE is currently working on a “guide” to be guided by XDS or XDS (Domain Community) of XDS or the MHD coverage to adjust their metadata requirements. These efforts have been delayed for a long time because IHE entrusts the churches to discover it for themselves. More societies have failed than successful. I am so grateful that they keep trying. They tend to try because most basic queries only query all the documents available to a particular patient. That is necessary, but not enough. Let me explain the next level of document transfer consultation (XDS, XCA, MHD).As part of the discussion on the Metadata Guide, Charles explains the “very elegant” best practice in using XDS / XCA / MHD queries instead of obtaining local input / reference metadata processing for the resulting best document results You should apply the best practice, but I know it will not be used. The main reason for non-use is that it is not explained to IHE readers.
The XDS Query transaction stores a large number of queries. Actually, there is only one query: FindDocuments
Other stored queries are useless, but have more specific goals. It focuses primarily on submission sets, folders and associations. These are not only useful for major consumers near general purpose. These are absolutely necessary when someone gets the situation where other skills are needed.
The fact that FindDocuments is more dominant is recognized because some servers only employ FindDocuments and do not support any other queries. This is especially true for XCA (across the community), which means they are not compatible with SubmissionSet, folders or associations. It also applies to the Argonaut specification, where submissions sets, folders and associations are not compatible.
XDS FindDocuments query parameter
The FindDocuments query contains 18 query parameters. You only need 5 of them. The other 13 parameters can be used, but are likely to provide poor results. They ensure that FindDocuments is complete, but the use of super parameters is extremely poor. The system of consumption has been distressed should be in accordance with the publication system, it has not been thought for decades in the direct direction. Later, I will explain how to deal with this weakness.
Patient: It needs XDS, but I just mention it to complete it. You must have a patient ID that interests you. Use of PIX, PDQ, XCPD, or any other patient identification system is required.
ClassCode: This is an element of metadata that is not fully understood, but the goal is to be the most powerful. The idea is the main focus of the new IHE Guide, which shows that some vocabulary, collective documents, should be given a logical “classification”. These labels are useful for buyers of documents. It should be designed (set of vocabulary design values) so that when searching documents can choose one or two values that can show results.
ServiceStartTimeFrom – ServiceStopTimeTo: Work to define a period of time within documents. This is different from the time the document was created. Hours of service are more specific for the treatment period. The episode episode will then display the loop time range. It is important to know that these two parameters work together to set a period of time and this period has no beginning (the beginning of time) or no end (end time). Therefore, you may request documents covering pre-1998 treatment. Another example is the only documents that cover the last 6 months if you set StartTimeFrom and leave the inactive hour open.
PracticeSettingCode: This is a clinical specialty in which the verb in which the result of the document was performed. Like classCode, it should be filled with a controlled value for a range of pre-vocal vocabulary that represents the broad training classifications.
ValueSets classification is required.