Managing OIDs

I have no problem with our setting up a structure and getting an OID for Elbonia in which to create it. But I think “setting up a county’s RA” definitely “is out of scope for the work we are doing.” We can prepare guidance for them, we can give them sample charters and example requests, but there must be both capacity and willingness to undertake this much and more if the country is going to be able to run its exchange.

The national base OID is of larger scope than the country’s healthcare base OID which is of larger scope than the OIDs of repository codesets with which we are working. Countries with a federal structure are going to have additional issues to address.


On Fri, Oct 25, 2013 at 2:01 PM, Carl Leitner 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:

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

    Application form is here

  • 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

  • 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:

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



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

For more options, visit

Ryan Crichton

Software Developer, Jembi Health Systems | SOUTH

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


I would suggest we look to HL7 for some guidance in this. Canada, and a lot of other countries, maintain their OIDs thru HL7.
I would also echo Roger's worries about OID governance ... It is very much a national issue.