I will provide a personal lesson on both of them in “IHE in FHIR”
HL7 Working Group Gathering from 12 to 18 May in Cologne
FHIR Dave Days in Boston from June 19 to 21
If you are in Europe, sign up for the HL7 Working Group meeting tutorial. If you’re in the US, join the FHIR Dev Days tutorial.
There is a difference in time available to me. In the days of Dev FHIR, all I need to do is focus on the IHE profiles available on IHE that promote FHIR. When HL7 meeting I will be able to discuss the general relationship between HL7, IHE and IHE profiles that will be available from IHE and benefit from Fhir.
Here are the IHE profiles that are promoting FHIR today …
Add a restful query to ATNA: A query on Fhir Audit Event asks everyone in the audit log registered audit record and the monitoring repository for node authentication from
Authorizing Internet Users: A key OAuth interaction specifies the ability to enable application and user permissions. The purpose is to strengthen based on the study of usage cases.
Mobile access to integrity documents (MHDs): Determines the FHIR interface for the XDS / XCA environment in one way that can be used independently. Equivalent form is the arrival of the Argonaut’s document.
Mobile Alert Management (mACM): Specifies how unassigned SMS alerts are sent to someone who uses the CommunicationRequest resource
Mobile Services Discovery Services (mCSD) (including HPD): Provides a complete provider directory with an organization, location, service, and professionals.
Extracting a data item for a mobile document refers to the method, data level level (Fhir) data with Divorced Documents (XDS) is accessed.
Non-Patient Identification Files (NPFSm): Specifies the method for managing and publishing non-patient files, such as: Styles, policies and settings
Demographic Consultation of the Patient (PDQm): Determines the equivalent function of PDQ, a simple patient consultation
PIXm: The equivalent PIX function refers to requesting IDs from patients who only accept an ID.
Query on current mobile data (QEDm): Allows queries on items of clinical data, including observations, sensitivity, non-tolerance, conditions, diagnostic results, drugs, vaccines, procedures, meetings and backgrounds information on other systems that are within reach and between organizations.
Clinical Planning (CMAP): Supports the need for systems to translate codes from one term to another to support the exchange of information between different systems.
Dynamic Care Planning (DCP): Provides structured and transaction management plans and issues care plans that meet the needs of many, such as: As providers, patients and advocates.
Dynamic Management of Dynamic Care (DCTM) provides opportunities to share information with patient care patients with patient care patients who meet the needs of many users, including: care, patient and advocate
Balance of clinical and pflegerischem content (RECON): The profile provides the ability to deliver balanced clinical data sheets relative to resources and CDA® FHIR®.
Point Medical Tracking Device (PMDT): Defines a portable device.
Remote Patient Monitoring (RPM) allows reporting of measurements made by personal health systems in a remote area
Routine Transport Routes (RIPT): provides the ability to update the transport team with important and necessary medical information about the patient to take
Standard Event Log (SOLE): AuditEvent is used to record business events so that Business Intelligence has great data to study.
UBP refers to a method for sending information contained in barcodes. Conversely, the resulting content of this barcode is obtained as a FHIR provider: drugs, devices, patients or devices.
Mobile Drug Management (MMA): Identifies the integration of health care systems and mobile clients (or other clients) through silent web services.