IHE Supply white paper Process for cross-domain case capture and analysis

Why? This is a broad topic. A process helps distribute the discussion and work. We want to ensure other domains contribute and relate to our findings Collaboration across SDOs should be traced to a common, non-technical ground

Process summary 1.Describe the domain and the problem to solve 2.Identify High-level directives (Business requirements) 3.Expose Use Cases 4.Each use case may bring new requirements (functional/technical) 5.Trace and reconcile all requirements 6.Include risk management

Business Requirements Should be attended in any implementation, but are not implementable in itself

Use Cases Structure: – Summary – Preconditions – Steps – (sequence diagram) – Requirements

Use Case Summary and preconditions

Steps description A verbal description of the scenario

Sequence Diagram (source is included in the document)

Requirements For each case, the newly introduced requirements are listed. Requirements can be: – New interoperability mechanisms – New data that must be included in an interface

Risks In the writing, a new topic emerged: how to deal with risks. Example and approach:

Use case scope There is a very broad scope, but an expected functional overlap. Examples: – Registering the use of a medication is similar to registering the use of a device Except for payload/... – Ordering a medication resupply from a vendor could have the same flow as resupply of devices Unless a use case shows otherwise – Informing about the medication dispense should be the same for traceable or non-traceable items The use cases do not need to be repeated in all detail, only the differences

Approach Have an initial section of “detailed” use cases New use cases can be summarized if they are similar to existing ones.

Additional use cases

Evolution We have created sections for – Automated systems – Radiology – Operating Theater.. – (more can be created) Invite other domains and groups to contribute with their use cases. – A short description is enough. – Put as many functional details as you want, leave the analysis for a joint discussion

IHE Supply white paper Status and goals

Introduction to topic and key concepts – Process and players – Product types and physical items – Packaging, product identification – Traceability levels – AIDC (Barcodes and RFIDs)

Use cases – Hospital medication (several variants) Clinical flows (Re)supply flows – Ordered vs non-ordered – Consignment – Community resupply – Other care institutions – Inventory management – Traceability –... Use Cases and variations

Invite other domains to review content and add use cases – Radiology – Operating Theater Invite other contributions – Automated systems Next steps

Interoperabiity – HL7 v2 Some issues – GS1 Must update IHE template – FHIR Alignment needed AIDC – GS1 – now we have a better rationale Profile standards

With other IHE groups With HL7 and GS1 Prepare new domain? Joint discussions