From 5e22899104f0ec4ab757f15db6dad1f400cddc2f Mon Sep 17 00:00:00 2001 From: Eldon Metz Date: Wed, 5 Nov 2025 12:50:27 -0800 Subject: [PATCH 1/3] Initial text for CP-DEV-019. --- CPs/draft/cp-dev-019.html | 583 ++++++++++++++++++++++++++++++++++++++ asciidoc/cp-dev-019.adoc | 104 +++++++ asciidoc/index.adoc | 8 +- 3 files changed, 694 insertions(+), 1 deletion(-) create mode 100644 CPs/draft/cp-dev-019.html create mode 100644 asciidoc/cp-dev-019.adoc diff --git a/CPs/draft/cp-dev-019.html b/CPs/draft/cp-dev-019.html new file mode 100644 index 0000000..9bc859e --- /dev/null +++ b/CPs/draft/cp-dev-019.html @@ -0,0 +1,583 @@ + + + + + + + +IHE Change Proposal + + + + + +
+
+

Tracking Information

+
+ ++++ + + + + + + + + + + + + + + + + + + + + + + +

IHE Domain/Program

DEV Domain / Patient Care Device (PCD) Program

Change Proposal ID:

CP-DEV-019

Change Proposal Status:

Draft

Date of last update:

2025-11-05

Person Assigned:

Eldon Metz

+
+
+
+

Change Proposal Summary Information

+
+ ++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

OBR-7/8 clarifications

Submitter’s Name(s) and e-mail address(es):

Eldon Metz, emetz@innovisionmedical.com

Submission Date:

TBD

Integration Profile(s) affected:

Point-of-Care Identity Management (PCIM)

Actor(s) affected:

Device-Patient Association Consumer
+Device-Patient Association Manager
+Device-Patient Association Reporter

IHE Technical Framework or Supplement modified:

PCIM Profile TI (PCIM TI) revision 2.2, dated 2024-12-05

Volume(s) and Section(s) affected:

PCIM TI, Section A.1.2.4

Rationale for Change:

+

During the drafting of CP-DEV-018, it was identified that the OBR-7 and OBR-8 field descriptions required correction, and the accompanying text describing the number of participants needed revision.

+

This Change Proposal (CP) proposes changes to PCIM TI to implement the profile clarifications and positions for the above issue.

+ +++ + + + + + +

Section A.1.2.4 in PCIM TI - OBR - Observation Request, change the last sentence before Table A.1.2.4-1 to clarify OBR-7 and OBR-8 represent the times of participant involvement:

+
+

Existing Text:

+
+
+

It gives the timestamp of the beginning of the association (OBR-7), and when it is known, the end of the association (OBR-8).

+
+ +
+
+

Proposed Text:

+
+
+

It gives the timestamp of the earliest participant involvement (OBR-7) and the latest participant involvement (OBR-8).

+
+ +++ + + + + + +

Section A.1.2.4 in PCIM TI - OBR - Observation Request, change the paragraph after Table A.1.2.4-1 to clarify OBR-7 and OBR-8 semantics:

+
+

Existing Text:

+
+
+

The OBR shall also include the timestamp of the earliest participant involvement (OBR-7) and latest participant involvement (OBR-8) for an association or disassociation event report. +Each report consists of two Participation Information Segments (PRT) and each may have timestamps for their involvement in PRT-11 and/or PRT-12. +OBR-7 and OBR-8 conveys the range of time of both participants. See Table A.1.2.6-3 and Table A.1.2.6-4 for definitions of the timestamp semantics in PRT-11 and PRT-12. +The logic for filling in the timestamp values for OBR-7 and OBR-8 is to examine both the PRT segments that will be sent out in the report and set OBR-7 to the earliest timestamp value and OBR-8 to the latest timestamp value. OBR-7 and 8 may contain the same timestamp.

+
+
+

Proposed Text:

+
+
+

The OBR shall also include the timestamp of the earliest participant involvement (OBR-7) and latest participant involvement (OBR-8) for an association or disassociation event report. +Each report consists of two or more Participation Information Segments (PRT) and each may have timestamps for their involvement in PRT-11 and/or PRT-12. +OBR-7 and OBR-8 conveys the range of time of all participants. See Table A.1.2.6-3 and Table A.1.2.6-4 for definitions of the timestamp semantics in PRT-11 and PRT-12. +The logic for filling in the timestamp values for OBR-7 and OBR-8 is to examine the PRT segments that will be sent out in the report and set OBR-7 to the earliest timestamp value and OBR-8 to the latest timestamp value. OBR-7 and 8 may contain the same timestamp.

