This page is a collection of short explanations and definitions of the many domain-specific terms, you will encounter on the 4S webpages. It is not meant to be read from beginning to end, but rather to be used as a place to look up the words or acronyms. Please use the table-of-contents to the right or your browsers “Find” function when searching for information (typically the
CTRL + F or
CMD + F keyboard shortcut).
This page also serves as the central “cross-referencing hub” of the 4S website, in the sense that all pages will link terms and acronyms to this vocabulary page, and from here links to more information (either on the 4S webpages or externally) will be found.
Also know as: 4SDC4S Device Communication (module collection)
The 4S Device Communication module collection is a library for applications interacting with personal health devicesPersonal Health Device (like blood pressure monitors, oximeters, thermometers, weight scales, exercise bikes and so on).
“The HL7Health Level 7 Version 3 Clinical Document ArchitectureHL7 Clinical Document Architecture (CDAHL7 Clinical Document Architecture®) is a document markup standard that specifies the structure and semantics of “clinical documents” for the purpose of exchange between healthcare providers and patients. It defines a clinical document as having the following six characteristics: 1) Persistence, 2) Stewardship, 3) Potential for authentication, 4) Context, 5) Wholeness and 6) Human readability.
A CDAHL7 Clinical Document Architecture can contain any type of clinical content – typical CDAHL7 Clinical Document Architecture documents would be a Discharge Summary, Imaging Report, Admission & Physical, Pathology Report and more.”
Also known as: CDGContinua Design Guidelines, X.810-14
Kort beskrivelse af ContinuaContinua Health Alliance og ITU-T
Also known as: ContinuaContinua Health Alliance
Also known as: XCAIHE Cross-Community Access
Also known as: XDMIHE Cross-Enterprise Document Media Interchange
Also known as: XDRIHE Cross-Enterprise Document Reliable Interchange
Also known as: XDSIHE Cross-Enterprise Document Sharing
IHE Cross-Enterprise Document SharingIHE Cross-Enterprise Document Sharing is a specification that focuses on sharing document based information about patients between different actors within healthcare. With XDSIHE Cross-Enterprise Document Sharing patient information can be indexed and retrieved across organisation, department and professional boundaries.
Also known as: XUAIHE Cross-Enterprise User Assertion
Also known as: GATTGeneric ATTribute profile
Also known as: HDP(Bluetooth) Health Device Profile
Also known as: Health Level 7Health Level 7
HL7Health Level 7 is a collection of standards for clinical and administrative document formats and (to some degree) data exchange. The standards are managed and developed by the “HL7Health Level 7 International” organisation. The international organisation is open to direct personal as well as organisational membership, but it also has local (national) affiliated organisations in many countries where membership is possible as well.
This international standard, named “Medical device software – Software life cycle processes” applies to all products with a medical purpose containing software (including pure software products). In EU this is a harmonized standard, which means that it is mandatory for all products with a medical purpose sold in the EU to comply with this standard, if the product contains software.
Also known as: IHEIntegrating the Healthcare Enterprise
IHEIntegrating the Healthcare Enterprise is an initiative by healthcare professionals and industry focused on improving the sharing of information within healthcare. In their own words “IHEIntegrating the Healthcare Enterprise promotes the coordinated use of established standards such as DICOM and HL7Health Level 7 to address specific clinical needs in support of optimal patient care. Systems developed in accordance with IHEIntegrating the Healthcare Enterprise communicate with one another better, are easier to implement, and enable care providers to use information more effectively.”
IHEs recommendations are organised in so-called profiles within a number of domains, like cardiology, pharmacy or radiology. Furthermore, one of these domains is called IT Infrastructure and contains a number of technical profiles each focused on a different aspect of detailed recommendations that enable the provision of infrastructure for sharing information within the healthcare domain.
Within IHEIntegrating the Healthcare Enterprise, each domain is covered by a so-called technical framework defining “specific implementations of established standards to achieve effective systems integration, facilitate appropriate sharing of medical information and support optimal patient care”.
Also known as: IUAIHE Internet User Authorization
Also known as: X73ISO/IEEE 11073 PHD
The (ISO/)IEEE 11073ISO/IEEE 11073 PHD is a large family of standards all related to medical monitoring equipment. Originally developed for hospital equipment in the 1990s (also known as Point-of-Care devices), the original standards were very complex. In the late 00s the work on a new branch of these standards for much simpler “home use” were started, leading to the first version of the “IEEE 11073 PHDISO/IEEE 11073 PHD” (Personal Health DevicePersonal Health Device) standards in early 2010. The “old” Point-of-Care equipment standards are now known as “ISO/IEEE 11073ISO/IEEE 11073 PHD PoC”. The ISO/IEEE 11073 PHDISO/IEEE 11073 PHD core standard documents are ISO/IEEE 11073ISO/IEEE 11073 PHD-20601:2010 \cite phd20601 (along with two later IEEE revisions), and the IEEE 11073ISO/IEEE 11073 PHD-00103 \cite phd00103 overview document, offering a shorter and less technical introduction to the PHDPersonal Health Device standard family. In addition to these core documents, there is one specialisation document for each device type (blood pressure, pulse oximetry, weight scale and so on). These documents are all identified by (ISO/)IEEE 11073ISO/IEEE 11073 PHD-104xx, where “xx” is a two-digit code. In some cases the PHDPersonal Health Device standard documents refer back to the PoC standards (such as 11073-10101, 11073-10201, and 11073-20101). However, these references are mostly “informational” and may be ignored by the reader. Understanding the complexity of the PoC standards is not a prerequisite when working with the PHDPersonal Health Device standards.
Also known as: LANLocal Area Network
Also known as: MDDMedical Devices Directive, Council Directive 93/42/EEC
This EU directive applies to all products with a medical purpose sold in the EU. The directive mandates the adherence to a number of international standards from ISO and IEC, which have been adopted by CEN/CENELEC as harmonized European standards.
Also known as: MHDIHE Mobile access to Health Documents
MHDIHE Mobile access to Health Documents stands for “Mobile access to Health DocumentsIHE Mobile access to Health Documents” and is an IHEIntegrating the Healthcare Enterprise profile defining a light weight RESTful service interface to document sharing environments like XDSIHE Cross-Enterprise Document Sharing (MHDIHE Mobile access to Health Documents on IHEIntegrating the Healthcare Enterprise wiki). The profile was started simultaneously with HL7Health Level 7's work on the new FHIRHL7 Fast Healthcare Interoperability Resources standard framework and there has been a lot of interaction between the two.
Also known as: PROPatient Reported Outcome
Also known as: IHEIntegrating the Healthcare Enterprise Patient Care Device – transaction 1
Also known as: PANPersonal Area Network
Also known as: PHDPersonal Health Device
This is the general term used for all the kinds of devices that may be used for personal monitoring in the home. The term comprises medical sensors (such as blood pressure monitors, thermometers, oximeters etc.), medical actuators (e.g. insulin pumps), as well as health and fitness devices (e.g. weight scales, pedometers, activity monitors, exercise bikes, treadmills).
Also known as: PHMRPersonal Health Monitoring Report
Also known as: PHDC(USB or NFC) Personal Healthcare Device Class
(USB or NFC)
In a public open source project, it is rarely desirable to allow anyone in the world access to add or change code in the shared repository, as a malicious person could wreak havoc. Instead, the repository is typically read-only accessible to everyone, whereas only a few trusted administrators may write to it. In order for everyone else to submit code to the repository, the submission must pass through one of the administrators. 4S uses Bitbucket, and here the mechanism to do this, is called a “pull requestPull Request”. You can learn more in the tutorial below.
Also known as: QRDQuestionnaire Response Document
Also known as: SOUPSoftware Of Unknown Provenance
The IEC 62304IEC 62304 standard uses the term “Software Of Unknown ProvenanceSoftware Of Unknown Provenance” or SOUPSoftware Of Unknown Provenance to describe 3rd-party software components used in software with a medical purpose, and using SOUPSoftware Of Unknown Provenance components in a software product is intentionally made cumbersome, typically requiring more testing and risk mitigations – not to mention a lot of paper work.
Also known as: TANTouch Area Network
Also known as: ZHCZigBee HealthCare Profile