http://www.linkehr.com/
Regards,
David Moner
2008/8/8 Pab
> Hi, I'm starting a research on EN13606. In many places mention that
> EN13606 defines archetypes to constraint it RM, but I can't find the spec of
> such archetypes.
> Anyone knows if there is a spec for EN13606 a
chnical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valenci
-based ids, it doesn't seem a very good
solution since it may have conflicts with the values of some attributes of
the RM in data instances, e.g the LOCATABLE.archetype_node_id which
explicitly requires a valid at syntax.
2008/7/17 Thomas Beale :
> David Moner wrote:
>
> Hello,
&
Hello Thomas,
About your petition, there are some Changes in our group. Now it is called
Biomedical Informatics Group and the team is composed by Monserrat Robles,
Jos? Alberto Maldonado, David Moner and Diego Bosc?. Jesualdo is still at
the Murcia University.
We are currently involver in
RM_CODE_REF*
| SYM_ALLOW_ARCHETYPE error
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-- next part --
> - thomas beale
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
I
... }
}
or if we want to redefine the cardinality:
ITEM_TREE[at0001] matches {
items container cardinality matches {1..*; ordered} matches
{ ... }
}
Just some quick thoughts,
David
2009/7/3 Thomas Beale
> David Moner wrote:
>
> I agree with the initial idea about the optional
to represent
correctly the DV_DATE value as a "xs:date" type with the appropriate ISO8601
facet or the archetypes should take the form
value matches {"-??-XX"}
to be parsed as a String according to the RM definition.
I'm right with this?
-
> Heath
>
>
>
> Heath Frankel
>
> Product Development Manager
>
> Ocean Informatics
>
>
>
> heath.frankel at oceaninformatics.com
>
> +61 (0) 8 7127 5574
>
>
>
>
>
>
>
> *From:* openehr-technical-bounces at openehr.org [mailto:
> openehr
; attribute
of an archetype should be renamed to "license" to best fit the conditions of
usage of archetypes.
What's your opinion?
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Cam
is -
> http://www.openehr.org/wiki/display/oecom/Archetypes+-+Copyright+and+Licensing
>
> - thomas beale
>
> David Moner wrote:
>
> Dear all,
>
> These days I have been thinking about the legal issues involving the use of
> existing archetypes. I have seen that openEHR archety
ture since they are local implementations, but I
think that it is possible to design a kind of common framework to deal with
them together with archetypes and structural templates.
David
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad P
part of the new data and that can affect your
interpretation of it.
That's why structural templates must be also shared in some cases.
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino d
at the
specifications, the web or the wiki. Every developer should know that
(coming back to the topic of this thread) if they hand-code a
visualization template all that work is only useful for the data
generated at their own system and not for the data from an external
one, even if it is using the s
12/2010 21:01, David Moner wrote:
>>
>>> #3. The templates you use should only restrict data entry. It should
>>> not filter existing data of the same structure. If it does; there goes
>>> interoperability. Along with the entire premise for the use of and
>>>
pen a .DOC document with Microsoft Word
2007/2010, it will never change it to .DOCX automatically.
David
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3?
specifically, ADL) should not impose rules in this
aspect. What's your opinion?
David
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46
No comments or opinions about this?
2010/11/4 David Moner
> While working with archetypes for different reference models we have faced
> a problem regarding the uppercase/lowercase rules for naming archetype nodes
> at ADL.
>
> The ADL specifications imposes the following rule:
l description
> of where a purely automated conversion algorithm that Erik is talking about
> goes.
>
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso
ode id (at0001.1) as
archetype identifier? Or phrased differently, for the second case, if I
communicate the instance, should I also share the template definition to
better describe it or would be enough by sharing only the clinical
archetype?
David
--
David Moner Cano
Grupo de Inform?tica Biom?di
ry Health Care www.phcsg.org
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - I
h.
Finally, I also agree that is not the same to talk about "RM version of an
archetype" than to talk about "archetype validity regarding a RM", but one
should not exclude the other.
David
2011/4/7 Thomas Beale
> On 05/04/2011 19:16, David Moner wrote:
>
> Hello,
&
ship between particular archetypes and particular releases of
> the CDA model.
>
> - thomas
>
>
So, at the end you are putting the RM version somewhere at the identifier...
:-)
(btw, I don't know which will be the changes at R3)
David
--
David Moner Cano
Grupo de Inform?tic
mber is reset to 0.
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-- next part --
An HTML attachment w
d to, at least, warn systems that use archetypes
that something has changed.
David
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022
t; http://www.openehr.org/svn/knowledge2/TRUNK/rm_schemas/EXAMPLE.bmm.txt
>
> - thomas
>
>
>
>
>
>
> On Thu, Dec 1, 2011 at 6:56 AM, David Moner wrote:
>
>> Hello Thomas,
>>
>> Is there any grammar or documentation of the RM schema format? I have
>>
ke a useful idea?
>
> - thomas beale
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica
this meeting are invited to
> subscribe.
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIM
us making really
complicated the process of automatically transforming it to a very specific
reference model. This is not the case when we use 13606.
A different thing is if 13606 scope changes during the revision. In that
case, I agree that reducing layers of modelling by introducing specific
classes
early defines a
> deterministic (and tested) conversion algorithm from "the detailed
> clinically focused" RM (6 or 1b) to the "healthcare a-specific" RM
> (1a)?
>
>
>From what I have heard, it is possible to add new part to the standard.
David
--
David
ectly instantiable. Thus, an implementer can choose to use it if the
lower OBSERVATION, INSTRUCTION, etc. classes do not accommodate his needs.
Moreover, it would be easy to cast an ENTRY instance into any of its
descendants when needed.
David
--
David Moner Cano
Grupo de Inform?tica Biom?d
here<http://www.openehr.org/issues/browse/AWBPR>
> .
>
> - thomas beale
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
--
our gives us the reason for that case. I
think the DV_BOOLEAN is perfect as it is and if in some case it is not good
for your needs, then you should use a different data type (a coded text for
example).
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibi
onding node in the EHR from which it was extracted."
So, as you said, in a 13606 extract we can have a mix of FOLDERs created to
organise the information of the Extract and FOLDERs existing at the original
EHR system, but they can be clearly distinguished by the synthesised
attribute.
David
-
> >>> nodes to the archetype, I need to change the ITEM_SINGLE to another
> >>> ITEM_STRUCTURE, but if the archetype is modeled with an ITEM_TREE, I
> >>> can add any nodes without changing the ITEM_STRUCTURE type. I think
> >>> this way is more simple to c
archetypes,
> including a lot of directly copied openEHR material, and no attribution
> at all to openEHR! Lucky it is not an academic paper
>
> - thomas
>
> --
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnic
r the easiest. If we stay focussed, unofficial (for now),
> and
> >>>> make progress on that then we can tackle bigger beasts...
> >>>>
> >>>> - thomas
> >>>>
> >>>>
> >>>>
complete history about the technology behind.
David
2011/9/9 Thomas Beale
> On 09/09/2011 19:04, David Moner wrote:
> >
> > Thomas,
> >
> > Could you please clarify this sentence?
> >
> > I'm the main author of that document. As you said, it is a 4
h
>I think is a necessary future step for both openEHR and 13606.
>
> If HL7 goes this way, some real convergence finally looks possible, and
> people working on openEHR and 13606 need to think about how to go about it.
>
> - thomas beale
>
>
> ___
/EN13606trainingcourse.pdf
You are all welcome to participate in any of these activities.
Best regards,
David Moner
Secretary of the EN 13606 Association
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera
ssages and
> Clinical Documents??
>
> ** **
>
> I know there is deep learning curve and would very much appreciated for
> any pointers.
>
> ** **
>
> Thanks in advance for any help!
>
> ** **
>
> --Wo
>
> ** **
>
> __
tierrez
> Blog: http://informatica-medica.blogspot.com/
> Twitter: http://twitter.com/ppazos <http://twitter.com/ppazos>
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at openehr.org
> http://lists.chime
_
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de
chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-- next part
- thomas
>
> _______
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ib
r to a data item definition in an
archetype.
Thoughts on this?
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
-
pop-up
or something like that.
2012/1/25 Diego Bosc?
> Would this attribute value change depending on where is the archetype
> used? i.e. if we use it on a GUI of a smartphone rather than a
> standalone or web application
>
> 2012/1/25 David Moner :
> >
> > 2012/1/25 Thom
led vocabulary, such as 'mandatory',
> 'recommended', 'passable'/'skippable'...
>
> 2012/1/26 David Moner :
> > Following this new sense for it, I think that the implications for a GUI
> or
> > visual representation would depend on a decis
*">
>
The "*" is the default value inserted by the archetype editor. Shouldn't
have more sense to make description a not mandatory field? For very simple
data items probably it will not be needed. This also applies to the
constraint_definition that follows the same struc
the concept "derived work".
David
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Espa?a)
--
e a
balance between what it is perfectly modelled and what can be implemented
by most.
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
ends on
the previous one. The fact of representing clinical models in a different
format (if we see ADL just as a format for defining models) should not
change the essence of the problem as we saw in point 2.
See that I'm just trying to set out the limits of the problem to find a
general rule
uot;This is a ITEM_TREE object">
> >
> ["at0002"] = <
>text = <"ELEMENT">
>description = <"This is a ELEMENT object">
> >
>["at0003"] = <
&
info/openehr-**
> technical_lists.openehr.org<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org>
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, A
difficult to improve tools if we do not receive comments about them.
Regards,
David
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (Es
purpose of arcehtype-editors to rework archetypes in
> text-editors. I can do that, I have seen enough archetypes. But I know many
> people who can't, but they also have to do it.
>
>
Yes, I meant to avoid generating that line when it is not needed, not
removing it by hand.
David
would require a deep analysis
and changes of the models, but that could be the idea.
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? planta
Valencia ? 46022 (
at metainformation should not be part of the BMM
requirements.
We have uploaded the JavaCC specification of the BMM grammar to the openEHR
wiki: http://www.openehr.org/wiki/display/dev/BMM+grammar+and+parsers
Feel free to use or modify it.
David
--
David Moner Cano
Grupo de Inform?tica Biom?d
te classes.
The logic of the tools and the validation checks of archetypes are built
based on those interpretations. I agree with Bert in one thing: tools
shouldn't change things without notifications, but in this case we face a
methodological difference, not just a configuration one, and th
efines a terminology
binding (internally the ontology structures are created). When the
archetype is used or processed, the systems will only use the information
they have available.
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.link
2013/8/28 Thomas Beale
> On 28/08/2013 10:07, David Moner wrote:
>
>
>
>
> No, currently all at codes are also found at the ontology in
> LinkEHR, even if they are empty, to be compatible with the VATDF2 check,
> although we would like to avoid it :-)
>
>
"This is a PQ type node" or "The sky is blue" or " " are correct or have a
sense, only a human validation check can work here.
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Uni
7;m just saying that
this is a very subjective topic, dependant on the context of use, the
availability of some resources (e.g terminological codes) and many other
factors. So, we can all do our best but it will be very difficult to have
rules that guide which nodes of the archetype have to be i
, whose
definition should remain immutable.
That, said, I must say that we are not big fans of BMM :-)
While we agree that current alternatives (i.e XMI) are not usable in
practice nowadays, we find extremely improbable that BMM gains big
acceptance outside the openEHR world. I doubt that we ever s
>
> wait time <= 5 days
>
> - thomas
>
>
> ___ openEHR-technical mailing
> list openEHR-technical at lists.openehr.org
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
> _______
ess since they are related
to the basic internal philosophy of the tool, such use adding an id to
every node.
We'll try tu publish an updated version of the editor sooner than later.
David
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
U
nt model and propose changes. If people think this isn't
> sufficiently detailed, feel free to rework it in another way.
>
> - thomas
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/
discussion. In
the previous example, an instance data value (not DataValue) belong to the
node [at0009], that's all even if that node has multiple occurrences. ADL
paths are used to reference object nodes within an archetype, not
instances, and in an archetype every node type is unique. A differe
several organizations, and
we think these identifiers are needed both technically and
methodologically, so we will continue our way of doing thing :-)
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Universidad P
ption or terminology binding due to
clinical reasons.
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Universidad Polit?cnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acceso B, 3? plant
2013/9/2 Thomas Beale
> On 02/09/2013 08:49, David Moner wrote:
>
>
>
>
> 2013/9/2 Thomas Beale
>>
>>
>> Well, LinkEHR is a real implementation in use by several organizations,
>> and we think these identifiers are needed both technically and
>&g
items[at0008]/value/value
>>
>> Thanks very much
>>
>> Bert
>>
>>
>>
>> ___
>> openEHR-technical mailing list
>> openEHR-technical at lists.openehr.org
>>
>> http://lists.openehr.org/mailma
s it has on
> specific things.
>
> Hopefully this is a useful starting point.
>
> - thomas
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-tech
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
>
>
>
>
> --
>
> -
> http://www.healthintersections.com.au / grahame at healthinters
ownload/attachments/45645905/AOM_archetype_package.png?version=2&modificationDate=1412032298000&api=v2>.
> Note that it is currently spelt in international English, not US English
> ('license', which is only a verb in International English).
>
> - thomas
>
> On 13/11/2014
"Intermountain model xyz avalable at ">
> time = <2014-10-12T12:44:00>
> method = <"IHCModelConverter v3.134.0.78">
> other_details = < >-- tagged values
> >
>
> thoughts on this?
>
> - thomas
>
> _
I don't think so, but maybe we could use the release_candidate state,
instead the draft one that I mentioned.
2014-11-13 19:32 GMT+01:00 Diego Bosc? :
> Could "autogenerated" be a valid lifecycle state?
>
> 2014-11-13 19:23 GMT+01:00 Thomas Beale >:
> > On 13
2014-11-13 19:23 GMT+01:00 Thomas Beale :
> On 13/11/2014 16:50, David Moner wrote:
>
> As you say, this information should be somehow related to the
> "is_generated" flag. But if we consider that once a human user reviews the
> archetype that flag is set to false, then
/11/2014 18:37, David Moner wrote:
>
> I don't think so, but maybe we could use the release_candidate state,
> instead the draft one that I mentioned.
>
>
> well I think either could be correct, depending on the circumstances. E.g.
> the latest openEHR/FHIR joint Adverse
we no longer have this requirement.
>
> - thomas
>
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica
I can see the point now. I couldn't understand the benefits of the new UID
attributes.
It is OK if they become mandatory in 2.0. We just have to have clear rules
to know when a new instance_id has to be created.
2014-11-18 14:31 GMT+01:00 Thomas Beale :
> On 18/11/2014 12:50, David Mon
as their hash code. And in that case, changing to v0
should not mean any difference or additional problem.
David
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Universidad Polit?cnica de Valencia (UPV)
D dept, E-health section, Bergen Hospital Trust
>
> Tel. +47 40203298
>
>
>
>
> _______
> openEHR-technical mailing listopenEHR-technical at
> lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.open
rules from the archetype
constraints, that is arguably an adaptation, not just a use.
And it is also important to note that if you sell a software you are also
publicly sharing it. Publicly share does not imply for free, but outside of
a personal use.
I fully support the comments of Grahame. Pro
constraint_bindings = <
["BI98"] = <
items = <
["ac0001"] =
["ac0001"] =
>
>
>
Is it mandatory to use predefined subsets to define a coded value set with
multiple values in a constraint binging?
Isn't it reasonable t
kground on the need you have? It's not out of the question to get
> it into the soon-to-be-finalised ADL2, but we'd need something pretty clear
> to go on.
>
> Secondly, your statement:
> Isn't it reasonable to allow defining coded value sets explicitly at the
>
;
> ___
> openEHR-technical mailing list
> openEHR-technical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
--
David Moner Cano
Grupo de Inform?tica Biom?dica - IBIME
Institu
2014-10-31 9:02 GMT+01:00 Thomas Beale :
> On 31/10/2014 07:39, David Moner wrote:
>
> I will explain it in another way.
>
> ac codes are used as "placeholder constraints", i.e. a kind of link
> to a query or subset in a terminological systems that defines the p
>
> Thanks,
>
> Pablo.
>
>
> Sent from my LG Mobile
>
> ___
> openEHR-clinical mailing list
> openEHR-clinical at lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-clinical_lists.openehr.org
>
--
David Moner Cano
Grupo de In
he latter can occur when a doctor asks the patient for medication
> taken. I agree the real time record of the event can also occur.
>
>
> Thanks!
>
>
> Sent from my LG Mobile
>
> -- Original message--
>
> *From: *David Moner
>
> *Date: *Tue,
kshops by the middle of January. Keep an eye on the lists
> for
> > details.>>>> Looking forward to working with you all in 2015!>>>> Cheers,
> > Sam>>>> Dr Sam Heard>> Chairman, openEHR Foundation>>>>>>
> > _
el
>> emisor no puede garantizar nada al respecto y no será responsable de
>> cualesquiera daños que puedan resultar de una transmisión de virus.
>> ___
>> openEHR-technical mailing list
>> openEHR-technical@lists.openehr.org
>>
on support systems. With this
approach, existing EHR data becomes available in a standardized and
interoperable format, thus opening a world of possibilities toward semantic
or concept-based reuse, query and communication of clinical data.
--
David Moner Cano
Grupo de Informática Biomédica - IBIME
>
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
--
David Moner Cano
Grupo de Informática Biomédica - IBI
cal@lists.openehr.org
>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
--
David Moner Cano
Grupo de Informática Biomédica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Universidad Politécnica de Valencia (
on 3*: Promote the new candidate archetype to the public trunk, run
> formal content reviews on it and plan to re-publish as v2
>
>
>
> Please, your thoughts?
>
>
>
> Regards
>
>
>
> Heather
>
>
>
> *Dr Heather Leslie *MBBS FRACGP FACHI
> *Consulting Lead*, Ocean Informatics <htt
ated solution is to just follow the
versioning rules that already exist.
David
--
David Moner Cano
Grupo de Informática Biomédica - IBIME
Instituto ITACA
http://www.ibime.upv.es
http://www.linkedin.com/in/davidmoner
Universidad Politécnica de Valencia (UPV)
Camino de Vera, s/n, Edificio G-8, Acce
hanged the receiver
will use its own archetype to validate the received data, and if it
includes the 'deg' unit it will just fail the validation. Breaking
revisions are not only about changing the archetype structure, but also
about generating a different set of possible instances.
--
Dav
t;>>
> >>>
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
> >>
> >> ___
> >> openEHR-technical mailing list
> >> openEHR-technical@lists.openehr.org
> >>
> >
mailing list
> > openEHR-technical@lists.openehr.org
> >
> http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
>
> ___
> openEHR-technical mailing list
> openEHR-technical@lists.openehr.org
>
&g
1 - 100 of 127 matches
Mail list logo
