What the five layers do together, in Marble's own products and in any product built on Marble.
The authorization that fits every lock. Every source accepts a different form; Marble meets each one so the person and the requester do not have to.
SettLiT
Medchart
Marble APIThe right sources, in the right order, for the reason you are asking. An asbestos case and a talc case do not need the same records.
SettLiTMedchartMarble APIOne queue for the organizations that hold the information. Every request arrives verified, with its authorization attached, and every release is logged.
Medchart
Marble HIEThe right person, confirmed before anything is requested. A name and a date of birth are not enough across hundreds of systems that never agreed on an identifier.
SettLiTMedchartMarble APIEvery provider this person has seen, found from the trail they leave. Most people cannot list them from memory.
SettLiTMarble APIA lab or pharmacy connects to Marble once and answers every authorized request through it, instead of hundreds of requesters, one fax at a time.
Marble HIEThe access path when the source needs the individual to show up. The person verifies who they are and grants access, and Marble carries it through patient portals, TEFCA Individual Access Services, CMS Patient Access APIs and their own copy of the record.
SettLiTMarble APIOne record from nine sources in nine formats, de-duplicated, with the source on every element, so a reviewer sees one picture.
SettLiTMedchartMarble APIThe answer to "does this person meet the criteria," not just "what came back." The normalized record is run against the rules the case or policy sets.
SettLiTMedchartMarble APIDoes this case qualify, answered from the records before a firm invests in it. One case at a time, or a whole docket in bulk.
SettLiTMarble APIA time-stamped chronology pulled from the normalized record, with the source on every entry. Extraction, not a rewrite of the record.
SettLiTMarble APIThe same answers, delivered where the work happens. API and MCP servers carry them into case management systems and the AI tools built on them.
SettLiTMarble APIThe authorization that fits every lock. Every source accepts a different form; Marble meets each one so the person and the requester do not have to.
Marble accommodates each source's own authorization rules, carries the right one to each request and checks it, and the purpose that source agreed to, at every release. The onus for getting it right sits with Marble, before anything is sent.
SettLiTMedchartMarble APIThe right sources, in the right order, for the reason you are asking. An asbestos case and a talc case do not need the same records.
Marble sequences networks, claims, pharmacy and lab sources by purpose and stitches the results into one, which returns far more than an individual access request on its own.
SettLiTMedchartMarble APIOne queue for the organizations that hold the information. Every request arrives verified, with its authorization attached, and every release is logged.
Holders get one queue: requests arrive with authorization and identity already verified, the holder releases once, and every release is logged.
MedchartMarble HIEThe right person, confirmed before anything is requested. A name and a date of birth are not enough across hundreds of systems that never agreed on an identifier.
Before any search, Marble enriches the person's profile from authorized identity sources, so every source is queried with enough to return the right person the first time.
SettLiTMedchartMarble APIEvery provider this person has seen, found from the trail they leave. Most people cannot list them from memory.
Marble traces where protected information about a person could exist, from claims, prescriptions and visits, so a request reaches every source, including the ones nobody wrote on the intake form.
SettLiTMarble APIA lab or pharmacy connects to Marble once and answers every authorized request through it, instead of hundreds of requesters, one fax at a time.
A holder connects to the exchange once. Every authorized request after that is fulfilled through it, with the authorization checked and the release logged, on the same layer SettLiT and Medchart run on.
Marble HIEThe access path when the source needs the individual to show up. The person verifies who they are and grants access, and Marble carries it through patient portals, TEFCA Individual Access Services, CMS Patient Access APIs and their own copy of the record.
Some sources will only release to the person themselves: patient portals, the national networks through Individual Access Services under TEFCA, payer and plan data under the CMS Patient Access rules, benefits and financial systems. Marble Pass is how that access is granted. The individual verifies who they are and grants access, and Marble carries it through to SettLiT, to a product built on the API, or to the person's own copy of the record, in a form they can read and share.
SettLiTMarble APIOne record from nine sources in nine formats, de-duplicated, with the source on every element, so a reviewer sees one picture.
Everything that comes back is normalized, de-duplicated and kept with its provenance, and reads the same whether it arrived as structured data or a faxed page.
SettLiTMedchartMarble APIThe answer to "does this person meet the criteria," not just "what came back." The normalized record is run against the rules the case or policy sets.
The normalized data is run against a defined set of criteria, and each one comes back met, unmet or pending, with the evidence that answers it. The same layer produces the pre-qualification report, the time-stamped chronology and the data origination statement, and feeds all of it into downstream workflows through the API and MCP servers.
SettLiTMedchartMarble APIDoes this case qualify, answered from the records before a firm invests in it. One case at a time, or a whole docket in bulk.
The firm sets the criteria once. Marble runs each case against them as the records arrive and returns a report that says what is met, what is not and what is still pending, with the evidence behind each answer. Run it across a docket and the same report ranks the cases worth the next dollar.
SettLiTMarble APIA time-stamped chronology pulled from the normalized record, with the source on every entry. Extraction, not a rewrite of the record.
Every encounter, diagnosis, prescription and result is placed on one timeline in the order it happened, with codes inferred where the source left them out. A data origination statement sits behind it, naming where each entry came from and under what authorization, so the chronology holds up where it is used.
SettLiTMarble APIThe same answers, delivered where the work happens. API and MCP servers carry them into case management systems and the AI tools built on them.
Criteria results, chronologies and the records themselves do not stop at a download. The Marble API returns them into the systems a firm already runs, and MCP servers expose the same answers to the AI assistants and agents those firms are building, with the authorization and the source carried on every element.
SettLiTMarble APINative to Marble, packaged by SettLiT and Medchart, and available to your product through the Marble API or white-label.