Pharm Tech Minutes 2010.06.07-08: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Simon.letellier (talk | contribs)
Simon.letellier (talk | contribs)
Line 60: Line 60:
Introduce administration report send to Pharmaceutical adviser to inform pharmacist (human actor) which medications are really administer to the patient.
Introduce administration report send to Pharmaceutical adviser to inform pharmacist (human actor) which medications are really administer to the patient.


Discussion on "medication aviability" ==> it's the dispense report
It's what needed for cabinet management.


Check the IHE's "Security Cookbook" for security issues


Looking for a common master Model for HMW.
Looking for a common Master Model for HMW.
 
 
 
   
   
Start about CPMD   
Start about CPMD   

Revision as of 10:07, 7 June 2010

Day 1 : Monday : HMW profile development

Work on the Technical Framework :

- volume 1 Integration profiles & volume 2 Transactions



JB introduce the structure of the TF documents

3 parts

table 1 is very important : link Volume 1 and Volume 2 , the detailled transactions.

8 transactions [PHARM-1] to [PHARM-8]

Transactions can be used by ( max. 7 ) differents actors.

1) CMPD discussion

Introduce the new actor Pharmacy document registry :

Glue together repository and registry.

XDS is eb-XML

Define the interface of the interface for the PR (prescription repository) if it's possible to query a "black box" : XDS or something else like a DB (database)

Blackbox have to support the complexity , to know how and where integrate datas.

Interfaces are the crucial point.

Registries are in a repository. Interface (XDS based or not) is at the entry of the repository.

Registries are databases.

Labelleing the document ? in order to do it (pharmaceutical advise) validated. Use status on prescription document.

Link between the different items ?

HWM

Status on documents are not necessary : messages based. Status are implicit. Messages are not send until validation, change of status in the workflow.

Postscription : prescription after administration use case usefull for Pyxis cabinet in ICU not present in the White Paper.

Addition of OMS : HL7v2 message request for refill cabinets. Not necessary against business /stock refill rules. Define triggers !

trigger from nurse report (stock order) Something the pharmacy already known the stock levels ans the needs for the next weeks (based on prescriptions).

Introduce administration report send to Pharmaceutical adviser to inform pharmacist (human actor) which medications are really administer to the patient.

Discussion on "medication aviability" ==> it's the dispense report It's what needed for cabinet management.

Check the IHE's "Security Cookbook" for security issues

Looking for a common Master Model for HMW.

Start about CPMD - volume 3 Content Specifications

Discussion about page 13 of TF volume 3

Management of medication items inside each prescription:

how pharmaceutical advisor validate the prescription items links between prescription, pharmaceutical advise and dispense.

Looking for ITI specifications

Day 2 : Tuesday : CMPD profile development

Work on the Technical Framework :

- volume 1 Integration profiles

- volume 2 Transactions

- volume 3 Content Specifications

IHE Pharmacy Planning committee

- Roadmap

- Communications

- IHE 2010 webinars serie