RE: AQL query for blood pressure from the AQL documentation

2019-05-02 Thread Bjørn Næss
quot;: "at0004", "name": { "value": "Systolisk" }, "value": { "_type": "DV_QUANTITY", "magnitude": 160.0, "units": "mm[Hg]" } } Vennlig hilse

RE: AQL questions

2019-04-26 Thread Bjørn Næss
EHR-CLUSTER.laboratory_test_panel.v1]" Which gives "c2" + "path" to be: "/content[openEHR-EHR-OBSERVATION.laboratory_test.v1]/data[at0001]/events[at0002]/data[at0003]/items[openEHR-EHR-CLUSTER.laboratory_test_panel.v1]/ /items[at0002]/items[at0001]/value/magnitude&quo

RE: AQL questions

2019-04-25 Thread Bjørn Næss
ype is to only query for Composition with the CLUSTER. Like this: SELECT e FROM EHR e CONTAINS COMPOSITION c CONTAINS CLUSTER c2[openEHR-EHR-CLUSTER.laboratory_test_panel.v1] LIMIT 10 Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10 -Origi

RE: AQL on specific list of compositions

2018-08-21 Thread Bjørn Næss
such that the COMPOSITION c MUST be referenced in FOLDER f and not any sub-folder. This was needed to avoid circular references and explosion in the result set. Vennlig hilsen Bjørn Næss Product owner DIPS ASA Mobil +47 93 43 29 10 From: openEHR-technical On Behalf Of Ian McNicoll Sent: mandag 20. august 2018 11

RE: information about allowable data in a openEHR format

2017-11-27 Thread Bjørn Næss
this Template you can create Compositions. Compositions are documents or transactions containing data into an openEHR system. There are several ways to serialize this data. Both JSON and XML are used in production systems today. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47

Re: AQL for multi-occurrence nodes

2017-11-03 Thread Bjørn Næss
I would also look at the ITS specification. https://github.com/openEHR/specifications-ITS/tree/master/REST_API There is a XSD there which defines some structures. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Opprinnelig melding Fra: Thomas Beale <thomas

RE:

2017-11-01 Thread Bjørn Næss
This is great work. Look forward to read the details. Congratulations! Sincerely Bjørn Næss Product Owner openEHR platform DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Ingram, Davi

How to use ACTION.procedure for Surgery Reports

2017-11-01 Thread Bjørn Næss
/C7U9JD1EK Sincerely Bjørn Næss Product Owner openEHR platform DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/o

RE: AQL for multi-occurrence nodes

2017-11-01 Thread Bjørn Næss
occurences to appear. Take a look at the examples given above. I would be happy to answer follow ups on this. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On

RE: Does aql support multiple ehrids?

2017-11-01 Thread Bjørn Næss
. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Dileep V S Sent: fredag 27. oktober 2017 11:52 To: For openEHR technical discussions <openehr-

Re: [openEHR SEC] CONTAINS in AQL

2017-10-01 Thread Bjørn Næss
for Folder navigate through object references. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Opprinnelig melding Fra: Ian McNicoll <ian.mcnic...@gmail.com> Dato: 01.10.2017 19:05 (GMT+01:00) Til: For openEHR technical discussions <openehr-technical@lists.op

RE: Using aql for data set in DV_CODED_TEXT

2017-07-05 Thread Bjørn Næss
Hi We have implemented this in the form based on the operational template. Then we put reuse information with AQL to query structures to be reused for different purposes. Works perfectly well :-) Regards Bjørn Næss Product owner Arena EHR DIPS ASA Mobil +47 93 43 29 10 -Original

Re: Random / Synthetic Data Generation over Templates

2017-05-03 Thread Bjørn Næss
. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Opprinnelig melding Fra: "Anastasiou A." <a.anastas...@swansea.ac.uk> Dato: 18.04.2017 11:46 (GMT+01:00) Til: For openEHR technical discussions <openehr-technical@lists.openehr.org> Emne: RE: Random / Syntheti

Re: Add SNOMED codes to values in Internal code set

