Meta tags:

Headings (most frequently used words):

api, data, openthc, proposal, interoperability, and, is, for, with, common, model, github, com, regulatory, compliance, complicated, complex, closed, systems, are, bad, key, so, we, maintain, community, driven, models, documentation, examples,

Text of the page (most frequently used words):
and (8), the (7), api (6), type (6), data (6), #openthc (5), openapi (4), lab (4), are (4), schema (4), json (4), for (3), common (3), examples (3), com (2), documentation (2), html (2), details (2), some (2), also (2), metric (2), product (2), contact (2), license (2), company (2), yaml (2), sale (2), these (2), models (2), proposal (2), interoperability (2), model (2), privacy, terms, service, has, been, spun, into, various, formats, too, redoc, swagger, reference, provides, authentication, plants, inventory, transfers, retail, sales, others, necessary, create, robust, cannabis, applications, file, bug, you, find, any, issues, available, describe, modeling, why, when, operations, would, executed, revealjs, pdf, manual, requirement, base, handled, collections, files, etc, b2c, b2b, result, sample, variety, lot, items, defined, components, here, links, definition, validation, primary, purpose, which, have, published, references, regulatory, compliance, complicated, complex, maintain, community, driven, key, closed, systems, bad, github, with,

Text of the page (random words):
api openthc data model json schema json examples openthc api a proposal for interoperability with a common data model and api github com openthc api regulatory compliance data is complicated and complex closed systems are bad interoperability is key so we maintain a community driven proposal data models the primary purpose of the openthc api are these common data models which have published json schema references examples here are some examples and also links to a json schema definition for validation these items are defined by yaml in components schema company contact license lot product variety lab sample lab result b2b sale b2c sale the requirement for common base or type data is handled by collections of yaml files in etc company type license type contact type product type lab metric type lab metric documentation an api manual is available also in pdf and revealjs to describe some of the modeling and the why and when operations would be executed it provides details on authentication plants inventory transfers retail sales and the others details necessary to create robust cannabis applications file a bug if you find any issues the openapi documentation has been spun into various formats too swagger openapi reference openapi html openapi html v2 and redoc openthc com terms of service privacy