openehr-technical  

Messages by Thread

• • Re: Activity based workflow - request for literature & resources Subhrajyoti Moitra
  • Re: Activity based workflow - request for literature & resources Thomas Beale
  • Re: Activity based workflow - request for literature & resources Klaus Veil
  • Re: Activity based workflow - request for literature & resources Thomas Beale
  • Re: Activity based workflow - request for literature & resources Diego Boscá
  • Re: Activity based workflow - request for literature & resources Diego Boscá
• EC EXPERT PANEL ON EFFECTIVE WAYS OF INVESTING IN HEALTH - Disruptive innovation - openEHR comments Thomas Beale
  • Re: EC EXPERT PANEL ON EFFECTIVE WAYS OF INVESTING IN HEALTH - Disruptive innovation - openEHR comments Ian McNicoll
• AOM C_STRING - single regex, or a list of strings? Thomas Beale
  • Re: AOM C_STRING - single regex, or a list of strings? Diego Boscá
  • Re: AOM C_STRING - single regex, or a list of strings? Thomas Beale
  • Re: AOM C_STRING - single regex, or a list of strings? Bert Verhees
  • Re: AOM C_STRING - single regex, or a list of strings? Diego Boscá
  • Re: AOM C_STRING - single regex, or a list of strings? Thomas Beale
  • Re: AOM C_STRING - single regex, or a list of strings? Diego Boscá
  • Re: AOM C_STRING - single regex, or a list of strings? Thomas Beale
  • Re: AOM C_STRING - single regex, or a list of strings? Bert Verhees
  • Re: AOM C_STRING - single regex, or a list of strings? Bert Verhees
  • Re: AOM C_STRING - single regex, or a list of strings? Thomas Beale
  • Re: AOM C_STRING - single regex, or a list of strings? Bert Verhees
  • Re: AOM C_STRING - single regex, or a list of strings? Thomas Beale
  • Re: AOM C_STRING - single regex, or a list of strings? Bert Verhees
  • Re: AOM C_STRING - single regex, or a list of strings? Thomas Beale
• Composition commit and change types pazospablo
  • Re: Composition commit and change types Karsten Hilbert
  • Re: Composition commit and change types Bert Verhees
  • Re: Composition commit and change types Ian McNicoll
  • Re: Composition commit and change types pazospablo
  • Re: Composition commit and change types Ian McNicoll
  • Re: Composition commit and change types pazospablo
  • Re: Composition commit and change types Ian McNicoll
  • Re: Composition commit and change types pazospablo
  • Re: Composition commit and change types Ian McNicoll
  • RE: Composition commit and change types pablo pazos
  • Re: Composition commit and change types Ian McNicoll
  • Re: Composition commit and change types Heath Frankel
  • RE: Composition commit and change types pablo pazos
  • RE: Composition commit and change types Heath Frankel
  • RE: Composition commit and change types pablo pazos
  • Re: Composition commit and change types Thomas Beale
  • Re: Composition commit and change types pazospablo
  • Re: Composition commit and change types Thomas Beale
  • RE: Composition commit and change types pablo pazos
  • Re: Composition commit and change types Ian McNicoll
  • RE: Composition commit and change types pablo pazos
• Re: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Daniel Curto-Millet
  • Re: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Thomas Beale
• Adressing of i.e. discharge summaries Bjørn Næss
  • RE: Adressing of i.e. discharge summaries Heath Frankel
  • RE: Adressing of i.e. discharge summaries Heather Leslie
  • Re: Adressing of i.e. discharge summaries Thomas Beale
• rm_type_name for the DV_DURATIONs primitive object in XML Sebastian Garde
  • Re: rm_type_name for the DV_DURATIONs primitive object in XML Boštjan Lah
  • Re: rm_type_name for the DV_DURATIONs primitive object in XML Diego Boscá
  • RE: rm_type_name for the DV_DURATIONs primitive object in XML Sebastian Garde
  • Re: rm_type_name for the DV_DURATIONs primitive object in XML Diego Boscá
  • Re: rm_type_name for the DV_DURATIONs primitive object in XML Boštjan Lah
  • Re: rm_type_name for the DV_DURATIONs primitive object in XML Heath Frankel
  • RE: rm_type_name for the DV_DURATIONs primitive object in XML Sebastian Garde
  • Re: rm_type_name for the DV_DURATIONs primitive object in XML Gerard Freriks (privé)
  • Re: rm_type_name for the DV_DURATIONs primitive object in XML pazospablo
  • RE: rm_type_name for the DV_DURATIONs primitive object in XML Sebastian Garde
  • RE: rm_type_name for the DV_DURATIONs primitive object in XML pablo pazos
