openehr-technical  

Messages by Thread

• • 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 吕旭东
  • Re: Archetype relational mapping - a practical openEHR persistence solution Bert Verhees
  • Re: Archetype relational mapping - a practical openEHR persistence solution 吕旭东
• concept maps (Cmaps) for archetyping? Thomas Beale
• New EHRServer v0.5 and roadmap pablo pazos
  • Re: New EHRServer v0.5 and roadmap Thomas Beale
  • Re: New EHRServer v0.5 and roadmap Seref Arikan
  • RE: New EHRServer v0.5 and roadmap pablo pazos
  • RE: New EHRServer v0.5 and roadmap pablo pazos
  • RE: New EHRServer v0.5 and roadmap Koray Atalag
  • Re: New EHRServer v0.5 and roadmap Bert Verhees
  • RE: New EHRServer v0.5 and roadmap pablo pazos
  • RE: New EHRServer v0.5 and roadmap pablo pazos
  • Re: New EHRServer v0.5 and roadmap pazospablo
  • Re: New EHRServer v0.5 and roadmap pazospablo
• Specifications Committee meeting Feb 2016 - have your say Thomas Beale
• Trial of openEHR's own 'stackExchange' on the openEHR wiki Thomas Beale
  • RE: Trial of openEHR's own 'stackExchange' on the openEHR wiki Bakke, Silje Ljosland
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Bert Verhees
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Diego Boscá
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Bert Verhees
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Seref Arikan
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Thomas Beale
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Seref Arikan
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Bert Verhees
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Thomas Beale
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Thomas Beale
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Bert Verhees
  • Re: Trial of openEHR's own 'stackExchange' on the openEHR wiki Bert Verhees
• CAMSS assessment of openEHR Bakke, Silje Ljosland
  • Re: CAMSS assessment of openEHR Thomas Beale
  • RE: CAMSS assessment of openEHR Bakke, Silje Ljosland
  • Re: CAMSS assessment of openEHR Thomas Beale
  • RE: CAMSS assessment of openEHR Bakke, Silje Ljosland
  • Re: CAMSS assessment of openEHR Ian McNicoll
  • RE: CAMSS assessment of openEHR Bakke, Silje Ljosland
  • Re: CAMSS assessment of openEHR Ian McNicoll
  • RE: CAMSS assessment of openEHR Bakke, Silje Ljosland
  • RE: CAMSS assessment of openEHR Bakke, Silje Ljosland
  • Re: CAMSS assessment of openEHR Thomas Beale
  • Re: CAMSS assessment of openEHR Erik Sundvall
  • Re: CAMSS assessment of openEHR Thomas Beale
  • Re: CAMSS assessment of openEHR Ian McNicoll
  • Re: CAMSS assessment of openEHR Ian McNicoll
  • RE: CAMSS assessment of openEHR Bakke, Silje Ljosland
  • Re: CAMSS assessment of openEHR Ian McNicoll
  • SV: CAMSS assessment of openEHR Erik Sundvall
  • RE: CAMSS assessment of openEHR Koray Atalag
• some differences between specs and implementation Bert Verhees
  • Re: some differences between specs and implementation Bert Verhees
• Making FHIR work for everybody Thomas Beale
• Medication Order archetype review open Heather Leslie
• Specialization depth Bert Verhees
  • Re: Specialization depth Diego Boscá
  • Re: Specialization depth Bert Verhees
  • Re: Specialization depth Diego Boscá
  • Re: Specialization depth Bert Verhees
  • Re: Specialization depth David Moner
  • Re: Specialization depth Bert Verhees
  • Re: Specialization depth Diego Boscá
  • Re: Specialization depth Bert Verhees
  • Re: Specialization depth Bert Verhees
  • Re: Specialization depth Thomas Beale
  • Re: Specialization depth Bert Verhees
  • Re: Specialization depth Thomas Beale
  • Re: Specialization depth Thomas Beale
  • Re: Specialization depth Diego Boscá
  • Re: Specialization depth Bert Verhees
  • Re: Specialization depth Thomas Beale
  • Re: Specialization depth Bert Verhees
  • Re: Specialization depth Thomas Beale
  • Re: Specialization depth Bert Verhees
