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
Requirements
| R1: Regulatory IDMP product data exchange |
| Regulators need to provide fully descriptive data of medication products. This description is based on EMA / IDMP concepts (Pharmaceutical Product, Medicinal Product or Packaged Product) and using IDMP-terms (SPOR). |
| R2: IDMP-compatible MPD product data exchange |
| Nationally, regulators and MPD vendors need to provide fully descriptive data of medication products for their products, using their own concepts and / or own terms. This product data may be expressed in IDMP compatible - which is needed but not across all actors. |
| R3: National product concept data exchange - product catalogs |
| National product data may be expressed in nationally accepted terms, using national concepts, vocabularies and identifiers. Soe actors may use IDMP concepts and valuesets, others may use only national concepts and valuesets, and others may mix them. Such transition is important to support the actual clinical flows. |
| R3: National product description in clinical documents |
| inside clinical documents (prescriptions, dispenses, etc.) product data may be expressed in nationally accepted terms, using national concepts, vocabularies and identifiers. Such possibility shall be preserved. |
| R4: Cross-border prescription in common concepts and attributes |
| Cross-border prescription shall be expressed in common concepts. Regardless of how the information is used, |
| R5: Phased or different IDMP adoption paths |
| Adoption of IDMP by member states may be phased and in different approaches. For example some countries may adopt IDMP concepts or even IDMP data in the netire chain, while others may support IDMP only at the NCP. |
| R7: Cross-border product identification is based on IDMP terms |
| Cross-border product identification is based on IDMP terms (i.e. IDMP data elements using IDMP semantics) |
| R6: Cross-border documents shall contain sufficient information for identification and substitution |
| Cross-border prescription must contain or be able to infer the elements needed for substitution |
| R7: Substitution rules should be expressed in compatible terms |
| Substitution rules should be expressed in |
|
Propose a change