2017-05-02 Thread Bjørn Næss
/EyeModule/FU%20-%20Synsfelt.oet Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Opprinnelig melding Fra: Dileep V S <dil...@healthelife.in> Dato: 15.04.2017 11:00 (GMT+01:00) Til: For openEHR technical discussions <openehr-technical@lists.openehr.org> Emne: Add

RE: SNOMEDCT - correct representation

2017-04-25 Thread Bjørn Næss
on openEHR archetypes. Thanks for the feedback from all of you! Vennlig hilsen Bjørn Næss Product owner DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> From: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] On Behalf Of Ian McNicoll Sent: tirsdag 25. apri

SNOMEDCT - correct representation

2017-04-24 Thread Bjørn Næss
18944008 Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> ___ openEHR-technical mailing list openEHR-technical@lists.opene

SV: better diagram for 'clinical investigator recording process'

2017-02-08 Thread Bjørn Næss
Great Thomas. I did a translation of this to Norwegian (attached). Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> Fra: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] På vegne av Thomas Beale Sendt: on

SV: Context in persistent COMPOSITION archetypes?

2017-01-18 Thread Bjørn Næss
Hi To the first question – technical: Is it possible to have context on a persistent composition? Yes – I think that should be possible. Some will argue that the context is an EVENT_CONTEXT and such context should only be used for event based Compositions. I think it makes sense to have some

SV: Use of RM:provider

2017-01-18 Thread Bjørn Næss
this requirement. If it is only national then there should be some extension slots in the Archetypes – or we need some specialization of the Archetype to handle this. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> Fra: openEHR-technical [mailto:o

SV: Could the specs group consider making uid mandatory?

2016-12-19 Thread Bjørn Næss
it breaks existing systems. Which also tells it is not needed since existing systems didn't need to use the optional UID. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Opprinnelig melding Fra: Thomas Beale <thomas.be...@openehr.org> Dato: 19.12.2016 02:07 (GMT+01:0

SV: Could the specs group consider making uid mandatory?

2016-12-15 Thread Bjørn Næss
a simple LINK endpoint. This looks like this: /api/v1/link?ehruri=ehr%3Acompositions%2F131b9960-a2b0-452b-a140-34990dd3487d%3A%3A9624982A-9F42-41A5-9318-AE13D5F5031F%3A%3A1%2Fcontent%5BopenEHR-EHR-OBSERVATION.body_weight.v1%20and%20name%2Fvalue%3D'Body%20weight_001'%5D Vennlig hilsen Bjørn Næss

SV: Converting Archetype into Nosql Schemes

2016-10-24 Thread Bjørn Næss
The key part of our openEHR server is the composition/path index based on Lucene and served by Apache Solr. There are no SQLs involved in the query part here. Vennlig hilsen Bjørn Næss Product owner DIPS ASA Mobil +47 93 43 29 10 -Opprinnelig melding- Fra: openEHR-technical

SV: More generic reference model

2016-09-09 Thread Bjørn Næss
Disease Ontologies. In the end I think we need a shared pattern on how to model and implement this - and as mentioned the most important thing is to be able to do queries on this hierarchical/graph structured ontologies/terminologies. / Bjørn Næss - Product Owner | DIPS ASA Mobil +47 93 43 29 10

SV: Personal Health Record using CHBase (related to Health Vault)

2016-06-15 Thread Bjørn Næss
models developed in CHBase? Who is the owner of this platform and specification? Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> Fra: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] På vegne av Erik Sundvall Sendt:

SV: SV: Usage of Compositoin.Category

2016-04-11 Thread Bjørn Næss
On 11/04/2016 11:07, Bjørn Næss wrote: But if we want to avoid double results in querying, we need some sort of 'is_derived' or 'is_copy' marker (and a link to original content) on the copy. At least that's where I got to the last time I thought about it. Yes - I think we need some kind

SV: Usage of Compositoin.Category

2016-04-11 Thread Bjørn Næss
. a Blood Pressure with an attribute ‘is_copy’ should by default be excluded from AQL queries. Something like that? Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> Fra: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.o

Adressing of i.e. discharge summaries

