CSD Facility Cross-Referencing

(See Hanne’s message below - Just copying this CSD question to some other lists for greater feedback)

@Carl Leitner, Derek, could you help provider some light on this?

Cheers,

Ryan

···

On Wed, Nov 27, 2013 at 10:18 AM, Hannes Venter hannes@jembi.org wrote:

Hi Everyone,

(I wasn’t too sure which list to send this to, hope this is ok…)

We’re currently adding functionality to the HIM to lookup facilities using CSD.

Specifically we’re looking up facilities for validation in the normal save encounter flow.

However, I see that there are no attributes for “otherID” on facilities, only the primary id oid.

This will mean that we can only lookup facilities by their primary ids rather cross-referencing them with, say, a fosaid.

Did I understand this correctly? Or is there some other attribute that we can use?

Is cross-referencing completely out of scope for CSD?

(I know it’s not a primary function to begin with)

Kind Regards

Hannes


Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

You received this message because you are subscribed to the Google Groups “OHIE IHE SDO” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-ihe-standardsdev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org

Dear Hannes,
Sorry I didn’t see your message come in for some reason. The element has a sub-element that you can use to capture FOSSAID, etc, see the diagram below. This is a similar patter for provider and organization.

You can see this in use for provider here:

https://github.com/his-interop/openinfoman/blob/master/resources/service_directories/providers.xml

on lines 8, 21 etc.

One thing to note is the use of OIDs to indicate the ID type as the “assigning authority name.” The presence of these OIDs was the reason for starting the thread on managing OIDs some time back. As we haven’t come to any consensus as to where these OIDs should me tracked, we are unfortunately reduced to looking at source code. For the sample provider directory data based on the RHEA implementation, the OIDs can be seen here:

http://bazaar.launchpad.net/~rwandaehealth/rhea-pr/trunk/view/head:/UserInterface/modules/CSD_ServiceDirectory/pr_data_dump_to_csd.xsl

on line 6-13. This tells us that the IDs referenced on 8,21, etc are the NID.

Cheers.

-carl

PS @Ryan, @Derek: Sorry about the multiple sends — I am wrestling with my mail settings.

PastedGraphic-1.pdf (98.2 KB)

Hi Carl,

Thanks for the info. I actually initially suspected that I should try use otherID, however I don’t see the element specified in the spec:

ftp://ftp.ihe.net/DocumentPublication/CurrentPublished/ITInfrastructure/IHE_ITI_Suppl_CSD.pdf

(I’m looking at page 49 as well the query definition in figure 3.73.4.1.2.3-2 on page 51).

When I first looked at this, trying to figure it out, I also didn’t see otherID being used in the base stored queries:

https://github.com/his-interop/openinfoman/blob/master/repo/csd_base_stored_queries.xqm#L73-L98

So it’s sounding from what you said that it should be there, so am I just missing something?

(oh and I’ll try some run queries again to check; as you’re aware I’m just upgrading our instance quickly atm :slight_smile: )

Thanks

Hannes

···

On 9 December 2013 14:49, Carl Leitner litlfred@gmail.com wrote:

Dear Hannes,
Sorry I didn’t see your message come in for some reason. The element has a sub-element that you can use to capture FOSSAID, etc, see the diagram below. This is a similar patter for provider and organization.

You can see this in use for provider here:

https://github.com/his-interop/openinfoman/blob/master/resources/service_directories/providers.xml

on lines 8, 21 etc.

One thing to note is the use of OIDs to indicate the ID type as the “assigning authority name.” The presence of these OIDs was the reason for starting the thread on managing OIDs some time back. As we haven’t come to any consensus as to where these OIDs should me tracked, we are unfortunately reduced to looking at source code. For the sample provider directory data based on the RHEA implementation, the OIDs can be seen here:

http://bazaar.launchpad.net/~rwandaehealth/rhea-pr/trunk/view/head:/UserInterface/modules/CSD_ServiceDirectory/pr_data_dump_to_csd.xsl

on line 6-13. This tells us that the IDs referenced on 8,21, etc are the NID.

Cheers.

-carl

PS @Ryan, @Derek: Sorry about the multiple sends — I am wrestling with my mail settings.