• RE: openEHR-technical Digest, Vol 46, Issue 1 Culley Dave
  • Re: openEHR-technical Digest, Vol 46, Issue 1 Bert Verhees
• errorhandling in AOM/ADLParser Bert Verhees
• ADL 1.4 specification - now in Asciidoctor format Thomas Beale
  • Re: ADL 1.4 specification - now in Asciidoctor format Ian McNicoll
• EHRServer v0.4 released pazospablo
  • Re: EHRServer v0.4 released Ian McNicoll
  • RE: EHRServer v0.4 released Koray Atalag
  • Re: EHRServer v0.4 released pazospablo
• Missing support for ISM_TRANSITION/transition in Archetype Editor and Template Designer Ivar Yrke
  • Re: Missing support for ISM_TRANSITION/transition in Archetype Editor and Template Designer Peter Gummer
  • Re: Missing support for ISM_TRANSITION/transition in Archetype Editor and Template Designer Ian McNicoll
  • RE: Missing support for ISM_TRANSITION/transition in Archetype Editor and Template Designer Heath Frankel
• Party-actor-folder relationships in hierarchy Dmitry Baranov
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Dmitry Baranov
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Dmitry Baranov
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Dmitry Baranov
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Thomas Beale
  • RE: Party-actor-folder relationships in hierarchy Sebastian Garde
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Thomas Beale
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Peter Gummer
  • Re: Party-actor-folder relationships in hierarchy Ian McNicoll
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Thomas Beale
  • Re: Party-actor-folder relationships in hierarchy Dmitry Baranov
  • Re: Party-actor-folder relationships in hierarchy pazospablo
  • Re: Party-actor-folder relationships in hierarchy Dmitry Baranov
  • RE: Party-actor-folder relationships in hierarchy pablo pazos
  • Re: Party-actor-folder relationships in hierarchy pazospablo
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Birger Haarbrandt
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Bert Verhees
  • Re: Party-actor-folder relationships in hierarchy Ian McNicoll
• openEHR RM Release-1.0.3 - EHR Extract - SURVEY OF USE Thomas Beale
• Adverse reaction archetype... just published Heather Leslie
  • Re: Adverse reaction archetype... just published Ian McNicoll
  • Re: Adverse reaction archetype... just published Bert Verhees
  • Re: Adverse reaction archetype... just published Ian McNicoll
  • Re: Adverse reaction archetype... just published Bert Verhees
  • Re: Adverse reaction archetype... just published Ian McNicoll
  • RE: Adverse reaction archetype... just published Sam Heard
• Maven Archetype – About Koray Atalag
  • RE: Maven Archetype – About pablo pazos
• Jack Rabbit Bert Verhees
  • Re: Jack Rabbit Subhrajyoti Moitra
  • Re: Jack Rabbit Bert Verhees
  • Re: Jack Rabbit Bert Verhees
• OPT2 specification, choosing terminology bindings... Thomas Beale
  • Re: OPT2 specification, choosing terminology bindings... Thomas Beale
• Binding to multiple terminologies / code systems Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE)
  • Re: Binding to multiple terminologies / code systems Dmitry Baranov
  • Re: Binding to multiple terminologies / code systems Thomas Beale
  • Re: Binding to multiple terminologies / code systems Ian McNicoll
  • Re: Binding to multiple terminologies / code systems Heath Frankel
  • Re: Binding to multiple terminologies / code systems Thomas Beale
  • RE: Binding to multiple terminologies / code systems Barnet David (HEALTH AND SOCIAL CARE INFORMATION CENTRE)
  • Re: Binding to multiple terminologies / code systems Thomas Beale
