[prev in list] [next in list] [prev in thread] [next in thread]
List: openmrs-dev
Subject: Re: Use of FHIR encounter$everything to represent OpenMRS encounters [spoiler alert: contains actual
From: Burke Mamlin <burke () openmrs ! org>
Date: 2015-04-08 12:25:22
Message-ID: CAKgo1ZY8w6ohr0hfsSbdOC9F2AhDxwauN-dk_LZEkMmvvUV-Kg () mail ! gmail ! com
[Download RAW message or body]
Include name iff <https://en.wikipedia.org/wiki/If_and_only_if> it is
populated. Also, don't forget to include the local code (i.e., the UUID of
the concept on the server itself). For example:
"code": {
"coding": [
{
"system": "http://qa01.openmrs.org:8080/openmrs/",
"code": "5090AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
"display": "Height (cm)"
},
{
"system": "http://snomed.info/sct",
"code": "50373000",
"display": "Body Height"
},
{
"system": "http://loinc.org",
"code": "8302-2",
}
]
}
-Burke
On Tue, Apr 7, 2015 at 10:57 PM, Harsha Kumara <harsz89@gmail.com> wrote:
> Hey Suranga,
>
> If you look at [1], it has some mapping names also. But mapping names for
> some mappings are not there. It's better the mapping name also associate
> with relevant concept name of each concept source which is associate with
> concept dictionary concept.
>
> [1] -
> http://qa01.openmrs.org:8080/openmrs/dictionary/concept.htm?conceptId=5090
>
> Thanks,
> Harsha
>
> On Wed, Apr 8, 2015 at 12:10 AM, Suranga Kasthurirathne <
> surangakas@gmail.com> wrote:
>
> >
> > Thanks everyone,
> >
> > Agree what was discussed about obs.location, so we can go ahead and
> > remove it from the FHIR Observation resource.
> >
> > And yes, many of the concept mappings we were looking at don't seem to
> > have names. Maybe @Andy can comment on this?
> > Harsha, are you suggesting something like "conceptmappingname:uuid" for
> > concept mapping name?
> >
> > PS: My My, it seems that we're on the brink of starting to modify the
> > OpenMRS API to match the FHIR API ;-)
> >
> > On Tue, Apr 7, 2015 at 1:15 PM, Harsha Kumara <harsz89@gmail.com> wrote:
> >
> > > @Burke, +1 for avoid using location within FHIR Observation and let
> > > client to use location in Encounter resource. As Darius mentioned we also
> > > can include location as extension in Observation if and only if it's differ
> > > from Encounter. But if we going to depreciate Location within OpenMRS, we
> > > no need to do this either.
> > >
> > > Regarding concept mappings why concept mappings not associate with a
> > > name most of the time[1]? For example if we take concept mappings of LOINC
> > > code, it's always better to include the name and code together. @Burke I
> > > agree that we should include readable value for display as it's meant to
> > > include more readable term which is concept name.
> > >
> > > [1] -
> > > http://qa01.openmrs.org:8080/openmrs/dictionary/concept.htm?conceptId=5088
> > >
> > > Thanks,
> > > Harsha
> > >
> > > On Tue, Apr 7, 2015 at 8:34 AM, Burke Mamlin <burke@openmrs.org> wrote:
> > >
> > > > We've had obs.location forever (in fact, it used to be *required*),
> > > > but I'm not not sure why it's there. I searched my old emails for a hint;
> > > > no luck. I may have overlooked it, but I didn't see location in HL7v2 OBX
> > > > or OBR... nor in FHIR's Observation resource.
> > > >
> > > > I'd second Darius, but guessing obs.location != obs.encounter.location
> > > > is <0.0001% and less sure there's some random scenario where it's
> > > > important. :-)
> > > >
> > > > How about just not implementing obs.location in FHIR, assuming it will
> > > > eventually be deprecated within OpenMRS? When we introduce the ability to
> > > > track technical transactions of obs, it will become more obsolete.
> > > >
> > > > Regarding concept mappings, I would expect "display" to be something
> > > > human readable, not a UUID. If you were to include UUIDs, which could be
> > > > useful to clients, OpenMRS-specific UUIDs would make more sense, IMHO, as
> > > > an extension on the code. If you don't have a human readable display value
> > > > for a reference term (i.e., name is blank), then omit the display value in
> > > > the FHIR resource.
> > > >
> > > > Cheers,
> > > >
> > > > -Burke
> > > >
> > > > On Mon, Apr 6, 2015 at 6:19 PM, Darius Jazayeri <darius@openmrs.org>
> > > > wrote:
> > > >
> > > > > In my experience, having obs.location != obs.encounter.location is a
> > > > > <1% use case. But I'm sure there's *some* random scenario where it's
> > > > > important.
> > > > >
> > > > > Can you suppress exporting that value + extension except when it
> > > > > differs from the encounter location?
> > > > >
> > > > > -Darius
> > > > >
> > > > > On Mon, Apr 6, 2015 at 3:04 PM, Suranga Kasthurirathne <
> > > > > surangakas@gmail.com> wrote:
> > > > >
> > > > > >
> > > > > > Hi everyone,
> > > > > >
> > > > > > We (or more truthfully, Harsha) worked on a number of improvements to
> > > > > > the previous version of the encounter$everything operation.
> > > > > > You can find the updated bundle here <http://pastebin.com/knZAntM4>.
> > > > > >
> > > > > > 1) Note the WONDERFUL new system value url's for concept mappings!
> > > > > > as you can see, this observation has eight different concept mappings.
> > > > > > 2) We've also upgraded to using observation.encounter instead of
> > > > > > observation.extension for linking to encounters.
> > > > > >
> > > > > > Question for the OpenMRS experts:
> > > > > > 1) In OpenMRS, each Observation has a specific Location assigned..
> > > > > > which is why we have a location extension in the FHIR Observation \
> > > > > > resource to specify this. Under practical circumstances, will the \
> > > > > > location specified per Observation change from the location specified per \
> > > > > > the Encounter that it belongs to? Is there value is specifically listing \
> > > > > > a Location per each Observation?
> > > > > > If we don't need to include locations per Observation, we don't need
> > > > > > to worry about the <extension url=..." which still says "
> > > > > > http://resources.openmrs.org/doc/fhir/profiles/vitalsigns.xml#location"
> > > > > > > -(
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sat, Apr 4, 2015 at 3:15 AM, Grahame Grieve <
> > > > > > grahame@healthintersections.com.au> wrote:
> > > > > >
> > > > > > > hi Suranga
> > > > > > >
> > > > > > > name : (etc.) height
> > > > > > > > Source: (etc.) LOINC
> > > > > > > > code: (etc.) 8302-2
> > > > > > > >
> > > > > > > > Problems:
> > > > > > > > 1) LOINC, CIEL, SNOMED mappings may sometimes lack names. For
> > > > > > > > example, consider:
> > > > > > > > http://demo.openmrs.org/openmrs/dictionary/concept.htm?conceptId=5090.
> > > > > > > > As you can see, these mappings do not have names assigned.
> > > > > > > >
> > > > > > > > In such a case, we currently use concept maps' uuid instead of the
> > > > > > > > 'name'. Should we do this, or else simply not include the FHIR name
> > > > > > > > parameter where OpenMRS lacks this info?
> > > > > > > >
> > > > > > >
> > > > > > > This is observation.name name? (now known as 'code')
> > > > > > >
> > > > > > > Put whatever you have.
> > > > > > >
> > > > > > > 2) FHIR resource mapping includes a system url for each concept
> > > > > > > > mapping type. For example, for a concept mapping of LOINC, the \
> > > > > > > > defined system url is http://loinc.org. LOINC, SNOMED and CIEL have \
> > > > > > > > such mappings, which are stored as constants. However, many OpenMRS
> > > > > > > > concept sources don't have such url's defined. Since we can't report \
> > > > > > > > these as simply UNDEFINED (its against the FHIR spec) can we use \
> > > > > > > > global properties for users to define these instead?
> > > > > > > >
> > > > > > >
> > > > > > > put nothing if you can't work it out. CIEL should identify the
> > > > > > > source for everything, and the code populates it if it's there, \
> > > > > > > otherwise leave it blank
> > > > > > >
> > > > > > > 3) Also, we seem to have used an extension to map an extension to an
> > > > > > > > encounter. We will be getting rid of this, and using the
> > > > > > > > encounter field instead.
> > > > > > > >
> > > > > > >
> > > > > > > great. FHIR is a moving target, but mostly we move to *better*
> > > > > > >
> > > > > > > Grahame
> > > > > > >
> > > > > > > --
> > > > > > > OpenMRS Developers: http://om.rs/dev
> > > > > > > Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org
> > > > > > > Manage your OpenMRS subscriptions: http://om.rs/id
> > > > > > >
> > > > > > > *** ALERT! This group will be moved to OpenMRS Talk effective 10
> > > > > > > April 2015 at 19:00 UTC. Please visit
> > > > > > > https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508
> > > > > > > for details and to make necessary changes.
> > > > > > >
> > > > > > > To unsubscribe from this group and stop receiving emails from it,
> > > > > > > send an email to dev+unsubscribe@openmrs.org.
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best Regards,
> > > > > > Suranga
> > > > > >
> > > > > > --
> > > > > > OpenMRS Developers: http://om.rs/dev
> > > > > > Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org
> > > > > > Manage your OpenMRS subscriptions: http://om.rs/id
> > > > > >
> > > > > > *** ALERT! This group will be moved to OpenMRS Talk effective 10
> > > > > > April 2015 at 19:00 UTC. Please visit
> > > > > > https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508
> > > > > > for details and to make necessary changes.
> > > > > >
> > > > >
> > > > > --
> > > > > OpenMRS Developers: http://om.rs/dev
> > > > > Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org
> > > > > Manage your OpenMRS subscriptions: http://om.rs/id
> > > > >
> > > > > *** ALERT! This group will be moved to OpenMRS Talk effective 10 April
> > > > > 2015 at 19:00 UTC. Please visit
> > > > > https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508
> > > > > for details and to make necessary changes.
> > > > >
> > > >
> > > > --
> > > > OpenMRS Developers: http://om.rs/dev
> > > > Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org
> > > > Manage your OpenMRS subscriptions: http://om.rs/id
> > > >
> > > > *** ALERT! This group will be moved to OpenMRS Talk effective 10 April
> > > > 2015 at 19:00 UTC. Please visit
> > > > https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508
> > > > for details and to make necessary changes.
> > > >
> > > > To unsubscribe from this group and stop receiving emails from it, send
> > > > an email to dev+unsubscribe@openmrs.org.
> > > >
> > >
> > >
> > >
> > > --
> > > *Harsha Kumara*
> > > *Software Engineer*
> > > *WSO2 Inc.*
> > > *Sri Lanka.*
> > >
> > > --
> > > OpenMRS Developers: http://om.rs/dev
> > > Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org
> > > Manage your OpenMRS subscriptions: http://om.rs/id
> > >
> > > *** ALERT! This group will be moved to OpenMRS Talk effective 10 April
> > > 2015 at 19:00 UTC. Please visit
> > > https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508
> > > for details and to make necessary changes.
> > >
> > > To unsubscribe from this group and stop receiving emails from it, send
> > > an email to dev+unsubscribe@openmrs.org.
> > >
> >
> >
> >
> > --
> > Best Regards,
> > Suranga
> >
> > --
> > OpenMRS Developers: http://om.rs/dev
> > Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org
> > Manage your OpenMRS subscriptions: http://om.rs/id
> >
> > *** ALERT! This group will be moved to OpenMRS Talk effective 10 April
> > 2015 at 19:00 UTC. Please visit
> > https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508
> > for details and to make necessary changes.
> >
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to dev+unsubscribe@openmrs.org.
> >
>
>
>
> --
> *Harsha Kumara*
> *Software Engineer*
> *WSO2 Inc.*
> *Sri Lanka.*
>
> --
> OpenMRS Developers: http://om.rs/dev
> Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org
> Manage your OpenMRS subscriptions: http://om.rs/id
>
> *** ALERT! This group will be moved to OpenMRS Talk effective 10 April
> 2015 at 19:00 UTC. Please visit
> https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508
> for details and to make necessary changes.
>
--
OpenMRS Developers: http://om.rs/dev
Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org
Manage your OpenMRS subscriptions: http://om.rs/id
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508 \
for details and to make necessary changes.
To unsubscribe from this group and stop receiving emails from it, send an email to \
dev+unsubscribe@openmrs.org.
[Attachment #3 (text/html)]
<div dir="ltr">Include name <a \
href="https://en.wikipedia.org/wiki/If_and_only_if">iff</a> it is populated. Also, \
don't forget to include the local code (i.e., the UUID of the concept on the \
server itself). For example:<div><br></div><div><font face="monospace, \
monospace">"code": {</font></div><div><font face="monospace, monospace"> \
"coding": [</font></div><div><font face="monospace, monospace"> \
{</font></div><div><font face="monospace, monospace"> "system": \
"<a href="http://qa01.openmrs.org:8080/openmrs/">http://qa01.openmrs.org:8080/openmrs/</a>",</font></div><div><font \
face="monospace, monospace"> "code": \
"5090AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",</font></div><div><font \
face="monospace, monospace"> "display": "Height \
(cm)"</font></div><div><font face="monospace, monospace"> \
},</font></div><div><font face="monospace, monospace"> {</font></div><div><font \
face="monospace, monospace"> "system": "<a \
href="http://snomed.info/sct">http://snomed.info/sct</a>",</font></div><div><font \
face="monospace, monospace"> "code": \
"50373000",</font></div><div><font face="monospace, monospace"> \
"display": "Body Height"</font></div><div><font face="monospace, \
monospace"> },</font></div><div><font face="monospace, monospace"> \
{</font></div><div><font face="monospace, monospace"> "system": \
"<a href="http://loinc.org">http://loinc.org</a>",</font></div><div><font \
face="monospace, monospace"> "code": \
"8302-2",</font></div><div><font face="monospace, monospace"> \
}<br></font></div><div><font face="monospace, monospace"> \
]<br></font></div><div><font face="monospace, \
monospace">}</font></div><div><br></div><div>-Burke</div><div><br></div><div><br></div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 7, 2015 at 10:57 PM, \
Harsha Kumara <span dir="ltr"><<a href="mailto:harsz89@gmail.com" \
target="_blank">harsz89@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Hey Suranga,<div><br></div><div>If you look at \
[1], it has some mapping names also. But mapping names for some mappings are not \
there. It's better the mapping name also associate with relevant concept name of \
each concept source which is associate with concept dictionary concept. \
</div><div><br></div><div>[1] - <a \
href="http://qa01.openmrs.org:8080/openmrs/dictionary/concept.htm?conceptId=5090" \
target="_blank">http://qa01.openmrs.org:8080/openmrs/dictionary/concept.htm?conceptId=5090</a></div><div><br></div><div>Thanks,</div><div>Harsha</div></div><div \
class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div \
class="gmail_quote">On Wed, Apr 8, 2015 at 12:10 AM, Suranga Kasthurirathne <span \
dir="ltr"><<a href="mailto:surangakas@gmail.com" \
target="_blank">surangakas@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><br><div>Thanks \
everyone,</div><div><br></div><div>Agree what was discussed about obs.location, so we \
can go ahead and remove it from the FHIR Observation \
resource.</div><div><br></div><div>And yes, many of the concept mappings we were \
looking at don't seem to have names. Maybe @Andy can comment on \
this?</div><div>Harsha, are you suggesting something like \
"conceptmappingname:uuid" for concept mapping \
name?</div><div><br></div><div>PS: My My, it seems that we're on the brink of \
starting to modify the OpenMRS API to match the FHIR API \
;-)</div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On \
Tue, Apr 7, 2015 at 1:15 PM, Harsha Kumara <span dir="ltr"><<a \
href="mailto:harsz89@gmail.com" target="_blank">harsz89@gmail.com</a>></span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex"><div dir="ltr">@Burke, +1 for avoid using location \
within FHIR Observation and let client to use location in Encounter resource. As \
Darius mentioned we also can include location as extension in Observation if and only \
if it's differ from Encounter. But if we going to depreciate Location within \
OpenMRS, we no need to do this either.<div><br></div><div>Regarding concept mappings \
why concept mappings not associate with a name most of the time[1]? For example if we \
take concept mappings of LOINC code, it's always better to include the name and \
code together. @Burke I agree that we should include readable value for display as \
it's meant to include more readable term which is concept name. \
</div><div><br></div><div>[1] - <a \
href="http://qa01.openmrs.org:8080/openmrs/dictionary/concept.htm?conceptId=5088" \
target="_blank">http://qa01.openmrs.org:8080/openmrs/dictionary/concept.htm?conceptId=5088</a></div><div \
class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div \
class="gmail_extra">Harsha</div><div class="gmail_extra"><div><div><br><div \
class="gmail_quote">On Tue, Apr 7, 2015 at 8:34 AM, Burke Mamlin <span \
dir="ltr"><<a href="mailto:burke@openmrs.org" \
target="_blank">burke@openmrs.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">We've had obs.location forever (in fact, \
it used to be <i>required</i>), but I'm not not sure why it's there. I \
searched my old emails for a hint; no luck. I may have overlooked it, but I \
didn't see location in HL7v2 OBX or OBR... nor in FHIR's Observation \
resource.<div><br></div><div>I'd second Darius, but guessing obs.location != \
obs.encounter.location is <0.0001% and less sure there's some random scenario \
where it's important. :-)</div><div><br></div><div>How about just not \
implementing obs.location in FHIR, assuming it will eventually be deprecated within \
OpenMRS? When we introduce the ability to track technical transactions of obs, it \
will become more obsolete.</div><div><br></div><div>Regarding concept mappings, I \
would expect "display" to be something human readable, not a UUID. If you \
were to include UUIDs, which could be useful to clients, OpenMRS-specific UUIDs would \
make more sense, IMHO, as an extension on the code. If you don't have a human \
readable display value for a reference term (i.e., name is blank), then omit the \
display value in the FHIR \
resource.</div><div><br></div><div>Cheers,</div><div><br></div><div>-Burke</div></div><div><div><div \
class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 6, 2015 at 6:19 PM, \
Darius Jazayeri <span dir="ltr"><<a href="mailto:darius@openmrs.org" \
target="_blank">darius@openmrs.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">In my experience, having obs.location != \
obs.encounter.location is a <1% use case. But I'm sure there's <i>some</i> \
random scenario where it's important.<div><br></div><div>Can you suppress \
exporting that value + extension except when it differs from the encounter \
location?</div><span><font \
color="#888888"><div><br></div><div>-Darius</div></font></span></div><div><div><div \
class="gmail_extra"><br><div class="gmail_quote">On Mon, Apr 6, 2015 at 3:04 PM, \
Suranga Kasthurirathne <span dir="ltr"><<a href="mailto:surangakas@gmail.com" \
target="_blank">surangakas@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><font face="arial, helvetica, \
sans-serif"><br></font><div><font face="arial, helvetica, sans-serif">Hi \
everyone,</font></div><div><font face="arial, helvetica, sans-serif"><br>We (or more \
truthfully, Harsha) worked on a number of improvements to the previous version of the \
encounter$everything operation.</font></div><div><font face="arial, helvetica, \
sans-serif">You can find the updated bundle <a href="http://pastebin.com/knZAntM4" \
target="_blank">here</a>.</font></div><div><font face="arial, helvetica, \
sans-serif"><br></font></div><div><font face="arial, helvetica, sans-serif">1) Note \
the WONDERFUL new <span style="color:rgb(0,0,0);line-height:21px">system value \
url's for concept mappings! as you can see, this observation has eight different \
concept mappings.</span></font></div><div><span \
style="color:rgb(0,0,0);line-height:21px"><font face="arial, helvetica, \
sans-serif">2) We've also upgraded to using observation.encounter instead of \
observation.extension for linking to encounters.</font></span></div><div><span \
style="color:rgb(0,0,0);line-height:21px"><font face="arial, helvetica, \
sans-serif"><br></font></span></div><div><span \
style="color:rgb(0,0,0);line-height:21px"><font face="arial, helvetica, \
sans-serif">Question for the OpenMRS experts:</font></span></div><div><font \
color="#000000" face="arial, helvetica, sans-serif"><span style="line-height:21px">1) \
In OpenMRS, each Observation has a specific Location assigned.. which is why we have \
a location extension in the FHIR Observation resource to specify this. Under \
practical circumstances, will the location specified per </span></font><span \
style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;line-height:21px">Observation</span><font \
color="#000000" face="arial, helvetica, sans-serif"><span style="line-height:21px"> \
change from the location specified per the Encounter that it belongs to? Is there \
value is specifically listing a Location per each \
Observation?</span></font></div><div><font face="arial, helvetica, sans-serif">If we \
don't need to include locations per Observation, we don't need to worry about \
the <extension url=..." which still says "<a \
href="http://resources.openmrs.org/doc/fhir/profiles/vitalsigns.xml#location" \
target="_blank">http://resources.openmrs.org/doc/fhir/profiles/vitalsigns.xml#location</a>" \
:-(</font></div><div><span \
style="color:rgb(0,0,0);font-family:Consolas,Menlo,Monaco,'Lucida \
Console','Liberation Mono','DejaVu Sans Mono','Bitstream Vera \
Sans Mono',monospace,serif;font-size:12px;line-height:21px"><br></span></div><div><br></div><div><br></div><div><br></div><div \
class="gmail_extra"><br><div class="gmail_quote"><div><div>On Sat, Apr 4, 2015 at \
3:15 AM, Grahame Grieve <span dir="ltr"><<a \
href="mailto:grahame@healthintersections.com.au" \
target="_blank">grahame@healthintersections.com.au</a>></span> \
wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div \
dir="ltr">hi Suranga<div><br></div><div class="gmail_extra"><div \
class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><font face="arial, helvetica, sans-serif">name : (etc.) height<br>Source: \
(etc.) LOINC<br>code: (etc.) 8302-2<br><br>Problems: <br>1) LOINC, CIEL, SNOMED \
mappings may sometimes lack names. For example, consider: <a \
href="http://demo.openmrs.org/openmrs/dictionary/concept.htm?conceptId=5090" \
target="_blank">http://demo.openmrs.org/openmrs/dictionary/concept.htm?conceptId=5090</a>. \
As you can see, these mappings do not have names assigned.<br><br>In such a case, \
we currently use concept maps' uuid instead of the 'name'. Should we do \
this, or else simply not include the FHIR name parameter where OpenMRS lacks this \
info?<br></font></div></blockquote><div><br></div></span><div>This is <a \
href="http://observation.name" target="_blank">observation.name</a> name? (now known \
as 'code')</div><div><br></div><div>Put whatever you have. \
</div><span><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><font face="arial, helvetica, sans-serif">2) FHIR resource mapping includes \
a system url for each concept mapping type. For example, for a concept mapping of \
LOINC, the defined system url is <a href="http://loinc.org" \
target="_blank">http://loinc.org</a>. LOINC, SNOMED and CIEL have such mappings, \
which are stored as constants. However, many OpenMRS concept sources don't have \
such url's defined. Since we can't report these as simply UNDEFINED (its \
against the FHIR spec) can we use global properties for users to define these \
instead?</font></div></blockquote><div><br></div></span><div>put nothing if you \
can't work it out. CIEL should identify the source for everything, and the code \
populates it if it's there, otherwise leave it \
blank</div><span><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px \
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div><span style="font-family:arial,helvetica,sans-serif">3) Also, we seem \
to have used an extension to map an extension to an encounter. We will be getting \
rid of this, and using the encounter field \
instead.</span></div></div></blockquote><div><br></div></span><div>great. FHIR is a \
moving target, but mostly we move to \
*better*</div><div><br></div><div>Grahame</div><div><br></div></div> \
</div></div><span>
<p></p>
-- <br>
OpenMRS Developers: <a href="http://om.rs/dev" \
target="_blank">http://om.rs/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a> | \
Unsubscribe: <a href="mailto:dev%2Bunsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS \
subscriptions: <a href="http://om.rs/id" target="_blank">http://om.rs/id</a><br> \
<br></span>
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit <a \
href="https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508" \
target="_blank">https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508</a> \
for details and to make necessary changes.</div></div><div><div><br>
<p></p>
To unsubscribe from this group and stop receiving emails from it, send an email to <a \
href="mailto:dev+unsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a>.<span><font color="#888888"><br> \
</font></span></div></div></blockquote></div><span><font color="#888888"><br><br \
clear="all"><div><br></div>-- <br><div><div dir="ltr">Best \
Regards,<div>Suranga</div></div></div> </font></span></div></div><div><div>
<p></p>
-- <br>
OpenMRS Developers: <a href="http://om.rs/dev" \
target="_blank">http://om.rs/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a> | \
Unsubscribe: <a href="mailto:dev%2Bunsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS \
subscriptions: <a href="http://om.rs/id" target="_blank">http://om.rs/id</a><br> \
<br>
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit <a \
href="https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508" \
target="_blank">https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508</a> \
for details and to make necessary changes.<br> \
</div></div></blockquote></div><br></div>
<p></p>
-- <br>
OpenMRS Developers: <a href="http://om.rs/dev" \
target="_blank">http://om.rs/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a> | \
Unsubscribe: <a href="mailto:dev%2Bunsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS \
subscriptions: <a href="http://om.rs/id" target="_blank">http://om.rs/id</a><br> \
<br>
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit <a \
href="https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508" \
target="_blank">https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508</a> \
for details and to make necessary changes.<br> \
</div></div></blockquote></div><br></div>
<p></p>
-- <br>
OpenMRS Developers: <a href="http://om.rs/dev" \
target="_blank">http://om.rs/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a> | \
Unsubscribe: <a href="mailto:dev%2Bunsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS \
subscriptions: <a href="http://om.rs/id" target="_blank">http://om.rs/id</a><br> \
<br>
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit <a \
href="https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508" \
target="_blank">https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508</a> \
for details and to make necessary changes.<br>
<p></p>
To unsubscribe from this group and stop receiving emails from it, send an email to <a \
href="mailto:dev+unsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a>.<br> \
</div></div></blockquote></div><br><br \
clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div><div \
dir="ltr"><font style="background-color:rgb(255,255,255)" color="#666666"><i>Harsha \
Kumara</i></font><div><font color="#666666"><i>Software \
Engineer</i></font></div><div><font color="#666666"><i>WSO2 \
Inc.</i></font></div><div><font style="background-color:rgb(255,255,255)" \
color="#666666"><i>Sri Lanka.</i></font></div></div></div> \
</font></span></div></div><div><div>
<p></p>
-- <br>
OpenMRS Developers: <a href="http://om.rs/dev" \
target="_blank">http://om.rs/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a> | \
Unsubscribe: <a href="mailto:dev%2Bunsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS \
subscriptions: <a href="http://om.rs/id" target="_blank">http://om.rs/id</a><br> \
<br>
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit <a \
href="https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508" \
target="_blank">https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508</a> \
for details and to make necessary changes.<br>
<p></p>
To unsubscribe from this group and stop receiving emails from it, send an email to <a \
href="mailto:dev+unsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a>.<br> \
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div \
dir="ltr">Best Regards,<div>Suranga</div></div></div> </div>
<p></p>
-- <br>
OpenMRS Developers: <a href="http://om.rs/dev" \
target="_blank">http://om.rs/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a> | \
Unsubscribe: <a href="mailto:dev%2Bunsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS \
subscriptions: <a href="http://om.rs/id" target="_blank">http://om.rs/id</a><br> \
<br>
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit <a \
href="https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508" \
target="_blank">https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508</a> \
for details and to make necessary changes.<br>
<p></p>
To unsubscribe from this group and stop receiving emails from it, send an email to <a \
href="mailto:dev+unsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a>.<br> \
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div \
dir="ltr"><font style="background-color:rgb(255,255,255)" color="#666666"><i>Harsha \
Kumara</i></font><div><font color="#666666"><i>Software \
Engineer</i></font></div><div><font color="#666666"><i>WSO2 \
Inc.</i></font></div><div><font style="background-color:rgb(255,255,255)" \
color="#666666"><i>Sri Lanka.</i></font></div></div></div> </div>
<p></p>
-- <br>
OpenMRS Developers: <a href="http://om.rs/dev" \
target="_blank">http://om.rs/dev</a><br>
Post: <a href="mailto:dev@openmrs.org" target="_blank">dev@openmrs.org</a> | \
Unsubscribe: <a href="mailto:dev%2Bunsubscribe@openmrs.org" \
target="_blank">dev+unsubscribe@openmrs.org</a><br> Manage your OpenMRS \
subscriptions: <a href="http://om.rs/id" target="_blank">http://om.rs/id</a><br> \
<br>
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit <a \
href="https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508" \
target="_blank">https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508</a> \
for details and to make necessary changes.<br> \
</div></div></blockquote></div><br></div>
<p></p>
-- <br />
OpenMRS Developers: <a href="http://om.rs/dev">http://om.rs/dev</a><br />
Post: dev@openmrs.org | Unsubscribe: dev+unsubscribe@openmrs.org<br />
Manage your OpenMRS subscriptions: <a href="http://om.rs/id">http://om.rs/id</a><br \
/> <br />
*** ALERT! This group will be moved to OpenMRS Talk effective 10 April 2015 at 19:00 \
UTC. Please visit <a \
href="https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508">https://talk.openmrs.org/t/openmrs-developers-group-changes-2015-04-10/1508</a> \
for details and to make necessary changes.<br />
<p></p>
To unsubscribe from this group and stop receiving emails from it, send an email to <a \
href="mailto:dev+unsubscribe@openmrs.org">dev+unsubscribe@openmrs.org</a>.<br />
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic