IHE UNICOM Transactions, published by UNICOM. This guide is not an authorized publication; it is the continuous build for version 0.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/unicom-project-eu/unicom-ihe-transactions and changes regularly. See the Directory of published versions

1. Home

Official URL: https://profiles.ihe.net/Pharm/unicom-transactions/ImplementationGuide/ihe.pharm.unicom.transactions				Version: 0.0.1
Active as of 2024-02-08				Computable Name: IHEUnicomTransactions

This specification provides the foundation for cross-border product description and identification in the common uses that have been identified by the UNICOM projecct - Prescription, Dispense, Patient Summary - and including the product information retrieval and equivalent finding for substitution handling. This provides testable specifications for cross-border product description and identification, as well as some test cases for evaluating the cross-border identification of products for UNICOM.

This specification relies on IHE International profiles and is expected to be appended back to IHE International profiles, in all pertinent aspects.

Organization of This Guide

This guide is organized into the following sections:

1. Volume 1:
   1. Introduction
   2. Actors and Transactions
   3. Actor Options
   4. Actor Required Groupings
   5. Overview
   6. Security Considerations
   7. Cross Profile Considerations
2. Volume 2: Transaction Detail
   1. ​Submit product data [U1]
   2. ​Query product data [U2]
   3. ​Query equivalents [U3]
3. Test Plan
   • ​Test Plan

See also the Table of Contents and the index of Artifacts defined as part of this implementation guide.

Conformance Expectations

IHE uses the normative words: Shall, Should, and May according to standards conventions.

Must Support

The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor shall populate the elements marked with MustSupport, if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors should handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.

Download

You can also download:

• this entire guide,
• the definition resources in json, xml, ttl, or csv format, or
• the example resources in json, xml or ttl format.

The source code for this Implementation Guide can be found on https://github.com/unicom-project-eu/unicom-ihe-transactions

Cross Version Analysis

Dependency Table

Package hl7.fhir.uv.extensions.r5#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package hl7.eu.fhir.unicom#current UnicomIG (built Sat, Jan 27, 2024 15:50+0000+00:00)

Globals Table

There are no Global profiles defined

IP Statements

No use of external IP (other than from the FHIR specification)