General Requirements for use of IEEE 11073 Standards:
A creator (manufacturer, developer, etc.) of a solution (device, application, etc.) based on any IEEE 11073 Standard should have a purchased copy of the IEEE 11073 Standards that were used. The purchase of the Standard(s) provides the purchaser with a royalty free license to apply the contents to the creator’s specific solution(s).
The creator is also permitted to provide appropriate guidance material in the solution collateral (IFU (Instructions for Use), Implementation Guide, etc.) which would allow a system integrator adequate information to interface with that solution. The creator should not directly copy tables, figures, text, etc. without requesting permission from the IEEE.
In all cases proper reference to the IEEE Standards used should be provided. For example:
Specific Requirements for use of IEEE 11073 Nomenclature:
IEEE has established a special case relating to the IEEE 11073 Nomenclature, i.e. IEEE 11073-1010x. NIST has established a special database of a subset of 11073-1010x terms called the RTMMS (Rosetta Terminology Mapping Management System). It allows free of charge access and use of Reference IDs, Terminology Codes, Descriptions, Systematic Names and Common Terms provided in the RTMMS database.
The specific wording is as follows: “IEEE, as part of its support for the RTMMS database and on-going royalty-free agreement with the NIST, makes these terms available for the development of IEEE 11073 compliant products (e.g. in user documentation, collateral, etc.). Any use of IEEE terms beyond compliant product development may require royalty payment. Please notify IEEE of any request to use, modify, or reproduce these terms in any manner beyond the permitted use described above.”
Frequently Asked Questions on Use of Nomenclature
Q. If I am writing a commercial application that takes medical measurements (perhaps from a proprietary device) and transcodes it to an HL7 V2 message or V3 document or FHIR resources using IEEE 11073 nomenclature codes, ref-ids, and descriptions obtained from RTMSS or are my own, am I required to pay any type of fee to IEEE?
A. No. If you wish to obtain the official 11073-10101 standard you will need to purchase that document. However, if you are just interested in using the codes, Ref-ids, and even descriptions, they are freely available in the NIST RTMMS tool.
Q. If I am writing a commercial application that decodes HL7 V2 messages, V3 documents, and FHIR resources, and displays the contents in a human readable form where the descriptions of the codes are my own or are from RTMMs , am I required to pay any type of fee to IEEE?
A. No.
Q. If I make a commercial library with source where one of the source files contains all the codes, ref-id, and descriptions (either my own or from the RTMMS tool) needed for the type of application it supports, am I required to pay any type of fee to IEEE?
A. No.
Q. Am I freely able to use the codes, refids and above descriptions in customer-facing documentation?
A. Yes
A creator (manufacturer, developer, etc.) of a solution (device, application, etc.) based on any IEEE 11073 Standard should have a purchased copy of the IEEE 11073 Standards that were used. The purchase of the Standard(s) provides the purchaser with a royalty free license to apply the contents to the creator’s specific solution(s).
The creator is also permitted to provide appropriate guidance material in the solution collateral (IFU (Instructions for Use), Implementation Guide, etc.) which would allow a system integrator adequate information to interface with that solution. The creator should not directly copy tables, figures, text, etc. without requesting permission from the IEEE.
In all cases proper reference to the IEEE Standards used should be provided. For example:
- IEEE Std 11073-10101™-2004, Health Informatics -- Point-of-care medical device communication -- Part 10101: Nomenclature
Specific Requirements for use of IEEE 11073 Nomenclature:
IEEE has established a special case relating to the IEEE 11073 Nomenclature, i.e. IEEE 11073-1010x. NIST has established a special database of a subset of 11073-1010x terms called the RTMMS (Rosetta Terminology Mapping Management System). It allows free of charge access and use of Reference IDs, Terminology Codes, Descriptions, Systematic Names and Common Terms provided in the RTMMS database.
The specific wording is as follows: “IEEE, as part of its support for the RTMMS database and on-going royalty-free agreement with the NIST, makes these terms available for the development of IEEE 11073 compliant products (e.g. in user documentation, collateral, etc.). Any use of IEEE terms beyond compliant product development may require royalty payment. Please notify IEEE of any request to use, modify, or reproduce these terms in any manner beyond the permitted use described above.”
Frequently Asked Questions on Use of Nomenclature
Q. If I am writing a commercial application that takes medical measurements (perhaps from a proprietary device) and transcodes it to an HL7 V2 message or V3 document or FHIR resources using IEEE 11073 nomenclature codes, ref-ids, and descriptions obtained from RTMSS or are my own, am I required to pay any type of fee to IEEE?
A. No. If you wish to obtain the official 11073-10101 standard you will need to purchase that document. However, if you are just interested in using the codes, Ref-ids, and even descriptions, they are freely available in the NIST RTMMS tool.
Q. If I am writing a commercial application that decodes HL7 V2 messages, V3 documents, and FHIR resources, and displays the contents in a human readable form where the descriptions of the codes are my own or are from RTMMs , am I required to pay any type of fee to IEEE?
A. No.
Q. If I make a commercial library with source where one of the source files contains all the codes, ref-id, and descriptions (either my own or from the RTMMS tool) needed for the type of application it supports, am I required to pay any type of fee to IEEE?
A. No.
Q. Am I freely able to use the codes, refids and above descriptions in customer-facing documentation?
A. Yes