2016-03-16 Thread Bjørn Næss
to do this? Best regards Bjørn Næss Product owner DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.openehr.org/mailman/listinfo/o

SV: SV: Usage of Compositoin.Category

2016-03-15 Thread Bjørn Næss
chieved. Not saying there are not reasons to do it, just that the normal way today seems to satisfy the requirement. Secondly, just a mechanical AQL thing: it should normally be possible to do: WHERE c/category/defining_code matches {[openehr::434]} - thomas On 10/03/2016 12:32, Bjørn Næss wro

SV: Socio-technical challenges when the openEHR approach is put to use in Norwegian hospitals

2016-03-15 Thread Bjørn Næss
-operate in this work. I think all agree that the development and deployment of ICT solutions for healthcare is a large socio-organizational-technical challenge. The work done by domain experts is only a (important and essential) part of that problem domain. Best regards Bjørn Næss Product owner

SV: Usage of Compositoin.Category

2016-03-10 Thread Bjørn Næss
hat there is a class of compositions which belongs to the "report" group. Then we should add such semantic into the RM to make it precise and consistent. Best regards Bjørn Næss Product owner DIPS ASA Mobil +47 93 43 29 10 -Opprinnelig melding- Fra: openEHR-technical [mailto:openehr-techn

SV: Usage of Compositoin.Category

2016-03-04 Thread Bjørn Næss
regarding creating, saving and querying content based on these attributes. The concrete number, 434, was picked since it was not used and was in the same serie as the other category number. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010>

SV: Usage of Compositoin.Category

2016-03-04 Thread Bjørn Næss
? Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> Fra: openEHR-technical [mailto:openehr-technical-boun...@lists.openehr.org] På vegne av Bjørn Næss Sendt: onsdag 17. februar 2016 22.00 Til: openehr-technical@lists.openehr.org Emne:

Usage of Compositoin.Category

2016-02-17 Thread Bjørn Næss
f the box". Any comments on this? Best regards Bjørn Næss Product Owner - Arena EHR DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> ___ openEHR-technical mailing list openEHR-technical@lists.openehr.org http://lists.

RE: Archetype publication question - implications for implementers

2015-10-09 Thread Bjørn Næss
(v2-ALPHA) and collect more changes before forcing a new major version. Vennlig hilsen Bjørn Næss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10<tel:+47%2093%2043%2029%2010> From: openEHR-implementers [mailto:openehr-implementers-boun...@lists.openehr.org] On Behalf Of Heather Lesli

LOCATABLE REF and EHR URI

2015-03-09 Thread Bjørn Næss
Looking at the Locatable Ref class: http://openehr.org/releases/1.0.2/architecture/rm/support_im.pdf The as_uri function of LOCATABLE_REF is defined to return the following: ehr:// + id.value + / + path If we read Architecture Overview:

ISM Transition : definition of allowed transitions

2015-03-03 Thread Bjørn Næss
NB! This is a new e-mail on the same subject since I didn't see any mail on the mailing list. Just to check if it is working We are currently developing a module for Careplan based on openEHR Archetypes. We are using INSTRUCTION/ACTIVITY/ACTION archetypes to model the clinical process. One

Problem-oriented records and querying by problem

2014-11-25 Thread Bjørn Næss
I like this approach. The master care plan is what we call Patient plan. There should be only one of this in a given EHR. This plan evolves over time as more items are addes or removed. To administer this plan you need a dashboard with functionality to filter on overdue, finished, etc. And

Postulate: DV_QUANTITY should be modelled with fewest possible units

2014-11-14 Thread Bjørn Næss
An application need that kind of service. But this is actually not the problem. See my latest mail regarding guildelines and population queries. Vennlig hilsen Bj?rn N?ss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10tel:+47%2093%2043%2029%2010 Original message From: pablo

Postulate: DV_QUANTITY should be modelled with fewest possible units

2014-11-14 Thread Bjørn Næss
I have been thinking about profiling. I am not sure if this fix the problem regarding complexity. This may be an governance thing. If we define a metric and british imperial profile we may define that in Norway every application MUST use the metric profile and other countries may select

Postulate: DV_QUANTITY should be modelled with fewest possible units

2014-11-14 Thread Bjørn Næss
I guess smart querying services would do the work. But should it also be possible for the client to say when unit conversion should be used and when not? Use case is when user only want the units stored as grams, and not kilos. Maybe a pattern from HTTP could be used. The accept pattern.

Archetype Naming proposals - do we need V0?

2014-10-13 Thread Bjørn Næss
I also agree on this. It is a good idea to decide the versioning from Archetype to Archetype. If there are no need for breaking changes in the Archetype then the version should not be altered. If some of the archetypes from a clinical point of view must be changed in a not backward

New online archetype and template tooling project

2014-10-10 Thread Bjørn Næss
What a great start! I really look forward to the next weeks in this important project. Vennlig hilsen Bj?rn N?ss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10tel:+47%2093%2043%2029%2010 Original message From: Erik Sundvall Date:10/10/2014 18:03 (GMT+01:00) To: openehr

SV: Exception messages on TemplateDesigner 2.7.60.2

2013-11-28 Thread Bjørn Næss
Nice ;-) Vennlig hilsen Bj?rn N?ss Produktansvarlig DIPS ASA Mobil +47 93 43 29 10tel:+47%2093%2043%2029%2010 Opprinnelig melding Fra: Kjetil J?rgensen kjo at dips.no Dato: 28.11.2013 15.12 (GMT+01:00) Til: For openEHR technical discussions openehr-technical at