+
+
+
+
+ + + \ No newline at end of file diff --git a/asciidoc/cp-dev-019.adoc b/asciidoc/cp-dev-019.adoc new file mode 100644 index 0000000..21a9be4 --- /dev/null +++ b/asciidoc/cp-dev-019.adoc @@ -0,0 +1,104 @@ +:imagesdir: images +[.text-center] += IHE Change Proposal + +[.text-center] +== Tracking Information +[cols="1,1"] +|=== + +|IHE Domain/Program +|DEV Domain / Patient Care Device (PCD) Program + +|Change Proposal ID: +|CP-DEV-019 + +|Change Proposal Status: +|Draft + +|Date of last update: +|2025-11-05 + +|Person Assigned: +|Eldon Metz + +|=== + +[.text-center] +== Change Proposal Summary Information + +[cols="1,1"] +|=== + +2+^|*OBR-7/8 clarifications* + +|Submitter’s Name(s) and e-mail address(es): +|Eldon Metz, emetz@innovisionmedical.com + +|Submission Date: +| TBD + +|Integration Profile(s) affected: +|Point-of-Care Identity Management (PCIM) + +|Actor(s) affected: +|Device-Patient Association Consumer + +Device-Patient Association Manager + +Device-Patient Association Reporter + +|IHE Technical Framework or Supplement modified: +|PCIM Profile TI (PCIM TI) revision 2.2, dated 2024-12-05 + +|Volume(s) and Section(s) affected: +|PCIM TI, Section A.1.2.4 + +2+|Rationale for Change: + +During the drafting of CP-DEV-018, it was identified that the OBR-7 and OBR-8 field descriptions required correction, and the accompanying text describing the number of participants needed revision. + +This Change Proposal (CP) proposes changes to PCIM TI to implement the profile clarifications and positions for the above issue. + +|=== + +|=== + +| _Section A.1.2.4 in PCIM TI - OBR - Observation Request_, change the last sentence before Table A.1.2.4-1 to clarify OBR-7 and OBR-8 represent the times of participant involvement: + +|=== + +[.text-left] +[underline]#Existing Text:# + +[.text-left] +It gives the timestamp of the beginning of the association (OBR-7), and when it is known, the end of the association (OBR-8). + +|=== + +|=== +[.text-left] +[underline]#Proposed Text:# + +[.text-left] +It gives the timestamp of the earliest participant involvement (OBR-7) and the latest participant involvement (OBR-8). + +|=== + +| _Section A.1.2.4 in PCIM TI - OBR - Observation Request_, change the paragraph after Table A.1.2.4-1 to clarify OBR-7 and OBR-8 semantics: + +|=== + +[.text-left] +[underline]#Existing Text:# +[.text-left] +The OBR shall also include the timestamp of the earliest participant involvement (OBR-7) and latest participant involvement (OBR-8) for an association or disassociation event report. +Each report consists of two Participation Information Segments (PRT) and each may have timestamps for their involvement in PRT-11 and/or PRT-12. +OBR-7 and OBR-8 conveys the range of time of both participants. See Table A.1.2.6-3 and Table A.1.2.6-4 for definitions of the timestamp semantics in PRT-11 and PRT-12. +The logic for filling in the timestamp values for OBR-7 and OBR-8 is to examine both the PRT segments that will be sent out in the report and set OBR-7 to the earliest timestamp value and OBR-8 to the latest timestamp value. OBR-7 and 8 may contain the same timestamp. + +[.text-left] +[underline]#Proposed Text:# +[.text-left] +The OBR shall also include the timestamp of the earliest participant involvement (OBR-7) and latest participant involvement (OBR-8) for an association or disassociation event report. +Each report consists of two or more Participation Information Segments (PRT) and each may have timestamps for their involvement in PRT-11 and/or PRT-12. +OBR-7 and OBR-8 conveys the range of time of all participants. See Table A.1.2.6-3 and Table A.1.2.6-4 for definitions of the timestamp semantics in PRT-11 and PRT-12. +The logic for filling in the timestamp values for OBR-7 and OBR-8 is to examine the PRT segments that will be sent out in the report and set OBR-7 to the earliest timestamp value and OBR-8 to the latest timestamp value. OBR-7 and 8 may contain the same timestamp. diff --git a/asciidoc/index.adoc b/asciidoc/index.adoc index 5b653bf..499ba12 100644 --- a/asciidoc/index.adoc +++ b/asciidoc/index.adoc @@ -58,13 +58,19 @@ DEV-52 |Draft |Eldon Metz (emetz@innovisionmedical.com) -|FHIR retrospective query support +|OBR-7/8 Timestamp Clarifications |xref:cp-dev-019.adoc[DEV-019] |DEV-51 + DEV-52 |Draft |Eldon Metz (emetz@innovisionmedical.com) +|FHIR retrospective query support +|xref:cp-dev-020.adoc[DEV-020] +| +|Draft +|Eldon Metz (emetz@innovisionmedical.com) + |DEV-51/52 and OBX-11 semantics (association error resolution scenarios with commit level and application Acknowledgements) | |DEV-51 + From 07e29df9819ec54f636ac5ba049ae879b404bbe6 Mon Sep 17 00:00:00 2001 From: Eldon Metz Date: Thu, 6 Nov 2025 13:53:20 -0800 Subject: [PATCH 2/3] Update title. --- asciidoc/cp-dev-019.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/asciidoc/cp-dev-019.adoc b/asciidoc/cp-dev-019.adoc index 21a9be4..9c66af0 100644 --- a/asciidoc/cp-dev-019.adoc +++ b/asciidoc/cp-dev-019.adoc @@ -30,7 +30,7 @@ [cols="1,1"] |=== -2+^|*OBR-7/8 clarifications* +2+^|*OBR-7/8 Timestamp Clarifications* |Submitter’s Name(s) and e-mail address(es): |Eldon Metz, emetz@innovisionmedical.com From ead00b465ec9636f954281e2090cec12c059fba9 Mon Sep 17 00:00:00 2001 From: Eldon Metz Date: Thu, 22 Jan 2026 11:19:43 -0800 Subject: [PATCH 3/3] Change status to submitted. --- asciidoc/cp-dev-019.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/asciidoc/cp-dev-019.adoc b/asciidoc/cp-dev-019.adoc index 9c66af0..510bbfb 100644 --- a/asciidoc/cp-dev-019.adoc +++ b/asciidoc/cp-dev-019.adoc @@ -14,10 +14,10 @@ |CP-DEV-019 |Change Proposal Status: -|Draft +|Submitted |Date of last update: -|2025-11-05 +|2026-01-22 |Person Assigned: |Eldon Metz @@ -36,7 +36,7 @@ |Eldon Metz, emetz@innovisionmedical.com |Submission Date: -| TBD +|2026-01-22 |Integration Profile(s) affected: |Point-of-Care Identity Management (PCIM)