From 210d311b8d71888d98186c0248f116c90002dca9 Mon Sep 17 00:00:00 2001 From: JavierEspina Date: Thu, 30 Jul 2026 15:53:53 +0200 Subject: [PATCH 1/8] =?UTF-8?q?Corrected=20reference=20to=20BICEPS=20(from?= =?UTF-8?q?=20=E2=80=9C10207-2017=E2=80=9D=20to=20=E2=80=9C10207-2017/Cor1?= =?UTF-8?q?-2025=E2=80=9D)=20and=20all=20its=20quotes?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- ...sdpi-article-ihe-tf-asciidoc-cookbook.adoc | 2 +- asciidoc/volume0/tf0-ch-d-glossary.adoc | 10 ++++----- ...mance-statement-ieee-11073-10207-2017.adoc | 5 ++--- asciidoc/volume1/tf1-ch-10-sdpi-p.adoc | 10 ++++----- asciidoc/volume1/tf1-ch-11-sdpi-r.adoc | 6 ++--- asciidoc/volume1/tf1-ch-12-sdpi-a.adoc | 6 ++--- asciidoc/volume1/tf1-ch-13-sdpi-xc.adoc | 4 ++-- .../tf1-ch-b-ref-standards-conformance.adoc | 7 +++--- .../use-cases/tf1-ch-c-use-case-stad.adoc | 2 +- asciidoc/volume2/dev-23/tf2-dev-23.adoc | 2 +- asciidoc/volume2/dev-24/tf2-dev-24.adoc | 2 +- .../volume2/dev-25/tf2-ch-a-mdpws-dev-25.adoc | 2 +- asciidoc/volume2/dev-25/tf2-dev-25.adoc | 6 ++--- .../volume2/dev-27/tf2-ch-a-mdpws-dev-27.adoc | 16 +++++++------- asciidoc/volume2/dev-27/tf2-dev-27.adoc | 22 +++++++++---------- .../volume2/dev-28/tf2-ch-a-mdpws-dev-28.adoc | 2 +- asciidoc/volume2/dev-28/tf2-dev-28.adoc | 2 +- .../volume2/dev-29/tf2-ch-a-mdpws-dev-29.adoc | 12 +++++----- asciidoc/volume2/dev-29/tf2-dev-29.adoc | 2 +- .../volume2/dev-30/tf2-ch-a-mdpws-dev-30.adoc | 8 +++---- asciidoc/volume2/dev-30/tf2-dev-30.adoc | 4 ++-- asciidoc/volume2/dev-32/tf2-dev-32.adoc | 2 +- .../volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc | 8 +++---- asciidoc/volume2/dev-33/tf2-dev-33.adoc | 2 +- asciidoc/volume2/dev-34/tf2-dev-34.adoc | 2 +- asciidoc/volume2/dev-35/tf2-dev-35.adoc | 6 ++--- asciidoc/volume2/dev-36/tf2-dev-36.adoc | 2 +- asciidoc/volume2/dev-37/tf2-dev-37.adoc | 2 +- asciidoc/volume2/dev-38/tf2-dev-38.adoc | 6 ++--- asciidoc/volume2/dev-39/tf2-dev-39.adoc | 2 +- asciidoc/volume2/dev-40/tf2-dev-40.adoc | 2 +- asciidoc/volume2/dev-46/tf2-dev-46.adoc | 2 +- asciidoc/volume2/dev-47/tf2-dev-47.adoc | 2 +- .../gateways/tf2-ch-b-gateway-acm.adoc | 2 +- .../gateways/tf2-ch-b-gateway-dec.adoc | 2 +- .../tf2-ch-b-gateway-pid-mapping.adoc | 2 +- .../tf2-ch-a-mdpws-history-service.adoc | 2 +- .../tf2-ch-a-mdpws-service-mapping.adoc | 4 ++-- .../volume3/tf3-ch-8.3.2-biceps-content.adoc | 14 ++++++------ asciidoc/volume3/tf3-ch-a-xml-schemas.adoc | 2 +- 40 files changed, 98 insertions(+), 100 deletions(-) diff --git a/articles/sdpi-article-ihe-tf-asciidoc-cookbook.adoc b/articles/sdpi-article-ihe-tf-asciidoc-cookbook.adoc index cb44e757..79e9ef65 100644 --- a/articles/sdpi-article-ihe-tf-asciidoc-cookbook.adoc +++ b/articles/sdpi-article-ihe-tf-asciidoc-cookbook.adoc @@ -895,7 +895,7 @@ The example below illustrates the AsciiDoc source required to define a content m [#vol3_clause_sdc_biceps_semantic_content_module,role="content-module", content-module-id="biceps",oid-arcs=".1,.1.1"] ===== SDC/BICEPS Content Module -The biceps standard, <>, provides an extensive semantic... +The biceps standard, <>, provides an extensive semantic... ---- Attaching the `content-module` role to a section marks it as a [content module](https://profiles.ihe.net/DEV/SDPi/index.html#vol3). A (document-unique) identifier must be defined in the `content-module-id` attribute. The section title is used for the content module label. An <> is required for each content module. Typical a content module gets a version neutral oid (e.g., `.1`) and a versioned oid (e.g., `.1.1`). diff --git a/asciidoc/volume0/tf0-ch-d-glossary.adoc b/asciidoc/volume0/tf0-ch-d-glossary.adoc index d110f307..f7e56cdf 100644 --- a/asciidoc/volume0/tf0-ch-d-glossary.adoc +++ b/asciidoc/volume0/tf0-ch-d-glossary.adoc @@ -38,7 +38,7 @@ | General reference to the abstract, implementation technology independent SDC components defined in the IEEE 11073-10207 standard. | | [[acronym_biceps,BICEPS]] BICEPS -| <> +| <> | SDC | [[term_central_station,Central Station]] Central Station @@ -201,7 +201,7 @@ | Structured collection of any data objects that are provided by a <> or <>, including both descriptive and state information. | | [[acronym_mdib,MDIB]] MDIB -| <> +| <> | SDC | [[term_mdib_configuration, MDIB Configuration]] MDIB Configuration @@ -250,7 +250,7 @@ | A core object type in the IEEE 11073 device communication standards. It represents the top-level containment of the hierarchy of information objects contained in a device. | | [[acronym_mds,MDS]] MDS -| <>, <> +| <>, <> | | [[term_model_based_systems_engineering,Model-Based Systems Engineering (MBSE)]] Model-Based Systems Engineering @@ -408,7 +408,7 @@ elements, from requirements to system components to Verification & Validation te implements a service-oriented <> architecture composed of service providers and service consumers. | | [[acronym_somds,SOMDS]] SOMDS -| <> +| <> | SDC | [[term_slewing_adjustments,slewing time adjustments]] Slewing time adjustments @@ -506,7 +506,7 @@ implements a service-oriented <> architecture composed of service p | A core object type in the IEEE 11073 device communication standards. It represents the second-level containment of the hierarchy of information objects contained in a device. | | [[acronym_vmd,VMD]] VMD -| <>, <> +| <>, <> | |=== diff --git a/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc b/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc index e5815bd5..1a069e50 100644 --- a/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc +++ b/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc @@ -1,4 +1,4 @@ -// Standard Conformance Statement: IEEE 11073-10207:2017 +// Standard Conformance Statement: IEEE 11073-10207-2017/Cor 1-2025 ==== ISO/IEC 11073-10207 BICEPS ICS Tables @@ -12,7 +12,7 @@ Requirement Definition (this table's rows) will be referenced where they are sat |=== -*Standard Version:* IEEE 11073-10207:2017 +*Standard Version:* IEEE 11073-10207:2025 ===== General @@ -47,4 +47,3 @@ A future version of SDPi will describe how to cope with contexts, with device co |=== ADD IEEE: *Context Processing ICS table here* - diff --git a/asciidoc/volume1/tf1-ch-10-sdpi-p.adoc b/asciidoc/volume1/tf1-ch-10-sdpi-p.adoc index cdbb80fa..adcb2e58 100644 --- a/asciidoc/volume1/tf1-ch-10-sdpi-p.adoc +++ b/asciidoc/volume1/tf1-ch-10-sdpi-p.adoc @@ -159,7 +159,7 @@ include::../plantuml/vol1-figure-sdpi-p-example-sequence-diagram.puml[] [#vol1_spec_sdpi_p_actor_somds_participant, reftext='SOMDS Participant',role="actor-alias",actor-id="somds_participant"] Actor Summary Definition: [none] -. A foundational abstract actor that provides the SOA architectural constructs for interoperating in a Service-Oriented Medical Device System (SOMDS) network instance, including information, messaging and dynamic behavior models. (See <> “PARTICIPANT” definition) +. A foundational abstract actor that provides the SOA architectural constructs for interoperating in a Service-Oriented Medical Device System (SOMDS) network instance, including information, messaging and dynamic behavior models. (See <> “PARTICIPANT” definition) All systems participating in a SOMDS network instance must implement this Abstract actor. @@ -178,7 +178,7 @@ See <> fo [#vol1_spec_sdpi_p_actor_somds_provider, reftext='SOMDS Provider',role="actor-alias",actor-id="somds_provider"] Actor Summary Definition: [none] -. A <> that provides at least one service to the other participant systems. (See <> “SERVICE PROVIDER” definition.) +. A <> that provides at least one service to the other participant systems. (See <> “SERVICE PROVIDER” definition.) Every <> is paired with (inherits from) the abstract _<>_ Actor. @@ -189,7 +189,7 @@ A system that participates in a SOMDS network instance can include both <> that discovers and utilizes at least one service, functional capability, exposed to a network communications backbone by a <>. (See <> “SERVICE CONSUMER” and “SERVICE” definitions.) +. A <> that discovers and utilizes at least one service, functional capability, exposed to a network communications backbone by a <>. (See <> “SERVICE CONSUMER” and “SERVICE” definitions.) Every <> is paired with (inherits from) the abstract _<>_ Actor. @@ -326,7 +326,7 @@ See <> for additional discussion. [#vol1_spec_sdpi_p_actor_biceps_content_creator, reftext='BICEPS Content Creator',role=actor-alias,actor-id="biceps_content_creator"] Actor Summary Definition: [none] -. Provides <> content conformant to <> BICEPS specification and for consumption by other <> systems. +. Provides <> content conformant to <> BICEPS specification and for consumption by other <> systems. All content created and provided by a <> shall be conformant to the BICEPS content module specifications in <> and related sections. @@ -350,7 +350,7 @@ sdpi_include_content_module::dialysis[actor-id="biceps_content_creator",support= [#vol1_spec_sdpi_p_actor_biceps_content_consumer, reftext='BICEPS Content Consumer',role=actor-alias,actor-id="biceps_content_consumer"] Actor Summary Definition: [none] -. Processes <> information conformant to <> BICEPS specifications provided by <> systems. +. Processes <> information conformant to <> BICEPS specifications provided by <> systems. A <> shall be capable of processing information provided by a <>, in accordance to the BICEPS content module specifications in <> and related sections. diff --git a/asciidoc/volume1/tf1-ch-11-sdpi-r.adoc b/asciidoc/volume1/tf1-ch-11-sdpi-r.adoc index 4a3e782f..d5a24226 100644 --- a/asciidoc/volume1/tf1-ch-11-sdpi-r.adoc +++ b/asciidoc/volume1/tf1-ch-11-sdpi-r.adoc @@ -108,7 +108,7 @@ Actor Summary Definition: [none] . A <> grouped actor that sends medical data to a <>. -This actor is designed to process information with an _intended medical purpose_, and thus will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards (<> and <>). +This actor is designed to process information with an _intended medical purpose_, and thus will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards (<> and <>). Every <> is grouped with an <> to enable <>-based connectivity. This actor inherits all the capabilities of the paired <>. @@ -124,7 +124,7 @@ Actor Summary Definition: [none] . A <> grouped actor that receives medical data from a <>. -This actor is designed to process information with an _intended medical purpose_, and thus will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards (<> and <>). +This actor is designed to process information with an _intended medical purpose_, and thus will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards (<> and <>). Every <> is grouped with an <> to enable <>-based connectivity. This actor inherits all the capabilities of the paired <>. @@ -140,7 +140,7 @@ Actor Summary Definition: [none] . A <> grouped actor that supports the bi-directional exchange of medical data using IHE Device Enterprise Communication (DEC) messages with non-SOMDS systems and applications. -This actor is designed to process information with an _intended medical purpose_, and thus will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards (<> and <>). +This actor is designed to process information with an _intended medical purpose_, and thus will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards (<> and <>). Every <> is grouped with an <> to enable <>-based connectivity. This actor inherits all the capabilities of the paired <>. diff --git a/asciidoc/volume1/tf1-ch-12-sdpi-a.adoc b/asciidoc/volume1/tf1-ch-12-sdpi-a.adoc index 3833ff25..d6874d62 100644 --- a/asciidoc/volume1/tf1-ch-12-sdpi-a.adoc +++ b/asciidoc/volume1/tf1-ch-12-sdpi-a.adoc @@ -127,7 +127,7 @@ Actor Summary Definition: This actor is designed to publish medical device alert information to a <>, which in turn can communicate it safely and reliably to a clinician. Transactions enabled for this actor are identified in <> above. -Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Alert <>). +Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Alert <>). Every <> is grouped with an <> to enable <>-based connectivity. This actor inherits all the capabilities of the paired <>. @@ -146,7 +146,7 @@ Actor Summary Definition: This actor is designed to receive and manage medical device alert information to communicate it safely and reliably to a clinician. Transactions enabled for this actor are identified in <> above. -Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Alert <>). +Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Alert <>). Every <> is grouped with an <> to enable <>-based connectivity. This actor inherits all the capabilities of the paired <>. @@ -170,7 +170,7 @@ Note that optional capabilities for this specification, as specified in <> above. -Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Alert <>). +Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Alert <>). This actor shall implement the <> capabilities, receiving alert information provided by <> systems and publishing them as [DEV-04] / [PCD-04] Transactions to external ACM Alert Manager (AM) systems. If <> is implemented, then this actor will also support the <> capabilities, receiving [DEV-04] / [PCD-04] Transactions from external ACM Device Observation Reporter (DOR) systems and making them available to other <> systems. diff --git a/asciidoc/volume1/tf1-ch-13-sdpi-xc.adoc b/asciidoc/volume1/tf1-ch-13-sdpi-xc.adoc index 7536bdba..9d5a24f6 100644 --- a/asciidoc/volume1/tf1-ch-13-sdpi-xc.adoc +++ b/asciidoc/volume1/tf1-ch-13-sdpi-xc.adoc @@ -92,7 +92,7 @@ Actor Summary Definition: This actor is designed to publish medical device operational control services to a <>, which in turn can invoke the services and remotely manage the device, safely and securely. Transactions enabled for this actor are identified in <> above. -Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Control <>). +Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Control <>). Every <> is grouped with an <> to enable <>-based connectivity. This actor inherits all the capabilities of the paired <>. @@ -109,7 +109,7 @@ Actor Summary Definition: This actor is designed to invoke and manage medical device control operations, safely, effectively and securely. Transactions enabled for this actor are identified in <> above. -Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Control <>). +Given this _intended medical purpose_, the actor will fully address applicable requirements from the core <> standards (<> and <>), as well as the <> standards <> and <> (Control <>). Every <> is grouped with an <> to enable <>-based connectivity. This actor inherits all the capabilities of the paired <>. diff --git a/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc b/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc index a266dded..91055bb0 100644 --- a/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc +++ b/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc @@ -8,7 +8,7 @@ |=== | *{supplement_note}*: The inclusion of a References appendix is unique for IHE Technical Framework specifications. Typically, referenced standards sections are distributed throughout the specifications where appropriate; however, standards from other organizations (e.g., IEEE, ISO, IEC) typically have a "Normative References" clause and when desired a "Bibliography" clause. -Also, integration of explicit standards' <> specifications (e.g., <> <> tables) is unique, but needed to support requirements interoperability. +Also, integration of explicit standards' <> specifications (e.g., <> <> tables) is unique, but needed to support requirements interoperability. Ultimately, the content of this appendix may be rearranged and even relocated; however, for early versions of the SDPi supplement, it has proven helpful, and even of critical importance and value. |=== @@ -42,7 +42,7 @@ No content from those three standards - including their requirements - is norma * [[[ref_ieee_11073_10201_2004,IEEE 11073-10201:2004]]] IEEE 11073-10201™ International Standard - Health informatics--Device interoperability--Part 10201:Point-of-care medical device communication--Domain information model. Note this was updated in 2020. Available at https://standards.ieee.org/ieee/11073-10201/10263/. -* [[[ref_ieee_11073_10207_2017,IEEE 11073-10207:2017]]] IEEE 11073-10207-2017, Health informatics — Point-of-care medical device communication — Part 10207: Domain Information and Service Model for Service-Oriented Point-of-Care Medical Device Communication, 2017-12, available at https://standards.ieee.org/ieee/11073-10207/6032 footnote:ieee_permission[]. +* [[[ref_ieee_11073_10207_2017_Cor1_2025,IEEE 11073-10207-2017/Cor 1-2025]]] IEEE 11073-10207-2017/Cor 1-2025, Health informatics — Point-of-care medical device communication — Part 10207: Domain Information and Service Model for Service-Oriented Point-of-Care Medical Device Communication Corrigendum 1, 2025-12, available at https://standards.ieee.org/ieee/11073-10207-2017_Cor_1/11316/ footnote:ieee_permission[]. * [[[ref_ieee_11073_10700_2022,IEEE 11073-10700:2022]]] IEEE 11073-10700™ IEEE Standard -- Health Informatics--Device Interoperability Part 10700: Point‐of‐Care Medical Device Communication--Standard for Base Requirements for Participants in a Service‐Oriented Device Connectivity (SDC) System, available at https://standards.ieee.org/ieee/11073-10700/10630/. @@ -125,7 +125,7 @@ a| *{supplement_note}*: This section intentionally left blank for the current v #TODO: Provide a general overview of the topic, including some standards that provide Conformity statements, ICS tables, etc., and those that are moot on the topic - and how all of this is handled in this appendix and TF specification# //// -// IEEE 11073-10207:2017 ICS +// IEEE 11073-10207-2017/Cor 1-2025 ICS include::conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc[] @@ -184,4 +184,3 @@ The following bibliographic references include slide decks and recordings that a * [[[ref_ihe_eu_experience_2021_presentation_cooper_schlichting,IHE EU Experience-2021 IHE CA for MedTech Solutions]]] "IHE & IHE Catalyst: Advancing Interoperable MedTec Solutions with "Regulatory Submission Ready" Conformity Assessment", presentation by Todd Cooper and Dr. Stefan Schlichting, available at https://connectathon.ihe-europe.net/experience-sessions-2021-presentations[IHE Europe Experience 2021 Presentations web page]. - diff --git a/asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc b/asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc index 743a045f..e2063786 100644 --- a/asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc +++ b/asciidoc/volume1/use-cases/tf1-ch-c-use-case-stad.adoc @@ -380,7 +380,7 @@ When the <> detects an <> of the <> considers the risks arising from <>s spanning <>s from an <> having occurred at the <> when the <> receives a changed value in the <>'s MDIB sequence identifier or when the `pm:ClockState/@ActivationState` is `StndBy`. -* This clarifies the ambiguity in <>, section B.182 and <>, R0014 when a participant uses slewing to make <> (using, for example, the <> <>) where information from one or more <>s is used to maintain clock-discipline and does not (generally) "set" the clock. +* This clarifies the ambiguity in <>, section B.182 and <>, R0014 when a participant uses slewing to make <> (using, for example, the <> <>) where information from one or more <>s is used to maintain clock-discipline and does not (generally) "set" the clock. * Any <> strictly-less than `pm:ClockState/@LastSet` in the MDIB when `pm:ClockState/@ActivationState` is set to `StndBy` may be untrustworthy. ==== diff --git a/asciidoc/volume2/dev-23/tf2-dev-23.adoc b/asciidoc/volume2/dev-23/tf2-dev-23.adoc index 1ce45e06..52c26769 100644 --- a/asciidoc/volume2/dev-23/tf2-dev-23.adoc +++ b/asciidoc/volume2/dev-23/tf2-dev-23.adoc @@ -30,7 +30,7 @@ Listens for <> Section 9.2 Implicit Discovery +* <> Section 9.2 Implicit Discovery ==== Messages diff --git a/asciidoc/volume2/dev-24/tf2-dev-24.adoc b/asciidoc/volume2/dev-24/tf2-dev-24.adoc index 9f1f0dae..365c0c4e 100644 --- a/asciidoc/volume2/dev-24/tf2-dev-24.adoc +++ b/asciidoc/volume2/dev-24/tf2-dev-24.adoc @@ -33,7 +33,7 @@ Listens for <> Section 9.3 Explicit Discovery +* <> Section 9.3 Explicit Discovery ==== Messages diff --git a/asciidoc/volume2/dev-25/tf2-ch-a-mdpws-dev-25.adoc b/asciidoc/volume2/dev-25/tf2-ch-a-mdpws-dev-25.adoc index d494a922..40a9da47 100644 --- a/asciidoc/volume2/dev-25/tf2-ch-a-mdpws-dev-25.adoc +++ b/asciidoc/volume2/dev-25/tf2-ch-a-mdpws-dev-25.adoc @@ -1,6 +1,6 @@ :var_uri_ws_discovery_transfer: https://www.w3.org/Submission/2006/SUBM-WS-Transfer-20060927/#Get :var_uri_dpws: http://docs.oasis-open.org/ws-dd/dpws/1.1/os/wsdd-dpws-1.1-spec-os.html#_Toc228672092 -:var_ref_biceps_service_model: <> Section 7.3 Service Model +:var_ref_biceps_service_model: <> Section 7.3 Service Model :var_uri_namespace_sdc: http://standards.ieee.org/downloads/11073/11073-20701-2018 [#vol2-clause-appendix-mdpws-dev-25] diff --git a/asciidoc/volume2/dev-25/tf2-dev-25.adoc b/asciidoc/volume2/dev-25/tf2-dev-25.adoc index 22891845..5d21bc40 100644 --- a/asciidoc/volume2/dev-25/tf2-dev-25.adoc +++ b/asciidoc/volume2/dev-25/tf2-dev-25.adoc @@ -24,8 +24,8 @@ Sends its resource representation to the <> Section 9 Discovery Model -* <> Section 7.3 Service Model +* <> Section 9 Discovery Model +* <> Section 7.3 Service Model ==== Messages .Message Interaction Diagram [DEV-25] @@ -53,7 +53,7 @@ The GetMetadataResponse message is sent in response to an incoming <> receives a <> message. ====== Message Semantics -[[payload_dev_25_get_metadata_biceps_services]]BICEPS Services:: Collection of BICEPS services the <> offers, including but not limited to, one or more of the following BICEPS services (<> Section 7.3 Service Model): +[[payload_dev_25_get_metadata_biceps_services]]BICEPS Services:: Collection of BICEPS services the <> offers, including but not limited to, one or more of the following BICEPS services (<> Section 7.3 Service Model): * GET SERVICE (mandatory) * SET SERVICE diff --git a/asciidoc/volume2/dev-27/tf2-ch-a-mdpws-dev-27.adoc b/asciidoc/volume2/dev-27/tf2-ch-a-mdpws-dev-27.adoc index 6762981c..66e35626 100644 --- a/asciidoc/volume2/dev-27/tf2-ch-a-mdpws-dev-27.adoc +++ b/asciidoc/volume2/dev-27/tf2-ch-a-mdpws-dev-27.adoc @@ -57,28 +57,28 @@ include::../dev-a-default-trigger-events.adoc[] |=== |BICEPS report type |Action URI -|DescriptionModificationReport as specified in <>, Annex C.5 +|DescriptionModificationReport as specified in <>, Annex C.5 |http://standards.ieee.org/downloads/11073/11073-20701-2018/DescriptionEventService/DescriptionModificationReport -|EpisodicAlertReport as specified in <>, Annex C.11 +|EpisodicAlertReport as specified in <>, Annex C.11 |http://standards.ieee.org/downloads/11073/11073-20701-2018/StateEventService/EpisodicAlertReport -|EpisodicComponentReport as specified in <>, Annex C.12 +|EpisodicComponentReport as specified in <>, Annex C.12 |http://standards.ieee.org/downloads/11073/11073-20701-2018/StateEventService/EpisodicComponentReport -|EpisodicContextReport as specified in <>, Annex C.13 +|EpisodicContextReport as specified in <>, Annex C.13 |http://standards.ieee.org/downloads/11073/11073-20701-2018/ContextService/EpisodicContextReport -|EpisodicMetricReport as specified in <>, Annex C.14 +|EpisodicMetricReport as specified in <>, Annex C.14 |http://standards.ieee.org/downloads/11073/11073-20701-2018/StateEventService/EpisodicMetricReport -|EpisodicOperationalStateReport as specified in <>, Annex C.15 +|EpisodicOperationalStateReport as specified in <>, Annex C.15 |http://standards.ieee.org/downloads/11073/11073-20701-2018/StateEventService/EpisodicOperationalStateReport -|OperationInvokedReport as specified in <>, Annex C.77 +|OperationInvokedReport as specified in <>, Annex C.77 |http://standards.ieee.org/downloads/11073/11073-20701-2018/SetService/OperationInvokedReport -|WaveformStream as specified in <>, Annex C.112 +|WaveformStream as specified in <>, Annex C.112 |http://standards.ieee.org/downloads/11073/11073-20701-2018/WaveformService/WaveformStream |=== diff --git a/asciidoc/volume2/dev-27/tf2-dev-27.adoc b/asciidoc/volume2/dev-27/tf2-dev-27.adoc index 681f5f0e..8fe4836d 100644 --- a/asciidoc/volume2/dev-27/tf2-dev-27.adoc +++ b/asciidoc/volume2/dev-27/tf2-dev-27.adoc @@ -41,9 +41,9 @@ When at some point the subscription has to be ended, the <> Section 7.2.3 Publish-Subscribe -* <> Section 7.2.4 Streaming -* <> Annex C +* <> Section 7.2.3 Publish-Subscribe +* <> Section 7.2.4 Streaming +* <> Annex C ==== Messages @@ -76,14 +76,14 @@ The {var_label_dev_27_message_subscribe} message is sent whenever a <>, Annex C.5 -- EpisodicAlertReport as specified in <>, Annex C.11 -- EpisodicComponentReport as specified in <>, Annex C.12 -- EpisodicContextReport as specified in <>, Annex C.13 -- EpisodicMetricReport as specified in <>, Annex C.14 -- EpisodicOperationalStateReport as specified in <>, Annex C.15 -- OperationInvokedReport as specified in <>, Annex C.77 -- WaveformStream as specified in <>, Annex C.112 +- DescriptionModificationReport as specified in <>, Annex C.5 +- EpisodicAlertReport as specified in <>, Annex C.11 +- EpisodicComponentReport as specified in <>, Annex C.12 +- EpisodicContextReport as specified in <>, Annex C.13 +- EpisodicMetricReport as specified in <>, Annex C.14 +- EpisodicOperationalStateReport as specified in <>, Annex C.15 +- OperationInvokedReport as specified in <>, Annex C.77 +- WaveformStream as specified in <>, Annex C.112 [[payload_dev_27_susbcribe_expiration_time]]Expiration Time:: A time requested for subscription expiration. diff --git a/asciidoc/volume2/dev-28/tf2-ch-a-mdpws-dev-28.adoc b/asciidoc/volume2/dev-28/tf2-ch-a-mdpws-dev-28.adoc index b51a5e1d..dd55efba 100644 --- a/asciidoc/volume2/dev-28/tf2-ch-a-mdpws-dev-28.adoc +++ b/asciidoc/volume2/dev-28/tf2-ch-a-mdpws-dev-28.adoc @@ -16,7 +16,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:EpisodicContextReport +* <> msg:EpisodicContextReport ====== Message Outline diff --git a/asciidoc/volume2/dev-28/tf2-dev-28.adoc b/asciidoc/volume2/dev-28/tf2-dev-28.adoc index 2dddd64e..0afe3cd9 100644 --- a/asciidoc/volume2/dev-28/tf2-dev-28.adoc +++ b/asciidoc/volume2/dev-28/tf2-dev-28.adoc @@ -28,7 +28,7 @@ While a subscription is running, the <> d ==== Referenced Standards -* <> Section 7.4 Message Model +* <> Section 7.4 Message Model ==== Messages diff --git a/asciidoc/volume2/dev-29/tf2-ch-a-mdpws-dev-29.adoc b/asciidoc/volume2/dev-29/tf2-ch-a-mdpws-dev-29.adoc index 0d8747b8..e6a5626a 100644 --- a/asciidoc/volume2/dev-29/tf2-ch-a-mdpws-dev-29.adoc +++ b/asciidoc/volume2/dev-29/tf2-ch-a-mdpws-dev-29.adoc @@ -22,7 +22,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:EpisodicAlertReport +* <> msg:EpisodicAlertReport ====== Message Outline @@ -51,7 +51,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:EpisodicMetricReport +* <> msg:EpisodicMetricReport ====== Message Outline @@ -81,7 +81,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:EpisodicComponentReport +* <> msg:EpisodicComponentReport ====== Message Outline @@ -110,7 +110,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:DescriptionModificationReport +* <> msg:DescriptionModificationReport ====== Message Outline @@ -139,7 +139,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:EpisodicOperationalStateReport +* <> msg:EpisodicOperationalStateReport ====== Message Outline @@ -168,7 +168,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:WaveformStream +* <> msg:WaveformStream ====== Message Outline diff --git a/asciidoc/volume2/dev-29/tf2-dev-29.adoc b/asciidoc/volume2/dev-29/tf2-dev-29.adoc index 19a28014..73382067 100644 --- a/asciidoc/volume2/dev-29/tf2-dev-29.adoc +++ b/asciidoc/volume2/dev-29/tf2-dev-29.adoc @@ -28,7 +28,7 @@ While a subscription is running, the <> d ==== Referenced Standards -* <> Section 7.4 Message Model +* <> Section 7.4 Message Model ==== Messages diff --git a/asciidoc/volume2/dev-30/tf2-ch-a-mdpws-dev-30.adoc b/asciidoc/volume2/dev-30/tf2-ch-a-mdpws-dev-30.adoc index 6bc8cb43..8aeabb68 100644 --- a/asciidoc/volume2/dev-30/tf2-ch-a-mdpws-dev-30.adoc +++ b/asciidoc/volume2/dev-30/tf2-ch-a-mdpws-dev-30.adoc @@ -15,7 +15,7 @@ The <> m ====== Referenced Standards * <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:GetMdib +* <> msg:GetMdib ====== Message Outline @@ -44,7 +44,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:GetMdibResponse +* <> msg:GetMdibResponse ====== Message Outline @@ -81,7 +81,7 @@ A <> shall enclose all context states in [NOTE] ==== -This requirement restricts optionality in including context states in GetMdibResponse messages as specified in <>, C.57 GetMdibResponse: +This requirement restricts optionality in including context states in GetMdibResponse messages as specified in <>, C.57 GetMdibResponse: [quote] ____ @@ -89,7 +89,7 @@ Since contexts might include privacy-related information, a SERVICE PROVIDER MAY the MDS contexts empty. ____ -Since transmission of GetMdibResponse messages is required to be secured, there is no need for omitting context states to meet confidentiality; R0121 in <> is still met. +Since transmission of GetMdibResponse messages is required to be secured, there is no need for omitting context states to meet confidentiality; R0121 in <> is still met. ==== **** diff --git a/asciidoc/volume2/dev-30/tf2-dev-30.adoc b/asciidoc/volume2/dev-30/tf2-dev-30.adoc index 36e68895..a9f35325 100644 --- a/asciidoc/volume2/dev-30/tf2-dev-30.adoc +++ b/asciidoc/volume2/dev-30/tf2-dev-30.adoc @@ -28,7 +28,7 @@ Listens for <> Section 7.3.2 Get Service +* <> Section 7.3.2 Get Service ==== Messages @@ -82,7 +82,7 @@ The {var_label_dev_30_message_getmdibresponse} message is sent whenever a <> R0121.) +(As the communication is encrypted, this can include ContextStates without violating <> R0121.) [#vol2_clause_dev_30_message_getmdibresponse_expected_actions] ====== Expected Actions diff --git a/asciidoc/volume2/dev-32/tf2-dev-32.adoc b/asciidoc/volume2/dev-32/tf2-dev-32.adoc index e6a6c621..384d82b5 100644 --- a/asciidoc/volume2/dev-32/tf2-dev-32.adoc +++ b/asciidoc/volume2/dev-32/tf2-dev-32.adoc @@ -27,7 +27,7 @@ While a subscription is running, the <> d ==== Referenced Standards -* <> Section 7.4 Message Model +* <> Section 7.4 Message Model ==== Messages diff --git a/asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc b/asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc index b7f4b24e..d85604d5 100644 --- a/asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc +++ b/asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc @@ -14,7 +14,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:GetSupportedLanguages +* <> msg:GetSupportedLanguages ====== Message Outline @@ -45,7 +45,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:GetSupportedLanguagesResponse +* <> msg:GetSupportedLanguagesResponse ====== Message Outline @@ -76,7 +76,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:GetLocalizedText +* <> msg:GetLocalizedText ====== Message Outline @@ -111,7 +111,7 @@ The <> {var_uri_dpws_messaging}[Section 2 Messaging] -* <> msg:GetLocalizedTextResponse +* <> msg:GetLocalizedTextResponse ====== Message Outline diff --git a/asciidoc/volume2/dev-33/tf2-dev-33.adoc b/asciidoc/volume2/dev-33/tf2-dev-33.adoc index c820d322..6b40cbbc 100644 --- a/asciidoc/volume2/dev-33/tf2-dev-33.adoc +++ b/asciidoc/volume2/dev-33/tf2-dev-33.adoc @@ -31,7 +31,7 @@ Listens for <> Section 7.3.10 Localization Service +* <> Section 7.3.10 Localization Service ==== Messages diff --git a/asciidoc/volume2/dev-34/tf2-dev-34.adoc b/asciidoc/volume2/dev-34/tf2-dev-34.adoc index f2f53a9d..4186e9a4 100644 --- a/asciidoc/volume2/dev-34/tf2-dev-34.adoc +++ b/asciidoc/volume2/dev-34/tf2-dev-34.adoc @@ -35,7 +35,7 @@ Listens for <> m ==== Referenced Standards -* <> Section 9.2 Implicit Discovery +* <> Section 9.2 Implicit Discovery ==== Messages diff --git a/asciidoc/volume2/dev-35/tf2-dev-35.adoc b/asciidoc/volume2/dev-35/tf2-dev-35.adoc index facd685f..a83c53e9 100644 --- a/asciidoc/volume2/dev-35/tf2-dev-35.adoc +++ b/asciidoc/volume2/dev-35/tf2-dev-35.adoc @@ -27,9 +27,9 @@ Listens for {var_label_dev_35_message_subscribe} messages, which it responds to ==== Referenced Standards -* <> Section 7.2.3 Publish-Subscribe -* <> Section 7.2.4 Streaming -* <> Annex C +* <> Section 7.2.3 Publish-Subscribe +* <> Section 7.2.4 Streaming +* <> Annex C ==== Messages diff --git a/asciidoc/volume2/dev-36/tf2-dev-36.adoc b/asciidoc/volume2/dev-36/tf2-dev-36.adoc index b2a49491..c83c1d37 100644 --- a/asciidoc/volume2/dev-36/tf2-dev-36.adoc +++ b/asciidoc/volume2/dev-36/tf2-dev-36.adoc @@ -27,7 +27,7 @@ While a subscription is running, the <> Section 7.4 Message Model +* <> Section 7.4 Message Model ==== Messages diff --git a/asciidoc/volume2/dev-37/tf2-dev-37.adoc b/asciidoc/volume2/dev-37/tf2-dev-37.adoc index e41e4e06..0706c9a6 100644 --- a/asciidoc/volume2/dev-37/tf2-dev-37.adoc +++ b/asciidoc/volume2/dev-37/tf2-dev-37.adoc @@ -26,7 +26,7 @@ Listens for {var_label_dev_37_message_getmdib} messages, which it responds to wi ==== Referenced Standards -* <> Section 7.3.2 Get Service +* <> Section 7.3.2 Get Service ==== Messages diff --git a/asciidoc/volume2/dev-38/tf2-dev-38.adoc b/asciidoc/volume2/dev-38/tf2-dev-38.adoc index 843139ea..f67340e4 100644 --- a/asciidoc/volume2/dev-38/tf2-dev-38.adoc +++ b/asciidoc/volume2/dev-38/tf2-dev-38.adoc @@ -25,9 +25,9 @@ Listens for {var_label_dev_38_message_subscribe} messages, which it responds to ==== Referenced Standards -* <> Section 7.2.3 Publish-Subscribe -* <> Section 7.2.4 Streaming -* <> Annex C +* <> Section 7.2.3 Publish-Subscribe +* <> Section 7.2.4 Streaming +* <> Annex C ==== Messages diff --git a/asciidoc/volume2/dev-39/tf2-dev-39.adoc b/asciidoc/volume2/dev-39/tf2-dev-39.adoc index 3677957f..bff5a920 100644 --- a/asciidoc/volume2/dev-39/tf2-dev-39.adoc +++ b/asciidoc/volume2/dev-39/tf2-dev-39.adoc @@ -25,7 +25,7 @@ While a subscription is running, the <> Section 7.4 Message Model +* <> Section 7.4 Message Model ==== Messages diff --git a/asciidoc/volume2/dev-40/tf2-dev-40.adoc b/asciidoc/volume2/dev-40/tf2-dev-40.adoc index 2528a6eb..c651164d 100644 --- a/asciidoc/volume2/dev-40/tf2-dev-40.adoc +++ b/asciidoc/volume2/dev-40/tf2-dev-40.adoc @@ -28,7 +28,7 @@ Listens for {var_label_dev_40_message_getmdib} messages, which it responds to wi ==== Referenced Standards -* <> Section 7.3.2 Get Service +* <> Section 7.3.2 Get Service ==== Messages diff --git a/asciidoc/volume2/dev-46/tf2-dev-46.adoc b/asciidoc/volume2/dev-46/tf2-dev-46.adoc index 58190080..eb95938a 100644 --- a/asciidoc/volume2/dev-46/tf2-dev-46.adoc +++ b/asciidoc/volume2/dev-46/tf2-dev-46.adoc @@ -34,7 +34,7 @@ When joining a <>, it announces its presence to the ==== Referenced Standards -* <> Section 9. Discovery Model +* <> Section 9. Discovery Model ==== Messages diff --git a/asciidoc/volume2/dev-47/tf2-dev-47.adoc b/asciidoc/volume2/dev-47/tf2-dev-47.adoc index 4217bc5a..44f12cb8 100644 --- a/asciidoc/volume2/dev-47/tf2-dev-47.adoc +++ b/asciidoc/volume2/dev-47/tf2-dev-47.adoc @@ -42,7 +42,7 @@ and <> message ==== Referenced Standards -* <> Section 9. Discovery Model +* <> Section 9. Discovery Model ==== Messages diff --git a/asciidoc/volume2/gateways/tf2-ch-b-gateway-acm.adoc b/asciidoc/volume2/gateways/tf2-ch-b-gateway-acm.adoc index bc6b45fe..26dfe7d9 100644 --- a/asciidoc/volume2/gateways/tf2-ch-b-gateway-acm.adoc +++ b/asciidoc/volume2/gateways/tf2-ch-b-gateway-acm.adoc @@ -15,7 +15,7 @@ This section provides an overview about the referenced standards and profiles us * <> * <> * <> -* <> +* <> ==== Private MDC Codes Consideration Please refer to general Section <>. diff --git a/asciidoc/volume2/gateways/tf2-ch-b-gateway-dec.adoc b/asciidoc/volume2/gateways/tf2-ch-b-gateway-dec.adoc index 84b53d1d..975cd44e 100644 --- a/asciidoc/volume2/gateways/tf2-ch-b-gateway-dec.adoc +++ b/asciidoc/volume2/gateways/tf2-ch-b-gateway-dec.adoc @@ -14,7 +14,7 @@ This section provides an overview about the referenced standards and profiles us * <> * <> * <> -* <> +* <> ==== Private MDC Codes Consideration Please refer to general Section <>. diff --git a/asciidoc/volume2/gateways/tf2-ch-b-gateway-pid-mapping.adoc b/asciidoc/volume2/gateways/tf2-ch-b-gateway-pid-mapping.adoc index 5c83ebdf..627582df 100644 --- a/asciidoc/volume2/gateways/tf2-ch-b-gateway-pid-mapping.adoc +++ b/asciidoc/volume2/gateways/tf2-ch-b-gateway-pid-mapping.adoc @@ -217,7 +217,7 @@ xsd:date: *2001-10-26* -> HL7 DTM: *20011026* ====== PID-8 Administrative Sex -The sex and gender of a patient (or a newborn) cannot exactly be mapped from <> to <>. The <> model only contains an attribute for sex (*pm:PatientContextState/pm:CoreData/pm:Sex*) as defined by biological and physiological characteristics. <>, on the other hand, only provides a field for the administrative sex as defined by the socially constructed roles, behaviours, activities, and attributes that a given society considers appropriate. The biological sex, however, does not necessarily match a person’s administrative gender or sex. Mapping from one to the other would therefore introduce errors. However, in the clinical context of a <> the *sex for clinical use* is important for various algorithms, range and limit settings, and so on. +The sex and gender of a patient (or a newborn) cannot exactly be mapped from <> to <>. The <> model only contains an attribute for sex (*pm:PatientContextState/pm:CoreData/pm:Sex*) as defined by biological and physiological characteristics. <>, on the other hand, only provides a field for the administrative sex as defined by the socially constructed roles, behaviours, activities, and attributes that a given society considers appropriate. The biological sex, however, does not necessarily match a person’s administrative gender or sex. Mapping from one to the other would therefore introduce errors. However, in the clinical context of a <> the *sex for clinical use* is important for various algorithms, range and limit settings, and so on. In order to avoid an erroneous mapping of potentially different sex concept interpretations, the sex as defined in <> is required to be mapped to a separate OBX segment as defined in <>. diff --git a/asciidoc/volume2/history-service/tf2-ch-a-mdpws-history-service.adoc b/asciidoc/volume2/history-service/tf2-ch-a-mdpws-history-service.adoc index dae70699..58c3a8ca 100644 --- a/asciidoc/volume2/history-service/tf2-ch-a-mdpws-history-service.adoc +++ b/asciidoc/volume2/history-service/tf2-ch-a-mdpws-history-service.adoc @@ -267,7 +267,7 @@ All object identifiers used by the <> are specified in <> shows the XML Schema file that specifies the <> XML grammar. -The XML Schema includes the BICEPS message, participant and extension Model files as provided as an additional resource at https://standards.ieee.org/ieee/11073-10207/6032/. +The XML Schema includes the BICEPS message, participant and extension Model files as provided as an additional resource at https://standards.ieee.org/downloads/. .<> XML Schema outline [source#vol2_clause_appendix_a_mdpws_history_service_xmlschema,xml] diff --git a/asciidoc/volume2/service-mapping/tf2-ch-a-mdpws-service-mapping.adoc b/asciidoc/volume2/service-mapping/tf2-ch-a-mdpws-service-mapping.adoc index cb993dc5..fc3e0385 100644 --- a/asciidoc/volume2/service-mapping/tf2-ch-a-mdpws-service-mapping.adoc +++ b/asciidoc/volume2/service-mapping/tf2-ch-a-mdpws-service-mapping.adoc @@ -22,7 +22,7 @@ A <> shall at least provide the port type .Minimum required port types [#vol2_table_appendix_mdpws_service_mapping_port_types,cols="3,1"] |=== -|Port Type (as <>) |BICEPS service <> +|Port Type (as <>) |BICEPS service <> |++{++{uri_sdc_port_type}++}++GetService |GET SERVICE @@ -48,7 +48,7 @@ A <> should not request context states by [NOTE] ==== -* `GetContextStatesByIdentification` and `GetContextStatesByFilter` are insufficiently defined in <> and are likely to be obsoleted in a future revision of the specification. +* `GetContextStatesByIdentification` and `GetContextStatesByFilter` are insufficiently defined in <> and are likely to be obsoleted in a future revision of the specification. * A <> may retrieve context states by using `GetContextStates` and perform filtering by itself. ==== diff --git a/asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc b/asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc index a806f868..baf98e08 100644 --- a/asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc +++ b/asciidoc/volume3/tf3-ch-8.3.2-biceps-content.adoc @@ -3,7 +3,7 @@ [#vol3_clause_sdc_biceps_semantic_content_module] ===== SDC/BICEPS Content Module -The <> standard, <>, provides an extensive semantic model for all information exchanged between <> systems. This section provides a general background for <>-based content, including both what is unique to this standard (e.g., different from the <>), and any extensions that are made by this SDPi supplement. +The <> standard, <>, provides an extensive semantic model for all information exchanged between <> systems. This section provides a general background for <>-based content, including both what is unique to this standard (e.g., different from the <>), and any extensions that are made by this SDPi supplement. .R0701 @@ -11,7 +11,7 @@ The <> standard, <>, provides an exte **** [NORMATIVE] ==== -All <> systems shall fully implement the semantic content requirements in the <> <> standard. +All <> systems shall fully implement the semantic content requirements in the <> <> standard. ==== [NOTE] @@ -36,7 +36,7 @@ As described in <> (see <>, provides a basic set of objects and containment relationships for describing the information and services supported by a medical device. +This model, detailed in <>, provides a basic set of objects and containment relationships for describing the information and services supported by a medical device. The core Medical Device System (*MDS*), Virtual Medical Device (*VMD*), Channel, and Metric objects are utilized for communicating basic information; whereas, the Alert System objects (not all are included on this diagram) support the specialized information around medical device alerts, alarms, and special events. What is unique to this descriptor model, though, is the inclusion of a set of SystemContext objects, as identified in <> below: @@ -49,7 +49,7 @@ These context types combine to support description of the operational environme Depending on a systems capabilities, they may be configured -- statically or dynamically -- with context information such as location or patient identification, or they may discover a <> on the network from which they can retrieve the information. These context types represent a significant improvement over previous medical device <> description capabilities. -NOTE: A detailed description of this <> description information model is beyond the scope of this specification. Detailed information is available in the <> standard and other materials identified in <>. +NOTE: A detailed description of this <> description information model is beyond the scope of this specification. Detailed information is available in the <> standard and other materials identified in <>. [%noheader] [%autowidth] @@ -88,7 +88,7 @@ Future versions will include general discussion about how BICEPS-based content i The <> specification fully supports the private nomenclature extensions as defined in <>. Additionally it supports integration of other non-<> terminology systems. -See <> for additional details. +See <> for additional details. // 8.3.2. [#vol3_clause_system_type_nomenclature_extensions] @@ -206,7 +206,7 @@ This includes OIDs for private codes as detailed in < [%autowidth] [cols="1"] |=== -a| *{supplement_note}*: The <> standards community is evaluating the use of safety class elements in the BICEPS specification (see <>), and the related https://github.com/IHE/DEV.SDPi/issues/11[Github Issue #11 _Topic: SDPi-xC with Mixed Device Safety Classes_]. +a| *{supplement_note}*: The <> standards community is evaluating the use of safety class elements in the BICEPS specification (see <>), and the related https://github.com/IHE/DEV.SDPi/issues/11[Github Issue #11 _Topic: SDPi-xC with Mixed Device Safety Classes_]. The result of that discussion will directly impact the BICEPS SES Considerations Section below. For this version of the specification, the following wording has been suggested: @@ -254,7 +254,7 @@ However, the fundamental rules are: Do not use a proprietary extension if the pu The borders of using extension are given by: -* <> Clause 8, especially R0109, and +* <> Clause 8, especially R0109, and * <> Clause 6.7 There are two kinds of extensions, those the <> must understand to perform system functions safely with the <>, and those the <> does not have to understand. diff --git a/asciidoc/volume3/tf3-ch-a-xml-schemas.adoc b/asciidoc/volume3/tf3-ch-a-xml-schemas.adoc index e2d904bd..32789ee5 100644 --- a/asciidoc/volume3/tf3-ch-a-xml-schemas.adoc +++ b/asciidoc/volume3/tf3-ch-a-xml-schemas.adoc @@ -1,7 +1,7 @@ [appendix#vol3_appendix_a_xml_schemas,sdpi_offset=A] == BICEPS Extension Provisions XML Schemas -XML Schemas in this appendix include the BICEPS message, participant and extension Model files as provided as an additional resource at https://standards.ieee.org/ieee/11073-10207/6032/. +XML Schemas in this appendix include the BICEPS message, participant and extension Model files as provided as an additional resource at https://standards.ieee.org/downloads/. include::biceps-extension-provisions/tf3-ch-a-xml-schemas-coded-attribute.adoc[] From 4079078600a9545fb1b0e6172d7d0fc9b0097684 Mon Sep 17 00:00:00 2001 From: Javier Espina <47562907+JavierEspina@users.noreply.github.com> Date: Thu, 30 Jul 2026 16:10:18 +0200 Subject: [PATCH 2/8] Update asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc --- .../tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc b/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc index 1a069e50..4fa929a4 100644 --- a/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc +++ b/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc @@ -1,4 +1,4 @@ -// Standard Conformance Statement: IEEE 11073-10207-2017/Cor 1-2025 +// Standard Conformance Statement: IEEE 11073-10207:2025 ==== ISO/IEC 11073-10207 BICEPS ICS Tables From bc4141f2d579c0792bdd0528f7bbabd13fcdee49 Mon Sep 17 00:00:00 2001 From: Javier Espina <47562907+JavierEspina@users.noreply.github.com> Date: Thu, 30 Jul 2026 16:10:53 +0200 Subject: [PATCH 3/8] Update asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc --- asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc b/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc index 91055bb0..322fd25b 100644 --- a/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc +++ b/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc @@ -42,7 +42,7 @@ No content from those three standards - including their requirements - is norma * [[[ref_ieee_11073_10201_2004,IEEE 11073-10201:2004]]] IEEE 11073-10201™ International Standard - Health informatics--Device interoperability--Part 10201:Point-of-care medical device communication--Domain information model. Note this was updated in 2020. Available at https://standards.ieee.org/ieee/11073-10201/10263/. -* [[[ref_ieee_11073_10207_2017_Cor1_2025,IEEE 11073-10207-2017/Cor 1-2025]]] IEEE 11073-10207-2017/Cor 1-2025, Health informatics — Point-of-care medical device communication — Part 10207: Domain Information and Service Model for Service-Oriented Point-of-Care Medical Device Communication Corrigendum 1, 2025-12, available at https://standards.ieee.org/ieee/11073-10207-2017_Cor_1/11316/ footnote:ieee_permission[]. +* [[[ref_ieee_11073_10207_2017_Cor1_2025,IEEE 11073-10207:2025]]] IEEE 11073-10207-2017/Cor 1-2025, Health informatics — Point-of-care medical device communication — Part 10207: Domain Information and Service Model for Service-Oriented Point-of-Care Medical Device Communication Corrigendum 1, 2025-12, available at https://standards.ieee.org/ieee/11073-10207-2017_Cor_1/11316/ footnote:ieee_permission[]. * [[[ref_ieee_11073_10700_2022,IEEE 11073-10700:2022]]] IEEE 11073-10700™ IEEE Standard -- Health Informatics--Device Interoperability Part 10700: Point‐of‐Care Medical Device Communication--Standard for Base Requirements for Participants in a Service‐Oriented Device Connectivity (SDC) System, available at https://standards.ieee.org/ieee/11073-10700/10630/. From ac86cf7a73cee63f115acc5525be594fd3dee290 Mon Sep 17 00:00:00 2001 From: Javier Espina <47562907+JavierEspina@users.noreply.github.com> Date: Thu, 30 Jul 2026 16:11:03 +0200 Subject: [PATCH 4/8] Update asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc --- asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc b/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc index 322fd25b..17488b23 100644 --- a/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc +++ b/asciidoc/volume1/tf1-ch-b-ref-standards-conformance.adoc @@ -125,7 +125,7 @@ a| *{supplement_note}*: This section intentionally left blank for the current v #TODO: Provide a general overview of the topic, including some standards that provide Conformity statements, ICS tables, etc., and those that are moot on the topic - and how all of this is handled in this appendix and TF specification# //// -// IEEE 11073-10207-2017/Cor 1-2025 ICS +// IEEE 11073-10207:2025 ICS include::conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc[] From 85889a552827bfb425c2b6b08bb49717f4279a71 Mon Sep 17 00:00:00 2001 From: JavierEspina Date: Thu, 30 Jul 2026 16:37:34 +0200 Subject: [PATCH 5/8] Updated file name and title of BICEP ICS file --- ...-conformance-statement-ieee-11073-10207-2017-Cor1-2025.adoc} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename asciidoc/volume1/conformance-statements/{tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc => tf1-ch-c-conformance-statement-ieee-11073-10207-2017-Cor1-2025.adoc} (97%) diff --git a/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc b/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017-Cor1-2025.adoc similarity index 97% rename from asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc rename to asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017-Cor1-2025.adoc index 4fa929a4..f7bd7e1c 100644 --- a/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017.adoc +++ b/asciidoc/volume1/conformance-statements/tf1-ch-c-conformance-statement-ieee-11073-10207-2017-Cor1-2025.adoc @@ -1,6 +1,6 @@ // Standard Conformance Statement: IEEE 11073-10207:2025 -==== ISO/IEC 11073-10207 BICEPS ICS Tables +==== ISO/IEC 11073-10207/Cor1-2025 BICEPS ICS Tables [%noheader] [%autowidth] From 1631d473635fa87044e2cd841d75b765b50d42fe Mon Sep 17 00:00:00 2001 From: JavierEspina Date: Thu, 30 Jul 2026 17:02:02 +0200 Subject: [PATCH 6/8] Updated changelog for issue 485 (plus a few editorials on other issues) --- CHANGELOG.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index a6658d56..5382a8bf 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -18,12 +18,12 @@ Each section shall contain a list of action items of the following format: ` Date: Thu, 30 Jul 2026 17:57:49 +0200 Subject: [PATCH 7/8] Deprecated requirements R1007, R1008, R1009, R1011, R0503, R0504, R0505, R0506, R0507, R0508, R1012 and R1013 --- asciidoc/volume2/dev-33/tf2-dev-33.adoc | 26 +++++++- .../volume2/qnames/tf2-ch-a-mdpws-qnames.adoc | 62 ++++++++++--------- .../tf3-ch-8.3.2.9-mdib-report-retrofit.adoc | 16 +++++ 3 files changed, 74 insertions(+), 30 deletions(-) diff --git a/asciidoc/volume2/dev-33/tf2-dev-33.adoc b/asciidoc/volume2/dev-33/tf2-dev-33.adoc index 6b40cbbc..b01b1425 100644 --- a/asciidoc/volume2/dev-33/tf2-dev-33.adoc +++ b/asciidoc/volume2/dev-33/tf2-dev-33.adoc @@ -118,6 +118,9 @@ The {var_label_dev_33_message_getlocalizedtext} message is sent whenever a <> sends this message, the receiving <> responds with a <> message. +//R0503 deprecated as it is superseded by new BICEPS R0261 +DeprecateRequirement::R0503[version="2.5.0"] +//// .R0503 [sdpi_requirement#r0503,sdpi_req_level=shall,sdpi_req_type=tech_feature] **** @@ -131,7 +134,11 @@ A <> shall respond to a {var_label_dev_33 The filtering of localized texts sets is specified by <>, <>, <>, <>, and <>. ==== **** +//// +//R0504 deprecated as it is superseded by new BICEPS R0250 +DeprecateRequirement::R0504[version="2.5.0"] +//// .R0504 [sdpi_requirement#r0504,sdpi_req_level=shall,sdpi_req_type=tech_feature] **** @@ -143,7 +150,11 @@ A <> shall select a set of localized text - If no <> is given, the set contains all localized texts ==== **** +//// +//R0505 deprecated as it is superseded by new BICEPS R0248 +DeprecateRequirement::R0505[version="2.5.0"] +//// .R0505 [sdpi_requirement#r0505,sdpi_req_level=shall,sdpi_req_type=tech_feature] **** @@ -156,7 +167,11 @@ A <> shall select a set of localized text - If <> is not specified, then the latest version of localized texts are added to the set ==== **** +//// +//R0506 deprecated as it is superseded by new BICEPS R0249 +DeprecateRequirement::R0506[version="2.5.0"] +//// .R0506 [sdpi_requirement#r0506,sdpi_req_level=shall,sdpi_req_type=tech_feature] **** @@ -168,7 +183,11 @@ A <> shall select a set of localized text - If no <> is given, the set contains all localized texts ==== **** +//// +//R0507 deprecated as it is superseded by new BICEPS R0238 +DeprecateRequirement::R0507[version="2.5.0"] +//// .R0507 [sdpi_requirement#r0507,sdpi_req_level=shall,sdpi_req_type=tech_feature] **** @@ -180,7 +199,11 @@ A <> shall select a set of localized text - If no <> is given, the set contains all localized texts ==== **** +//// +//R0508 deprecated as it is superseded by new BICEPS R0239 +DeprecateRequirement::R0508[version="2.5.0"] +//// .R0508 [sdpi_requirement#r0508,sdpi_req_level=shall,sdpi_req_type=tech_feature] **** @@ -192,6 +215,7 @@ A <> shall select a set of localized text - If no <> is given, the set contains all localized texts ==== **** +//// // ---------- GetLocalizedTextResponse --------- @@ -211,7 +235,7 @@ The {var_label_dev_33_message_getlocalizedtextresponse} message is sent whenever [#vol2_clause_dev_33_message_getlocalizedtextresponse_semantics] ====== Message Semantics -[[payload_dev_33_getlocalizedtextresponse_text]]Text:: The sequence of filtered localized texts, based on <>. +[[payload_dev_33_getlocalizedtextresponse_text]]Text:: The sequence of filtered localized texts. [#vol2_clause_dev_33_message_getlocalizedtextresponse_expected_actions] ====== Expected Actions diff --git a/asciidoc/volume2/qnames/tf2-ch-a-mdpws-qnames.adoc b/asciidoc/volume2/qnames/tf2-ch-a-mdpws-qnames.adoc index 05ada98d..d8403f75 100644 --- a/asciidoc/volume2/qnames/tf2-ch-a-mdpws-qnames.adoc +++ b/asciidoc/volume2/qnames/tf2-ch-a-mdpws-qnames.adoc @@ -1,29 +1,33 @@ -==== Processing of QNames - -<>s are problematic when used in XML element content or attribute values (see <>). -Unfortunately, the BICEPS Participant and Message Model as well some Web Services standards that are normatively referenced by <>, use <>s in XML element content or attribute values. - -In order to increase interoperability between implementations of this profile, this section specifies requirements towards <> handling in XML instances. - -.R1012 -[sdpi_requirement#r1012,sdpi_req_level=shall,sdpi_req_type=tech_feature] -**** - -[NORMATIVE] -==== -A <> shall resolve the namespace of a prefixed <> in XML attribute values and content of elements to the namespace that is associated with its prefix and is valid for the smallest element, which encloses the <>, by XML content. -==== - -**** - -.R1013 -[sdpi_requirement#r1013,sdpi_req_level=shall,sdpi_req_type=tech_feature] -**** - -[NORMATIVE] -==== -A <> shall resolve the namespace of an unprefixed <> in XML attribute values and content of elements to the default namespace that is valid for the smallest element, which encloses the <>, by XML content. -==== - -**** - +==== Processing of QNames + +NOTE: This section was deprecated in SDPi 2.5.0 as it was no longer needed. It is kept for keeping section numbers unaltered. + +//R1012 deprecated as it is superseded by new BICEPS R0214 +DeprecateRequirement::R1012[version="2.5.0"] +//// +.R1012 +[sdpi_requirement#r1012,sdpi_req_level=shall,sdpi_req_type=tech_feature] +**** + +[NORMATIVE] +==== +A <> shall resolve the namespace of a prefixed <> in XML attribute values and content of elements to the namespace that is associated with its prefix and is valid for the smallest element, which encloses the <>, by XML content. +==== + +**** +//// + +//R1013 deprecated as it is superseded by new BICEPS R0215 +DeprecateRequirement::R1013[version="2.5.0"] +//// +.R1013 +[sdpi_requirement#r1013,sdpi_req_level=shall,sdpi_req_type=tech_feature] +**** + +[NORMATIVE] +==== +A <> shall resolve the namespace of an unprefixed <> in XML attribute values and content of elements to the default namespace that is valid for the smallest element, which encloses the <>, by XML content. +==== + +**** +//// diff --git a/asciidoc/volume3/mdib-report-retrofit/tf3-ch-8.3.2.9-mdib-report-retrofit.adoc b/asciidoc/volume3/mdib-report-retrofit/tf3-ch-8.3.2.9-mdib-report-retrofit.adoc index 12d5f16e..8d137d1d 100644 --- a/asciidoc/volume3/mdib-report-retrofit/tf3-ch-8.3.2.9-mdib-report-retrofit.adoc +++ b/asciidoc/volume3/mdib-report-retrofit/tf3-ch-8.3.2.9-mdib-report-retrofit.adoc @@ -23,6 +23,9 @@ BICEPS does not specify the order in which report messages are sent to <> sequence and subscription, a <> there will be no two reports with the same <> version. Furthermore, it prohibits decrementing version numbers within an <> sequence. ==== **** +//// +//R1008 deprecated as it is superseded by new BICEPS R0212 +DeprecateRequirement::R1008[version="2.5.0"] +//// .R1008 [sdpi_requirement#r1008,sdpi_req_level=shall,sdpi_req_type=tech_feature] **** @@ -52,7 +59,11 @@ A <> shall not send msg:DescriptionModifi * DEPRECATION NOTICE - This requirement is being incorporated into the IEEE 11073-10207 BICEPS standard through a corrigendum. Once IEEE has published the IEEE 11073-10207 BICEPS Corrigenda, this SDPi requirement will be no longer needed, and will hence be removed. ==== **** +//// +//R1009 deprecated as it is superseded by new BICEPS R5025 +DeprecateRequirement::R1009[version="2.5.0"] +//// .R1009 [sdpi_requirement#r1009,sdpi_req_level=shall,sdpi_req_type=tech_feature] **** @@ -68,6 +79,7 @@ A <> shall order msg:DescriptionModificat * DEPRECATION NOTICE - This requirement is being incorporated into the IEEE 11073-10207 BICEPS standard through a corrigendum (albeit without the clarification note immediately above). Once IEEE has published the IEEE 11073-10207 BICEPS Corrigenda, this SDPi requirement will be no longer needed, and will hence be removed. ==== **** +//// ====== Corrigenda @@ -87,6 +99,9 @@ Replaces biceps:R5024: "Descriptors in this list SHALL not include nested descri ==== **** +//R1011 deprecated as it is superseded by reworded BICEPS R5046 +DeprecateRequirement::R1011[version="2.5.0"] +//// Requirement <> replaces biceps:R5046. .R1011 @@ -104,3 +119,4 @@ A <> shall communicate a parent descripto * DEPRECATION NOTICE - This requirement is being incorporated into the IEEE 11073-10207 BICEPS standard through a corrigendum. Once IEEE has published the IEEE 11073-10207 BICEPS Corrigenda, this SDPi requirement will be no longer needed, and will hence be removed. ==== **** +//// From 2274551c98bef370b7f62dd8d1a192d72d5a61ee Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Thu, 30 Jul 2026 16:04:56 +0000 Subject: [PATCH 8/8] Fix invalid deprecated requirement reference in dev-33 --- asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc b/asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc index d85604d5..e99e600f 100644 --- a/asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc +++ b/asciidoc/volume2/dev-33/tf2-ch-a-mdpws-dev-33.adoc @@ -126,7 +126,7 @@ include::../dev-a-default-trigger-events.adoc[] ====== Message Semantics -`s12:Envelope/s12:Body/msg:GetLocalizedTextResponse/msg:Text`:: The filtered list of localized texts, see also <>. +`s12:Envelope/s12:Body/msg:GetLocalizedTextResponse/msg:Text`:: The filtered list of localized texts. :var_expected_actions_ref: <> include::../dev-a-default-expected-actions.adoc[] @@ -143,4 +143,3 @@ In such cases, it is recommended that the requesting <