ihe / dev Goto Github PK

Resolution:

1. Provide TF-1 Archive Service Guidance (for short updates)

note: longer term issue w.r.t. longer term archive support (find notes somewhere in Confluence)

See confluence page.

Resolution:

Link to Topics page

Resolution:

1. Discussion in TF-2 Appendix A MDPWS & services
2. TF-1 SDPi-P Options as BICEPS service links
3. TF-2 DEV-xyz Transactions links to BICEPS services

Complete integration of the 2019 PCD TF-1 and TF-2 into the 2020 TF-1 & TF-2 versions. TF-3 conversion is complete.

Same resolution as #5

Resolution:

1. Examples from SDC RI (Java implementation used for CA tooling) ...
2. Identify key use cases that need to be profiled...
   2.a. Nomenclature "private" space in TF-3 example
   2.b BICEPS descriptive model objects (rationale and example)
   2.b.1 See technical spec HERE
   2.c BICEPS service model extension (rationale & example)

Note: for SDPi (1.0) intent is to provide examples for what early / initial implementers may want to have.

Resolution: TBD ...

Resolution:

As part of the SDPi specification, an expansion of the DEV OID allocations was required. This was discussed during the April 2022 IHE DEV Spring meetings (see attached slides, #15 to 17 ). The general topic was discussed per the SDPi Topic: SDPi BICEPS Extension Namespace , and a decision was decided at the Gemini 2022-04-08 SDPi Friday (see Discussion Notes (3.a.v)).

Proposal

1. Create an AsciiDoc / HTML page based on the current PCD OID Management wiki page
2. Update the content to reflect DEV, while maintaining the PCD history
3. Update the content to reflect new profiles actors and transactions since the page was last updated
4. Update the content to reflect the SDPi additions (see slide #17 below)
5. Publish content on profiles.ihe.net/DEV as a special page (working with IHE Publications)
6. (TBD) Update the IHE wiki OID Management page linked in (1) above

Background

• Gemini SES+MDI Project Update 2022-04-28A.pdf

Resolution:

Resolution: TBD pending review of what should be in SDPi 1.0 (see items in confluence page)

With the 2019 extension of the IHE PCD scope to include both Personal Connected Health (PCH) and Device Point-of-care Interoperability (DPI) as additional to the Patient Care Devices (PCD) scope, and with the rebranding of the domain as simply "Devices", the IHE Devices TF should have an introductory section explaining these use context distinctions, a brief history of the domain - namely from PCD to DEV - and generally "What is a device?" since there are explicit exclusions (like radiological devices) and new inclusions like Software as a Medical Device.

Proposal
Add a section to the technical framework with the above mentioned content. This could be an initial article in DEV TF-1:2.

Resolution: (see confluence page)

Resolution

1. DEV-24 SES provide guidance