Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

View Transaction

View Transaction Information

Id: 119

Keyword: ITI-18

Name: Registry Stored Query

Description: The Query Registry transaction is issued by the Document Consumer Actor on behalf of a care provider (EHR-CR) to a Document Registry. The Document Registry Actor searches the registry to locate documents that meet the provider s specified query criteria. It will return a list of document entries that contain metadata found to meet the specified criteria including the locations and identifier of each corresponding document in one or more Document Repositories. The stored query uses parameters and not direct SQL

TF Reference:

Status: Final Text

Document Section :

None

Id
Keyword
Name
Description
Action
29 XCA Cross-Community Access The Cross-Community Access profile supports the means to query and retrieve patient relevant medical data held by other communities. A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information via an established mechanism. Facilities/enterprises may host any type of healthcare application such as EHR, PHR, etc. A community is identifiable by a globally unique id called the homeCommunityId. Membership of a facility/enterprise in one community does not preclude it from being a member in another community. Such communities may be XDS Affinity Domains which define document sharing using the XDS profile or any other communities, no matter what their internal sharing structure.
36 TP13 Manage Sharing of Documents Transaction Package with Doc Integrity Check US HITSP: TP13: Manage Sharing of Documents Transaction Package with Doc The Manage Sharing of Documents Transaction Package supports the sharing of patient records in the form of source attested objects called documents. A healthcare document is a composite of structured and coded health information, both narrative and tabular, that describes acts, observations and services for the purpose of exchange. No assumption is made by this construct in terms of the format and structure of the content of documents shared.
38 DEPRECATED:XDS.a DEPRECATED: Cross-Enterprise Clinical Documents Share (XDS.a) The Cross-Enterprise Clinical Document Sharing IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient electronic health records. Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.
39 XDS.b Cross-Enterprise Document Sharing The Cross-Enterprise Document Sharing (XDS.b) IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient electronic health records. Cross-Enterprise Document Sharing is focused on providing a standards-based specification for managing the sharing of documents between any healthcare enterprise, ranging from a private physician office to a clinic to an acute care in-patient facility.
46 DSG Digital Signature DSG is document content profile that describes the digital signature content and how it is managed in XDS, as well as guidance on how other IHE domains (such as Patient Care Coordination) could create document content profiles for such purposes as e-referral and e-prescription.
90 CH:XDS-I.b Cross-Enterprise Document Sharing for Imaging
146 TP13a Manage Sharing of Documents (XDS.A Option) US HITSP: TP13a: Manage Sharing of Documents (XDS.A Option). The Manage Sharing of Documents Transaction Package supports the sharing of patient records in the form of source attested objects called documents. A healthcare document is a composite of structured and coded health information, both narrative and tabular, that describes acts, observations and services for the purpose of exchange. No assumption is made by this construct in terms of the format and structure of the content of documents shared.
151 TP49 HITSP Sharing Radiology Results Transaction Package US HITSP: TP49: Sharing Radiology Results Transaction Package. The Sharing Imaging Results Transaction Package supports the sharing of radiology result data in a document sharing functional flow scenario.
244 CMPD Community Medication Prescription and Dispense The Community Medication Prescription and Dispense Integration Profile (CMPD) describes the process of prescription, validation and dispense of medication in the community domain.
354 CH:ATNA Deprecated Audit Trail and Node Authentication Swiss Extension Deprecated
386 CH:XDS.b Cross-Enterprise Document Sharing Swiss Extension
Id
Keyword
Name
Description
Action
1ARRAudit Record RepositoryA system unit that receives and collects audit records from multiple systems.
42DOC_CONSUMERDocument ConsumerThe Document Consumer Actor queries a Document Registry Actor for documents meeting certain criteria, and retrieves selected documents from one or more Document Repository actors.
43DOC_REGISTRYDocument RegistryThe Document Registry Actor maintains metadata about each registered document in a document entry. This includes a link to the Document in the Repository where it is stored. The Document Registry responds to queries from Document Consumer actors about documents meeting specific criteria. It also enforces some healthcare specific technical policies at the time of document registration.
89INIT_GATEWAYInitiating Gateway
184DOC_ADMINISTRATORDocument AdministratorThe Document Administrator actor supports metadata update by issuing the Update Document Set transaction [ITI-57] and Delete Document Set [ITI-61 ] transaction to the Document Registry actor.
1183PRES_PLACERPrescription PlacerThe main role of this actor consists in placing the prescription (initial or modified in case of a substitution of invalidation, for example). It sends the cancellation of the prescription or its discontinuation, as well. In order to fulfill this task, the prescription placer retrieves the current treatment of the patient and medication already dispensed recently. The prescription placer receives the pharmaceutical validation and status tracking information such as substitution, availability, administration plan and reports and cancellation. The corresponding human actor is a prescriber.
1184PHA_ADVPharmaceutical AdviserThis actor is responsible for the validation of prescriptions from a pharmacist’s perspective. Therefore, it receives the initial prescription, validates it and sends it back (accepted, cancelled, modified, substitution of pharmaceutical product); therefore it provides the pharmaceutical advice. To perform this task it checks the current treatment. The pharmaceutical advice can be due to clinical, legal, or supply aspects. This actor may be implemented in the hospital pharmacy module of a hospital information system or the point of sale software of the pharmacy. The corresponding human actor is typically a pharmacist (or pharmacist assistant).
1185MED_DISMedication DispenserThis actor is responsible for the process of dispensing medication to the patient, fulfilling the prescription. Therefore it produces the information on the medication dispensed to the patient. In order to achieve this, it receives prescriptions already validated. It also confirms drug availability for administration and it receives the administration plan and administration reports. This actor may be implemented as the point of sale software of a community pharmacy or the hospital pharmacy module of a hospital information system. The human actor behind this system actor is usually a pharmacist or a pharmacist assistant. In addition to the dispense, in this version this actor is considered to take care of all the dependencies to ensure a proper dispensing.
1190CPMCommunity Pharmacy ManagerThe main role of this actor consists in providing the business logic for status management and other purposes. As a second role it acts as a “relaying role” where certain standard XDS communication is routed through for providing the possibility of applying project-specific business logic on it. It provides special query-transactions which consuming actors (prescription placer, pharmaceutical adviser or medication dispenser) used for reducing the amount of data flowing to them. They return just “relevant” information for specific purposes (e.g., returning just all “active” prescriptions ready for being validated or dispensed together with all related documents). This actor is usually a system actor without human participation.
1321DOC_AUDIT_CONSUMERDocument Audit Consumer
Assertion Id
Description
CH-ADR-032 The <AttributeValue> child element SHALL convey the resource identifier.- For ADR due to XDS [ITI-18], there SHALL BE three Resources to be identified, each representing a class of documents, i.e. urn:e-health-suisse:2015:epr-subset:<patient_id>:normal, urn:e-health-suisse:2015:epr-subset:<patient_id>:restricted, urn:e-health-suisse:2015:epr-subset:<patient_id>:secret- For ADR due to PPQ, an Authorization Decision MUST be requested for each object itself, not a class of objects. For CH:ADRdue to CH:ATC, there is exactly one Resource to be identified, representing the object class of patient audit trail records (see Section 3.1.6.5 Semantics)
CH-ADR-073 The PEP authorizing ITI-18 transactions by implementing an Authorization Decision Consumer MUST, in addition to the result from the Authorization Decision Query, validate that the resource-id from the SAML Assertion identifies the same patient as the MPI-PID supplied in the Registry Stored Query transaction. If not true, the transaction MUST be denied (see Section 3.1.6.1 CH:ADRdue to XDS Registry Stored Query [ITI-18])
ITI18-1 The ebXML Registry stored query facility (Invoke Stored Query transaction) accepts the following parameters for returnType : 'LeafClass' or 'ObjectRef'
ITI18-10 Document Consumer actors implementing this transaction (ITI-18) shall implement one or more of these queries as needed to support the use cases it implements
ITI18-11 If the query includes a patient identifier parameter and that patient identity matches the subsumed patient identifier of a merge message then the query shall return no results
ITI18-12 If the query includes a patient identifier and that patient identifier matches the surviving patient identifier of a previous merge message then the query shall return the composite of: Metadata registered against the surviving patient identifier Metadata registered against the subsumed patient identifier
ITI18-13 An error shall be returned when an unsupported stored query ID is received
ITI18-14 If this parameter $XDSDocumentEntryType is specified, and the Document Registry does not support it, the Document Registry shall ignore
ITI18-15 If $XDSDocumentEntryType parameter is specified, and the Document Registry does support it, the proper information is returned
ITI18-16 The query request and response will be transmitted using Web Services, according to the requirements specified in ITI TF-2x: Appendix V
ITI18-17 The Document Registry Actor shall accept a Registry Stored Query Request formatted as a SIMPLE SOAP message and respond with a Registry Stored Query Response formatted as a SIMPLE SOAP message
ITI18-18 The Document Consumer Actor shall generate the Registry Stored Query Request formatted as a SIMPLE SOAP message and accept a Registry Stored Query Response formatted as a SIMPLE SOAP message
ITI18-19 The Document Registry Actor shall Accept a parameterized query in an AdhocQueryRequest message
ITI18-2 When returnType=ObjectRef, a list of object UUIDs (references) SHALL be returned
ITI18-20 The Document Registry Actor shall verify the required parameters are included in the request. Additionally, special rules documented in the above section Parameters for Required Queries shall be verified
ITI18-21 The Document Registry Actor shall return an error for the following condition : Unknown query ID (error code XDSUnknownStoredQuery)
ITI18-22 The Document Registry Actor shall return an error for the following condition : Required parameter missing (error code XDSStoredQueryParamNumber)
ITI18-23 The Document Registry shall accept the homeCommunityId value if it is specified in a Registry Stored Query request
ITI18-24 If a patient identifier specified as a parameter to the query is unknown to the Document Registry it shall return a successful response with no elements.
ITI18-25 The Document Registry may specify the homeCommunityID attribute on any appropriate elements

Tool index

  • Simulators

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top