The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed
or info@snomed.org
.
Using RxNorm codes of type SAB=RXNORM as this specification describes does not require a UMLS license. Access to the full set of RxNorm definitions, and/or additional use of other RxNorm structures and information requires a UMLS license. The use of RxNorm in this specification is pursuant to HL7's status as a licensee of the NLM UMLS. HL7's license does not convey the right to use RxNorm to any users of this specification; implementers must acquire a license to use RxNorm in their own right.
HL7 Europe Patient Summary, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 1.0.0-xtehr built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/eps/ and changes regularly. See the Directory of published versions ( src
)
There are examples where a medication request may include the option of an oral dose or an Intravenous or Intramuscular dose. For example, "Ondansetron 8mg orally or IV twice a day as needed for nausea" or "Compazine® (prochlorperazine) 5-10mg PO or 25mg PR bid prn nausea or vomiting". In these cases, two medication requests would be created that could be grouped together. The decision on which dose and route of administration to use is based on the patient's condition at the time the dose is needed. ( src
)
HL7 Europe Patient Summary, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 1.0.0-xtehr built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/eps/
and changes regularly. See the Directory of published versions
For example codes, see
eHDSI Dose Form http://hl7.org/fhir/ValueSet/medication-form-codes|4.0.1
( example
to http://terminology.ehdsi.eu/ValueSet/eHDSIDoseForm
)
The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
Specify a set of rules to be applied to HL7 FHIR to define how to represent a Patient Summary
in the European
Context, coherently with the European eHN Guidelines (see the European eHealth - Key documents
).
s
This guide is based on and aligned with the eHealth Network (eHN) Guideline on the Patient Summary
, which define the scope, purpose, and semantic content of the European Patient Summary in the context of cross-border healthcare within the European Union.
Logical data models (or information models) for the European Health Data Space (EHDS)
are currently being developed
by the Xt-EHR Joint Action
. These models will form the basis of the Joint Action's proposal
for the future EHDS Implementing Act.
They represent evolving, refined interpretations
of the data sets described in the eHealth Network (eHN) Guidelines
, and are expected to be further updated during the Joint Action process.