SV: Rich text format in DV_TEXT

2013-09-23 Thread Bjørn Næss
This is a very relevant issue. We have the same in our application. Some of the fields will be DV_TEXT but we want to show some rich formatting. It is crucial to be compatible with Archetypes from CKM, and different vendors producing or consuming Archetypes. So it is not an option to make

SV: State transitions - ACTIVITY/ACTION

2013-09-11 Thread Bjørn Næss
Hi Yes that is my opinion as well. And there is one more missing link in my understanding: Given that there is an ACTIVITY in INITIAL state and the user want to cancel the ACTIVITY; then it should be possible to do a transition from INITIAL directly to CANCELLED state. This transition is not

State transitions - ACTIVITY/ACTION

2013-09-10 Thread Bjørn Næss
Hi all. We are discussing some details with the INSTRUCTION STATE MACINE. I will go directly to my two questions: 1 The state machine define transition from all not-terminated states to a terminated state. Except from POSTPONED state. There is no defined transition from POSTPONED to

SV: openEHR-technical Digest, Vol 18, Issue 50

2013-08-31 Thread Bjørn Næss
You are absolutely right. Yesterday I where in a meeting with two national stakeholders for data specification regarding patient with drug/alcohol problems. The problem we as a vendor and our customers and users face is that they ask for almost the same thing. And they can not agree. That's

SV: ACTIVITY and timing

2013-08-11 Thread Bjørn Næss
Hi Pablo Thanks for the quick response! I guess you are right regarding Cron and ISO 8601 when it comes to implement the DV_PARSABLE attribute timing on the ACTIVITY class. The openEHR-EHR-CLUSTER.timing.v1 is developed to define structured information about the timing (intended or actual) of

ACTIVITY and timing

2013-08-10 Thread Bjørn Næss
Hi ACTIVITY has a field for timing. It's datatype is parsable. Some archetypes use a CLUSTER archetype to define detailed timing information for the given ACTIVITY. I am curious if anyone have experiences with implementing timing for Activity and which strategy you are using? Will detailed

SV: How to model this XML type as Archetype?

2013-05-14 Thread Bjørn Næss
Hi Ian Thank you for a quick response! Ok - so my modeling is ok :) Still there is a minor problem/challenge. I have to make a report from the Archetype. Given the following value instance of the archetype element: items xsi:type=ELEMENT archetype_node_id=at0072 name

How to model this XML type as Archetype?

2013-05-13 Thread Bjørn Næss
Authorities require the reporting of injury. It is defined XSD for the message to be sent. Some items have numbers. These are perfect ordinal. The problem is the following XML type. How should these be modeled as archetype data types? simpleType name = ' accidentSite ' restriction base=