Pharm Tech Minutes 2011.10.05: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Simon.letellier (talk | contribs)
Simon.letellier (talk | contribs)
Line 122: Line 122:
* glossary IHE.  
* glossary IHE.  


Doodle on the meeting places.
HL7                  IHE
Application Role    =    Actor
Interaction          =    Transaction

Revision as of 18:02, 8 October 2011

IHE Pharmacy & HL7 Pharmacy Joint Meeting

Attendees

  • Brandstätter, Jürgen (CodeWerk Software Services and Development GmbH)
  • Canu, Nicolas (Phast)
  • Cocchiglia, Arianna (Arsenal IT)
  • Costa Teixeira, Jose (AGFA)
  • De Jong, Tom (Nova Pro)
  • Demarmels, Marco (Lake Griffin, LLC)
  • Duteau, Jean-Henri (Gordon Point Informatics, HL7 Pharmacy)
  • Estelrich, Ana (Phast)
  • Gengler, Winfried (Epic)
  • Géraud, Thierry (CareFusion)
  • Gibaud, Isabelle (Syndicat Interhospitalier de Bretagne - SIB)
  • Glover, Hugh (Bluewave Informatics, HL7 Pharmacy)
  • Hatem, John (Oracle, HL7 Pharmacy)
  • James, Julie (Bluewave Informatics, HL7 Pharmacy)
  • Koelewijn, Gert (Nictiz, HL7 Pharmacy)
  • Lefebvre, Nicolas (INRIA)
  • Letellier, Simon (EAHP)
  • Liot, Pierre (HAS)
  • Mohammad, Mirojane (HAS)
  • Peters, Melva (HL7 Pharmacy)
  • Poiseau, Eric (INRIA)
  • Rica, Charles (ASIP Santé)
  • Robberecht, Marc (AGFA)
  • Robertson, Scott (Kaiser Permanente, HL7 Pharmacy)
  • Rodrigues, Orlando (Glintt - Heatlhcare Solutions, S.A)
  • Soley, Richard (OMG)
  • Sprenger, Michiel (Nictiz)
  • Surugue, Jacqueline (EAHP)
  • Costa Teixeira, Jose (AGFA)
  • Tzimis, Leonidas (EAHP)
  • Zalunardo, Luca (Arsenal IT)

By WebEx:

  • Bourquard, Karima (In-Systems)
  • Peytchev, Vassil (Epic)


Introductions, ambitions and timelines

Presentation of IHE Pharmacy

Jürgen : young domain, young working group, first profile in pharmacy last year.

General lines of the roadmap includes cross domain activity foreseen to be increased due to overlapping borderlines and complying to IHE Governance requirements.

Presentation of HL7 Pharmacy

Tom : HL7 25 years, resulting in HL7 v2 as the most used standard in hospitals. HL7 Headquarters in Michigan US, international scope. Technical steering committee, 40 Working Groups, some of them like Patient care with 6 cochairs. (Most groups have 2 co chairs, 3 in Pharmacy). See: http://www.hl7.org

All healthcare domains represented, based on healthcare sectors, but there is another domain CDA, which is just a methodology to structure the data, and is the most successful standard group, very popular as it should be implemented in all groups. Also Common Product Model, a overarching model, which is standardization within the standards.

Medication Documentation/Profile

Introductions

Tom :

The (virtual) medication profile (or medication documentation or whatever)

[ PPT ]

Nictiz: HL7 v3. It is the responsibility of the data host to make the data retrievable 24/24h.

Julie James

[ PPT ]

Medication profile: content? Location and length of storage, queries, ways information is retrieved and the structure under which they are reported

Discussion

IHE focus on process, HL7 the design

Common understanding, good balance, good hope for good progress together.

Supply chain

Thierry Gerault

summarizes the work done so far on the white paper on the supply chain: consideration focusing of the organisation behind, including stock availability

Centralized or decentralized systems as well as controlled drugs (narcotics). Question on the version of HL7 to be used: V2, but in the near future,V3?

Infusion administrations

Smart pump are just slaves – the dosage calculation according to patient’s weight should be done somewhere else.

Some already existing pumps are able to adjust on biological tests.

Infusion rate: when it varies, could each variation be considered as one administration?

Expression of substitution

  • in the prescription, the prescriber indicates the way it can be substituted
  • dispenser indicates the substitution operated

Cf: EPSOS

Workflow management

Business architecture issue to be determined Each content profile is neutral and real life. HL7: different, this is a role, if you query, this is the way you have to do. HL7 is building a tool.

Nicolas quoted the «  cadre d’interopérabilité publié par l’ASIP

Roadmap planning HL7 – IHE

productive, energetic meeting, synchronise once of twice a year just to be sure we stay aligned,

  • glossary HL7,
  • glossary health informatics glossary,
  • shared definition of terms,
  • glossary IHE.

HL7 IHE Application Role = Actor Interaction = Transaction