• Re: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Thomas Beale
  • Re: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Bert Verhees
  • Re: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Ian McNicoll
  • Re: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Bert Verhees
  • RE: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Koray Atalag
  • SV: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Bjørn Næss
  • Re: SV: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals Bert Verhees
• openEHR-Based PhD Thesis Successfully Defended Nadim Anani
  • Re: openEHR-Based PhD Thesis Successfully Defended Diego Boscá
  • Re: openEHR-Based PhD Thesis Successfully Defended Jan-Marc Verlinden
  • Re: openEHR-Based PhD Thesis Successfully Defended Hildegard Franke
  • RE: openEHR-Based PhD Thesis Successfully Defended Koray Atalag
  • RE: openEHR-Based PhD Thesis Successfully Defended Nadim Anani
  • RE: openEHR-Based PhD Thesis Successfully Defended Nadim Anani
  • Re: openEHR-Based PhD Thesis Successfully Defended Grahame Grieve
• Any work on PHR? Koray Atalag
  • Re: Any work on PHR? Ian McNicoll
  • RE: Any work on PHR? pablo pazos
  • SV: Any work on PHR? Mikael Nyström
  • Re: Any work on PHR? Mate Beštek
• GDL rules with "age-dependent" reference ranges Birger Haarbrandt
  • RE: GDL rules with "age-dependent" reference ranges Rong Chen
• Template Designer alternatives pablo pazos
  • Re: Template Designer alternatives Diego Boscá
  • RE: Template Designer alternatives pablo pazos
  • RE: Template Designer alternatives Heath Frankel
  • RE: Template Designer alternatives pablo pazos
• Usage of Compositoin.Category Bjørn Næss
  • SV: Usage of Compositoin.Category Bjørn Næss
  • RE: Usage of Compositoin.Category Heath Frankel
  • Re: Usage of Compositoin.Category Thomas Beale
  • SV: Usage of Compositoin.Category Bjørn Næss
  • Re: Usage of Compositoin.Category Ian McNicoll
  • SV: Usage of Compositoin.Category Bjørn Næss
  • RE: Usage of Compositoin.Category Ivar Yrke
  • Re: Usage of Compositoin.Category Thomas Beale
  • Re: Usage of Compositoin.Category Ian McNicoll
  • RE: Usage of Compositoin.Category Ivar Yrke
  • Re: Usage of Compositoin.Category Ian McNicoll
  • RE: Usage of Compositoin.Category Ivar Yrke
  • Re: Usage of Compositoin.Category Thomas Beale
  • SV: Usage of Compositoin.Category Bjørn Næss
  • Re: SV: Usage of Compositoin.Category Thomas Beale
  • SV: SV: Usage of Compositoin.Category Bjørn Næss
  • Re: SV: Usage of Compositoin.Category Thomas Beale
  • SV: SV: Usage of Compositoin.Category Bjørn Næss
  • Re: SV: SV: Usage of Compositoin.Category Thomas Beale
• Strange use of 'offset' as a settable RM attribute Koray Atalag
  • Re: Strange use of 'offset' as a settable RM attribute Ian McNicoll
  • Re: Strange use of 'offset' as a settable RM attribute Heath Frankel
  • Re: Strange use of 'offset' as a settable RM attribute Ian McNicoll
  • Re: Strange use of 'offset' as a settable RM attribute Heath Frankel
  • RE: Strange use of 'offset' as a settable RM attribute Koray Atalag
  • RE: Strange use of 'offset' as a settable RM attribute Sebastian Garde
  • Re: Strange use of 'offset' as a settable RM attribute Diego Boscá
  • RE: [FORGED] Re: Strange use of 'offset' as a settable RM attribute Koray Atalag
  • Re: [FORGED] Re: Strange use of 'offset' as a settable RM attribute Diego Boscá
  • Re: Strange use of 'offset' as a settable RM attribute Thomas Beale
  • RE: Strange use of 'offset' as a settable RM attribute Koray Atalag
  • Re: Strange use of 'offset' as a settable RM attribute Thomas Beale
  • Re: Strange use of 'offset' as a settable RM attribute Thomas Beale
• A report of openEHR events in Japan Shinji KOBAYASHI
  • Re: A report of openEHR events in Japan Ian McNicoll
  • RE: [FORGED] A report of openEHR events in Japan Koray Atalag
  • Re: A report of openEHR events in Japan Tomaž Gornik