You received this message because you are subscribed to the Google Groups “OHIE IHE SDO” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-ihe-standardsdev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

On Dec 9, 2013, at 4:08 AM, Ryan Crichton ryan@jembi.org wrote:

(See Hanne’s message below - Just copying this CSD question to some other lists for greater feedback)

@Carl Leitner, Derek, could you help provider some light on this?

Cheers,

Ryan

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

On Wed, Nov 27, 2013 at 10:18 AM, Hannes Venter hannes@jembi.org wrote:

Hi Everyone,

(I wasn’t too sure which list to send this to, hope this is ok…)

We’re currently adding functionality to the HIM to lookup facilities using CSD.

Specifically we’re looking up facilities for validation in the normal save encounter flow.

However, I see that there are no attributes for “otherID” on facilities, only the primary id oid.

This will mean that we can only lookup facilities by their primary ids rather cross-referencing them with, say, a fosaid.

Did I understand this correctly? Or is there some other attribute that we can use?

Is cross-referencing completely out of scope for CSD?

(I know it’s not a primary function to begin with)

Kind Regards

Hannes


Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

You received this message because you are subscribed to the Google Groups “OHIE IHE SDO” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-ihe-standardsdev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

Dear Hannes,

The element is defined in the .xsd in IHE_ITI_Suppl_CSD.pdf on line 2495 (page 92) and just above line 2500 you can see the child element. It is also in Table Y.1-2 on page 80 — see the row “Facility Identifiers."

I do see that is not present as a parameter to the “Facility Search” stored query on line 49. It probably should be added by submitting a Change Proposal.

http://wiki.ihe.net/index.php?title=ITI_Change_Proposals_2014

It looks like the next CP processing call is Dec 19. I can help you go through this process if you want.

Cheers.

-carl

···

On 9 December 2013 14:49, Carl Leitner litlfred@gmail.com wrote:

Dear Hannes,
Sorry I didn’t see your message come in for some reason. The element has a sub-element that you can use to capture FOSSAID, etc, see the diagram below. This is a similar patter for provider and organization.

You can see this in use for provider here:

https://github.com/his-interop/openinfoman/blob/master/resources/service_directories/providers.xml

on lines 8, 21 etc.

One thing to note is the use of OIDs to indicate the ID type as the “assigning authority name.” The presence of these OIDs was the reason for starting the thread on managing OIDs some time back. As we haven’t come to any consensus as to where these OIDs should me tracked, we are unfortunately reduced to looking at source code. For the sample provider directory data based on the RHEA implementation, the OIDs can be seen here:

http://bazaar.launchpad.net/~rwandaehealth/rhea-pr/trunk/view/head:/UserInterface/modules/CSD_ServiceDirectory/pr_data_dump_to_csd.xsl

on line 6-13. This tells us that the IDs referenced on 8,21, etc are the NID.

Cheers.

-carl
PS @Ryan, @Derek: Sorry about the multiple sends — I am wrestling with my mail settings.

You received this message because you are subscribed to the Google Groups “OHIE IHE SDO” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-ihe-standardsdev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

On Dec 9, 2013, at 4:08 AM, Ryan Crichton ryan@jembi.org wrote:

(See Hanne’s message below - Just copying this CSD question to some other lists for greater feedback)

@Carl Leitner, Derek, could you help provider some light on this?

Cheers,

Ryan

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

On Wed, Nov 27, 2013 at 10:18 AM, Hannes Venter hannes@jembi.org wrote:

Hi Everyone,

(I wasn’t too sure which list to send this to, hope this is ok…)

We’re currently adding functionality to the HIM to lookup facilities using CSD.

Specifically we’re looking up facilities for validation in the normal save encounter flow.

However, I see that there are no attributes for “otherID” on facilities, only the primary id oid.

This will mean that we can only lookup facilities by their primary ids rather cross-referencing them with, say, a fosaid.

Did I understand this correctly? Or is there some other attribute that we can use?

Is cross-referencing completely out of scope for CSD?

(I know it’s not a primary function to begin with)

Kind Regards

Hannes


Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

You received this message because you are subscribed to the Google Groups “OHIE IHE SDO” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-ihe-standardsdev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org

Ok great, thanks Carl.

Cheers

Hannes

···

