Solor is striving to enable better healthcare interoperability by making data standardization simpler to use, update, and extend for implementers.
FAQs
What problem does Solor address?
What is Solor?
Solor integrates specific terminologies such as – but not limited to – SNOMED CT, LOINC, RX-Norm. These three terminologies form the foundation of Solor because they are meaningful use standards, where when integrated together, they represent the breadth of information necessary for clinical data representation.
The Solor integration uses a common model in which the integrated terminologies are transformed. During transformation, the content from one or more terminologies populate the common model. Each Solor data element retains the original identifiers and additionally provides a common UUID based identifier.
What is Solor’s common model?
Solor’s model is centered around STAMP (status, time, author, module, and path) based chronologies of concepts and the semantics associated with those concepts. For example, when utilizing a description and dialect model that are substantially based on SNOMED CT, for those trained, it should be clear on how SNOMED CT represents concepts and descriptions.
Is Solor different from mapping?
Yes, Solor does not map one terminology system to another. An in-depth discussion about this issue is available in a whitepaper linked here: From retrospective mapping to prospective standardization: A comparison of integration strategies to achieve semantic data interoperability.
Who is behind Solor?
The ideas behind Solor span at least 2 decades; however, development within the VHA started in 2014. Solor is being funded by the Veterans Health Administration (VHA) and recently received sponsorship from the Healthcare Services Platform Consortium (HSPC). To find out more about HSPC, go to http://hspconsortium.org. There are other organizations that have helped the VHA develop Solor.
How is licensing addressed in Solor?
Solor does not redistribute content. It enables the community of Solor to integrate terminologies – their own terminology and others’ terminology. Those who are distributing terminology must have a license to distribute these terminologies. For example: If organization A is distributing SNOMED CT, LOINC and its curated terminology then organization A needs to ensure they have a license to redistribute SNOMED CT and LOINC.
Solor’s transformation processes and architectural foundation are available under the Apache 2 Open Source License.
Is Solor competing with terminology standards?
No, SNOMED CT, LOINC and RX-Norm are foundational terminologies in Solor. Solor fully supports and relies on these standards and their organizations. Solor’s intent is to compliment these standards. Organizations are free to integrate Solor content into their standards.