• Updated XSLT pablo pazos
• Representing microseconds in DateTime Koray Atalag
  • Re: Representing microseconds in DateTime Bert Verhees
  • RE: [FORGED] Re: Representing microseconds in DateTime Koray Atalag
  • Re: [FORGED] Re: Representing microseconds in DateTime Bert Verhees
  • RE: [FORGED] Re: [FORGED] Re: Representing microseconds in DateTime Koray Atalag
  • RE: [FORGED] Re: [FORGED] Re: Representing microseconds in DateTime Koray Atalag
  • Re: Representing microseconds in DateTime Thomas Beale
  • RE: Representing microseconds in DateTime Koray Atalag
  • Re: Representing microseconds in DateTime Thomas Beale
  • Re: Representing microseconds in DateTime Diego Boscá
• EHRServer whitepaper pablo pazos
  • RE: EHRServer whitepaper pablo pazos
• Re: PhD Thesis online: Detailed clinical models and their relation with Electronic Health Records pazospablo
• PhD Thesis online: Detailed clinical models and their relation with Electronic Health Records Diego Boscá
  • Re: PhD Thesis online: Detailed clinical models and their relation with Electronic Health Records Carlos Luis Parra Calderón
  • RE: PhD Thesis online: Detailed clinical models and their relation with Electronic Health Records Nadim Anani
  • Re: PhD Thesis online: Detailed clinical models and their relation with Electronic Health Records Mate Beštek
  • Re: PhD Thesis online: Detailed clinical models and their relation with Electronic Health Records Jan-Marc Verlinden
  • Re: PhD Thesis online: Detailed clinical models and their relation with Electronic Health Records Ian McNicoll
• Re: RE: Archetype relational mapping - a practical openEHR persistence solution birger . haarbrandt
  • Re: RE: Archetype relational mapping - a practical openEHR persistence solution Erik Sundvall
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Birger Haarbrandt
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Birger Haarbrandt
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Birger Haarbrandt
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Karsten Hilbert
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Thomas Beale
  • Re: Archetype relational mapping - a practical openEHR persistence solution Seref Arikan
  • Re: Archetype relational mapping - a practical openEHR persistence solution Ian McNicoll
  • Re: Archetype relational mapping - a practical openEHR persistence solution Seref Arikan
  • Re: Archetype relational mapping - a practical openEHR persistence solution Thomas Beale
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Aw: Re: Archetype relational mapping - a practical openEHR persistence solution Karsten Hilbert
• Re: openEHR-technical Digest, Vol 47, Issue 31 [email protected]
• Re: openEHR-technical Digest, Vol 47, Issue 26 [email protected]
  • Re: openEHR-technical Digest, Vol 47, Issue 26 Birger Haarbrandt
• Archetype relational mapping - a practical openEHR persistence solution Ian McNicoll
  • Re: Archetype relational mapping - a practical openEHR persistence solution Dmitry Baranov
  • Re: Archetype relational mapping - a practical openEHR persistence solution Shinji KOBAYASHI
  • Re: Archetype relational mapping - a practical openEHR persistence solution 吕旭东
  • Re: Archetype relational mapping - a practical openEHR persistence solution Jan-Marc Verlinden
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Thomas Beale
  • Re: Archetype relational mapping - a practical openEHR persistence solution Jan-Marc Verlinden
  • Re: Archetype relational mapping - a practical openEHR persistence solution Thomas Beale
  • Re: Archetype relational mapping - a practical openEHR persistence solution Jan-Marc Verlinden
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Seref Arikan
  • Re: Archetype relational mapping - a practical openEHR persistence solution Jan-Marc Verlinden
  • Re: Archetype relational mapping - a practical openEHR persistence solution Seref Arikan
  • Re: Archetype relational mapping - a practical openEHR persistence solution Jan-Marc Verlinden
  • Re: Archetype relational mapping - a practical openEHR persistence solution Seref Arikan
  • Re: Archetype relational mapping - a practical openEHR persistence solution Jan-Marc Verlinden
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution 吕旭东
  • Re: Archetype relational mapping - a practical openEHR persistence solution pazospablo
  • Re: Archetype relational mapping - a practical openEHR persistence solution Thomas Beale
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution Birger Haarbrandt
  • RE: Archetype relational mapping - a practical openEHR persistence solution Mikael Nyström
  • RE: Archetype relational mapping - a practical openEHR persistence solution Birger Haarbrandt
  • RE: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • RE: Archetype relational mapping - a practical openEHR persistence solution pablo pazos
  • Re: Archetype relational mapping - a practical openEHR persistence solution Thomas Beale
  • RE: Archetype relational mapping - a practical openEHR persistence solution pablo pazos

• Earlier messages
• Later messages