On 9 December 2013 15:47, Carl Leitner litlfred@gmail.com wrote:

Dear Hannes,
The element is defined in the .xsd in IHE_ITI_Suppl_CSD.pdf on line 2495 (page 92) and just above line 2500 you can see the child element. It is also in Table Y.1-2 on page 80 — see the row “Facility Identifiers."

I do see that is not present as a parameter to the “Facility Search” stored query on line 49. It probably should be added by submitting a Change Proposal.

http://wiki.ihe.net/index.php?title=ITI_Change_Proposals_2014

It looks like the next CP processing call is Dec 19. I can help you go through this process if you want.

Cheers.

-carl

On Dec 9, 2013, at 8:31 AM, Hannes Venter hannes@jembi.org wrote:

Hi Carl,

Thanks for the info. I actually initially suspected that I should try use otherID, however I don’t see the element specified in the spec:

ftp://ftp.ihe.net/DocumentPublication/CurrentPublished/ITInfrastructure/IHE_ITI_Suppl_CSD.pdf

(I’m looking at page 49 as well the query definition in figure 3.73.4.1.2.3-2 on page 51).

When I first looked at this, trying to figure it out, I also didn’t see otherID being used in the base stored queries:

https://github.com/his-interop/openinfoman/blob/master/repo/csd_base_stored_queries.xqm#L73-L98

So it’s sounding from what you said that it should be there, so am I just missing something?

(oh and I’ll try some run queries again to check; as you’re aware I’m just upgrading our instance quickly atm :slight_smile: )

Thanks

Hannes

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

On 9 December 2013 14:49, Carl Leitner litlfred@gmail.com wrote:

Dear Hannes,
Sorry I didn’t see your message come in for some reason. The element has a sub-element that you can use to capture FOSSAID, etc, see the diagram below. This is a similar patter for provider and organization.

You can see this in use for provider here:

https://github.com/his-interop/openinfoman/blob/master/resources/service_directories/providers.xml

on lines 8, 21 etc.

One thing to note is the use of OIDs to indicate the ID type as the “assigning authority name.” The presence of these OIDs was the reason for starting the thread on managing OIDs some time back. As we haven’t come to any consensus as to where these OIDs should me tracked, we are unfortunately reduced to looking at source code. For the sample provider directory data based on the RHEA implementation, the OIDs can be seen here:

http://bazaar.launchpad.net/~rwandaehealth/rhea-pr/trunk/view/head:/UserInterface/modules/CSD_ServiceDirectory/pr_data_dump_to_csd.xsl

on line 6-13. This tells us that the IDs referenced on 8,21, etc are the NID.

Cheers.

-carl
PS @Ryan, @Derek: Sorry about the multiple sends — I am wrestling with my mail settings.

You received this message because you are subscribed to the Google Groups “OHIE IHE SDO” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-ihe-standardsdev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

On Dec 9, 2013, at 4:08 AM, Ryan Crichton ryan@jembi.org wrote:

(See Hanne’s message below - Just copying this CSD question to some other lists for greater feedback)

@Carl Leitner, Derek, could you help provider some light on this?

Cheers,

Ryan

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

On Wed, Nov 27, 2013 at 10:18 AM, Hannes Venter hannes@jembi.org wrote:

Hi Everyone,

(I wasn’t too sure which list to send this to, hope this is ok…)

We’re currently adding functionality to the HIM to lookup facilities using CSD.

Specifically we’re looking up facilities for validation in the normal save encounter flow.

However, I see that there are no attributes for “otherID” on facilities, only the primary id oid.

This will mean that we can only lookup facilities by their primary ids rather cross-referencing them with, say, a fosaid.

Did I understand this correctly? Or is there some other attribute that we can use?

Is cross-referencing completely out of scope for CSD?

(I know it’s not a primary function to begin with)

Kind Regards

Hannes


Hannes Venter
Software Developer, Jembi Health Systems | SOUTH AFRICA
Mobile: +27 73 276 2848 | Office: +27 21 701 0939 | Skype: venter.johannes
E-mail: hannes@jembi.org

You received this message because you are subscribed to the Google Groups “OHIE IHE SDO” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-ihe-standardsdev+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton

E-mail: ryan@jembi.org