• OS licences - CC-BY-SA 4 compatible with GPLv3 Thomas Beale
• Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Shinji KOBAYASHI
  • RE: Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Nadim Anani
  • Re: Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Ricardo Correia
  • Re: Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Gunnar Klein
  • RE: Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Rong Chen
  • Re: Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Ian McNicoll
  • RE: Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Heather Leslie
  • Re: Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Seung Jong Yu
  • Re: Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Shinji KOBAYASHI
  • RE: [FORGED] Nation wide EHR project by openEHR/ISO13606 got fund in Japan. Koray Atalag
• New adl-antlr GitHub project Thomas Beale
  • Re: New adl-antlr GitHub project Bert Verhees
• CKM feature request - bulk export of archetypes in XML format Dmitry Baranov
  • Re: CKM feature request - bulk export of archetypes in XML format Peter Gummer
  • Re: CKM feature request - bulk export of archetypes in XML format Dmitry Baranov
  • Re: CKM feature request - bulk export of archetypes in XML format Sebastian Garde
• Archetype publication question - implications for implementers Heather Leslie
  • Re: Archetype publication question - implications for implementers Sebastian Garde
  • Re: Archetype publication question - implications for implementers Diego Boscá
  • Re: Archetype publication question - implications for implementers Sebastian Garde
  • Re: Archetype publication question - implications for implementers Ian McNicoll
  • SV: Archetype publication question - implications for implementers Mikael Nyström
  • Re: Archetype publication question - implications for implementers Thomas Beale
  • RE: Archetype publication question - implications for implementers Heather Leslie
  • Re: Archetype publication question - implications for implementers David Moner
  • Re: Archetype publication question - implications for implementers Thomas Beale
  • Re: Archetype publication question - implications for implementers Ian McNicoll
  • RE: Archetype publication question - implications for implementers Heather Leslie
  • Re: Archetype publication question - implications for implementers Thomas Beale
  • Re: Archetype publication question - implications for implementers David Moner
  • RE: Archetype publication question - implications for implementers Bjørn Næss
  • Re: Archetype publication question - implications for implementers [ long ] Eric Browne
  • Re: Archetype publication question - implications for implementers [ long ] Thomas Beale
  • Re: Archetype publication question - implications for implementers [ long ] Grahame Grieve
  • Re: Archetype publication question - implications for implementers [ long ] Thomas Beale
  • Re: Archetype publication question - implications for implementers Thomas Beale
  • Re: Archetype publication question - implications for implementers Ian McNicoll
  • RE: Archetype publication question - implications for implementers Mikael Nyström
  • RE: Archetype publication question - implications for implementers Heather Leslie
  • RE: Archetype publication question - implications for implementers Heath Frankel
  • RE: Archetype publication question - implications for implementers Diego Boscá
  • Re: Archetype publication question - implications for implementers David Moner
  • Re: Archetype publication question - implications for implementers Heath Frankel
  • Re: Archetype publication question - implications for implementers Ian McNicoll
  • Re: Archetype publication question - implications for implementers Heath Frankel
  • RE: Archetype publication question - implications for implementers Heather Leslie
  • Re: Archetype publication question - implications for implementers Diego Boscá
  • RE: Archetype publication question - implications for implementers Heather Leslie
  • RE: Archetype publication question - implications for implementers Heather Leslie
• SNOMED CT constraint syntax - for querying instances or terminology? Thomas Beale
  • Re: SNOMED CT constraint syntax - for querying instances or terminology? Michael.Lawley
  • Re: SNOMED CT constraint syntax - for querying instances or terminology? Thomas Beale
  • Re: SNOMED CT constraint syntax - for querying instances or terminology? Michael.Lawley
  • Re: SNOMED CT constraint syntax - for querying instances or terminology? Thomas Beale
  • Re: SNOMED CT constraint syntax - for querying instances or terminology? Bert Verhees
  • Re: SNOMED CT constraint syntax - for querying instances or terminology? David Moner
  • Re: SNOMED CT constraint syntax - for querying instances or terminology? Michael.Lawley
• openEHR and IHTSDO (SNOMED CT) Mikael Nyström

• Earlier messages
• Later messages