Difference between revisions of "DEV Technical Framework"
(start a new page for the whole DEV domain, starting with material copied from old PCD Technical framework page) |
|||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | [[Category: | + | [[Category:DEV]] |
− | [[Category: | + | [[Category:DEV Reference Pages]] |
− | [[Category: | + | [[Category:DEV Pages Needing Work]] |
{{TOCright}} | {{TOCright}} | ||
==Overview== | ==Overview== | ||
− | + | ===DEV TF Transition=== | |
+ | :* With the 2019 domain name change from IHE Patient Care Devices (PCD) to simply Devices (DEV), the domain charter and organization also changed to incorporate a broader concept of integration profiles that include "health devices", and not the previously narrower focus on integration scenarios that include at least one "regulated medical device". This version of the IHE DEV TF page reflects the 2020 transition to this broader charter, still in process. | ||
+ | :* The 2020 Edition (10.0) of the IHE DEV Technical Framework (TF) will be updated to reflect both the name change, and more importantly the latest IHE International TF template (also updated early 2020). This page will be updated once the 2020 DEV TF is published later in the year. | ||
− | * [http://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol1.pdf Vol. 1 (PCD TF-1): Integration Profiles] | + | ===PCD TF References=== |
− | * [http://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol2.pdf Vol. 2 (PCD TF-2): Transactions] | + | :: The [https://www.ihe.net/resources/technical_frameworks/#dev IHE PCD Technical Framework] is composed of a set of profiles that address specific integration scenarios that include at least one regulated medical device (per the [[Patient_Care_Device#Domain_Overview | PCD Charter]]). |
− | * [http://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol3.pdf Vol. 3 (PCD TF-3): Semantic Content] | + | |
+ | :: * [http://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol1.pdf Vol. 1 (PCD TF-1): Integration Profiles] | ||
+ | :: * [http://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol2.pdf Vol. 2 (PCD TF-2): Transactions] | ||
+ | :: * [http://www.ihe.net/uploadedFiles/Documents/PCD/IHE_PCD_TF_Vol3.pdf Vol. 3 (PCD TF-3): Semantic Content] | ||
==Current Framework Status== | ==Current Framework Status== | ||
− | Links to current versions of all volumes of the IHE | + | Links to current versions of all volumes of the IHE DEV Technical Framework, and current IHE DEV Framework Supplements, may be found at: |
+ | |||
+ | [http://ihe.net/Technical_Frameworks/#dev DEV Technical Frameworks listing on ihe.net] | ||
+ | |||
+ | ==DEV Transaction Map== | ||
+ | Many of the DEV Profiles include transactions, specified in the ''Technical Framework Volume 2 Transactions'', which are allocated on a domain basis. | ||
− | + | ::'''Note: That the table indicates not only the DEV-x transaction labels, but for the PCD-x transactions that are from the pre-DEV technical framework versions (1.0 to 9.0), a 2nd column is added to maintain those aliased transaction identifiers as well.''' | |
− | + | For the ISO Object Identifiers (OID) that are used in the DEV Technical Framework see [[ PCD_OID_Management]]. | |
− | |||
+ | This table identifies the currently allocated transactions and the profiles to which they belong: | ||
+ | {{ :DEV_Transaction_List }} | ||
− | + | ==Technical Framework Section Numbers for Profiles== | |
− | = | + | {| class="wikitable" |
+ | |- | ||
+ | ! Section !! Profile | ||
+ | |- | ||
+ | | 3 || Device Enterprise Communication (DEC) | ||
+ | |- | ||
+ | | 4 || Point-of-Care Infusion Verification (PIV) | ||
+ | |- | ||
+ | | 5 || Implantable Device - Cardiac - Observation | ||
+ | |- | ||
+ | | 6 || Alert Communication Management (ACM) | ||
+ | |- | ||
+ | | 7 || Infusion Pump Event Communication (IPEC) | ||
+ | |- | ||
+ | | 8 || Reserved - Point-of-Care Identity Management (PCIM) | ||
+ | |- | ||
+ | | 9 || Reserved - Personal Health Device Observation Upload (POU) | ||
+ | |- | ||
+ | | 10 || Reserved - Service-oriented Device Point-of-care Interoperability - Plug-and-trust (SDPi-P) | ||
+ | |- | ||
+ | | 11 || Reserved - Service-oriented Device Point-of-care Interoperability - Reporting (SDPi-R) | ||
+ | |- | ||
+ | | 12 || Reserved - Service-oriented Device Point-of-care Interoperability - Alerting (SDPi-A) | ||
+ | |- | ||
+ | | 13 || Reserved - Service-oriented Device Point-of-care Interoperability - external Control (SDPi-xC) | ||
+ | |} | ||
− | + | ==Technical Framework Appendix Assignments== | |
− | == | + | The following table identifies both published and reserved appendix sections for the IHE DEV Technical Framework: |
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! Volume !! Appendix !! Title !! Status !! Comment | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-0''' || style="text-align:center;" | '''A''' || Actor Definitions || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-0''' || style="text-align:center;" | '''B''' || Transaction Descriptions || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-0''' || style="text-align:center;" | '''B''' || IHE Transaction Descriptions || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="background-color:#ffffcc;" | || style="background-color:#ffffcc;" | || style="background-color:#ffffcc;" | || style="background-color:#ffffcc;" | || style="background-color:#ffffcc;" | | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-1''' || style="text-align:center;" | '''A''' || Rosetta Terminology Mapping (RTM) || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-1''' || style="text-align:center;" | '''A''' || Requirements Management for Plug-and-Trust Interoperability || style="text-align:center;" | PPC || ''Reserved: SDPi Supplement (Pre-Public Comment) '' | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-1''' || style="text-align:center;" | '''B''' || ISO/IEEE 11073 SDC Requirements Coverage || style="text-align:center;" | PPC || ''Reserved: SDPi Supplement (Pre-Public Comment) '' | ||
+ | |- | ||
+ | | style="background-color:#ffffcc;" | || style="background-color:#ffffcc;" | || style="background-color:#ffffcc;" | || style="background-color:#ffffcc;" | || style="background-color:#ffffcc;" | | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''A''' || Mapping ISO/IEEE 11073 Domain Information Model to HL7 || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''B''' || Common Segment Descriptions || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''C''' || Common Data Types || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''D''' || Reserved || style="text-align:center;" | FT || Note: Previous content was deprecated; | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''E''' || Examples of messages || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''F''' || HL7 Message Profiling Convention || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''G''' || HL7 Implementation Notes || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''H''' || IHE Integration Statements || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''I''' || Message Transport using MLLP || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''J''' || Message Transport using WS* || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''K''' || Message Transport Using WCTP (ACM Transactions [PCD-06] and PCD-07) || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''L''' || Alert (Alarm) Fatigue || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''M''' || Infusion Pump Events || style="text-align:center;" | FT || | ||
+ | |- | ||
+ | | | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''A''' || Proposed Messages || style="text-align:center;" | TI || ''PCIM Supplement''; '''''Clarify appendix title''''' | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''A''' || POU Usage of FHIR Resource and RESTful FHIR API || style="text-align:center;" | TI || ''POU Supplement | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''A''' || Transaction Examples || style="text-align:center;" | TI || ''MEMDMC Supplement''; '''''Clarify appendix title''''' | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''A''' || Transaction Examples || style="text-align:center;" | TI || ''MEMLS Supplement''; '''''Clarify appendix title''''' | ||
+ | |- | ||
+ | | style="text-align:center;" | '''TF-2''' || style="text-align:center;" | '''A''' || ISO/IEEE 11073 SDC Message Specifications (Normative) || style="text-align:center;" | PPC || ''Reserved; SDPi Supplement (Pre-Public Comment)'' | ||
+ | |} | ||
+ | |||
+ | ==Note regarding above table== | ||
+ | For the Appendix Assignments table, once the TF gets integrated with the final text these appendices will be reassigned as appropriate. | ||
==Public Comments Archive== | ==Public Comments Archive== | ||
You can find an archive of early public comments on PCD documents at http://forums.rsna.org/forumdisplay.php?f=347. | You can find an archive of early public comments on PCD documents at http://forums.rsna.org/forumdisplay.php?f=347. |
Latest revision as of 13:10, 7 December 2022
Overview
DEV TF Transition
- With the 2019 domain name change from IHE Patient Care Devices (PCD) to simply Devices (DEV), the domain charter and organization also changed to incorporate a broader concept of integration profiles that include "health devices", and not the previously narrower focus on integration scenarios that include at least one "regulated medical device". This version of the IHE DEV TF page reflects the 2020 transition to this broader charter, still in process.
- The 2020 Edition (10.0) of the IHE DEV Technical Framework (TF) will be updated to reflect both the name change, and more importantly the latest IHE International TF template (also updated early 2020). This page will be updated once the 2020 DEV TF is published later in the year.
PCD TF References
- The IHE PCD Technical Framework is composed of a set of profiles that address specific integration scenarios that include at least one regulated medical device (per the PCD Charter).
Current Framework Status
Links to current versions of all volumes of the IHE DEV Technical Framework, and current IHE DEV Framework Supplements, may be found at:
DEV Technical Frameworks listing on ihe.net
DEV Transaction Map
Many of the DEV Profiles include transactions, specified in the Technical Framework Volume 2 Transactions, which are allocated on a domain basis.
- Note: That the table indicates not only the DEV-x transaction labels, but for the PCD-x transactions that are from the pre-DEV technical framework versions (1.0 to 9.0), a 2nd column is added to maintain those aliased transaction identifiers as well.
For the ISO Object Identifiers (OID) that are used in the DEV Technical Framework see PCD_OID_Management.
This table identifies the currently allocated transactions and the profiles to which they belong:
ID | PCD ID | Transaction Title | Profile | Source Actor | Receiving Actor | Notes |
---|---|---|---|---|---|---|
DEV-01 | PCD-01 | Communicate PCD Data | DEC | Device Observation Reporter (DOR) | Device Observation Consumer (DOC) | |
DEV-02 | PCD-02 | Subscribe to PCD Data | SPD | Device Observation Consumer (DOC) | Device Observation Filter (DOF) | |
DEV-03 | PCD-03 | Communicate Infusion Order | PIV | Infusion Order Programmer (IOP) | Infusion Order Consumer (IOC) | |
DEV-04 | PCD-04 | Report Alert (Alarm) | ACM | Alert (Alarm) Reporter (AR) | Alert (Alarm) Manager (AM) | Formerly ACM-01 |
DEV-05 | PCD-05 | Report Alert (Alarm) Status | ACM | Alert (Alarm) Manager (AM) | Alert (Alarm) Reporter (AR) | Formerly ACM-02 |
DEV-06 | PCD-06 | Disseminate Alert (Alarm) | ACM | Alert (Alarm) Manager (AM) | Alert (Alarm) Communicator (AC) | Formerly ACM-03 |
DEV-07 | PCD-07 | Report Dissemination Alert (Alarm) Status | ACM | Alert (Alarm) Communicator (AC) | Alert (Alarm) Manager (AM) | Formerly ACM-04 |
DEV-08 | PCD-08 | (Reserved) | ACM | |||
DEV-09 | PCD-09 | Communicate IDC Observation | IDCO | Device Observation Reporter (DOR) | Device Observation Consumer (DOC) | IDC WG Web Page |
DEV-10 | PCD-10 | Communicate Infusion Pump Event | IPEC | Device Observation Reporter (DOR) | Device Observation Consumer (DOC) | |
DEV-11 | PCD-11 | (Reserved) | ACM | |||
DEV-12 | PCD-12 | Retrospective Data Query | RDQ | Retrospective Data Consumer (RDC) | Retrospective Data Reporter(RDR) | |
DEV-13 | PCD-13 | Retrospective Data Reply | RDQ | Retrospective Data Reporter(RDR) | Retrospective Data Consumer (RDC) | |
DEV-14 | PCD-14 | (Reserved) | ||||
DEV-15 | PCD-15 | Device Management Information Observation (DMIO) | MEMDMC | Device Management Information Reporter (DMIR) | Device Management Information Consumer (DMIC) | |
DEV-16 | PCD-16 | Report Location Observation (RLO) | MEMLS | Location Observation Reporter (LOR) | Location Observation Consumer (LOC) | |
DEV-17 | PCD-17 | Assert Device-Patient Association | PCIM | Device-Patient Association Reporter (DPAR) | Device-Patient Association Manager (DPAM) | Deprecated, use DEV-51; |
DEV-18 | PCD-18 | Assert Device-Patient Disassociation | PCIM | Device-Patient Association Reporter (DPAR) | Device-Patient Association Manager (DPAM) | Deprecated, use DEV-51; |
DEV-19 | PCD-19 | Query Device-Patient Associations | PCIM | Device-Patient Association Consumer(DPAC) | Device-Patient Association Manager (DPAM) | |
DEV-20 | PCD-20 | Register Device | PCIM | Device-Patient Association Reporter (DPAR) | Device-Patient Association Manager (DPAM) | |
DEV-21 | Communicate FHIR PHD Data | POU | Device Observation Reporter | Device Observation Consumer | Formerly PCH-01; | |
DEV-22 | Communicate RESTful PHD Data | POU | Device Observation Reporter | Device Observation Consumer | Formerly PCH-02; | |
DEV-23 ... 50 | (Reserved) | SDPi | Note: Current SDPi (1.0) transaction count is 22; more highly possible for this version! | |||
DEV-51 | Assert Device-Patient Association State | PCIM | Device-Patient Association Reporter (DPAR) | Device-Patient Association Manager (DPAM) | Formerly PCD-17 & PCD-18 | |
DEV-52 | Report Device-Patient Association State | PCIM | Device-Patient Association Manager (DPAM) | Device-Patient Association Consumer (DPAC) |
NOTE: Hyperlinks need to be updated
Technical Framework Section Numbers for Profiles
Section | Profile |
---|---|
3 | Device Enterprise Communication (DEC) |
4 | Point-of-Care Infusion Verification (PIV) |
5 | Implantable Device - Cardiac - Observation |
6 | Alert Communication Management (ACM) |
7 | Infusion Pump Event Communication (IPEC) |
8 | Reserved - Point-of-Care Identity Management (PCIM) |
9 | Reserved - Personal Health Device Observation Upload (POU) |
10 | Reserved - Service-oriented Device Point-of-care Interoperability - Plug-and-trust (SDPi-P) |
11 | Reserved - Service-oriented Device Point-of-care Interoperability - Reporting (SDPi-R) |
12 | Reserved - Service-oriented Device Point-of-care Interoperability - Alerting (SDPi-A) |
13 | Reserved - Service-oriented Device Point-of-care Interoperability - external Control (SDPi-xC) |
Technical Framework Appendix Assignments
The following table identifies both published and reserved appendix sections for the IHE DEV Technical Framework:
Volume | Appendix | Title | Status | Comment |
---|---|---|---|---|
TF-0 | A | Actor Definitions | FT | |
TF-0 | B | Transaction Descriptions | FT | |
TF-0 | B | IHE Transaction Descriptions | FT | |
TF-1 | A | Rosetta Terminology Mapping (RTM) | FT | |
TF-1 | A | Requirements Management for Plug-and-Trust Interoperability | PPC | Reserved: SDPi Supplement (Pre-Public Comment) |
TF-1 | B | ISO/IEEE 11073 SDC Requirements Coverage | PPC | Reserved: SDPi Supplement (Pre-Public Comment) |
TF-2 | A | Mapping ISO/IEEE 11073 Domain Information Model to HL7 | FT | |
TF-2 | B | Common Segment Descriptions | FT | |
TF-2 | C | Common Data Types | FT | |
TF-2 | D | Reserved | FT | Note: Previous content was deprecated; |
TF-2 | E | Examples of messages | FT | |
TF-2 | F | HL7 Message Profiling Convention | FT | |
TF-2 | G | HL7 Implementation Notes | FT | |
TF-2 | H | IHE Integration Statements | FT | |
TF-2 | I | Message Transport using MLLP | FT | |
TF-2 | J | Message Transport using WS* | FT | |
TF-2 | K | Message Transport Using WCTP (ACM Transactions [PCD-06] and PCD-07) | FT | |
TF-2 | L | Alert (Alarm) Fatigue | FT | |
TF-2 | M | Infusion Pump Events | FT | |
TF-2 | A | Proposed Messages | TI | PCIM Supplement; Clarify appendix title |
TF-2 | A | POU Usage of FHIR Resource and RESTful FHIR API | TI | POU Supplement |
TF-2 | A | Transaction Examples | TI | MEMDMC Supplement; Clarify appendix title |
TF-2 | A | Transaction Examples | TI | MEMLS Supplement; Clarify appendix title |
TF-2 | A | ISO/IEEE 11073 SDC Message Specifications (Normative) | PPC | Reserved; SDPi Supplement (Pre-Public Comment) |
Note regarding above table
For the Appendix Assignments table, once the TF gets integrated with the final text these appendices will be reassigned as appropriate.
Public Comments Archive
You can find an archive of early public comments on PCD documents at http://forums.rsna.org/forumdisplay.php?f=347.