Explore the knowledge graph
Canonical node identities are pinned to this snapshot. Adjacency pages enumerate complete directed relationships; they are not ranked search results.
Search or traverse with the native contract
carried_in: register entry to the data compartment its bytes are carried in
read_by: data compartment to a tool that reads it
declares: register entry to a field name it declares. Taken `out` and then `in`, it is every other entry that declares the same field, which is what could be joined to it
refuses: tool to one reason it can refuse
names: refusal to a data compartment its own wording names. A refusal that reaches one is about data that is not here; a refusal that reaches none is a rule
gated_by: register entry to the access class that keeps it out
addresses: policy article to a code it names
issued_by: policy article to the contractor that issued it
bundled_with: procedure code to the code it is bundled with, in the direction the NCCI edit is written
priced_by: procedure code to the schedule class that prices it
rate_observed: payer to a code it published a rate for: the `procedure` node for a CPT or HCPCS code, the `drg` node for one of the union_all MS-DRGs, which is the same node the hospitals' `filed_charge` reaches
raises_risk_of: condition to a later outcome, in one cited effect size, and never composable
evidenced_by: effect-size edge to the published study it rests on
co_occurs_with: condition to a condition it co-occurs with, as a proportion of cases and never an effect measure
covers: register entry to a jurisdiction its rules bind, as declared in the registry
serves: contractor to a jurisdiction it serves
computed_by: tool to the estimator it is
member_of: code to a declared code set, which is curatorial and never clinical
refuses_composition: relation to a refusal the corpus states about composing it
asserts: document to a span-validated claim extracted from it
about_code: claim to the code it is about
co_priced: code to a code some payer filed a rate for at the same facility in the same month, per the compacted rate lake, either end a `procedure` or a `drg` node. Stored in both directions, so `out` and `in` reach the same codes; a co-occurrence count with its n beside it, never a billing rule, which is `bundled_with` and the NCCI edit file
manual_names: payer-manual claim to the code its extracted `code` field names. Names and does not claim: what the claim says, which program's manual it came out of, what Vertex classified it as and whether one reader or both produced it travel beside the claim in the rollup, never on the edge
manual_issued_by: payer manual to the program that issued it: a `program` node for CMS's Internet-Only Manuals (cms-iom) or a state Medicaid agency (medicaid-<state>), or the `payer` node itself for a commercial payer, under the slug its rates are keyed by, so a manual and a rate meet at one node
manual_asserts: payer manual to a span-validated claim the extraction tier read out of it; the manual is keyed by the digest of its bytes, so a re-issued edition is a second node
filed_charge: hospital to a code it filed a negotiated standard charge for under 45 CFR 180: the `procedure` node for a CPT or HCPCS code, a `drg` node for an MS-DRG. Stored hospital to code, so from a code it is taken `in`. The edge says a filing exists; the amount and its methodology stay in the hospital tier, and the rows, filings and payer strings behind the edge travel beside it, never on it
files: hospital to a payer whose name some payer_name string it filed under maps to, through the one string table in coverage-mrf; a bare `BCBS` names no state plan and reaches nothing. Stored hospital to payer, so from a payer it is taken `in`. It says the hospital filed a charge under the payer's name, as the regulation requires whether or not a contract is live, and never that it is in network