EMR-POS Vendor Type-4 OID Request for Leap Orbit

Hi Thomas, the OID is for use with PrescribeIT, which is using OIDs, for all their vendor identifiers. There has been discussions in the past about changing to a URL format, but it was decided to keep it consistent to for the vendors for storage and processing.

Thanks
Dean

Proposal: Add a value for the URL field in the application

This recommendation is supported by the following considerations:

1. FHIR Standard Compliance
FHIR(Fast Health Interoperability Resources) standard, one of primary HL7 Health Information exchange standards, accepts URIs for multiple purposes.
One key use case is the identifier.system field, which is used to represent namespaces or assigning authorities.
The standard defines three specific URI subtypes for this purpose:
a. OID represented as a URI (e.g. urn:oid:2.16.840.1.113883.6.1)
b. UUID (aka GUID) represented as a URI(e.g. urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6)
c. URL ( Uniform Resource Locator)(e.g. example.org/my-device)

2. FHIR Standard Preference for URLs:
Among these options, URLs are generally preferred within FHIR standard.
By adding support for an URL, the application can directly support data models that require this format while aligning with FHIR best practice.

3. Alternative OID Representation

Although OIDs can be represented as URIs by prefixing them with urn:oid:, this approach is often secondary and typically used when mapping data from other data models, such as HL7 V2 to FHIR.
Providing a direct URL option not only complies with FHIR best practices but also improves interoperability and facilitates cross-mapping between different health information data models.

OID Description: vendor OID for Leap Orbit to used with PrescribeIT implementation
OID Symbolic name: ca_LeapOrbit
Responsible Body & Contact Information: Leap Orbit LLC / www.leaporbit.com
Proposed FHIR URI: none
To be published: HL7 OID registry Leap Orbit_Identifier OID Registration Form