Managing OIDs

I don’t think we should be getting IDs except perhaps for testing. The countries who are running the HIEs should have their own OIDs. We can help them with this.

···

On Fri, Oct 25, 2013 at 2:01 PM, Carl Leitner cleitner@capacityplus.org wrote:

Hi All,

Digging into IHE profiles a bit, it seems quite likely we will need to start creating a series of OIDs for various OpenHIE implementations.

  • In CSD the identifiers of facilities and providers require the use of OID. There are also several places where the use of OIDs are recommended, such as for the provider’s identifier type (e.g. National ID, CSR, and Mutelle in the Rwandan context)
  • Identifying coded terminology in the "Sharing Value Sets” (Required)
    I am sure there are others we will run into as we use more and more of the IHE profiles.

I would recommend that we take a disciplined approach to generation of these OID. The first step is to obtain a root OID. There are free and non-fee options to do so — see below. Once we have a root OID, we are responsible for administering the child
nodes of the OID, and this:

http://www.oid-info.com/index.htm

seems like an appropriate place to do so.

Here are a few options for obtaining a root OID:

  • IANA issues free OIDS, but they are intended for SNMP context. These live under 1.3.6.1.4.1

    Application form is here http://pen.iana.org/pen/PenApplication.page

  • Another option for a free OID is to register one under 2.25 which is use for UUIDs. This could be the one I had generated in the earlier email: 2.25.309768652999692686176651983274504471835

  • There is a place for international organizations, under 2.23. Registration is £150 to BSI

    http://oid-info.com/doc/ICD%20application%20form.doc

  • Register with ISO, it looks like this is on the order of $1000

  • There are some country specific Registration Authorities, but neither Rwanda or the Philippines appears to have one:

    http://www.oid-info.com/doc/country-OIDs.htm

Once we have our root OID, we need to figure out how we are going allocate them. I would suggest the following:

Under these OIDs, we then start creating child nodes for the country specific needs. An example for Rwanda could be:

  • $rootOID.646.1 - node for personal identifier types
  • $rootOID.646.1.1 - node designating the National ID
  • $rootOID.646.1.2 - node designating the Muelle number
  • $rootOID.646.2 - identifiers for providers are children of this node, and would be $rootOID.645.2.$enterpriseID
  • $rootOID.646.3 - identifiers for facilities are children of this node, and could be $rootOID.643.3.$FOSSID

Cheers,

-carl

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.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH AFRICA

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

Hi Roger,
There are two things going on in the email, and it is perhaps worth making the distinction. The first part is determining the “root OID” under which we should be working for a county’s HIE. Here, I agree the countries should be managing and responsible
them. However it doesn’t seem that two or our early target counties (Philippines and Rwanda) have Registration Authorities to manage the assignment of OID. In this case, assuming that setting up a county’s RA is out of scope for the work we are doing, I
am suggesting we should have some fallback.

The second part of this is how should manage the structure of the OIDs for a particular country’s HIE under the “root OID.” Ideally we can be somewhat systematic about this to encourage easy reuse of different codes/scripts that may get written and to
avoid any collision. To the later point in particular, can we agree on a process/tool (such as
http://www.oid-info.com/index.htm) so that we can collectively document what OIDs we are using relative to the “root OID"

I hope that helps clarify, and I apologize for interchanging the use of we in my original email, by using we=“ohie-architeture group” and “we=”team deploying HIE in a country.”

Cheers,

-carl

···

On Fri, Oct 25, 2013 at 2:01 PM, Carl Leitner cleitner@capacityplus.org wrote:

Hi All,

Digging into IHE profiles a bit, it seems quite likely we will need to start creating a series of OIDs for various OpenHIE implementations.

  • In CSD the identifiers of facilities and providers require the use of OID. There are also several places where the use of OIDs are recommended, such as for the provider’s identifier type (e.g. National ID, CSR, and Mutelle in the Rwandan context)
  • Identifying coded terminology in the "Sharing Value Sets” (Required)
    I am sure there are others we will run into as we use more and more of the IHE profiles.

I would recommend that we take a disciplined approach to generation of these OID. The first step is to obtain a root OID. There are free and non-fee options to do so — see below. Once we have a root OID, we are responsible for administering the child
nodes of the OID, and this:

http://www.oid-info.com/index.htm

seems like an appropriate place to do so.

Here are a few options for obtaining a root OID:

  • IANA issues free OIDS, but they are intended for SNMP context. These live under 1.3.6.1.4.1

    Application form is here http://pen.iana.org/pen/PenApplication.page

  • Another option for a free OID is to register one under 2.25 which is use for UUIDs. This could be the one I had generated in the earlier email: 2.25.309768652999692686176651983274504471835

  • There is a place for international organizations, under 2.23. Registration is £150 to BSI

    http://oid-info.com/doc/ICD%20application%20form.doc

  • Register with ISO, it looks like this is on the order of $1000

  • There are some country specific Registration Authorities, but neither Rwanda or the Philippines appears to have one:

    http://www.oid-info.com/doc/country-OIDs.htm

Once we have our root OID, we need to figure out how we are going allocate them. I would suggest the following:

Under these OIDs, we then start creating child nodes for the country specific needs. An example for Rwanda could be:

  • $rootOID.646.1 - node for personal identifier types
  • $rootOID.646.1.1 - node designating the National ID
  • $rootOID.646.1.2 - node designating the Muelle number
  • $rootOID.646.2 - identifiers for providers are children of this node, and would be $rootOID.645.2.$enterpriseID
  • $rootOID.646.3 - identifiers for facilities are children of this node, and could be $rootOID.643.3.$FOSSID

Cheers,

-carl

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.


Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH
AFRICA

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

E-mail: ryan@jembi.org